| View previous topic :: View next topic |
| Author |
Message |
ashtophet
Guru
Joined: 08 Aug 2004
Posts: 397
|
 Posted: Mon May 30, 2005 2:10 pm Post subject: |
 |
|
sure, playfool... i'll look after it tomorrow and post a bug if needed
cheers |
|
| Back to top |
|
 |
qnx
l33t
Joined: 25 Jun 2002
Posts: 638
Location: Göteborg, Sweden
|
| Posted: Mon May 30, 2005 5:19 pm Post subject: |
|
|
Dies on boot-up. Right after fsck-ing partitions and that stuff, on mounting local partitions there comes a line below that which says "Disabling IRQ 18", and then nothing happens anymore. It's not dead however cause I can press num-lock on and off and the LED is working properly. Think it's something with ACPI. I use the same config as in rc3-love1, everything's fine here, therefore I can show you what dmesg says about ACPI and IRQ 18 here:
| Code: | dmesg | grep "IRQ 18"
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 18
bash-2.05b$ dmesg | grep ACPI
ACPI: RSDP (v000 Nvidia ) @ 0x000f6b00
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3000
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3040
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff79c0
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: Subsystem revision 20050309
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs *17), disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs *18), disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs *19), disabled.
ACPI: PCI Interrupt Link [APCE] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
PCI: Using ACPI for IRQ routing
ACPI: Thermal Zone [THRM] (42 C)
ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCH] -> GSI 22 (level, high) -> IRQ 22
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 18
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21 (level, high) -> IRQ 21
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 20 (level, high) -> IRQ 20
ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 22 (level, high) -> IRQ 22
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 21 (level, high) -> IRQ 21
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 19
|
With this release, however, it says "Disabling IRQ 18" and it doesn't repond anymore. What do you think?
_________________
Registred Linux user #191143!
Abit NF7-S rev. 2.00 (BIOS v. 2.7)
AMD AthlonXP 2500+ (Barton)
PATA Seagate ST3120022A
SATA Seagate ST3200822AS & Silicon Image 3112 chipset
Gentoo Linux  |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Mon May 30, 2005 5:53 pm Post subject: |
|
|
what about vanilla rc5 ?
the best test in the patchset aspect is a vanilla test.
If in vanilla will be the same we will know if this is a patchset fault or not
please just test vanilla rc5
there is no any ACPI patch in love.
or please try without Local APIC
| qnx in dmesg wrote: | | Code: |
ACPI: Using IOAPIC for interrupt routing |
|
Im not using it :
| Code: | | ACPI: Using PIC for interrupt routing |
and its ok , maybe this is a problem ?
( CONFIG_X86_UP_APIC )
this is mine
| Code: |
[4294667.296000] BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
[4294667.296000] BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
[4294667.296000] ACPI: RSDP (v000 VT8371 ) @ 0x000f7900
[4294667.296000] ACPI: RSDT (v001 VT8371 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff3000
[4294667.296000] ACPI: FADT (v001 VT8371 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0fff3040
[4294667.296000] ACPI: DSDT (v001 VT8371 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
[ 17.022579] ACPI: setting ELCR to 0020 (from 0c20)
[ 17.094620] ACPI: Subsystem revision 20050309
[ 17.107980] ACPI: Interpreter enabled
[ 17.108001] ACPI: Using PIC for interrupt routing
[ 17.108871] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 17.110101] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 17.111484] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
[ 17.112100] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 17.112716] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 17.113402] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
[ 17.117906] PCI: Using ACPI for IRQ routing
[ 17.466611] ACPI: Power Button (FF) [PWRF]
[ 17.466696] ACPI: Sleep Button (CM) [SLPB]
[ 17.466981] ACPI: CPU0 (power states: C1[C1] C2[C2])
[ 17.467081] ACPI: Processor [CPU0] (supports 2 throttling states)
[ 20.082908] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
[ 20.089020] ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
[ 20.147404] ACPI wakeup devices:
[ 20.153957] ACPI: (supports S0 S1 S4 S5)
[ 23.774875] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
[ 23.774893] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
[ 28.092069] ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
[ 28.252197] ACPI: PCI Interrupt 0000:00:07.3[D] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
|
gzcat /proc/config.gz | grep APIC
| Code: |
CONFIG_X86_GOOD_APIC=y
# CONFIG_X86_UP_APIC is not set
|
gzcat /proc/config.gz | grep ACPI
| Code: |
# Power management options (ACPI, APM)
# ACPI (Advanced Configuration and Power Interface) Support
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_PNPACPI is not set
|
cheers.
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard  |
|
| Back to top |
|
|
Marctraider
Guru
Joined: 24 Dec 2003
Posts: 387
|
| Posted: Mon May 30, 2005 7:07 pm Post subject: |
|
|
So anyone experiences even more better interactivity and latency then stable rc3-love1? 8O
_________________
MOBO: Maximus II Gene
RAM: DDR2 OCZ 4GB
CPU: E6400 Conroe
GPU: HD2600XT
SATA: 3x 250GB. |
|
| Back to top |
|
|
wing
Tux's lil' helper
Joined: 27 Aug 2002
Posts: 108
Location: Mountain View, CA
|
| Posted: Mon May 30, 2005 7:28 pm Post subject: |
|
|
This is the build error I get on amd64
| Code: | CC arch/x86_64/kernel/mce.o
In file included from arch/x86_64/kernel/mce.c:17:
include/linux/fs.h: In function `lock_super':
include/linux/fs.h:852: warning: implicit declaration of function `down'
include/linux/fs.h: In function `unlock_super':
include/linux/fs.h:858: warning: implicit declaration of function `up'
arch/x86_64/kernel/mce.c: In function `mce_read':
arch/x86_64/kernel/mce.c:383: warning: type defaults to `int' in declaration of `DECLARE_MUTEX'
arch/x86_64/kernel/mce.c:383: warning: parameter names (without types) in function declaration
arch/x86_64/kernel/mce.c:392: error: `mce_read_sem' undeclared (first use in this function)
arch/x86_64/kernel/mce.c:392: error: (Each undeclared identifier is reported only once
arch/x86_64/kernel/mce.c:392: error: for each function it appears in.)
make[1]: *** [arch/x86_64/kernel/mce.o] Error 1
make: *** [arch/x86_64/kernel] Error 2 |
Again, I know you don't support x86_64, just posting it for the people who do use it |
|
| Back to top |
|
|
pwe
Guru
Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland
|
| Posted: Mon May 30, 2005 8:05 pm Post subject: |
|
|
| wing wrote: | This is the build error I get on amd64
| Code: | CC arch/x86_64/kernel/mce.o
In file included from arch/x86_64/kernel/mce.c:17:
include/linux/fs.h: In function `lock_super':
include/linux/fs.h:852: warning: implicit declaration of function `down'
include/linux/fs.h: In function `unlock_super':
...
arch/x86_64/kernel/mce.c:392: error: for each function it appears in.)
make[1]: *** [arch/x86_64/kernel/mce.o] Error 1
make: *** [arch/x86_64/kernel] Error 2 |
Again, I know you don't support x86_64, just posting it for the people who do use it |
i have this too |
|
| Back to top |
|
|
qnx
l33t
Joined: 25 Jun 2002
Posts: 638
Location: Göteborg, Sweden
|
| Posted: Mon May 30, 2005 9:43 pm Post subject: |
|
|
fallow,
thanks for reply. I tried out disabling local APCI and other things and went back to use the old PIC for interrupts. However, this time it just died after "Mounting local drives [OK]". No num lock on/off this time... no message either. Seems somethin's really wrong here. Sorry but I haven't had time to try out with vanila yet... I'll let you know when I do that.
Cheers!
_________________
Registred Linux user #191143!
Abit NF7-S rev. 2.00 (BIOS v. 2.7)
AMD AthlonXP 2500+ (Barton)
PATA Seagate ST3120022A
SATA Seagate ST3200822AS & Silicon Image 3112 chipset
Gentoo Linux |
|
| Back to top |
|
|
ashtophet
Guru
Joined: 08 Aug 2004
Posts: 397
|
| Posted: Mon May 30, 2005 9:55 pm Post subject: |
|
|
qnx
It would be very interesting to see the results of yr. vanilla test... I don't get yr. error, but i also have problems with this love2 release (which are reproducing with vanilla... so, they're not love patchset related)... and we use practically same motherboard (here A7N8X-Deluxe)
cheers and luck |
|
| Back to top |
|
|
stalynx
Apprentice
Joined: 03 Oct 2002
Posts: 162
|
| Posted: Mon May 30, 2005 9:57 pm Post subject: |
|
|
doh, I'm getting kernel oops when trying to mount/umount filesystems, I get this when I reboot as well.
| Code: |
May 30 17:49:35 [kernel] BUG at fs/inode.c:1100!
May 30 17:49:35 [kernel] ------------[ cut here ]------------
May 30 17:49:35 [kernel] kernel BUG at fs/inode.c:1100!
May 30 17:49:35 [kernel] invalid operand: 0000 [#1]
May 30 17:49:35 [kernel] PREEMPT
May 30 17:49:35 [kernel] Modules linked in: orinoco_cs orinoco hermes radeon drm intel_agp agpgart
May 30 17:49:35 [kernel] CPU: 0
May 30 17:49:35 [kernel] EIP: 0060:[<c01789ad>] Not tainted VLI
May 30 17:49:35 [kernel] EFLAGS: 00010292 (2.6.12-rc5-love2)
May 30 17:49:35 [kernel] EIP is at iput+0xa2/0xaf
May 30 17:49:35 [kernel] eax: 0000001b ebx: ce12931c ecx: c04a624c edx: c04a624c
May 30 17:49:35 [kernel] esi: c04afd20 edi: ce129420 ebp: ce12931c esp: cd37beb4
May 30 17:49:35 [kernel] ds: 007b es: 007b ss: 0068 preempt: 00000001
May 30 17:49:35 [kernel] Process umount (pid: 9874, threadinfo=cd37a000 task=d4fc1540)
May 30 17:49:35 [kernel] Stack: c043a547 c043fcaa 0000044c cd37a000 ce129420 c01861e9 ce12931c 00000000
May 30 17:49:35 [kernel] 00000000 00000000 00000000 cd37a000 ce129428 ce12931c cd37a000 df109c74
May 30 17:49:35 [kernel] cd37bf08 cd37a000 c017791d df109c74 dfee2480 cd37bf08 cd37bf08 df18e164
May 30 17:49:35 [kernel] Call Trace:
May 30 17:49:35 [kernel] [<c01861e9>] inotify_unmount_inodes+0xdb/0x110 (24)
May 30 17:49:35 [kernel] [<c017791d>] invalidate_inodes+0x41/0x87 (52)
May 30 17:49:35 [kernel] [<c0163446>] generic_shutdown_super+0x6e/0x150 (32)
May 30 17:49:35 [kernel] [<c01640e7>] kill_block_super+0x2d/0x49 (20)
May 30 17:49:35 [kernel] [<c01632d2>] deactivate_super+0x5b/0x8a (20)
May 30 17:49:35 [kernel] [<c017a976>] sys_umount+0x3f/0x8c (20)
May 30 17:49:35 [kernel] [<c014f841>] do_munmap+0x11b/0x179 (24)
May 30 17:49:35 [kernel] [<c014f8ef>] sys_munmap+0x50/0x74 (44)
May 30 17:49:35 [kernel] [<c017a9da>] sys_oldumount+0x17/0x1b (16)
May 30 17:49:35 [kernel] [<c0102f67>] sysenter_past_esp+0x54/0x75 (12)
May 30 17:49:35 [kernel] Code: 74 24 10 83 c4 14 c3 89 1c 24 ff 56 14 eb aa c7 44 24 08 4c 04 00 00 c7 44 24 04 a74 24 10 89
May 30 17:49:35 [kernel] umount/9874: BUG in do_exit at kernel/exit.c:785
May 30 17:49:35 [kernel] [<c011c636>] do_exit+0x42b/0x43a (8)
May 30 17:49:35 [kernel] [<c0103d1e>] do_invalid_op+0x0/0xab (40)
May 30 17:49:35 [kernel] [<c01039c4>] do_trap+0x0/0x11d (8)
May 30 17:49:35 [kernel] [<c0103dc0>] do_invalid_op+0xa2/0xab (60)
May 30 17:49:35 [kernel] [<c01789ad>] iput+0xa2/0xaf (76)
May 30 17:49:35 [kernel] [<c011a01e>] release_console_sem+0xdc/0xe5 (20)
May 30 17:49:35 [kernel] [<c0119db3>] vprintk+0x16a/0x266 (32)
May 30 17:49:35 [kernel] [<c021b89c>] ntfs_destroy_big_inode+0x5b/0xd1 (36)
May 30 17:49:35 [kernel] [<c01031db>] error_code+0x4f/0x54 (36)
May 30 17:49:35 [kernel] [<c01789ad>] iput+0xa2/0xaf (44)
May 30 17:49:35 [kernel] [<c017791d>] invalidate_inodes+0x41/0x87 (52)
May 30 17:49:35 [kernel] [<c0163446>] generic_shutdown_super+0x6e/0x150 (32)
May 30 17:49:35 [kernel] [<c01640e7>] kill_block_super+0x2d/0x49 (20)
May 30 17:49:35 [kernel] [<c01632d2>] deactivate_super+0x5b/0x8a (20)
May 30 17:49:35 [kernel] [<c017a976>] sys_umount+0x3f/0x8c (20)
May 30 17:49:35 [kernel] [<c014f841>] do_munmap+0x11b/0x179 (24)
May 30 17:49:35 [kernel] [<c014f8ef>] sys_munmap+0x50/0x74 (44)
May 30 17:49:35 [kernel] [<c017a9da>] sys_oldumount+0x17/0x1b (16)
May 30 17:49:35 [kernel] [<c0102f67>] sysenter_past_esp+0x54/0x75 (12)
|
take note I applied inotify-0.23-rml-2.6.12-rc4-8.patch |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Mon May 30, 2005 10:09 pm Post subject: |
|
|
YEAP.
Please DONT reporting errors about release having additional patches.
We cut INOTIFY from this release , exactly because of potential errors.
and there is no INOTIFY in this release.
We had a solid reason to not include inotify , and we did this.
qnx : no problem
x86_64 : we are looking for potential maintainer.
for all people.
When You going to report some bug. Please do testing of vanilla + RTP or vanilla also .
by this way we can have sure about bug reason.
galizia_ceive : what errors , as I remember You said that You have the same bug with vanilla rc5 , so ?
oh , vacations for me will be good...
cheers.
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
ashtophet
Guru
Joined: 08 Aug 2004
Posts: 397
|
| Posted: Mon May 30, 2005 10:21 pm Post subject: |
|
|
| fallow wrote: |
galizia_ceive : what errors , as I remember You said that You have the same bug with vanilla rc5 , so ?
|
I explained myself very badly (remember my sore throat  ?)... I mean just that, for me it would be interesting to see if qnx gets the error is getting with love2 with a vanilla kernel (we have almost same hardware)... just as me.
And i say it again the error i have IS NOT LOVE-SOURCES PATCHSET RELATED... Furthermore, i am able to boot rc5-love2 (with magic_sysrq activated) and i am not able to boot vanilla... Tomorrow or at weekend i'll try out better and, if needed, post the bug at lkml.
cheers fallow
|
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Mon May 30, 2005 10:35 pm Post subject: |
|
|
ahh ok , I was affraid that You find something terrible new one
quick rtp update : http://vivid.dat.pl/fallow/pub/love-sources/2.6.12-rc5-love2/rtp12_to_15.diff
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
stalynx
Apprentice
Joined: 03 Oct 2002
Posts: 162
|
| Posted: Mon May 30, 2005 11:30 pm Post subject: |
|
|
I don't mean to be a jerk or anything but obviously the problem is RTP is not playing well with inotify. This is why you cut it from this release. However you will eventually have to put inotify back in... unless you don't want an inotify kernel. So sorry for wasting your time but the problem is going to have to be tackled eventually.... 
*EDIT* I take that back... I get the same oops when unmounting an ntfs filesystem on 2.6.12-rc5-skunk4 |
|
| Back to top |
|
|
dice
Guru
Joined: 21 Apr 2002
Posts: 577
|
| Posted: Tue May 31, 2005 2:10 am Post subject: |
|
|
| pwe wrote: | | dice wrote: | | BTW this update fixed those oops's I was getting with the nvidia module. Everything's working great here on the x86_64 front |
You have rc5-love2 on amd64? |
No, I was in the wrong thread. Sorry about that, I'm on 2.6.12-rc5-love1 |
|
| Back to top |
|
|
playfool
l33t
Joined: 01 Jun 2004
Posts: 688
Location: Ã
rhus, Denmark
|
| Posted: Tue May 31, 2005 6:59 am Post subject: |
|
|
| stalynx wrote: | I don't mean to be a jerk or anything but obviously the problem is RTP is not playing well with inotify. This is why you cut it from this release. However you will eventually have to put inotify back in... unless you don't want an inotify kernel. So sorry for wasting your time but the problem is going to have to be tackled eventually....
*EDIT* I take that back... I get the same oops when unmounting an ntfs filesystem on 2.6.12-rc5-skunk4 |
Well, it just so happens that inotify is lined up for merging for 2.6.13[1], which means that everyone will have to play nice with it by then.
[1] RML stated this at his GNOME Optimization talk on GUADEC, no Linus confirmation but I doubt anyone will seriously want to continue using dnotify as it sucks |
|
| Back to top |
|
|
lavacano
Apprentice
Joined: 29 May 2005
Posts: 190
Location: Poulsbo, WA
|
| Posted: Tue May 31, 2005 10:43 am Post subject: |
|
|
Oh snikes almost forgot to apply this; this is for 4love2? oh wells ima go find out the hard way; wish me luck! btw everything is no-oops here using hal/dbus from portage (i think .49 and .33 not sure) and back to using fam instead of gamin and all the bad stuff is better now haha.
edit: patch applied To apply this;
cd /usr/src
ln -s linux rtp12
ln -s linux rtp15
wget http://vivid.dat.pl/fallow/pub/love-sources/2.6.12-rc5-love2/rtp12_to_15.diff
patch -p0 < rtp12_to_15.diff
hey fallow or anyone to use all this new stuff should I leave
CONFIG_BLOCKER
and stuff like
CONFIG_CRITICAL_PREEMPT_TIMING
should I leave these on? or are they just there for monitoring?
_________________
Sincerely,
Chadwick Ferguson |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Tue May 31, 2005 11:54 am Post subject: |
|
|
this is enough :
| Code: |
cd /usr/src/linux-2.6.12-rc5-love2
wget http://vivid.dat.pl/fallow/pub/love-sources/2.6.12-rc5-love2/rtp12_to_15.diff
patch -p1 < rtp12_to_15.diff
|
all TIMINGs all for monitoring & debugging etc.
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard |
|
| Back to top |
|
|
fallow
Bodhisattva
Joined: 08 Jan 2004
Posts: 2208
Location: Poland
|
| Posted: Tue May 31, 2005 4:53 pm Post subject: |
|
|
OK , release marked as stable (x86)
cheers
_________________
"Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard
Last edited by fallow on Thu Jun 02, 2005 7:05 am; edited 1 time in total |
|
| Back to top |
|
|
playfool
l33t
Joined: 01 Jun 2004
Posts: 688
Location: Ã
rhus, Denmark
|
| Posted: Tue May 31, 2005 9:58 pm Post subject: |
|
|
great, another stable release.. and I see I made the FAQ, cool..
Rock on Fallow, you and Lovechild are doing a great job. |
|
| Back to top |
|
|
bosyotech
Tux's lil' helper
Joined: 29 Jan 2005
Posts: 79
Location: earth
|
| Posted: Wed Jun 01, 2005 8:28 am Post subject: |
|
|
very nice. i just have to ask, how does it compare to 2.6.12-rc3-love1? any improvements from rc3-love1?
_________________
of all the things i've lost, i miss my mind the most |
|
| Back to top |
|
|
lavacano
Apprentice
Joined: 29 May 2005
Posts: 190
Location: Poulsbo, WA
|
| Posted: Wed Jun 01, 2005 8:40 am Post subject: |
|
|
hey is that IRQ threading support gonna be in next version? I thought that was tight.
_________________
Sincerely,
Chadwick Ferguson |
|
| Back to top |
|
|
COiN3D
Guru
Joined: 02 Aug 2004
Posts: 543
Location: Munich, Germany
|
| Posted: Wed Jun 01, 2005 5:46 pm Post subject: |
|
|
Hey fallow,
is the framebuffer-splashimage support broken? I couldn't find the right kernel option. By the way, the 500Hz-usbmouse-polling option doesn't work for me. I entered "2" in the field, but when I look in usbview for it, my mouse still runs with a 10Ms delay. Former versions of this polling-patch worked for me, but now it's over 
I'm using a logitech MX500, if this helps you to fix my lil' problem )
_________________
e17 documentation | Be free and use Jabber as your IM! | Combine IRC and IM |
|
| Back to top |
|
|
Robin79
l33t
Joined: 18 Oct 2003
Posts: 632
Location: /home/valdemarsvik
|
| Posted: Wed Jun 01, 2005 6:09 pm Post subject: |
|
|
I would really wanan try this one but iam stick to the old ones cause my stupid ass reformated to hdds with reiser4  So now i can do ashit the both disks are 200 gb and full almost with things i want to have so hard to change i will try to chnage it to ordinary reiserfs or ext3 when i can... DAMM
_________________
Gentoo 2005.0
ASUS P5AD2 Deluxe MB
Intel P4 3.2GHz
PCI-E Nvidia Geforce PCX 5750
--------------------
Registered Linux User Nr # 319050 http://counter.li.org |
|
| Back to top |
|
|
ashtophet
Guru
Joined: 08 Aug 2004
Posts: 397
|
| Posted: Wed Jun 01, 2005 7:29 pm Post subject: |
|
|
| COiN3D wrote: | Hey fallow,
is the framebuffer-splashimage support broken? I couldn't find the right kernel option. By the way, the 500Hz-usbmouse-polling option doesn't work for me. I entered "2" in the field, but when I look in usbview for it, my mouse still runs with a 10Ms delay. Former versions of this polling-patch worked for me, but now it's over
I'm using a logitech MX500, if this helps you to fix my lil' problem ) |
Only about the fbsplash: it's not included in love, so if you wanna use it just patch manually at yr. own risk. Here is working. Cheers.
[OT]Well, after some research and tests i am here with latest love stable release ... About the problem with vanilla:
- If i use ACPI and old deprecated SATA drivers: no problem.
- If i use ACPI and libata drivers: kernel panic.
- If i don't use ACPI and use libata drivers: no problem.[/OT] |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
|
| Back to top |
|
|
|
Unsupported Software
