I'm currently running 2.6.9-r14 with three 250 GB Maxtor SATA drives - two on an onboard nforce controller, one on an onboard Marvell 88SR3020 SATA PHY controller. Everything works in the configuration. However, I've tried to upgrade my kernel several times to various releases of 2.6.10 and 2.6.11. Each time, on my first (and all subsequent) boots, the system pauses indefinitely when trying to bring the third disk (the one on the marvell) online. Reproducible: Always Steps to Reproduce: 1. Build a kernel 2.6.10+ 2. Boot new kernel 3. Actual Results: The system pauses indefinitely when trying to bring the third disk (the one on the marvell) online Expected Results: Brought the third disk online and continued booting. My machine is an AMD 64 3800+.
How long have you tried leaving it? Does caps lock / ctrl+alt+del respond when the machine is frozen? Is the system booting from the marvell disk or from one of the others?
I've tried leaving it for 10-15 minutes, with no change. I've tried ctrl-alt-del but nothing happens. The system is not booting from the marvell disk, it's booting for another regular IDE disk.
Does caps lock respond when the machine is frozen? What happens if you build the marvell support as a module, and load the module after bootup has completed. Does the freeze occur then?
I've looked through the kernel config menus and can't find an option for including/excluding/compiling-as-module support for the marvell controller. What would it be called?
Please post "lspci" and "lspci -n" output
lspci: 0000:00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 0000:00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 0000:00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 0000:00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 0000:00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 0000:00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 0000:00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2) 0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 0000:00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 0000:00:09.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 0000:00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2) 0000:00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 0000:00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 0000:01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2) 0000:02:06.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 0000:02:07.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 0000:02:08.0 Multimedia video controller: Conexant CX22702 DVB-T 2k/8k (rev 05) 0000:02:08.2 Multimedia controller: Conexant CX23883 Broadcast Decoder (rev 05) 0000:02:09.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) lspci -n: 0000:00:00.0 Class 0600: 10de:00e1 (rev a1) 0000:00:01.0 Class 0601: 10de:00e0 (rev a2) 0000:00:01.1 Class 0c05: 10de:00e4 (rev a1) 0000:00:02.0 Class 0c03: 10de:00e7 (rev a1) 0000:00:02.1 Class 0c03: 10de:00e7 (rev a1) 0000:00:02.2 Class 0c03: 10de:00e8 (rev a2) 0000:00:05.0 Class 0680: 10de:00df (rev a2) 0000:00:06.0 Class 0401: 10de:00ea (rev a1) 0000:00:08.0 Class 0101: 10de:00e5 (rev a2) 0000:00:09.0 Class 0101: 10de:00ee (rev a2) 0000:00:0a.0 Class 0101: 10de:00e3 (rev a2) 0000:00:0b.0 Class 0604: 10de:00e2 (rev a2) 0000:00:0e.0 Class 0604: 10de:00ed (rev a2) 0000:00:18.0 Class 0600: 1022:1100 0000:00:18.1 Class 0600: 1022:1101 0000:00:18.2 Class 0600: 1022:1102 0000:00:18.3 Class 0600: 1022:1103 0000:01:00.0 Class 0300: 10de:00f1 (rev a2) 0000:02:06.0 Class 0c00: 1106:3044 (rev 80) 0000:02:07.0 Class 0401: 13f6:0111 (rev 10) 0000:02:08.0 Class 0400: 14f1:8800 (rev 05) 0000:02:08.2 Class 0480: 14f1:8802 (rev 05) 0000:02:09.0 Class 0400: 4444:0803 (rev 01)
Are you sure you have marvell hardware? Do you use a PCI SATA card, or are you using the SATA connectors included on your motherboard?
I was using/trying to use the onboard sata ports 1,2 and 3 - leaving 4 empty. This post seems to indicate that 3/4 are marvell: http://forums.hexus.net/showthread.php?p=341643 It also seems to indicate that they are meant to be external phy which further reasearch indicates means they ar meant to be used to provide external sata ports. Not sure if my using them internally is causing the issue with 2.6.10+.
I assume you have the following already selected: Device Drivers ---> SCSI device support ---> SCSI low-level drivers ---> [*] Serial ATA (SATA) support <*> NVIDIA SATA support You could try building it as a module and loading it sometime after bootup, to see if the nvidia sata module is causing the freeze. It does look like you are supposed to have external hardware for ports 3+4.
I do have that selected. When I boot 2.6.9, here is what the log shows: May 15 14:57:50 tibeaux kernel: 3w-xxxx: No cards found. May 15 14:57:50 tibeaux kernel: ata1: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xCC00 irq 5 May 15 14:57:50 tibeaux kernel: ata2: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xCC08 irq 5 May 15 14:57:50 tibeaux kernel: ata1: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48 May 15 14:57:50 tibeaux kernel: ata1: dev 0 configured for UDMA/133 May 15 14:57:50 tibeaux kernel: scsi0 : sata_nv May 15 14:57:50 tibeaux kernel: ata2: no device found (phy stat 00000000) May 15 14:57:50 tibeaux kernel: scsi1 : sata_nv May 15 14:57:50 tibeaux kernel: Vendor: ATA Model: Maxtor 6Y250M0 Rev: YAR5 May 15 14:57:50 tibeaux kernel: Type: Direct-Access ANSI SCSI revision: 05 May 15 14:57:50 tibeaux kernel: ata3: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE400 irq 11 May 15 14:57:50 tibeaux kernel: ata4: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE408 irq 11 May 15 14:57:50 tibeaux kernel: ata3: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48 May 15 14:57:50 tibeaux kernel: ata3: dev 0 configured for UDMA/133 May 15 14:57:50 tibeaux kernel: scsi2 : sata_nv May 15 14:57:50 tibeaux kernel: ata4: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48 May 15 14:57:50 tibeaux kernel: ata4: dev 0 configured for UDMA/133 May 15 14:57:50 tibeaux kernel: scsi3 : sata_nv May 15 14:57:50 tibeaux kernel: Vendor: ATA Model: Maxtor 6Y250M0 Rev: YAR5 May 15 14:57:50 tibeaux kernel: Type: Direct-Access ANSI SCSI revision: 05 May 15 14:57:50 tibeaux kernel: Vendor: ATA Model: Maxtor 6Y250M0 Rev: YAR5 May 15 14:57:50 tibeaux kernel: Type: Direct-Access ANSI SCSI revision: 05 Now, the logs don't exactly match the boot output, but I think it freezes on other kernels somewhere around: May 15 14:57:50 tibeaux kernel: ata3: dev 0 configured for UDMA/133 Also, FWIW, I tried booting the new kernel several times, each time unplugging one drive to see that made a difference. It didn't.
Ok, I recompiled the 2.6.12 kernel with sata_nv as a module. It boots all the way. Then, when I modprobe sata_nv it just goes and goes, never finishing.
Ok.. You should now be in a position to capture the "dmesg" output once you have tried loading sata_nv ... Can you attach it here please?
Ok, here it is: libata version 1.10 loaded. sata_nv version 0.6 PCI: Setting latency timer of device 0000:00:09.0 to 64 ata1: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xCC00 irq 11 ata2: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xCC08 irq 11 ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c48 86:3e01 87:4003 88:407f ata1: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48 FWIW, this is what I did: -Boot 2.6.12-rc3 -login as root -alt-f2 to new term win -dmesg to find last line -alt-f1 back -modprobe sata_nv -alt-f2 back -dmesg | tail -n 20 > dmesg.txt I gave you all the lines after "modprobe sata_nv". The first term window just sat there. No messages.
Ok, and I'm right in saying that if you have *any* disk connected to *any* port of the SATA controllers (i.e. even with one disk connected to the first onboard port), the sata_nv module fails to load in this way?
Correct.
Close this. I've re-installed Gentoo and chose vanilla-sources 2.6.12-rc4 and all is working.
