From: Willy Tarreau <willy@w.ods.org>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
andrea@suse.de, linux-kernel@vger.kernel.org, green@namesys.com
Subject: Re: 2.4.22-pre lockups (now decoded oops for pre10)
Date: Wed, 6 Aug 2003 11:09:20 +0200 [thread overview]
Message-ID: <20030806090920.GA9492@alpha.home.local> (raw)
In-Reply-To: <20030806094150.4d7b0610.skraw@ithnet.com>
On Wed, Aug 06, 2003 at 09:41:50AM +0200, Stephan von Krawczynski wrote:
> Code; c0144b14 <__remove_from_queues+14/30>
> 00000000 <_EIP>:
> Code; c0144b14 <__remove_from_queues+14/30> <=====
> 0: 89 02 mov %eax,(%edx) <=====
> Code; c0144b16 <__remove_from_queues+16/30>
> 2: c7 41 30 00 00 00 00 movl $0x0,0x30(%ecx)
> Code; c0144b1d <__remove_from_queues+1d/30>
> 9: 89 4c 24 04 mov %ecx,0x4(%esp,1)
> Code; c0144b21 <__remove_from_queues+21/30>
> d: e9 7a ff ff ff jmp ffffff8c <_EIP+0xffffff8c>
> Code; c0144b26 <__remove_from_queues+26/30>
> 12: 8d 76 00 lea 0x0(%esi),%esi
once again, it's *pprev=next which is is causing trouble, with pprev=6 this
time (fs/buffer.c:523). There really seems to be something playing badly with
this...
I find amazing that such widely used portions of code only trigger panics on
your system ! either it's a rare combinations of several components/drivers, or
a strange hardware problem, although I can't imagine which (cpu? bus locking?).
Cheers,
Willy
next prev parent reply other threads:[~2003-08-06 9:09 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.55L.0307251040240.12645@freak.distro.conectiva>
[not found] ` <20030725174517.5b21116d.skraw@ithnet.com>
[not found] ` <Pine.LNX.4.55L.0307251545090.14733@freak.distro.conectiva>
2003-08-02 12:27 ` 2.4.22-pre lockups (decoded oops for pre8) Stephan von Krawczynski
2003-08-03 7:25 ` Willy Tarreau
2003-08-03 9:40 ` Stephan von Krawczynski
2003-08-05 16:40 ` Marcelo Tosatti
2003-08-06 2:37 ` Stephan von Krawczynski
2003-08-06 7:41 ` 2.4.22-pre lockups (now decoded oops for pre10) Stephan von Krawczynski
2003-08-06 8:58 ` Oleg Drokin
2003-08-06 9:09 ` Willy Tarreau [this message]
2003-08-06 9:36 ` Stephan von Krawczynski
2003-08-06 12:45 ` Willy Tarreau
2003-08-18 14:23 ` Andrea Arcangeli
2003-08-06 18:15 ` Marcelo Tosatti
2003-08-07 2:14 ` Stephan von Krawczynski
2003-08-07 5:35 ` Oleg Drokin
2003-08-07 12:45 ` Marcelo Tosatti
[not found] ` <3F325198.2010301@namesys.com>
2003-08-07 13:32 ` Stephan von Krawczynski
2003-08-18 20:29 ` Mike Fedyk
2003-08-18 20:39 ` Stephan von Krawczynski
2003-08-18 21:05 ` [grammar] " Matt Gibson
2003-08-18 21:09 ` Mike Fedyk
2003-08-07 15:52 ` Stephan von Krawczynski
[not found] <20030808002918.723abb08.skraw@ithnet.com>
2003-08-08 14:54 ` Marcelo Tosatti
2003-08-08 15:05 ` Stephan von Krawczynski
2003-08-08 15:33 ` Marcelo Tosatti
2003-08-10 21:35 ` Stephan von Krawczynski
2003-08-10 23:23 ` Neil Brown
2003-08-11 9:33 ` Stephan von Krawczynski
2003-08-18 20:43 ` Mike Fedyk
2003-08-13 10:55 ` Stephan von Krawczynski
2003-08-13 14:53 ` Marcelo Tosatti
2003-08-13 14:59 ` Oleg Drokin
2003-08-13 15:12 ` Stephan von Krawczynski
2003-08-13 15:30 ` Oleg Drokin
2003-08-13 16:04 ` Stephan von Krawczynski
2003-08-13 16:34 ` Oleg Drokin
2003-08-13 22:19 ` Stephan von Krawczynski
2003-08-14 8:45 ` Oleg Drokin
2003-08-14 17:26 ` Marcelo Tosatti
2003-08-14 17:42 ` Stephan von Krawczynski
2003-08-15 2:08 ` Chris Mason
2003-08-15 9:40 ` Stephan von Krawczynski
2003-08-15 10:28 ` Stephan von Krawczynski
2003-08-15 12:55 ` Chris Mason
2003-08-15 10:13 ` Stephan von Krawczynski
2003-08-15 10:31 ` Oleg Drokin
2003-08-18 15:06 ` Andrea Arcangeli
2003-08-18 20:19 ` Stephan von Krawczynski
2003-08-18 20:58 ` Mike Fedyk
2003-08-18 22:31 ` Andrea Arcangeli
2003-08-19 1:12 ` Mike Fedyk
2003-08-19 7:12 ` Stephan von Krawczynski
2003-08-19 13:10 ` Alan Cox
2003-08-19 14:18 ` Stephan von Krawczynski
2003-08-19 18:00 ` Mike Fedyk
2003-08-19 21:58 ` Stephan von Krawczynski
2003-08-19 13:27 ` Andrea Arcangeli
2003-08-13 15:21 ` Jim Gifford
2003-08-13 17:08 ` Marcelo Tosatti
2003-08-10 14:23 ` Keith Owens
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=20030806090920.GA9492@alpha.home.local \
--to=willy@w.ods.org \
--cc=andrea@suse.de \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=skraw@ithnet.com \
/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.