From: Nick Piggin <nickpiggin@yahoo.com.au>
To: pomac@vapor.com
Cc: Linux-kernel@vger.kernel.org
Subject: Re: [OOPS] related to swap?
Date: Wed, 05 Apr 2006 19:38:57 +1000 [thread overview]
Message-ID: <44339031.4040307@yahoo.com.au> (raw)
In-Reply-To: <1144225363.7112.10.camel@localhost>
Ian Kumlien wrote:
>>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.
>
If it doesn't cost you much time (ie. do it overnight) it could save some
developers a lot of time.
> 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)
>
OK, good.
> Since this is my *cough* desktop, running it without that ability is
> kinda a show stopper, thats why i included the thing above.
>
But if the problem can be reproduced in 15 minutes, it shouldn't be
too hard to get a trace without nvidia loaded.
> 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....)
>
If your network hardware or driver is flakey, try compiling a kernel
without that as well before reproducing this swap problem.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-04-06 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 8:22 [OOPS] related to swap? Ian Kumlien
2006-04-05 9:38 ` Nick Piggin [this message]
2006-04-06 21:28 ` Ian Kumlien
2006-04-09 19:31 ` Ian Kumlien
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 22:49 Ian Kumlien
2006-04-04 12:31 ` Nick Piggin
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=44339031.4040307@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Linux-kernel@vger.kernel.org \
--cc=pomac@vapor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox