From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Bryson <david@tsumego.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Oops on sleep w/2.6.4 tipb 1ghz
Date: Sat, 13 Mar 2004 15:07:22 +1100 [thread overview]
Message-ID: <1079150842.1967.77.camel@gaston> (raw)
In-Reply-To: <20040312084439.GA6929@heliosphan.futuretel.com>
On Fri, 2004-03-12 at 19:44, David Bryson wrote:
> Got an oops on sleep, this is entirely repeatable. This is me writing
> down the oops then typing it in, so there might be some discrepancies ;-)
>
> hdc: start_power_step (step:0)
> hdc: completing PM request, suspend
> hda: start_power_step (step:0)
> hda: start_power_step (step:1)
> hda: complete_power_step (step:1, stat:50, err:0)
> hda: completing PM request, suspend
> Oops: kernel access of bad area, sig 11 [#1]
> NIP: C00B8388 LR: C00b83A4 SP: EF433DA0 REGS: ef433cf0 TRAP: 0301 Nottainted
> MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 00000049, DSISR: 40000000
> TASK: ef4fc000[125] 'devfsd' Last syscall: 83
> GPR00: 00000002 EF433DA0 EF4FC000 C11B9A0D EDBF8F7C 00000005 C1029A0D
> EDBF8F24
> GPR08: EDBF4F1C C1144A0D EDBF8F0C C0270000 24002422
> Call trace:
> [c00b925c] devfs_lookup +0x58/0x2de
> [c0068fa8] __lookup_has +0xe4/0x17e
> [c00690ac] lookup_create +0xa4/0x120
> [c000560c] ret_from_syscall +0x0/0x04c
>
> looks like the oops is somewhere in the bowels of devfs... any hints
> on what might have bothered the kernel ?
Not at this point, I'll have a look. Looks like a NULL ptr deref,
I suspect a devfs bug, though devfs is mostly obsolete by now, so
I don't normally use it.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-03-13 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 8:44 Oops on sleep w/2.6.4 tipb 1ghz David Bryson
2004-03-13 4:07 ` Benjamin Herrenschmidt [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=1079150842.1967.77.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=david@tsumego.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).