Bug 1009 - (ide sii) Startup hangs with SiI 3112 driver compiled in for some time
Summary: (ide sii) Startup hangs with SiI 3112 driver compiled in for some time
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: IDE (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Bartlomiej Zolnierkiewicz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-28 23:32 UTC by Felix Seeger
Modified: 2006-04-15 02:06 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.0-test2
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Felix Seeger 2003-07-28 23:32:39 UTC 
Distribution: Debian unstable 
Hardware Environment: Asus A7N8X Deluxe (Nforce2) with SiI 3112 
Software Environment: plain 2.6.0-test2, gcc 3.3.1 
Problem Description: 
The driver for my SATA chip need some minutes at bootup because I don't have any devices 
connected to it. It probes for disks with an timeout 3 times per disk (if I am right) 
It takes way to long to startup with an SiI 3112 driver enabled kernel, but without disks 
connected to it. 
 
Steps to reproduce: 
Build the SiI 3112 driver into the kernel 
Remove both disks from the controller 
Startup and wait
Comment 1 davide.fanciola 2003-12-01 02:53:17 UTC 
Hello,

on the same hardware I'm having the same problems...

but I managed to have a nice startup passing this params to the kernel at boot :

ide3=0 ide4=0 ide5=0 ide6=0 ide7=0 ide8=0 ide9=0

I had to go til ide9, since the controller was taking the first ide channel free.
Comment 2 Jeff Garzik 2004-01-30 17:54:12 UTC 
Just to confirm... this is CONFIG_BLK_DEV_SIIMAGE and not CONFIG_SCSI_SATA_SIL,
correct?
Comment 3 Felix Seeger 2004-02-04 23:14:52 UTC 
Yes, I think so
Comment 4 Dominik Brodowski 2005-11-16 14:24:15 UTC 
Is this still a problem with, let's say, 2.6.14?
Comment 5 Adrian Bunk 2006-04-15 02:06:24 UTC 
I'm assuming this issue is already fixed in recent 2.6 kernels.

Please reopen this bug if it's still present in kernel 2.6.16.5.
Note You need to log in before you can comment on or make changes to this bug.