From: Thierry Godefroy <reserv0@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: [FIXED][BUG] 2.6.24.x can't boot (sysfs: could not mount)
Date: Tue, 11 Mar 2008 08:06:16 -0700 (PDT) [thread overview]
Message-ID: <15891.73472.qm@web45112.mail.sp1.yahoo.com> (raw)
OK... Sorry about the "noise". I traced the problem down to fs/super.c and a
the supermount patch I was using. Fixed now. Sorry again for the false alert...
--- Thierry Godefroy <reserv0@yahoo.com> wrote:
> Greetings,
>
> I tried to upgrade the Linux kernel to 2.6.24.3 on my laptop computer (Clevo
> D470K), which is currently running happily under 2.6.23.17, but the new
> kernel
> panics at the very start of the boot up sequence (can't even produce a dmesg
> to
> post here), with the following error:
>
> sysfs: could not mount !
> mnt_init: sysfs_init_error: -22
>
> This computer ran the whole series of 2.6 kernels so far, and I'm using the
> same configuration with 2.6.24.3 as with 2.6.23.17.
>
> It's a "vanilla" kernel with the exception of two patches: supermount (which
> is
> not even yet active when the panic occurs), and a patch to drivers/acpi/ec.c
> (ACPI_EC_DELAY set back to 50ms) because a change in 2.6.20 broke ACPI on
> this
> computer (slowing everything down to a crawl when ACPI_EC_DELAY is left to
> 500ms).
>
> I also tried with v2.6.24 sources, with the same result.
>
> Any idea ?
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
reply other threads:[~2008-03-11 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15891.73472.qm@web45112.mail.sp1.yahoo.com \
--to=reserv0@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®