IDE warning: "Wait for ready failed before probe!"

IDE warning: "Wait for ready failed before probe!"

[Alan Jenkins]

I have no problems (I hope!), but the warnings I get when linux (2.6.9) 
tries to probe a non existant IDE device (controller/channel (?) not  
hard disk) are slightly over the top..

1. Are these warnings usual for a nonexistant IDE drive?
2. Could they be toned down?

Exclamation marks might be appropriate if after the SIS ide controller  
had been detected one of its channels (ide0/1) could not be probed, but  
unless my hardware is not reacting as expected they are just "noise".

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with  
idebus=xx
SIS5513: IDE controller at PCI slot 0000:00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: WDC WD1200BB-00DWA0, ATA DISK drive
hdb: LITE-ON COMBO SOHC-5232K, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
hda: max request size: 1024KiB
hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,  
UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3 hda4

Re: IDE warning: "Wait for ready failed before probe!"

[Kurt Wall]

On Sat, Oct 23, 2004 at 08:47:33PM +0000, Alan Jenkins took 46 lines to write:
> I have no problems (I hope!), but the warnings I get when linux (2.6.9) 
> tries to probe a non existant IDE device (controller/channel (?) not  
> hard disk) are slightly over the top..
> 
> 1. Are these warnings usual for a nonexistant IDE drive?
> 2. Could they be toned down?

Disable CONFIG_IDE_GENERIC
- or -
Use the ideX=noprobe boot parm, replacing X with the interface number
not to probe.

Kurt
-- 
A lack of leadership is no substitute for inaction.

Re: IDE warning: "Wait for ready failed before probe!"

[Nick Warne]

>> 1. Are these warnings usual for a nonexistant IDE drive?
>> 2. Could they be toned down?

> Disable CONFIG_IDE_GENERIC
> - or -
> Use the ideX=noprobe boot parm, replacing X with the interface number
> not to probe.

> Kurt

I started to get these messages in logs since building 2.6.9, and a google 
reveals this from Alan Cox:

http://www.redhat.com/archives/fedora-test-list/2004-September/msg00300.html

So, will these be turned off, or do we have to follow above instructions?

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

Re: IDE warning: "Wait for ready failed before probe!"

[Bartlomiej Zolnierkiewicz]

On Sun, 24 Oct 2004 13:43:50 +0100, Nick Warne <nick@linicks.net> wrote:
> >> 1. Are these warnings usual for a nonexistant IDE drive?
> >> 2. Could they be toned down?
> 
> > Disable CONFIG_IDE_GENERIC
> > - or -
> > Use the ideX=noprobe boot parm, replacing X with the interface number
> > not to probe.
> 
> > Kurt
> 
> I started to get these messages in logs since building 2.6.9, and a google
> reveals this from Alan Cox:
> 
> http://www.redhat.com/archives/fedora-test-list/2004-September/msg00300.html
> 
> So, will these be turned off, or do we have to follow above instructions?

Send a patch and it will be turned off (printks should be replaced by
pr_debugs). :)

It is still a good thing to disable ide-generic if it is not needed
(faster boot).

IDE warning: "Wait for ready failed before probe!"

[Alan Jenkins]

I have no problems (I hope!), but the warnings I get when linux (2.6.9) 
tries to probe a non existant IDE device (controller/channel (?) not  
hard disk) are slightly over the top..

1. Are these warnings usual for a nonexistant IDE drive?
2. Could they be toned down?

Exclamation marks might be appropriate if after the SIS ide controller  
had been detected one of its channels (ide0/1) could not be probed, but  
unless my hardware is not reacting as expected they are just "noise".

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with  
idebus=xx
SIS5513: IDE controller at PCI slot 0000:00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
   ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
   ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: WDC WD1200BB-00DWA0, ATA DISK drive
hdb: LITE-ON COMBO SOHC-5232K, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
hda: max request size: 1024KiB
hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,  
UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4

IDE warning: "Wait for ready failed before probe!"

[Nick Warne]

Strangely, or even twilight zone stuff, I am building right now and will boot 
new kernel with the CONFIG_IDE_GENERIC = n - this fixes it reportedly.  Only 
warnings anyway, but I think we all like *clean* boots.

A couple of mails with Bartlomiej assured me that it isn't required on 
modern(ish) machines that have PCI (in theory), so do not need that option.

That will stop the probe, and the post from Alan re the Redhat thread suggests 
it is a debug warning anyway that maybe was never removed.

Nick

-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

IDE warning: "Wait for ready failed before probe!"

[Nick Warne]

> A couple of mails with Bartlomiej assured me that it isn't required on 
> modern(ish) machines that have PCI (in theory), so do not need that option.

> That will stop the probe, and the post from Alan re the Redhat thread
> suggests it is a debug warning anyway that maybe was never 
> removed.

*Reboot*

Also I forgot, Bartlomiej said machine would reboot faster.  *Wow* does it 
ever \o/

ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c586a (rev 27) IDE UDMA33 controller on pci0000:00:07.1
    ide0: BM-DMA at 0x6000-0x6007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x6008-0x600f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: QUANTUM FIREBALL CR8.4A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ATAPI CDROM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 16514064 sectors (8455 MB) w/418KiB Cache, CHS=16383/16/63, UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2 hda3
hdc: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20

No probes on wonky legacy stuff, all works :) :).

I really think the kconfig help on the CONFIG_IDE_GENERIC needs updating 
instead of the 'if unsure say Y'.  I would submit a patch, but I don't really 
know what the hell I am talking about on this subject.

Thanks Bartlomiej :)

Nick

-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

Re: IDE warning: "Wait for ready failed before probe!"

[Alan Cox]

On Maw, 2004-10-26 at 20:35, Alan Jenkins wrote:
> I have no problems (I hope!), but the warnings I get when linux (2.6.9) 
> tries to probe a non existant IDE device (controller/channel (?) not  
> hard disk) are slightly over the top..

They are KERN_DEBUG, and they can probably just go away now.