From: "Giacomo A. Catenazzi" <cate@cateee.net>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: bug in 2.6.26-rc9: sleeping function called from invalid context at kernel/rwsem:21
Date: Thu, 10 Jul 2008 11:49:44 +0200 [thread overview]
Message-ID: <4875DB38.4000209@cateee.net> (raw)
In-Reply-To: <19f34abd0807100234n46e2229ej5077d8c91d08e9f6@mail.gmail.com>
Vegard Nossum wrote:
> On Thu, Jul 10, 2008 at 10:19 AM, Giacomo A. Catenazzi <cate@cateee.net> wrote:
>> Hello,
>>
>> yesterday at shutdown I had a crash. Unfortunately it seems
>> that there was one (or more) oops missing. The bug appeared
>> at unmounting partition at shutdown, so there are no logs
>> of the previous messages.
>
> Thanks for the report.
>
> It would be really useful to know which filesystems you are/were
> using, including virtual filesystems like sysfs. Maybe you are using
> ecryptfs or FUSE?
>
> (It would also be interesting to see if you could run
> /etc/rc0.d/S40umountfs while the machine is up, to see if you can get
> the segfault but keep the machine usable enough to get the whole log.)
At home, my disks are only ext2.
sysfs, procfs and other system fs and /dev/* mount points are not
umounted in /etc/rc0.d/S40umountfs.
By a quick look (I'm not at home), it seems that on my home computer
only ext2 fs are umounted by /etc/rc0.d/S40umountfs.
As I said, the bug doesn't seems reproducible,
but I'll try harder later.
At subsequent boot, the unclean fs were: / /var and /usr,
Checking was done without error messages, so I think no busy
or opened files at time of crash.
Note: at the boot, one filesystem was checked (after 30+x),
I think it was /home. But I really think it is unrelated
(but it means that some of the other fs have a boot count > 30)
ciao
cate
prev parent reply other threads:[~2008-07-10 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 8:19 bug in 2.6.26-rc9: sleeping function called from invalid context at kernel/rwsem:21 Giacomo A. Catenazzi
2008-07-10 9:34 ` Vegard Nossum
2008-07-10 9:49 ` Giacomo A. Catenazzi [this message]
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=4875DB38.4000209@cateee.net \
--to=cate@cateee.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
/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