Re: Oops in 2.6.10-rc1 (almost solved)

From: Linus Torvalds
Date: Tue Nov 09 2004 - 13:55:37 EST

On Tue, 9 Nov 2004, Christian Kujau wrote:
> at least i finally found the "bad" .config option: it's CONFIG_EDD.
> when i disable this option (and only this options. i can use the same
> .config as usual only disbaling this very option. diff is my witness.)
> i can boot a current (!) 2.6.10-rc1-bk and a working snd-ens1371!

Very strange. There's not a lot of stuff that affects EDD directly that I
can see, but there is:

ChangeSet@xxxxxxxxxxxx, 2004-10-20 08:36:22-07:00, Matt_Domsch@xxxxxxxx

Some controller BIOSes have problems with the legacy int13 fn02 READ
SECTORS command. int13 fn42 EXTENDED READ is used in preference by most
boot loaders today, so lets use that. If EXTENDED READ fails or isn't
supported, fall back to READ SECTORS.

This hopefully resolves the three reports of BIOSes which would either
long-pause (30+ seconds) or hang completely on the legacy READ SECTORS

This also adds CONFIG_EDD_SKIP_MBR to eliminate reading the MBR on each
BIOS-presented disk, in case there are further problems in this area.

Signed-off-by: Matt Domsch <Matt_Domsch@xxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
Signed-off-by: Linus Torvalds <torvalds@xxxxxxxx>

which might fit the bill.

However, even that would just change the EDD _data_, it doesn't change the
code that actually runs in the kernel. And I _really_ don't see what EDD
has got to do with anything.

I wonder if the EDD stuff corrupts the sysfs tree or something, and you're
just seeing some strange kobject interference. Greg, you'd likely still be
on the line for that one.

Christian, finding which change triggers this would be very good indeed. I
think the merge with greg is still a good place to start, although even
just doing the snapshot trees (from _before_ -rc1: ie the patches in
/pub/linux/kernel/v2.6/snapshots/old: patch-2.6.9-bk*.gz) is actually also
a good way to narrow things down.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at