From: Mike Fedyk <mfedyk@matchmail.com>
To: Ram?n Rey Vicente???? <retes_simbad@yahoo.es>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.74-mm2 [kernel BUG at include/linux/list.h:148!]
Date: Tue, 8 Jul 2003 17:34:44 -0700 [thread overview]
Message-ID: <20030709003444.GD16488@matchmail.com> (raw)
In-Reply-To: <1057710738.1003.14.camel@debian>
On Wed, Jul 09, 2003 at 02:32:19AM +0200, Ram?n Rey Vicente???? wrote:
> El mi? 09-07-2003 a las 02:18, Mike Fedyk escribi?:
> > On Wed, Jul 09, 2003 at 01:17:32AM +0200, Ram?n Rey Vicente???? wrote:
> > > Call Trace: [<c0116ea0>] [<c013bb2e>] [<c013f522>] [<c011894e>]
> > > [<c011c44d>]
> > > [<c0109a20>] [<c01097d3>] [<c0109ab1>] [<c0118599>] [<c0130259>]
> > > [<c01621
> > > 8e>] [<c01307f8>] [<c01091ad>] [<c0118599>] [<c0193e05>]
> > > [<c0116f20>] [<c0
> > > 116f20>] [<c0156924>] [<c0156dae>] [<c0157a2a>] [<c014892c>]
> > > [<c0148db9>]
> > > [<c0108f47>]
> >
> > Now run it through ksymoops. You should consider using the in kernel oops
> > decoding. Just turn kksymoops on in the debugging menu.
>
> I'm currently doing that :), my pc is not a Sun 10000, so I try to build
> the kernel only de necessary.
>
> Whenever I get the errors, I'll report it inmediately
You can use the userspace ksymoops instead too...
next prev parent reply other threads:[~2003-07-09 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 20:25 2.5.74-mm2 Andrew Morton
2003-07-05 21:58 ` 2.5.74-mm2 paterley
2003-07-05 22:23 ` 2.5.74-mm2 paterley
2003-07-05 23:04 ` 2.5.74-mm2 Andrew Morton
2003-07-06 0:01 ` 2.5.74-mm2 paterley
2003-07-06 0:49 ` 2.5.74-mm2 Andrew Morton
2003-07-06 1:40 ` 2.5.74-mm2 [kernel BUG at include/linux/list.h:148!] Ramón Rey Vicente
2003-07-06 13:49 ` Nick Orlov
2003-07-08 0:43 ` Mike Fedyk
2003-07-08 23:17 ` Ramón Rey Vicente
2003-07-09 0:18 ` Mike Fedyk
2003-07-09 0:32 ` Ramón Rey Vicente
2003-07-09 0:34 ` Mike Fedyk [this message]
2003-07-09 0:44 ` Ramón Rey Vicente
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=20030709003444.GD16488@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=retes_simbad@yahoo.es \
/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