From: Alex Riesen <raa.lkml@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS (NULL pointer dereference) in v2.6.22-rc3
Date: Sat, 2 Jun 2007 16:45:15 +0200 [thread overview]
Message-ID: <20070602144515.GA2390@steel.home> (raw)
In-Reply-To: <20070602013502.a20ad424.akpm@linux-foundation.org>
Andrew Morton, Sat, Jun 02, 2007 10:35:02 +0200:
> On Sat, 2 Jun 2007 00:15:15 +0200 Alex Riesen <raa.lkml@gmail.com> wrote:
>
> > Ubuntu 7.04, P4, SMT, hyperthreading active. Not reproducable, context unknown,
> > seen only two times :(
> >
> > kernel: Call Trace:
> > kernel: [show_trace_log_lvl+26/47] show_trace_log_lvl+0x1a/0x2f
> > kernel: [show_stack_log_lvl+157/165] show_stack_log_lvl+0x9d/0xa5
> > kernel: [show_registers+441/651] show_registers+0x1b9/0x28b
> > kernel: [die+273/530] die+0x111/0x212
> > kernel: [do_page_fault+1060/1266] do_page_fault+0x424/0x4f2
> > kernel: [error_code+114/120] error_code+0x72/0x78
> > kernel: [vfs_ioctl+562/581] vfs_ioctl+0x232/0x245
> > kernel: [sys_ioctl+49/72] sys_ioctl+0x31/0x48
> > kernel: [sysenter_past_esp+95/133] sysenter_past_esp+0x5f/0x85
>
> I think we've seen a report of that before. Do you recall what the system
> was doing at the time?
>
Not really. One time it was when I started an old Opera browser I
discovered somewhere in my $HOME, the other is believe when I was
playing a scratched DVD with vlc (not sure, though).
> + if (!filp->f_op->ioctl) {
> + printk("%s: ioctl %p disappeared\n", __FUNCTION__, f);
Applied, but used KERN_EMERG (let's hope there will be no storm).
next prev parent reply other threads:[~2007-06-02 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 22:15 Alex Riesen
2007-06-02 8:35 ` Andrew Morton
2007-06-02 14:45 ` Alex Riesen [this message]
2007-06-02 16:50 ` Randy Dunlap
2007-06-02 22:57 ` Alex Riesen
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=20070602144515.GA2390@steel.home \
--to=raa.lkml@gmail.com \
--cc=akpm@linux-foundation.org \
--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®