Re: [OOPS] related to swap?

[Ian Kumlien <pomac@vapor.com>]

> Ian Kumlien wrote:
>
> > Yes, i run a tainted kernel! either live with it or ignore this mail
> > =)
>
> > starting swap lead to a deadlock within 15 mins
>
> > I have never had the energy to perform a full memtext86+
>
> It would be useful if you could perform a memtest overnight one night,
> then run a non-patched and non-tained 2.6.16.1 kernel, and try to
> reproduce the problems.

As i said, i really doubt that the memory is at fault here, it has done
several passes over the memory but not all tests. I can give it a go
though, but i really doubt it'll find anything.

The kernel i run is a plain 2.6.16.1 from kernel.org (i have heard that
you can actually compile gentoos own these days)

Since this is my *cough* desktop, running it without that ability is
kinda a show stopper, thats why i included the thing above.

But the thing is, my laptop runs with the same compiler, "same" nvidia
driver and the "same" kernel ("same" as in 32 bit not 64 bit).
Eventhough "same" in this case usually means nothing, i doubt that one
would have a serius bug and the other wouldn't, ie it's most likley a
bug related to 64 bits or one or more of the drivers involved.

The only errors i get in dmesg atm is:
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c
(283)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c
(150)

Which is related to TSO, from what i gather, but i can't turn off tso on
forcedeth... (i suspected this to cause corruption a while back....)

And:
eth0: too many iterations (6) in nv_nic_irq.

Which seems to be a warning of some sort (haven't checked the source
yet).

PS. Reply-to-all is your friend... =)
DS.

-- 
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net