From: Andrew Morton <andrewm@uow.edu.au>
To: mingo@elte.hu
Cc: jacob@chaos2.org, linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 del_timer_sync oops in schedule_timeout
Date: Mon, 21 May 2001 11:53:41 +1000 [thread overview]
Message-ID: <3B087525.3C498E9A@uow.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0105191417490.2956-100000@inbetween.blorf.net> <Pine.LNX.4.33.0105201945370.31113-100000@localhost.localdomain>
Ingo Molnar wrote:
>
> On Sat, 19 May 2001, Jacob Luna Lundberg wrote:
>
> > This is 2.4.4 with the aic7xxx driver version 6.1.13 dropped in.
>
> > Unable to handle kernel paging request at virtual address 78626970
>
> this appears to be some sort of DMA-corruption or other memory scribble
> problem. hexa 78626970 is ASCII "pibx", which shows in the direction of
> some sort of disk-related DMA corruption.
It could be timer-list corruption. Someone released some memory
which had a live timer in it. The memory got recycled and then
the timer list traversal fell over it.
There was a convincing report of this a few weeks back on a
system which didn't have any unusual drivers in it. It was
inconclusive. That system was SMP, so it could have been a
timer deletion race.
This bug is so damn hard to track down that it may be worth
putting some special walk-the-timer-lists code inside
kfree()+SLAB_POISON.
-
next prev parent reply other threads:[~2001-05-21 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 21:49 Jacob Luna Lundberg
2001-05-20 17:48 ` Ingo Molnar
2001-05-20 19:12 ` Jacob Luna Lundberg
2001-05-20 19:20 ` Ingo Molnar
2001-05-21 1:53 ` Andrew Morton [this message]
2001-05-22 2:23 ` Jacob Luna Lundberg
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=3B087525.3C498E9A@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=jacob@chaos2.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®