LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-21-2007, 04:22 AM   #1
Pommpie
LQ Newbie
 
Registered: Oct 2006
Posts: 13

Rep: Reputation: 0
SATA problem with 2.6.23.12 kernel


Running Slackware 12.0 with GRUB as the bootloader. The generic hugesmp.s kernel bundled with the Slackware DVD works magically, however, when I boot the machine with the 2.6.23.12 kernel I compiled myself, IRQ 5 borks and, with it, the SATA controller completely fails to work (no sd* devices in /dev). Other than that, the machine works fine, and the IDE drive works as well.

Here are the seemingly relevant portions of my dmesg:

Code:
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
(stuff relating to IDE cut)
sata_nv 0000:00:07.0: version 3.5
sata_nv 0000:00:07.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:07.0 to 64
scsi0 : sata_nv
scsi1 : sata_nv
ata1: SATA max UDMA/133 cmd 0xf9204480 ctl 0xf92044a0 bmdma 0x0001d400 irq 5
ata2: SATA max UDMA/133 cmd 0xf9204580 ctl 0xf92045a0 bmdma 0x0001d408 irq 5
ata1: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
sata_nv 0000:00:08.0: Using ADMA mode
PCI: Setting latency timer of device 0000:00:08.0 to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0xf9206480 ctl 0xf92064a0 bmdma 0x0001c000 irq 11
ata4: SATA max UDMA/133 cmd 0xf9206580 ctl 0xf92065a0 bmdma 0x0001c008 irq 11
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
irq 5: nobody cared (try booting with the "irqpoll" option)
 [<c0136dc4>] __report_bad_irq+0x36/0x75
 [<c0136eb7>] note_interrupt+0x98/0xcb
 [<c0137535>] handle_fasteoi_irq+0x8a/0xac
 [<c0104385>] do_IRQ+0x7b/0x93
 [<c011b127>] irq_exit+0x67/0x72
 [<c01030ab>] common_interrupt+0x23/0x28
 [<c0100854>] default_idle+0x0/0x3e
 [<c0100880>] default_idle+0x2c/0x3e
 [<c01008f8>] cpu_idle+0x63/0x91
 =======================
handlers:
[<c02a6eaa>] (nv_adma_interrupt+0x0/0x294)
Disabling IRQ #5
ata3.00: qc timeout (cmd 0x27)
ata3.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (976773168)
ata3.00: ATA-7: WDC WD5000AAKS-00TMA0, 12.01C01, max UDMA/133
ata3.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32)
ata3.00: failed to set xfermode (err_mask=0x40)
ata3: failed to recover some devices, retrying in 5 secs
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0x27)
ata3.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (976773168)
ata3.00: failed to set xfermode (err_mask=0x40)
ata3: limiting SATA link speed to 1.5 Gbps
ata3.00: limiting speed to UDMA/133:PIO3
ata3: failed to recover some devices, retrying in 5 secs
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3.00: qc timeout (cmd 0x27)
ata3.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (976773168)
ata3.00: failed to set xfermode (err_mask=0x40)
ata3.00: disabled
ata3: EH pending after completion, repeating EH (cnt=4)
ata3: soft resetting port
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3: EH complete
ata4: SATA link down (SStatus 0 SControl 300)
Included, for the sake of further insight, is my /proc/interrupts:

Code:
           CPU0       CPU1
  0:        350          1   IO-APIC-edge      timer
  1:          0          2   IO-APIC-edge      i8042
  2:          0          0    XT-PIC-XT        cascade
  3:       6630    9719991   IO-APIC-fasteoi   ohci_hcd:usb2, eth0
  5:         26      99975   IO-APIC-fasteoi   sata_nv, ehci_hcd:usb1
  8:          0          1   IO-APIC-edge      rtc
 11:         69      96125   IO-APIC-fasteoi   sata_nv, NVidia CK804
 12:          0          4   IO-APIC-edge      i8042
 14:         90      97439   IO-APIC-edge      ide0
 15:        197     245897   IO-APIC-edge      ide1
NMI:          0          0
LOC:   82134010   82133851
ERR:          1
MIS:          0
Any insight to this would obviously be appreciated. I'm fairly confident it's nothing in my configuration: besides the fact that it looks right to me when I check it out, it seems like the kernel is detecting things properly.
 
Old 12-21-2007, 10:11 PM   #2
guzzi
Member
 
Registered: Jun 2004
Location: Lawrence, KS
Distribution: Slackware
Posts: 313

Rep: Reputation: 40
2.6.23.12

Well Pommpie after seeing your post I just had to try it myself.

Downloaded a 2.6.23.12 from kernel.org and used my .config from a 2.6.23.9 kernel build, and all is well. This causes me to think that it's not the current kernel causing the problem, but more likely the config you created.

Getting the config right for the 2.6.23.9 took more work than any I have done prior. There are a lot more options in the kernel now, and a lot more to read.

Good luck
 
Old 12-21-2007, 10:37 PM   #3
duryodhan
Senior Member
 
Registered: Oct 2006
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
Posts: 1,054

Rep: Reputation: 46
it IS something in your configuration!
read the linux kernel in a nutshell book by Greg Kroah Hartmann (available free online) on what all you need to include to make SATA work...
 
Old 12-21-2007, 11:43 PM   #4
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
Not necessarily:
Code:
5:         26      99975   IO-APIC-fasteoi   sata_nv, ehci_hcd:usb1
The IRQ is shared between sata and usb controllers. It may cause conflicts.
Can you try to assign different IRQs at bios. What if you boot with irqpoll kernel option as suggested?
 
Old 12-22-2007, 12:56 AM   #5
Pommpie
LQ Newbie
 
Registered: Oct 2006
Posts: 13

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Alien_Hominid View Post
Not necessarily:
Code:
5:         26      99975   IO-APIC-fasteoi   sata_nv, ehci_hcd:usb1
The IRQ is shared between sata and usb controllers. It may cause conflicts.
Can you try to assign different IRQs at bios. What if you boot with irqpoll kernel option as suggested?
Cough.

I thought I had tried that, but I couldn't remember what had happened. So I tried it again and... it worked perfectly.

So. Thanks for... correcting my stupidity! That's what I get for compiling kernels at six in the morning.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem going from kernel version 2.4 to 2.6 - SATA related? Elbaron Debian 0 08-17-2005 04:42 AM
2.4.28 Debian Kernel SATA Problem topace Linux - General 2 02-24-2005 09:45 AM
Can somebody please solve my SATA problem?(kernel 2.6) Bultot Linux - Hardware 13 02-15-2005 04:06 PM
SATA problem with kernel 2.6.9 Zolex Debian 6 11-15-2004 05:46 AM
2.6.8-gentoo-r3 Kernel Sata Problem blackphiber Linux - General 2 09-27-2004 06:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration