mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: juhl-lkml@dif.dk, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc2-mm3 regression - certain applications get SIGSEGV but are fine with 2.6.12-rc2-mm2
Date: Fri, 29 Apr 2005 03:17:08 -0700	[thread overview]
Message-ID: <20050429031708.6b0e1731.akpm@osdl.org> (raw)
In-Reply-To: <1113908202.2067.1.camel@localhost.localdomain>

Alexander Nyberg <alexn@dsv.su.se> wrote:
>
> tis 2005-04-19 klockan 11:33 +0200 skrev Jesper Juhl:
> > Everything is fine with 2.6.12-rc2, 2.6.12-rc2-mm1, 2.6.12-rc2-mm2 & 
> > earlier kernels as well, but 2.6.12-rc2-mm3 seems to have a problem.
> > I don't know what's causing this, all I can do at the moment is describe 
> > the symptoms.
> > 
> > Certain applications (krootimage and ksplash from KDE 3.4 are 100% 
> > reproducible test cases) that used to run fine have started crashing with 
> > SIGSEGV on 2.6.12-rc2-mm3. I see nothing suspicious in dmesg.
> > I'm including dmesg output as well as strace output from krootimage and 
> > ksplash below.
> > If someone could give me a hint as to what the cause of this could be or 
> > what to try in order to track it down I'd appreciate it.
> > This is 100% reproducible.
> 
> Try backing out
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm3/broken-out/sched-unlocked-context-switches.patch
> 

y'know, if I'd been cc'ed on this email I'd have saved three hours.

Ho hum.

  parent reply	other threads:[~2005-04-29 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  9:33 Jesper Juhl
2005-04-19 10:56 ` Alexander Nyberg
2005-04-19 11:30   ` Jesper Juhl
2005-04-29 10:17   ` Andrew Morton [this message]
2005-04-29 11:03     ` Jesper Juhl

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=20050429031708.6b0e1731.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alexn@dsv.su.se \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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®