From: Tim Timmerman <Tim.Timmerman@asml.com>
To: "Mark Symonds" <mark@symonds.net>, linux-kernel@vger.kernel.org
Cc: "Marcelo Tosatti" <marcelo.tosatti@cyclades.com>
Subject: Re: 2.4.23 hard lock, 100% reproducible.
Date: Mon, 8 Dec 2003 08:12:49 +0100 [thread overview]
Message-ID: <16340.9329.913657.900605@asml.com> (raw)
In-Reply-To: <008501c3bd18$697361e0$7a01a8c0@gandalf>
>>>>> "Mark" == Mark Symonds <mark@symonds.net> writes:
Mark> Hi,
>>
>> The first oops looks like:
>>
>> Unable to handle kernel NULL pointer
>> dereference at virtual address: 00000000
>>
Mark> [...]
Mark> I'm using ipchains compatability in there, looks like
Mark> this is a possible cause - getting a patch right now,
Mark> will test and let y'all know (and then switch to
Mark> iptables, finally).
Let me just add a me-too here.
Haven't got the oops on my desk, here, but from what I could
see, the error occurred in find_appropriate_src, somewhere in
ipchains.
Further, possibly irrelevant datapoint: ABIT BP6, ne2k-pci and
3Com590 network cards. When the oops occurs, everything locks,
capslock and scrolllock are lit.
I can reproduce the error by letting a second system ping the
first, on the internal network. Sometimes it doesn't even
complete a full boot.
I'll try and capture more detail tonight.
TimT.
--
tim.timmerman@asml.nl 040-2683613
timt@timt.org Voodoo Programmer/Keeper of the Rubber Chicken
One time I went to a museum where all the work in the museum had been
done by children. They had all the paintings up on refrigerators.
--
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.
next prev parent reply other threads:[~2003-12-08 7:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 6:50 2.4.23 hard lock, 100% reproducible Alex Davis
2003-12-07 6:55 ` William Lee Irwin III
[not found] ` <046a01c3bca1$267ba5e0$7a01a8c0@gandalf>
2003-12-07 9:07 ` William Lee Irwin III
2003-12-07 9:16 ` Keith Owens
2003-12-07 9:36 ` William Lee Irwin III
2003-12-08 16:34 ` Oliver Teuber
2003-12-07 10:01 ` Mark Symonds
2003-12-07 11:34 ` Martin Josefsson
2003-12-07 14:40 ` Marcelo Tosatti
2003-12-07 23:18 ` Mark Symonds
2003-12-08 4:53 ` William Lee Irwin III
2003-12-08 7:12 ` Tim Timmerman [this message]
2003-12-08 11:06 ` Marcelo Tosatti
2003-12-09 6:29 ` Tim Timmerman
2003-12-08 10:17 ` Marcelo Tosatti
2003-12-08 15:54 ` Stephan von Krawczynski
2003-12-08 16:15 ` Marcelo Tosatti
2003-12-08 16:31 ` Jeff Garzik
2003-12-08 16:55 ` Stephan von Krawczynski
2003-12-08 19:56 ` Mark Symonds
2003-12-07 7:33 ` Mark Symonds
2003-12-07 16:24 ` Alex Davis
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 17:06 Xose Vazquez Perez
2003-12-07 2:36 Mark Symonds
2003-12-07 3:30 ` Philippe Troin
2003-12-07 4:34 ` Mark Symonds
2003-12-07 18:32 ` Chris Frey
2003-12-07 18:49 ` James Bourne
2003-12-07 19:21 ` David Rees
2003-12-07 20:19 ` James Bourne
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=16340.9329.913657.900605@asml.com \
--to=tim.timmerman@asml.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mark@symonds.net \
/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;
as well as URLs for NNTP newsgroup(s).