From: Duncan Sands <baldrick@wanadoo.fr>
To: no one in particular <lkml@krimedawg.org>, linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.5.46 (scheduler?)
Date: Sun, 10 Nov 2002 12:32:10 +0100 [thread overview]
Message-ID: <200211101232.12859.baldrick@wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0211091458160.484-100000@mcgruff.krimedawg.org>
> Trace; c0114380 <__wake_up+20/40>
> Trace; c0147b36 <pipe_write+1f6/240>
> Trace; c013e131 <vfs_write+c1/160>
> Trace; c013e3ea <sys_write+2a/40>
> Trace; c010897b <syscall_call+7/b>
I also got this once, but wasn't able to reproduce it.
Duncan.
prev parent reply other threads:[~2002-11-10 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 23:01 no one in particular
2002-11-10 11:32 ` Duncan Sands [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=200211101232.12859.baldrick@wanadoo.fr \
--to=baldrick@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@krimedawg.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®