Messages in this thread | | | Date | Mon, 8 Dec 2003 09:06:02 -0200 (BRST) | From | Marcelo Tosatti <> | Subject | Re: 2.4.23 hard lock, 100% reproducible. |
| |
On Mon, 8 Dec 2003, Tim Timmerman wrote:
> >>>>> "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.
Tim,
Please try the updated 2.4 BK tree (you can use -bk5, http://www.kernel.org/pub/linux/kernel/v2.4/snapshots/patch-2.4.23-bk5.bz2).
It contains a fix for a known bug in the netfilter which might what you're hitting.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |