Re: [bug] latest -git boot hang
From: Takashi Iwai
Date: Mon Oct 13 2008 - 04:42:16 EST
At Sat, 11 Oct 2008 09:50:19 +0900,
Tejun Heo wrote:
>
> Hello,
>
> Linus Torvalds wrote:
> > On Fri, 10 Oct 2008, Ingo Molnar wrote:
> >> | 870d6656126add8e383645732b03df2b7ccd4f94 is first bad commit
> >> | commit 870d6656126add8e383645732b03df2b7ccd4f94
> >> | Author: Tejun Heo <tj@xxxxxxxxxx>
> >> | Date: Mon Aug 25 19:47:25 2008 +0900
> >> |
> >> | block: implement CONFIG_DEBUG_BLOCK_EXT_DEVT
> >>
> >> and meanwhile 2 other test-systems failed to boot as well - both have
> >> CONFIG_DEBUG_BLOCK_EXT_DEVT=y.
> >>
> >> So i guess this debug feature is working as expected.
> >
> > Ahh, yeah, sounds that way.
> >
> >> I guess we should mark CONFIG_DEBUG_BLOCK_EXT_DEVT=y as really dangerous
> >> to enable because contemporary distributions (i tried Fedora 9) fail
> >> with it too?
> >
> > Tejun - do you know whether _any_ distro will boot with
> > CONFIG_DEBUG_BLOCK_EXT_DEVT=y?
>
> Hmmm... openSUSE 11.0 didn't have any problem with it, which I was a bit
> pleasantly surprised about. I haven't tested management tools but the
> base system worked just fine.
FYI, even on openSUSE 11.0, it gets a problem when you run mkinitrd on
the kernel with CONFIG_DEBUG_BLOCK_EXT_DEVT=y. It's a problem of SUSE
mkinitrd, though.
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/