From: Andrea Arcangeli <andrea@suse.de>
To: Jeff Sipek <jeffpc@optonline.net>
Cc: Marcus Hartig <m.f.h@web.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-aa1
Date: Mon, 5 Apr 2004 02:20:28 +0200 [thread overview]
Message-ID: <20040405002028.GB21069@dualathlon.random> (raw)
In-Reply-To: <200404041859.47940.jeffpc@optonline.net>
On Sun, Apr 04, 2004 at 06:59:41PM -0400, Jeff Sipek wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sunday 04 April 2004 17:05, Marcus Hartig wrote:
> <snip>
> > But now with the vanilla 2.6.5 and/or -aa1 my favourite game Enemy
> > Territory quits with "signal 11". With 2.6.5-rc3 it runs stable for hours.
> >
> > No change in the kernel config, all with preempt, no CONFIG_REGPARM for
> > nVidia binary drivers is set, or other changes. But only when I want to
> > access the net server game browser in ET to play online! Only then bumm!
>
> Same here (with vanilla 2.6.5, I didn't try -aa.)
did you get an oops or just a sigsegv? (see dmesg) If you only got a
sigsegv can you try to keep the segfaulting process under "strace -o
/tmp/o -p <pid>" and report the last few syscalls before the segfault?
That should reduce the scope of the problem, I had a look at the
diff between rc3 and 2.6.5 final but I found nothing obvious that could
explain your problem (yet).
next prev parent reply other threads:[~2004-04-05 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 21:05 2.6.5-aa1 Marcus Hartig
2004-04-04 22:59 ` 2.6.5-aa1 Jeff Sipek
2004-04-05 0:20 ` Andrea Arcangeli [this message]
2004-04-05 2:18 ` 2.6.5-aa1 Jeff Sipek
2004-04-05 5:39 ` 2.6.5-aa1 Marcus Hartig
2004-04-05 7:03 ` 2.6.5-aa1 Jeff Sipek
[not found] ` <1081185096.8036.3.camel@nosferatu.lan>
2004-04-05 17:28 ` 2.6.5-aa1 Marcus Hartig
2004-04-05 18:31 ` 2.6.5-aa1 Marcus Hartig
2004-04-05 19:02 ` 2.6.5-aa1 Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2004-04-04 5:22 2.6.5-aa1 Andrea Arcangeli
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=20040405002028.GB21069@dualathlon.random \
--to=andrea@suse.de \
--cc=jeffpc@optonline.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.f.h@web.de \
/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
all inboxes | Powered by JetHome®