Created attachment 22887 [details] dmesg When I boot My Fujitsu-Siemens P5SD1-FM2 with an Silicon Integrated Systems [SiS] 182 SATA/RAID Controller the boot process hangs for about 2-3 minutes
these people have the same problem: http://ubuntuforums.org/archive/index.php/t-1144924.html
could you try disabling the not connected sata port in the bios to see if this makes a difference ?
I can't find such option in the BIOS
Created attachment 22920 [details] classify-debug.patch Interesting... Can you please do the followings? 1. Apply the attached patch and report the boot log. 2. Attach the output of "lspci -nn" and "dmidecode". Thanks.
Created attachment 22923 [details] dmesg (with patch)
Created attachment 22924 [details] lspci -nn
Created attachment 22925 [details] dmidecode
Created attachment 22927 [details] classify-debug-1.patch Hmmm.... classification is working okay. Strange it's still failing. Can you please try this patch and report the log? Thanks.
Created attachment 22928 [details] dmesg
Created attachment 22929 [details] classify-debug-2.patch Hmmmm.... still. Can you please this? Thanks.
Created attachment 22930 [details] dmesg
Okay, I finally understood it. The problem is that sata_sis is using regular SCR handling ops while setting ATA_FLAG_SLAVE_POSS for SiS 182/965 controller. This tells libata core layer that the port can have a slave device. As sata_sis doesn't implement proper slave link, if the master link is online, the link slave device is supposed to be on seems online too which makes libata core layer believe that the driver failed to classify the present device on the slave link and retry. Heh... it's a bit convoluted. Ah.. okay, it's using the now obsolete (and broken) trick of combining SCR values in scr callbacks instead of using the slave mechanism. I'll see if I can fix this. Please standby a bit. Thanks.
Created attachment 22939 [details] sis-slave_link.patch Can you please try the attached patch and report the boot log? Thanks.
Created attachment 22949 [details] Simple Screenshot (kernel panic) I think it don't recognize any SATA drive with this patch?
Yeap, that's entirely possible. Can you please capture the failing log? This can be done by... 1. Using a small root fs on a usb stick or a drive attached to a different controller. 2. Setting up a serial console (Documentation/serial-console.txt) 3. Setting up a netconsole (Documentation/networking/netconsole.txt) Thanks.
Created attachment 22951 [details] dmesg (from kernel panic)
Created attachment 22953 [details] sis-slave_link-1.patch Can you please try this? Thanks.
Created attachment 22954 [details] dmesg Great Work! Thanks a lot!
Patch posted upstream. Resolving as FIXED. Thanks.
Resolving...