Re: 2.4.23 hard lock, 100% reproducible.

From: Mark Symonds
Date: Sun Dec 07 2003 - 18:19:09 EST


> The first oops looks like:
> Unable to handle kernel NULL pointer
> dereference at virtual address: 00000000
> Isnt it a bit weird that the full backtrace is not reported ?
> wli suggests that might stack corruption.

My bad - wrote it down by hand originally since
it was locked hard.

> I dont see any suspicious change around tcp_print_conntrack().
> Any clues?

I'm using ipchains compatability in there, looks like
this is a possible cause - getting a patch right now,
will test and let y'all know (and then switch to
iptables, finally).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at