Hi,
since at least kernel 2.6.9 I'm having a problem booting linux - it hangs
after this
Probing IDE interface ide0...
hda: HITACHI_DK23DA-30, ATA DISK drive
elevator: using anticipatory as default io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: TOSHIBA DVD-ROM SD-R2212, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
After about 30 seconds everything continues fine with
hda: max request size: 128KiB
I found additional lines in the log just before the line above:
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
But I only have ide0 and ide1. This problem persists even with 2.6.11-rc2. For
the last test I removed every option from the kernel that is not needed, but
the problem stays. So I'm sure it's not because of ACPI or PNP or the like.
With 2.6.11-rc2 I get in my syslog:
Feb 1 11:30:02 newton kernel: ICH3M: chipset revision 2
Feb 1 11:30:02 newton kernel: ICH3M: not 100%% native mode: will probe irqs
later
Feb 1 11:30:02 newton kernel: ide0: BM-DMA at 0xcfa0-0xcfa7, BIOS
settings: hda:DMA, hdb:pio
Feb 1 11:30:02 newton kernel: ide1: BM-DMA at 0xcfa8-0xcfaf, BIOS
settings: hdc:DMA, hdd:pio
Feb 1 11:30:02 newton kernel: Probing IDE interface ide0...
Feb 1 11:30:02 newton kernel: hda: HITACHI_DK23DA-30, ATA DISK drive
Feb 1 11:30:02 newton kernel: DEV: registering device: ID = 'ide0'
Feb 1 11:30:02 newton kernel: PM: Adding info for No Bus:ide0
Feb 1 11:30:02 newton kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 1 11:30:02 newton kernel: DEV: registering device: ID = '0.0'
Feb 1 11:30:02 newton kernel: PM: Adding info for ide:0.0
Feb 1 11:30:02 newton kernel: bus ide: add device 0.0
Feb 1 11:30:02 newton kernel: Probing IDE interface ide1...
Feb 1 11:30:02 newton kernel: hdc: TOSHIBA DVD-ROM SD-R2212, ATAPI CD/DVD-ROM
drive
Feb 1 11:30:02 newton kernel: DEV: registering device: ID = 'ide1'
Feb 1 11:30:02 newton kernel: PM: Adding info for No Bus:ide1
Feb 1 11:30:02 newton kernel: ide1 at 0x170-0x177,0x376 on irq 15
Feb 1 11:30:02 newton kernel: DEV: registering device: ID = '1.0'
Feb 1 11:30:02 newton kernel: PM: Adding info for ide:1.0
Feb 1 11:30:02 newton kernel: bus ide: add device 1.0
Feb 1 11:30:02 newton kernel: bus pci: add driver PIIX_IDE
Feb 1 11:30:02 newton kernel: bound device '0000:00:1f.1' to driver
'PIIX_IDE'
Feb 1 11:30:02 newton kernel: bus pci: add driver PCI_IDE
Feb 1 11:30:02 newton kernel: Probing IDE interface ide2...
Feb 1 11:30:02 newton kernel: Probing IDE interface ide3...
Feb 1 11:30:02 newton kernel: Probing IDE interface ide4...
Feb 1 11:30:02 newton kernel: ide4: Wait for ready failed before probe !
---> I guess the line above is the reason for the wait <---
Feb 1 11:30:02 newton kernel: Probing IDE interface ide5...
Feb 1 11:30:02 newton kernel: hda: max request size: 128KiB
Userspace is debian sid, my computer is a Toshiba Laptop (Satellite 2410-404),
you can find some information including an lspci on
http://www.thorstenhaas.de/toshiba2410/. Attached's my kernel config.
Please CC me, I'm not subscribed, thanks.
Cheers,
--
Michael Brade; KDE Developer, Student of Computer Science
|-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
?--web: http://www.kde.org/people/michaelb.html
KDE 3: The Next Generation in Desktop Experience
On Tue, 01 Feb 2005 12:57:33 +0100, Michael Brade wrote:
> Hi,
>
> since at least kernel 2.6.9 I'm having a problem booting linux - it hangs
> after this
>
> Probing IDE interface ide0...
> hda: HITACHI_DK23DA-30, ATA DISK drive
> elevator: using anticipatory as default io scheduler
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Probing IDE interface ide1...
> hdc: TOSHIBA DVD-ROM SD-R2212, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
>
> After about 30 seconds everything continues fine with
>
> hda: max request size: 128KiB
>
> I found additional lines in the log just before the line above:
Same here on 2.6.11-rc2-bk3 using a *Toshiba* Satellite Pro A10.
messages can be found here:
http://hughsie.no-ip.com/write/kernel/messages
please ask if you need any more info.
Richard Hughes
On Tue, 2005-02-01 at 20:22 +0000, Richard Hughes wrote:
> On Tue, 01 Feb 2005 12:57:33 +0100, Michael Brade wrote:
>
> > Hi,
> >
> > since at least kernel 2.6.9 I'm having a problem booting linux - it hangs
> > after this
> >
> > Probing IDE interface ide0...
> > hda: HITACHI_DK23DA-30, ATA DISK drive
> > elevator: using anticipatory as default io scheduler
> > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > Probing IDE interface ide1...
> > hdc: TOSHIBA DVD-ROM SD-R2212, ATAPI CD/DVD-ROM drive
> > ide1 at 0x170-0x177,0x376 on irq 15
> >
> > After about 30 seconds everything continues fine with
> >
> > hda: max request size: 128KiB
> >
> > I found additional lines in the log just before the line above:
>
> Same here on 2.6.11-rc2-bk3 using a *Toshiba* Satellite Pro A10.
>
> messages can be found here:
>
> http://hughsie.no-ip.com/write/kernel/messages
This looks like bogus HW, or bogus list of IDE interfaces ...
The IDE layer waits up to 30 seconds for a device to drop it's busy bit,
which is necessary for some drives that aren't fully initialized yet.
I suspect in your case, it's reading "ff", which indicates either that
there is no hardware where the kernel tries to probe, or that there is
bogus IDE interfaces which don't properly have the D7 line pulled low so
that BUSY appears not set in absence of a drive.
I'm not sure how the list of intefaces is probed on this machine, that's
probably where the problem is.
Ben.
Benjamin Herrenschmidt <benh <at> kernel.crashing.org> writes:
> This looks like bogus HW, or bogus list of IDE interfaces ...
How can I test to see if this is the case?
>
> The IDE layer waits up to 30 seconds for a device to drop it's busy bit,
> which is necessary for some drives that aren't fully initialized yet.
Sure, make sense.
> I suspect in your case, it's reading "ff", which indicates either that
> there is no hardware where the kernel tries to probe, or that there is
> bogus IDE interfaces which don't properly have the D7 line pulled low so
> that BUSY appears not set in absence of a drive.
Right. How do I find the value of D7?
> I'm not sure how the list of intefaces is probed on this machine, that's
> probably where the problem is.
Thanks, Richard Hughes
Richard Hughes wrote:
> Benjamin Herrenschmidt <benh <at> kernel.crashing.org> writes:
>
>>This looks like bogus HW, or bogus list of IDE interfaces ...
>
>
> How can I test to see if this is the case?
>
>
>>The IDE layer waits up to 30 seconds for a device to drop it's busy bit,
>>which is necessary for some drives that aren't fully initialized yet.
>
>
> Sure, make sense.
>
>
>>I suspect in your case, it's reading "ff", which indicates either that
>>there is no hardware where the kernel tries to probe, or that there is
>>bogus IDE interfaces which don't properly have the D7 line pulled low so
>>that BUSY appears not set in absence of a drive.
>
>
> Right. How do I find the value of D7?
>
>
>>I'm not sure how the list of intefaces is probed on this machine, that's
>>probably where the problem is.
I've read that people have had this problem go away if they disable this
option:
< > generic/default IDE chipset support
If you have chipset support for your IDE controller this isn't needed,
and I'd recommend disabling it. The "why" it made the problem go away is
something I can't answer.
Cheers,
Con
Con Kolivas <kernel <at> kolivas.org> writes:
> >>I'm not sure how the list of intefaces is probed on this machine, that's
> >>probably where the problem is.
>
> I've read that people have had this problem go away if they disable this
> option:
>
> < > generic/default IDE chipset support
Okay I'll try this tonight. I'm running a stock Fedora kernel at the moment
(rawhide) so this issue might affect more people than we think.
> If you have chipset support for your IDE controller this isn't needed,
> and I'd recommend disabling it. The "why" it made the problem go away is
> something I can't answer.
Richard.
Hi,
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of Michael Brade
>Sent: Tuesday, February 01, 2005 3:58 AM
>To: [email protected]
>Subject: Linux hangs during IDE initialization at boot for 30 sec
>
[snip]
>
>I found additional lines in the log just before the line above:
>
>Probing IDE interface ide2...
>Probing IDE interface ide3...
>Probing IDE interface ide4...
>Probing IDE interface ide5...
>
>But I only have ide0 and ide1. This problem persists even with
>2.6.11-rc2. For
>the last test I removed every option from the kernel that is
>not needed, but
>the problem stays. So I'm sure it's not because of ACPI or PNP
>or the like.
>
>With 2.6.11-rc2 I get in my syslog:
>
>Feb 1 11:30:02 newton kernel: ICH3M: chipset revision 2
>Feb 1 11:30:02 newton kernel: ICH3M: not 100%% native mode:
>will probe irqs
>later
>Feb 1 11:30:02 newton kernel: ide0: BM-DMA at 0xcfa0-0xcfa7, BIOS
>settings: hda:DMA, hdb:pio
>Feb 1 11:30:02 newton kernel: ide1: BM-DMA at 0xcfa8-0xcfaf, BIOS
>settings: hdc:DMA, hdd:pio
>Feb 1 11:30:02 newton kernel: Probing IDE interface ide0...
>Feb 1 11:30:02 newton kernel: hda: HITACHI_DK23DA-30, ATA DISK drive
>Feb 1 11:30:02 newton kernel: DEV: registering device: ID = 'ide0'
>Feb 1 11:30:02 newton kernel: PM: Adding info for No Bus:ide0
>Feb 1 11:30:02 newton kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>Feb 1 11:30:02 newton kernel: DEV: registering device: ID = '0.0'
>Feb 1 11:30:02 newton kernel: PM: Adding info for ide:0.0
>Feb 1 11:30:02 newton kernel: bus ide: add device 0.0
>Feb 1 11:30:02 newton kernel: Probing IDE interface ide1...
>Feb 1 11:30:02 newton kernel: hdc: TOSHIBA DVD-ROM SD-R2212,
>ATAPI CD/DVD-ROM
>drive
>Feb 1 11:30:02 newton kernel: DEV: registering device: ID = 'ide1'
>Feb 1 11:30:02 newton kernel: PM: Adding info for No Bus:ide1
>Feb 1 11:30:02 newton kernel: ide1 at 0x170-0x177,0x376 on irq 15
>Feb 1 11:30:02 newton kernel: DEV: registering device: ID = '1.0'
>Feb 1 11:30:02 newton kernel: PM: Adding info for ide:1.0
>Feb 1 11:30:02 newton kernel: bus ide: add device 1.0
>Feb 1 11:30:02 newton kernel: bus pci: add driver PIIX_IDE
>Feb 1 11:30:02 newton kernel: bound device '0000:00:1f.1' to driver
>'PIIX_IDE'
>Feb 1 11:30:02 newton kernel: bus pci: add driver PCI_IDE
>Feb 1 11:30:02 newton kernel: Probing IDE interface ide2...
>Feb 1 11:30:02 newton kernel: Probing IDE interface ide3...
>Feb 1 11:30:02 newton kernel: Probing IDE interface ide4...
>Feb 1 11:30:02 newton kernel: ide4: Wait for ready failed
>before probe !
>---> I guess the line above is the reason for the wait <---
>Feb 1 11:30:02 newton kernel: Probing IDE interface ide5...
>Feb 1 11:30:02 newton kernel: hda: max request size: 128KiB
>
Since you don't care about anything except ide0 & ide1, try to add
the following to the kernel's command line:
ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
Aleks.
>-----Original Message-----
>From: Michael Brade [mailto:[email protected]]
>Sent: Wednesday, February 02, 2005 11:55 AM
>To: Aleksey Gorelov
>Subject: Re: Linux hangs during IDE initialization at boot for 30 sec
>
>Hi,
>
>> Since you don't care about anything except ide0 & ide1, try to add
>> the following to the kernel's command line:
>> ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
>Awesome! Thanks, booting is finally acceptably fast again :-)
>Just strange
>that it worked for the last 3 years (in fact, 7 years) with
>just about every
>kernel version that's out there... but I'm happy with the workaround.
>
Was it exact same hardware ?
>Cheers,
>--
>Michael Brade; KDE Developer, Student of
>Computer Science
> |-mail: echo brade !#|tr -d "c oh"|s\e\d
>'s/e/\@/2;s/$/.org/;s/bra/k/2'
> ?--web: http://www.kde.org/people/michaelb.html
>
>KDE 3: The Next Generation in Desktop Experience
>
On Wednesday 02 February 2005 21:01, you wrote:
> >Awesome! Thanks, booting is finally acceptably fast again :-)
> >Just strange
> >that it worked for the last 3 years (in fact, 7 years) with
> >just about every
> >kernel version that's out there... but I'm happy with the workaround.
>
> Was it exact same hardware ?
Yes, absolutely.
cheers,
--
Michael Brade; KDE Developer, Student of Computer Science
|-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
?--web: http://www.kde.org/people/michaelb.html
KDE 3: The Next Generation in Desktop Experience
On Maw, 2005-02-01 at 23:18, Benjamin Herrenschmidt wrote:
> On Tue, 2005-02-01 at 20:22 +0000, Richard Hughes wrote:
> > On Tue, 01 Feb 2005 12:57:33 +0100, Michael Brade wrote:
> I suspect in your case, it's reading "ff", which indicates either that
> there is no hardware where the kernel tries to probe, or that there is
> bogus IDE interfaces which don't properly have the D7 line pulled low so
> that BUSY appears not set in absence of a drive.
>
> I'm not sure how the list of intefaces is probed on this machine, that's
> probably where the problem is.
Known, fixed
There is a patch that allows probing for ISA ide4,5,6 etc only if there
is
no PCI bus