linux-kernel - hda=none hda=noprobe is ignored by <=2.6.15-26

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <3df49b7b0608041529k274c3c38labe52259cee555db@mail.gmail.com>
Date:	Sat, 5 Aug 2006 00:29:59 +0200
From:	koko <citizenr@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	citizenr@...il.com
Subject: hda=none hda=noprobe is ignored by <=2.6.15-26

First some old Ignored(sadly) links to the same bug :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132708
http://lkml.org/lkml/2003/6/16/29
http://www.gatago.com/linux/kernel/6116284.html

This bug is ASUS VIA MB specific. Asus A7V133, hda hdb empty.

>>From Alan Cox (alan@...hat.com) 	on 2005-04-07 04:41 EST	[reply]	 	
>BIOS problem I believe not kernel. We only probe hda/hdb because the BIOS
>claims the slot may have a drive on it.

So why kernel probes IDE channel I just ordered him to IGNORE?

[snip]
[17179569.184000] Kernel command line: root=/dev/hdc3 ro quiet splash
hda=noprobe hdb=noprobe
[17179569.184000] ide_setup: hda=noprobe
[17179569.184000] ide_setup: hdb=noprobe
[snip]
[17179573.696000] VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100
controller on pci0000:00:04.1
[17179573.696000]     ide0: BM-DMA at 0xd800-0xd807, BIOS settings:
hda:pio, hdb:pio
[17179573.696000]     ide1: BM-DMA at 0xd808-0xd80f, BIOS settings:
hdc:DMA, hdd:pio
[17179573.696000] Probing IDE interface ide0...
[snip]
 Here we go, and ....
[snip]
[17179577.060000] Probing IDE interface ide0...
[17179611.848000] ide0: Wait for ready failed before probe !
[snip]

almost a minute here :/

Heres how it looks without noprobe :
[17179572.788000] VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100
controller on pci0000:00:04.1
[17179572.788000]     ide0: BM-DMA at 0xd800-0xd807, BIOS settings:
hda:pio, hdb:pio
[17179572.788000]     ide1: BM-DMA at 0xd808-0xd80f, BIOS settings:
hdc:DMA, hdd:pio
[17179572.788000] Probing IDE interface ide0...
[17179578.248000] hda: IRQ probe failed (0xfffffcf8)
[17179583.472000] hda: IRQ probe failed (0xfffffcf8)
[17179583.472000] hda: no response (status = 0x0a), resetting drive
[17179588.808000] hda: IRQ probe failed (0xfffffcf8)
[17179588.808000] hda: no response (status = 0x0a)
[17179594.312000] hdb: IRQ probe failed (0xfffffcf8)
[17179599.536000] hdb: IRQ probe failed (0xfffffcf8)
[17179599.536000] hdb: no response (status = 0x0a), resetting drive
[17179604.872000] hdb: IRQ probe failed (0xfffffcf8)
[17179604.872000] hdb: no response (status = 0x0a)
[17179604.928000] Probing IDE interface ide1...
[snip]
[17179608.240000] Probing IDE interface ide0...
[17179643.028000] ide0: Wait for ready failed before probe !
[17179648.476000] hda: IRQ probe failed (0xffff7cf0)
[17179653.700000] hda: IRQ probe failed (0xffff7cf0)
[17179653.700000] hda: no response (status = 0x0a), resetting drive
[17179659.036000] hda: IRQ probe failed (0xffff7cf0)
[17179659.036000] hda: no response (status = 0x0a)
[17179664.540000] hdb: IRQ probe failed (0xffff7cf0)
[17179669.764000] hdb: IRQ probe failed (0xffff7cf0)
[17179669.764000] hdb: no response (status = 0x0a), resetting drive
[17179675.100000] hdb: IRQ probe failed (0xffff7cf0)
[17179675.100000] hdb: no response (status = 0x0a)
[17179675.156000] Probing IDE interface ide2...

That one takes almost 3 minutes.

Why kernel probes IDE channels twice? Why it ignores noprobe in the
second probe? How is Asus A7V133 Bios broken (how can I check how its
broken) and how can I fix it?
Please dont ignore this message like kernel noprobe :)

PS:distro Ubuntu 6.06 and 2 random liveCD ones so its not distro specific.

-- 
Who logs in to gdm? Not I, said the duck.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/