From: Julien RF <julien.rf@no-log.org>
To: LKML <linux-kernel@vger.kernel.org>, Oleg Verych <olecom@flower.upol.cz>
Subject: Re: PROBLEM: Crash on device_shutdown
Date: Wed, 7 Mar 2007 11:10:49 +0100 [thread overview]
Message-ID: <200703071110.50553.julien.rf@no-log.org> (raw)
In-Reply-To: <slrnes44am.m64.olecom@flower.upol.cz>
Hi,
I still have the problem with 2.6.20.1 kernel :(
Julien
Le jeudi 01 février 2007 17:12, Oleg Verych a écrit :
> > From: Julien RF
> > Newsgroups: gmane.linux.kernel
> > Subject: PROBLEM: Crash on device_shutdown
> > Date: Mon, 29 Jan 2007 00:03:49 +0100
> > Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/487140>
>
> Hallo, Julien.
>
> Do you have such problem with more recent kernels, or mm one?
>
> Also, if would be good to have at least some of the stack trace.
>
> You can set up serial console for purpose of logging all information
> to remote host.
>
> > One line summary of the problem:
> > Crash on device_shutdown
> >
> >
> > Full description of the problem/report:
> > When I shut down the system, I get a crash on the device_shutdown
> > function (called by kernel_shutdown_prepare).
> > Since the bug happens when the system is almost shutted down, I can't get
> > the log...
> > I partially copied it by hand, ask me if you need further details :
> > Will now halt.
> > BUG: unable to handle kernel NULL pointer dereference at virtual adress
> > 00000128
> > ...
> > EIP is at device_shutdown + 0x49/0x6c
> > ...
> > Process halt
> > ...
> > /etc/rc0.d/S90halt: line 21: 11198 Segmentation fault halt -d -f
> > $shutdown $poweroff $hddown
> >
> > Julien Richard-Foy
>
> p.s. Please, care to honor "Mail-Followup-To" header information. Thanks.
> ____
prev parent reply other threads:[~2007-03-07 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 23:03 Julien RF
2007-02-01 16:03 ` Oleg Verych
2007-03-07 10:10 ` Julien RF [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=200703071110.50553.julien.rf@no-log.org \
--to=julien.rf@no-log.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/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®