PATA_HPT37X embezzles two ports
Just to inform everybody: PATA_HPT37X embezzles two ports. It was fixed on 2.6.23.1 by a patch from Alan http://bugzilla.kernel.org/show_bug.cgi?id=9261 But reoccurs in 2.6.24-rc5 I just diffed the dmesg here, you can find the complete dmesg in the bugzilla http://bugzilla.kernel.org/show_bug.cgi?id=9261 diff -Nrup hpt-2.6.23.1 hpt-2.6.24-rc5 --- hpt-2.6.23.12007-12-12 15:40:11.0 +0100 +++ hpt-2.6.24-rc5 2007-12-12 16:28:00.0 +0100 @@ -1,182 +1,4 @@ -Linux version 2.6.23.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Gentoo 4.1.2)) #2 Tue Dec 11 22:43:59 CET 2007 -BIOS-provided physical RAM map: - BIOS-e820: - 0009fc00 (usable) - BIOS-e820: 0009fc00 - 000a (reserved) - BIOS-e820: 000e4000 - 0010 (reserved) - BIOS-e820: 0010 - 5ff3 (usable) - BIOS-e820: 5ff3 - 5ff4 (ACPI data) - BIOS-e820: 5ff4 - 5fff (ACPI NVS) - BIOS-e820: 5fff - 6000 (reserved) - BIOS-e820: fffc - 0001 (reserved) -639MB HIGHMEM available. -896MB LOWMEM available. -Entering add_active_range(0, 0, 393008) 0 entries of 256 used -Zone PFN ranges: - DMA 0 -> 4096 - Normal 4096 -> 229376 - HighMem229376 -> 393008 -Movable zone start PFN for each node -early_node_map[1] active PFN ranges -0:0 -> 393008 -On node 0 totalpages: 393008 - DMA zone: 32 pages used for memmap - DMA zone: 0 pages reserved - DMA zone: 4064 pages, LIFO batch:0 - Normal zone: 1760 pages used for memmap - Normal zone: 223520 pages, LIFO batch:31 - HighMem zone: 1278 pages used for memmap - HighMem zone: 162354 pages, LIFO batch:31 - Movable zone: 0 pages used for memmap -DMI 2.3 present. -ACPI: RSDP 000F9BC0, 0014 (r0 ACPIAM) -ACPI: RSDT 5FF3, 0030 (r1 A M I OEMRSDT 2000503 MSFT 97) -ACPI: FACP 5FF30200, 0081 (r2 A M I OEMFACP 2000503 MSFT 97) -ACPI: DSDT 5FF30360, 343A (r1 P4V88 P4V880011 INTL 2002026) -ACPI: FACS 5FF4, 0040 -ACPI: APIC 5FF30300, 0052 (r1 A M I OEMAPIC 2000503 MSFT 97) -ACPI: OEMB 5FF40040, 003F (r1 A M I OEMBIOS 2000503 MSFT 97) -ACPI: PM-Timer IO Port: 0x808 -ACPI: Local APIC address 0xfee0 -ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) -Processor #0 15:4 APIC version 20 -ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) -ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) -IOAPIC[0]: apic_id 1, version 3, address 0xfec0, GSI 0-23 -ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) -ACPI: IRQ0 used by override. -ACPI: IRQ2 used by override. -ACPI: IRQ9 used by override. -Enabling APIC mode: Flat. Using 1 I/O APICs -Using ACPI (MADT) for SMP configuration information -Allocating PCI resources starting at 7000 (gap: 6000:9ffc) -Built 1 zonelists in Zone order. Total pages: 389938 -Kernel command line: root=/dev/md1 -mapped APIC to b000 (fee0) -mapped IOAPIC to a000 (fec0) -Enabling fast FPU save and restore... done. -Enabling unmasked SIMD FPU exception support... done. -Initializing CPU#0 -PID hash table entries: 4096 (order: 12, 16384 bytes) -Detected 2659.603 MHz processor. -Console: colour VGA+ 80x25 -console [tty0] enabled -Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) -Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 1552008k/1572032k available (3754k kernel code, 18872k reserved, 1349k data, 232k init, 654528k highmem) -virtual kernel memory layout: -fixmap : 0xfffa8000 - 0xf000 ( 348 kB) -pkmap : 0xff80 - 0xffc0 (4096 kB) -vmalloc : 0xf880 - 0xff7fe000 ( 111 MB) -lowmem : 0xc000 - 0xf800 ( 896 MB) - .init : 0xc060 - 0xc063a000 ( 232 kB) - .data : 0xc04aaa28 - 0xc05fc19c (1349 kB) - .text : 0xc010 - 0xc04aaa28 (3754 kB) -Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay using timer specific routine.. 5323.32 BogoMIPS (lpj=2661663) -Mount-cache hash table entries: 512 -CPU: After generic identify, caps: bfebfbff 441d -monitor/mwait feature present. -using mwait in idle threads. -CPU: Trace cache: 12K uops, L1 D cache: 16K -CPU: L2 cache: 256K -CPU: After all inits, caps: bfebfbff b180 441d -Intel machine check architecture supported. -Intel machine check reporting enabled on CPU#0. -CPU0: Intel P4/Xeon Extended MCE MSRs (12) available -CPU0: Thermal monitoring enabled -Compat vDSO mapped to e000. -CPU: Intel(R) Celeron(R) CPU 2.66GHz stepping 01 -Checking 'hlt' instruction... OK. -ACPI: Core revision 20070126 -ENABLING IO-APIC IRQs -..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 -xor: automatically using best checksumming function: pIII_sse - pIII_sse : 4320.000 MB/sec -xor: using
PATA_HPT37X embezzles two ports
Just to inform everybody: PATA_HPT37X embezzles two ports. It was fixed on 2.6.23.1 by a patch from Alan http://bugzilla.kernel.org/show_bug.cgi?id=9261 But reoccurs in 2.6.24-rc5 I just diffed the dmesg here, you can find the complete dmesg in the bugzilla http://bugzilla.kernel.org/show_bug.cgi?id=9261 diff -Nrup hpt-2.6.23.1 hpt-2.6.24-rc5 --- hpt-2.6.23.12007-12-12 15:40:11.0 +0100 +++ hpt-2.6.24-rc5 2007-12-12 16:28:00.0 +0100 @@ -1,182 +1,4 @@ -Linux version 2.6.23.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Gentoo 4.1.2)) #2 Tue Dec 11 22:43:59 CET 2007 -BIOS-provided physical RAM map: - BIOS-e820: - 0009fc00 (usable) - BIOS-e820: 0009fc00 - 000a (reserved) - BIOS-e820: 000e4000 - 0010 (reserved) - BIOS-e820: 0010 - 5ff3 (usable) - BIOS-e820: 5ff3 - 5ff4 (ACPI data) - BIOS-e820: 5ff4 - 5fff (ACPI NVS) - BIOS-e820: 5fff - 6000 (reserved) - BIOS-e820: fffc - 0001 (reserved) -639MB HIGHMEM available. -896MB LOWMEM available. -Entering add_active_range(0, 0, 393008) 0 entries of 256 used -Zone PFN ranges: - DMA 0 - 4096 - Normal 4096 - 229376 - HighMem229376 - 393008 -Movable zone start PFN for each node -early_node_map[1] active PFN ranges -0:0 - 393008 -On node 0 totalpages: 393008 - DMA zone: 32 pages used for memmap - DMA zone: 0 pages reserved - DMA zone: 4064 pages, LIFO batch:0 - Normal zone: 1760 pages used for memmap - Normal zone: 223520 pages, LIFO batch:31 - HighMem zone: 1278 pages used for memmap - HighMem zone: 162354 pages, LIFO batch:31 - Movable zone: 0 pages used for memmap -DMI 2.3 present. -ACPI: RSDP 000F9BC0, 0014 (r0 ACPIAM) -ACPI: RSDT 5FF3, 0030 (r1 A M I OEMRSDT 2000503 MSFT 97) -ACPI: FACP 5FF30200, 0081 (r2 A M I OEMFACP 2000503 MSFT 97) -ACPI: DSDT 5FF30360, 343A (r1 P4V88 P4V880011 INTL 2002026) -ACPI: FACS 5FF4, 0040 -ACPI: APIC 5FF30300, 0052 (r1 A M I OEMAPIC 2000503 MSFT 97) -ACPI: OEMB 5FF40040, 003F (r1 A M I OEMBIOS 2000503 MSFT 97) -ACPI: PM-Timer IO Port: 0x808 -ACPI: Local APIC address 0xfee0 -ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) -Processor #0 15:4 APIC version 20 -ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) -ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) -IOAPIC[0]: apic_id 1, version 3, address 0xfec0, GSI 0-23 -ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) -ACPI: IRQ0 used by override. -ACPI: IRQ2 used by override. -ACPI: IRQ9 used by override. -Enabling APIC mode: Flat. Using 1 I/O APICs -Using ACPI (MADT) for SMP configuration information -Allocating PCI resources starting at 7000 (gap: 6000:9ffc) -Built 1 zonelists in Zone order. Total pages: 389938 -Kernel command line: root=/dev/md1 -mapped APIC to b000 (fee0) -mapped IOAPIC to a000 (fec0) -Enabling fast FPU save and restore... done. -Enabling unmasked SIMD FPU exception support... done. -Initializing CPU#0 -PID hash table entries: 4096 (order: 12, 16384 bytes) -Detected 2659.603 MHz processor. -Console: colour VGA+ 80x25 -console [tty0] enabled -Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) -Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 1552008k/1572032k available (3754k kernel code, 18872k reserved, 1349k data, 232k init, 654528k highmem) -virtual kernel memory layout: -fixmap : 0xfffa8000 - 0xf000 ( 348 kB) -pkmap : 0xff80 - 0xffc0 (4096 kB) -vmalloc : 0xf880 - 0xff7fe000 ( 111 MB) -lowmem : 0xc000 - 0xf800 ( 896 MB) - .init : 0xc060 - 0xc063a000 ( 232 kB) - .data : 0xc04aaa28 - 0xc05fc19c (1349 kB) - .text : 0xc010 - 0xc04aaa28 (3754 kB) -Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay using timer specific routine.. 5323.32 BogoMIPS (lpj=2661663) -Mount-cache hash table entries: 512 -CPU: After generic identify, caps: bfebfbff 441d -monitor/mwait feature present. -using mwait in idle threads. -CPU: Trace cache: 12K uops, L1 D cache: 16K -CPU: L2 cache: 256K -CPU: After all inits, caps: bfebfbff b180 441d -Intel machine check architecture supported. -Intel machine check reporting enabled on CPU#0. -CPU0: Intel P4/Xeon Extended MCE MSRs (12) available -CPU0: Thermal monitoring enabled -Compat vDSO mapped to e000. -CPU: Intel(R) Celeron(R) CPU 2.66GHz stepping 01 -Checking 'hlt' instruction... OK. -ACPI: Core revision 20070126 -ENABLING IO-APIC IRQs -..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 -xor: automatically using best checksumming function: pIII_sse - pIII_sse : 4320.000 MB/sec -xor: using function:
Re: sata NCQ blacklist entry
On 11/29/07, Tejun Heo <[EMAIL PROTECTED]> wrote: > > I now have affected drives on my desk and am gonna try reproduce it. My > gut feeling says it's timing related problem on controller / driver > side. Please wait a bit. > > > by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun? > > No, not yet. Do you have a tracking number or something? > > Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sata NCQ blacklist entry
On 11/29/07, Tejun Heo <[EMAIL PROTECTED]> wrote: > > I now have affected drives on my desk and am gonna try reproduce it. My > gut feeling says it's timing related problem on controller / driver > side. Please wait a bit. > Okay, no problem, I am just curious. > > by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun? > > No, not yet. Do you have a tracking number or something? > No, I havn't... all I got is the bill... but that doesn't help because we choosed to use shipment without enshurance... there is no tracking number. Mhhh that sucks... i can't get rid of the bad feeling that it got lost. But I'll try to make some checks. CU Bjoern - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sata NCQ blacklist entry
On 11/7/07, Tejun Heo <[EMAIL PROTECTED]> wrote: > > Thanks. We're currently trying to find out what's actually going on > with all these drives. At first, drives which got blacklisted aren't > many and made sense (had other problems with NCQ, etc..) but with new > generation drives from many vendors showing the same symptom, we aren't > too sure now. > > I'll keep your email in my todo list and add the drive to the blacklist > once the problem is verified. > > Thanks. Something new on the NCQ front? Just asking if you need someone to test some of your ideas? I got the "WDC WD740ADFD-00NLR1" by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sata NCQ blacklist entry
On 11/7/07, Tejun Heo [EMAIL PROTECTED] wrote: Thanks. We're currently trying to find out what's actually going on with all these drives. At first, drives which got blacklisted aren't many and made sense (had other problems with NCQ, etc..) but with new generation drives from many vendors showing the same symptom, we aren't too sure now. I'll keep your email in my todo list and add the drive to the blacklist once the problem is verified. Thanks. Something new on the NCQ front? Just asking if you need someone to test some of your ideas? I got the WDC WD740ADFD-00NLR1 by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sata NCQ blacklist entry
On 11/29/07, Tejun Heo [EMAIL PROTECTED] wrote: I now have affected drives on my desk and am gonna try reproduce it. My gut feeling says it's timing related problem on controller / driver side. Please wait a bit. Okay, no problem, I am just curious. by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun? No, not yet. Do you have a tracking number or something? No, I havn't... all I got is the bill... but that doesn't help because we choosed to use shipment without enshurance... there is no tracking number. Mhhh that sucks... i can't get rid of the bad feeling that it got lost. But I'll try to make some checks. CU Bjoern - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: sata NCQ blacklist entry
On 11/29/07, Tejun Heo [EMAIL PROTECTED] wrote: I now have affected drives on my desk and am gonna try reproduce it. My gut feeling says it's timing related problem on controller / driver side. Please wait a bit. by the way, and OT, did the Plextor DVD-RW drive reach you, Tejun? No, not yet. Do you have a tracking number or something? Thanks. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6.22.5] irq X: nobody cared but X is successfully used by libata
On 10/19/07, Paul Rolland <[EMAIL PROTECTED]> wrote: > Hi Tejun, > > On Fri, 19 Oct 2007 12:23:15 +0900 > Tejun Heo <[EMAIL PROTECTED]> wrote: > > > > On 26/08/07, Paul Rolland <[EMAIL PROTECTED]> wrote: > > >> My machine (an ASUS P5W-DH-Deluxe, Core2, 4Go RAM, 3 SATA and 2IDE) is > > >> reporting a : > > >> irq 23: nobody cared (try booting with the "irqpoll" option) > > >> together with a Call Trace, but : > > >> - irqpoll is present on the command line, > > >> - the irq is reported to be used by libata, > > >> - the irqpoll option is mandatory if I want _some_ of my SATA disks to > > >> be accessible. > > > > Does this still happen with 2.6.23? If so, please post boot log. Thanks. > > > Not tested yet, will do so during the WE. > > Regards, > Paul No it does not. I have nearly the same setup (ASUS P5W-DH-Deluxe, Core2, 2GB RAM, 3 SATA and 2IDE) And a "dmesg | grep irqpoll does not show up with results. dmsg | grep 23 comes up with: wifi0: Atheros 5212: mem=0xeb9f, irq=23 And I no longer use IRQPOLL (I dropped it somwhere between 2.6.22.? and 2.6.23) as Kernel option. kernel (hd0,0)/vmlinuz root=/dev/sda3 video=nvidiafb:[EMAIL PROTECTED],mtrr,ywrap All SATA Ports are working (except the the PMP... it "works" but I would not recomment usign it right now because of these bugs: http://bugzilla.kernel.org/show_bug.cgi?id=9010 http://bugzilla.kernel.org/show_bug.cgi?id=9010 regards Bjoern Olausson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6.22.5] irq X: nobody cared but X is successfully used by libata
On 10/19/07, Paul Rolland [EMAIL PROTECTED] wrote: Hi Tejun, On Fri, 19 Oct 2007 12:23:15 +0900 Tejun Heo [EMAIL PROTECTED] wrote: On 26/08/07, Paul Rolland [EMAIL PROTECTED] wrote: My machine (an ASUS P5W-DH-Deluxe, Core2, 4Go RAM, 3 SATA and 2IDE) is reporting a : irq 23: nobody cared (try booting with the irqpoll option) together with a Call Trace, but : - irqpoll is present on the command line, - the irq is reported to be used by libata, - the irqpoll option is mandatory if I want _some_ of my SATA disks to be accessible. Does this still happen with 2.6.23? If so, please post boot log. Thanks. Not tested yet, will do so during the WE. Regards, Paul No it does not. I have nearly the same setup (ASUS P5W-DH-Deluxe, Core2, 2GB RAM, 3 SATA and 2IDE) And a dmesg | grep irqpoll does not show up with results. dmsg | grep 23 comes up with: wifi0: Atheros 5212: mem=0xeb9f, irq=23 And I no longer use IRQPOLL (I dropped it somwhere between 2.6.22.? and 2.6.23) as Kernel option. kernel (hd0,0)/vmlinuz root=/dev/sda3 video=nvidiafb:[EMAIL PROTECTED],mtrr,ywrap All SATA Ports are working (except the the PMP... it works but I would not recomment usign it right now because of these bugs: http://bugzilla.kernel.org/show_bug.cgi?id=9010 http://bugzilla.kernel.org/show_bug.cgi?id=9010 regards Bjoern Olausson - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[2.6.21.3] [pata_jmicron] BUG: soft lockup detected on CPU#0!
Dear list members, I am posting to this list just to get additional help for the bug I reported here: http://bugzilla.kernel.org/show_bug.cgi?id=8259 So the problem is the following: I have a Asus P5W-DH Delux Mainboard with an onboard JMicron 20360/20363 AHCI Controller. As soon as I enable this controller my system freezes after some time. I captured some of the soft lockups with and without the closed source Nvidia drivers. As no one has answered for some time now on my bug, I am seeking help on this list. My major question is: Does it look like a hardware issue or is it a bug in the driver? Thanks for your help in advance. Best regards Bjoern Below I will provide all logs/dmsg/lspci which could be from interest. If you need more info, blease let me kno === The soft lockup occurs still on 2.6.21.3 All logs/lspci/dmsg... can be found here http://olausson.name/bug/ The latest, captured today is http://olausson.name/bug/2007.05.25-freax-bug-nvidia.log Usefull information can be found on the following lines: --Line 764 lspci --vv --Line 1167 dmsg --Line 1803 lsmod --Line 1841 cat /proc/interrupts --Line 1865 lsusb --Line 1883 uname -a --Line 1886 cat /usr/src/linux/.config May 25 18:53:45 freax BUG: soft lockup detected on CPU#0! May 25 18:53:45 freax May 25 18:53:45 freax Call Trace: May 25 18:53:45 freax [] softlockup_tick+0xda/0xf5 May 25 18:53:45 freax [] update_process_times+0x42/0x68 May 25 18:53:45 freax [] smp_local_timer_interrupt+0x34/0x52 May 25 18:53:45 freax [] smp_apic_timer_interrupt+0x44/0x5e May 25 18:53:45 freax [] apic_timer_interrupt+0x66/0x70 May 25 18:53:45 freax [] handle_IRQ_event+0x1a/0x53 May 25 18:53:45 freax [] handle_edge_irq+0xe4/0x128 May 25 18:53:45 freax [] do_IRQ+0xf1/0x160 May 25 18:53:45 freax [] ret_from_intr+0x0/0xa May 25 18:53:45 freax [] ata_scsi_qc_complete+0x0/0x385 May 25 18:53:45 freax [] call_softirq+0x1c/0x28 May 25 18:53:45 freax [] __do_softirq+0x3e/0xb8 May 25 18:53:45 freax [] call_softirq+0x1c/0x28 May 25 18:53:45 freax [] do_softirq+0x2c/0x7d May 25 18:53:45 freax [] irq_exit+0x36/0x42 May 25 18:53:45 freax [] do_IRQ+0x13d/0x160 May 25 18:53:45 freax [] ret_from_intr+0x0/0xa May 25 18:53:45 freax [] _spin_unlock_irqrestore+0xc/0x31 May 25 18:53:45 freax [] scsi_dispatch_cmd+0x1f1/0x236 May 25 18:53:45 freax [] scsi_request_fn+0x26c/0x337 May 25 18:53:45 freax [] generic_unplug_device+0x18/0x25 May 25 18:53:45 freax [] sync_buffer+0x36/0x40 May 25 18:53:45 freax [] __wait_on_bit+0x40/0x6e May 25 18:53:45 freax [] sync_buffer+0x0/0x40 May 25 18:53:45 freax [] out_of_line_wait_on_bit+0x6c/0x78 May 25 18:53:45 freax [] wake_bit_function+0x0/0x23 May 25 18:53:45 freax [] journal_commit_transaction+0x68b/0x11fe May 25 18:53:45 freax [] lock_timer_base+0x1b/0x3c May 25 18:53:45 freax [] _spin_unlock_irqrestore+0x16/0x31 May 25 18:53:45 freax [] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [] kjournald+0xba/0x217 May 25 18:53:45 freax [] autoremove_wake_function+0x0/0x2e May 25 18:53:45 freax [] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [] kjournald+0x0/0x217 May 25 18:53:45 freax [] kthread+0xd1/0x100 May 25 18:53:45 freax [] child_rip+0xa/0x12 May 25 18:53:45 freax [] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [] kthread+0x0/0x100 May 25 18:53:45 freax [] child_rip+0x0/0x12 May 25 18:53:45 freax --- Older Soft Lockups: (NV in the filenames means the xorg's nvidia driver) (nvidia in the fienames means Nvidias closed source driver) Heres a soft-lockup without NVIDIA driver (using the xorgs NV driver instead) Apr 13 22:33:59 freax BUG: soft lockup detected on CPU#0! Apr 13 22:33:59 freax Apr 13 22:33:59 freax Call Trace: Apr 13 22:33:59 freax [] softlockup_tick+0xda/0xf5 Apr 13 22:33:59 freax [] update_process_times+0x42/0x68 Apr 13 22:33:59 freax [] smp_local_timer_interrupt+0x34/0x52 Apr 13 22:33:59 freax [] smp_apic_timer_interrupt+0x44/0x5e Apr 13 22:33:59 freax [] apic_timer_interrupt+0x66/0x70 Apr 13 22:33:59 freax [] handle_IRQ_event+0x1a/0x53 Apr 13 22:33:59 freax [] handle_edge_irq+0xe4/0x128 Apr 13 22:33:59 freax [] call_softirq+0x1c/0x28 Apr 13 22:33:59 freax [] do_IRQ+0xf1/0x160 Apr 13 22:33:59 freax [] ret_from_intr+0x0/0xa Apr 13 22:33:59 freax And this one is WITH the CS NVIDIA driver: Apr 13 18:14:09 freax BUG: soft lockup detected on CPU#0! Apr 13 18:14:09 freax Apr 13 18:14:09 freax Call Trace: Apr 13 18:14:09 freax [] softlockup_tick+0xda/0xf5 Apr 13 18:14:09 freax [] update_process_times+0x42/0x68 Apr 13 18:14:09 freax [] smp_local_timer_interrupt+0x34/0x52 Apr 13 18:14:09 freax [] smp_apic_timer_interrupt+0x44/0x5e Apr 13 18:14:09 freax [] apic_timer_interrupt+0x66/0x70 Apr 13 18:14:09 freax [] handle_IRQ_event+0x1a/0x53 Apr 13 18:14:09 freax [] handle_edge_irq+0xe4/0x128 Apr
[2.6.21.3] [pata_jmicron] BUG: soft lockup detected on CPU#0!
Dear list members, I am posting to this list just to get additional help for the bug I reported here: http://bugzilla.kernel.org/show_bug.cgi?id=8259 So the problem is the following: I have a Asus P5W-DH Delux Mainboard with an onboard JMicron 20360/20363 AHCI Controller. As soon as I enable this controller my system freezes after some time. I captured some of the soft lockups with and without the closed source Nvidia drivers. As no one has answered for some time now on my bug, I am seeking help on this list. My major question is: Does it look like a hardware issue or is it a bug in the driver? Thanks for your help in advance. Best regards Bjoern Below I will provide all logs/dmsg/lspci which could be from interest. If you need more info, blease let me kno === The soft lockup occurs still on 2.6.21.3 All logs/lspci/dmsg... can be found here http://olausson.name/bug/ The latest, captured today is http://olausson.name/bug/2007.05.25-freax-bug-nvidia.log Usefull information can be found on the following lines: --Line 764 lspci --vv --Line 1167 dmsg --Line 1803 lsmod --Line 1841 cat /proc/interrupts --Line 1865 lsusb --Line 1883 uname -a --Line 1886 cat /usr/src/linux/.config May 25 18:53:45 freax BUG: soft lockup detected on CPU#0! May 25 18:53:45 freax May 25 18:53:45 freax Call Trace: May 25 18:53:45 freax IRQ [802558d4] softlockup_tick+0xda/0xf5 May 25 18:53:45 freax [8023b301] update_process_times+0x42/0x68 May 25 18:53:45 freax [8021772d] smp_local_timer_interrupt+0x34/0x52 May 25 18:53:45 freax [80217e36] smp_apic_timer_interrupt+0x44/0x5e May 25 18:53:45 freax [8020a086] apic_timer_interrupt+0x66/0x70 May 25 18:53:45 freax [80255b95] handle_IRQ_event+0x1a/0x53 May 25 18:53:45 freax [80256d07] handle_edge_irq+0xe4/0x128 May 25 18:53:45 freax [8020ba7d] do_IRQ+0xf1/0x160 May 25 18:53:45 freax [80209931] ret_from_intr+0x0/0xa May 25 18:53:45 freax [80459072] ata_scsi_qc_complete+0x0/0x385 May 25 18:53:45 freax [8020a5dc] call_softirq+0x1c/0x28 May 25 18:53:45 freax [80237509] __do_softirq+0x3e/0xb8 May 25 18:53:45 freax [8020a5dc] call_softirq+0x1c/0x28 May 25 18:53:45 freax [8020b93b] do_softirq+0x2c/0x7d May 25 18:53:45 freax [802374bf] irq_exit+0x36/0x42 May 25 18:53:45 freax [8020bac9] do_IRQ+0x13d/0x160 May 25 18:53:45 freax [80209931] ret_from_intr+0x0/0xa May 25 18:53:45 freax EOI [805bf694] _spin_unlock_irqrestore+0xc/0x31 May 25 18:53:45 freax [8043a7d6] scsi_dispatch_cmd+0x1f1/0x236 May 25 18:53:45 freax [8043f373] scsi_request_fn+0x26c/0x337 May 25 18:53:45 freax [8039de56] generic_unplug_device+0x18/0x25 May 25 18:53:45 freax [8029bb5f] sync_buffer+0x36/0x40 May 25 18:53:45 freax [805be1c2] __wait_on_bit+0x40/0x6e May 25 18:53:45 freax [8029bb29] sync_buffer+0x0/0x40 May 25 18:53:45 freax [805be25c] out_of_line_wait_on_bit+0x6c/0x78 May 25 18:53:45 freax [80244f63] wake_bit_function+0x0/0x23 May 25 18:53:45 freax [802e1d75] journal_commit_transaction+0x68b/0x11fe May 25 18:53:45 freax [8023b0dc] lock_timer_base+0x1b/0x3c May 25 18:53:45 freax [805bf69e] _spin_unlock_irqrestore+0x16/0x31 May 25 18:53:45 freax [80244b96] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [802e6014] kjournald+0xba/0x217 May 25 18:53:45 freax [80244f35] autoremove_wake_function+0x0/0x2e May 25 18:53:45 freax [80244b96] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [802e5f5a] kjournald+0x0/0x217 May 25 18:53:45 freax [80244df1] kthread+0xd1/0x100 May 25 18:53:45 freax [8020a268] child_rip+0xa/0x12 May 25 18:53:45 freax [80244b96] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [80244d20] kthread+0x0/0x100 May 25 18:53:45 freax [8020a25e] child_rip+0x0/0x12 May 25 18:53:45 freax --- Older Soft Lockups: (NV in the filenames means the xorg's nvidia driver) (nvidia in the fienames means Nvidias closed source driver) Heres a soft-lockup without NVIDIA driver (using the xorgs NV driver instead) Apr 13 22:33:59 freax BUG: soft lockup detected on CPU#0! Apr 13 22:33:59 freax Apr 13 22:33:59 freax Call Trace: Apr 13 22:33:59 freax IRQ [802559c8] softlockup_tick+0xda/0xf5 Apr 13 22:33:59 freax [8023b42d] update_process_times+0x42/0x68 Apr 13 22:33:59 freax [80217775] smp_local_timer_interrupt+0x34/0x52 Apr 13 22:33:59 freax [80217e7e] smp_apic_timer_interrupt+0x44/0x5e Apr 13 22:33:59 freax [8020a086] apic_timer_interrupt+0x66/0x70 Apr 13 22:33:59 freax [80255c89] handle_IRQ_event+0x1a/0x53 Apr 13 22:33:59 freax [80256dfb]
[2.6.21.3] [pata_jmicron] BUG: soft lockup detected on CPU#0!
Dear list members, I am posting to this list just to get additional help for the bug I reported here: http://bugzilla.kernel.org/show_bug.cgi?id=8259 So the problem is the following: I have a Asus P5W-DH Delux Mainboard with an onboard JMicron 20360/20363 AHCI Controller. As soon as I enable this controller my system freezes after some time. I captured some of the soft lockups with and without the closed source Nvidia drivers. As no one has answered for some time now on my bug, I am seeking help on this list. My major question is: Does it look like a hardware issue or is it a bug in the driver? Thanks for your help in advance. Best regards Bjoern Below I will provide all logs/dmsg/lspci which could be from interest. If you need more info, blease let me kno === The soft lockup occurs still on 2.6.21.3 All logs/lspci/dmsg... can be found here http://olausson.name/bug/ The latest, captured today is http://olausson.name/bug/2007.05.25-freax-bug-nvidia.log Usefull information can be found on the following lines: --Line 764 lspci --vv --Line 1167 dmsg --Line 1803 lsmod --Line 1841 cat /proc/interrupts --Line 1865 lsusb --Line 1883 uname -a --Line 1886 cat /usr/src/linux/.config May 25 18:53:45 freax BUG: soft lockup detected on CPU#0! May 25 18:53:45 freax May 25 18:53:45 freax Call Trace: May 25 18:53:45 freax [] softlockup_tick+0xda/0xf5 May 25 18:53:45 freax [] update_process_times+0x42/0x68 May 25 18:53:45 freax [] smp_local_timer_interrupt+0x34/0x52 May 25 18:53:45 freax [] smp_apic_timer_interrupt+0x44/0x5e May 25 18:53:45 freax [] apic_timer_interrupt+0x66/0x70 May 25 18:53:45 freax [] handle_IRQ_event+0x1a/0x53 May 25 18:53:45 freax [] handle_edge_irq+0xe4/0x128 May 25 18:53:45 freax [] do_IRQ+0xf1/0x160 May 25 18:53:45 freax [] ret_from_intr+0x0/0xa May 25 18:53:45 freax [] ata_scsi_qc_complete+0x0/0x385 May 25 18:53:45 freax [] call_softirq+0x1c/0x28 May 25 18:53:45 freax [] __do_softirq+0x3e/0xb8 May 25 18:53:45 freax [] call_softirq+0x1c/0x28 May 25 18:53:45 freax [] do_softirq+0x2c/0x7d May 25 18:53:45 freax [] irq_exit+0x36/0x42 May 25 18:53:45 freax [] do_IRQ+0x13d/0x160 May 25 18:53:45 freax [] ret_from_intr+0x0/0xa May 25 18:53:45 freax [] _spin_unlock_irqrestore+0xc/0x31 May 25 18:53:45 freax [] scsi_dispatch_cmd+0x1f1/0x236 May 25 18:53:45 freax [] scsi_request_fn+0x26c/0x337 May 25 18:53:45 freax [] generic_unplug_device+0x18/0x25 May 25 18:53:45 freax [] sync_buffer+0x36/0x40 May 25 18:53:45 freax [] __wait_on_bit+0x40/0x6e May 25 18:53:45 freax [] sync_buffer+0x0/0x40 May 25 18:53:45 freax [] out_of_line_wait_on_bit+0x6c/0x78 May 25 18:53:45 freax [] wake_bit_function+0x0/0x23 May 25 18:53:45 freax [] journal_commit_transaction+0x68b/0x11fe May 25 18:53:45 freax [] lock_timer_base+0x1b/0x3c May 25 18:53:45 freax [] _spin_unlock_irqrestore+0x16/0x31 May 25 18:53:45 freax [] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [] kjournald+0xba/0x217 May 25 18:53:45 freax [] autoremove_wake_function+0x0/0x2e May 25 18:53:45 freax [] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [] kjournald+0x0/0x217 May 25 18:53:45 freax [] kthread+0xd1/0x100 May 25 18:53:45 freax [] child_rip+0xa/0x12 May 25 18:53:45 freax [] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [] kthread+0x0/0x100 May 25 18:53:45 freax [] child_rip+0x0/0x12 May 25 18:53:45 freax --- Older Soft Lockups: (NV in the filenames means the xorg's nvidia driver) (nvidia in the fienames means Nvidias closed source driver) Heres a soft-lockup without NVIDIA driver (using the xorgs NV driver instead) Apr 13 22:33:59 freax BUG: soft lockup detected on CPU#0! Apr 13 22:33:59 freax Apr 13 22:33:59 freax Call Trace: Apr 13 22:33:59 freax [] softlockup_tick+0xda/0xf5 Apr 13 22:33:59 freax [] update_process_times+0x42/0x68 Apr 13 22:33:59 freax [] smp_local_timer_interrupt+0x34/0x52 Apr 13 22:33:59 freax [] smp_apic_timer_interrupt+0x44/0x5e Apr 13 22:33:59 freax [] apic_timer_interrupt+0x66/0x70 Apr 13 22:33:59 freax [] handle_IRQ_event+0x1a/0x53 Apr 13 22:33:59 freax [] handle_edge_irq+0xe4/0x128 Apr 13 22:33:59 freax [] call_softirq+0x1c/0x28 Apr 13 22:33:59 freax [] do_IRQ+0xf1/0x160 Apr 13 22:33:59 freax [] ret_from_intr+0x0/0xa Apr 13 22:33:59 freax And this one is WITH the CS NVIDIA driver: Apr 13 18:14:09 freax BUG: soft lockup detected on CPU#0! Apr 13 18:14:09 freax Apr 13 18:14:09 freax Call Trace: Apr 13 18:14:09 freax [] softlockup_tick+0xda/0xf5 Apr 13 18:14:09 freax [] update_process_times+0x42/0x68 Apr 13 18:14:09 freax [] smp_local_timer_interrupt+0x34/0x52 Apr 13 18:14:09 freax [] smp_apic_timer_interrupt+0x44/0x5e Apr 13 18:14:09 freax [] apic_timer_interrupt+0x66/0x70 Apr 13 18:14:09 freax [] handle_IRQ_event+0x1a/0x53 Apr 13 18:14:09 freax [] handle_edge_irq+0xe4/0x128 Apr
[2.6.21.3] [pata_jmicron] BUG: soft lockup detected on CPU#0!
Dear list members, I am posting to this list just to get additional help for the bug I reported here: http://bugzilla.kernel.org/show_bug.cgi?id=8259 So the problem is the following: I have a Asus P5W-DH Delux Mainboard with an onboard JMicron 20360/20363 AHCI Controller. As soon as I enable this controller my system freezes after some time. I captured some of the soft lockups with and without the closed source Nvidia drivers. As no one has answered for some time now on my bug, I am seeking help on this list. My major question is: Does it look like a hardware issue or is it a bug in the driver? Thanks for your help in advance. Best regards Bjoern Below I will provide all logs/dmsg/lspci which could be from interest. If you need more info, blease let me kno === The soft lockup occurs still on 2.6.21.3 All logs/lspci/dmsg... can be found here http://olausson.name/bug/ The latest, captured today is http://olausson.name/bug/2007.05.25-freax-bug-nvidia.log Usefull information can be found on the following lines: --Line 764 lspci --vv --Line 1167 dmsg --Line 1803 lsmod --Line 1841 cat /proc/interrupts --Line 1865 lsusb --Line 1883 uname -a --Line 1886 cat /usr/src/linux/.config May 25 18:53:45 freax BUG: soft lockup detected on CPU#0! May 25 18:53:45 freax May 25 18:53:45 freax Call Trace: May 25 18:53:45 freax IRQ [802558d4] softlockup_tick+0xda/0xf5 May 25 18:53:45 freax [8023b301] update_process_times+0x42/0x68 May 25 18:53:45 freax [8021772d] smp_local_timer_interrupt+0x34/0x52 May 25 18:53:45 freax [80217e36] smp_apic_timer_interrupt+0x44/0x5e May 25 18:53:45 freax [8020a086] apic_timer_interrupt+0x66/0x70 May 25 18:53:45 freax [80255b95] handle_IRQ_event+0x1a/0x53 May 25 18:53:45 freax [80256d07] handle_edge_irq+0xe4/0x128 May 25 18:53:45 freax [8020ba7d] do_IRQ+0xf1/0x160 May 25 18:53:45 freax [80209931] ret_from_intr+0x0/0xa May 25 18:53:45 freax [80459072] ata_scsi_qc_complete+0x0/0x385 May 25 18:53:45 freax [8020a5dc] call_softirq+0x1c/0x28 May 25 18:53:45 freax [80237509] __do_softirq+0x3e/0xb8 May 25 18:53:45 freax [8020a5dc] call_softirq+0x1c/0x28 May 25 18:53:45 freax [8020b93b] do_softirq+0x2c/0x7d May 25 18:53:45 freax [802374bf] irq_exit+0x36/0x42 May 25 18:53:45 freax [8020bac9] do_IRQ+0x13d/0x160 May 25 18:53:45 freax [80209931] ret_from_intr+0x0/0xa May 25 18:53:45 freax EOI [805bf694] _spin_unlock_irqrestore+0xc/0x31 May 25 18:53:45 freax [8043a7d6] scsi_dispatch_cmd+0x1f1/0x236 May 25 18:53:45 freax [8043f373] scsi_request_fn+0x26c/0x337 May 25 18:53:45 freax [8039de56] generic_unplug_device+0x18/0x25 May 25 18:53:45 freax [8029bb5f] sync_buffer+0x36/0x40 May 25 18:53:45 freax [805be1c2] __wait_on_bit+0x40/0x6e May 25 18:53:45 freax [8029bb29] sync_buffer+0x0/0x40 May 25 18:53:45 freax [805be25c] out_of_line_wait_on_bit+0x6c/0x78 May 25 18:53:45 freax [80244f63] wake_bit_function+0x0/0x23 May 25 18:53:45 freax [802e1d75] journal_commit_transaction+0x68b/0x11fe May 25 18:53:45 freax [8023b0dc] lock_timer_base+0x1b/0x3c May 25 18:53:45 freax [805bf69e] _spin_unlock_irqrestore+0x16/0x31 May 25 18:53:45 freax [80244b96] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [802e6014] kjournald+0xba/0x217 May 25 18:53:45 freax [80244f35] autoremove_wake_function+0x0/0x2e May 25 18:53:45 freax [80244b96] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [802e5f5a] kjournald+0x0/0x217 May 25 18:53:45 freax [80244df1] kthread+0xd1/0x100 May 25 18:53:45 freax [8020a268] child_rip+0xa/0x12 May 25 18:53:45 freax [80244b96] keventd_create_kthread+0x0/0x6a May 25 18:53:45 freax [80244d20] kthread+0x0/0x100 May 25 18:53:45 freax [8020a25e] child_rip+0x0/0x12 May 25 18:53:45 freax --- Older Soft Lockups: (NV in the filenames means the xorg's nvidia driver) (nvidia in the fienames means Nvidias closed source driver) Heres a soft-lockup without NVIDIA driver (using the xorgs NV driver instead) Apr 13 22:33:59 freax BUG: soft lockup detected on CPU#0! Apr 13 22:33:59 freax Apr 13 22:33:59 freax Call Trace: Apr 13 22:33:59 freax IRQ [802559c8] softlockup_tick+0xda/0xf5 Apr 13 22:33:59 freax [8023b42d] update_process_times+0x42/0x68 Apr 13 22:33:59 freax [80217775] smp_local_timer_interrupt+0x34/0x52 Apr 13 22:33:59 freax [80217e7e] smp_apic_timer_interrupt+0x44/0x5e Apr 13 22:33:59 freax [8020a086] apic_timer_interrupt+0x66/0x70 Apr 13 22:33:59 freax [80255c89] handle_IRQ_event+0x1a/0x53 Apr 13 22:33:59 freax [80256dfb]
