From: Kasper Dupont <kasperd@daimi.au.dk>
To: Alan Cox <alan@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-ac1
Date: Wed, 07 Aug 2002 14:33:06 +0200 [thread overview]
Message-ID: <3D511382.BBC4D352@daimi.au.dk> (raw)
In-Reply-To: 3D504C10.7975CCD8@daimi.au.dk
Kasper Dupont wrote:
>
> I'm using 2.4.19-ac1 with patch-int-2.4.18.2. The system
> was running and heavily used for 2 days and 22 hours
> without a single glitch, but at shutdown I got an Oops
> from S01halt. I had no way to save the output, so I just
> wrote down the IP and calltrace, here is the output from
> ksymoops with that input:
>
> Trace; c012c077 <kmem_cache_free+37/a0>
> Trace; c011df6c <free_uid+2c/30>
> Trace; c01188cc <release_task+2c/120>
> Trace; c0119746 <sys_wait4+2f6/380>
> Trace; c01089f3 <system_call+33/40>
>
> I don't think it is related to the patch, which have
> been working flawlessly since 2.4.18. I don't know yet
> if the problem can be reproduced.
I have not been able to reproduce the problem, and I have
no idea what so ever about the cause. What I forgot to
mention in my previous mail was that this happened on a
UP system, and the Oops message was a kernel paging
request (at some 0xC... address AFAIR).
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razrep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk
next prev parent reply other threads:[~2002-08-07 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-03 18:59 Linux 2.4.19-ac1 Alan Cox
2002-08-03 21:42 ` bert hubert
2002-08-03 23:08 ` Bruce Harada
2002-08-07 1:49 ` bill davidsen
2002-08-07 14:40 ` Bruce Harada
2002-08-06 22:22 ` Kasper Dupont
2002-08-07 12:33 ` Kasper Dupont [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-04 1:10 Stas Sergeev
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=3D511382.BBC4D352@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=alan@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.