All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-parisc@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.38-rc3 regression on parisc: segfaults
Date: Tue, 01 Feb 2011 16:12:40 -0600	[thread overview]
Message-ID: <1296598360.18277.11.camel@mulgrave.site> (raw)
In-Reply-To: <alpine.SOC.1.00.1102012342200.25944@math.ut.ee>

On Wed, 2011-02-02 at 00:00 +0200, Meelis Roos wrote:
> I have been testing devel kernels on SMP L1000 successfully until 
> 2.6.38-rc2-00324-g70d1f36 included. The testing means booting the new 
> kernel and running aptitude to update to current debian unstable.
> 
> Now I tried 2.6.38-rc3 and got a crash from aptitude on 2 out of 2 
> tries. Maybe aptitude was broken inbetween but it looks like a kernel 
> bug. Retried 2.6.38-rc2-00324-g70d1f36 and that seemed to work fine so 
> it's more likely a kernel problem.
> 
> What additional information can I provide?

Probably a bisection, if you could.  There have been no parisc patches
between -rc2 and -rc3, so it's coming from outside the architecture.

Thanks,

James



  reply	other threads:[~2011-02-01 22:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 22:00 2.6.38-rc3 regression on parisc: segfaults Meelis Roos
2011-02-01 22:12 ` James Bottomley [this message]
2011-02-03 22:36   ` Meelis Roos
2011-02-03 22:36     ` Meelis Roos
2011-02-01 22:16 ` Carlos O'Donell
2011-02-01 22:16   ` Carlos O'Donell
2011-02-03  2:24 ` John David Anglin
2011-02-03  7:03   ` Meelis Roos
2011-02-04 10:11   ` Meelis Roos
2011-02-04 15:07     ` John David Anglin
2011-02-04 15:20       ` Carlos O'Donell
2011-02-04 15:20         ` Carlos O'Donell
2011-02-04 16:17         ` John David Anglin

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=1296598360.18277.11.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.