All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Bruno Pr?mont <bonbons@linux-vserver.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6.27-rc2-git4] Kernel panic on VIA Ester+VIA CX700
Date: Sat, 9 Aug 2008 23:01:54 +0100	[thread overview]
Message-ID: <20080809220154.GO28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <200808100000.25402.rjw@sisk.pl>

On Sun, Aug 10, 2008 at 12:00:24AM +0200, Rafael J. Wysocki wrote:
> On Saturday, 9 of August 2008, Bruno Pr?mont wrote:
> > Hi,
> 
> Hi,
> 
> > Trying out 2.6.27-rc2-git4 on a VIA Ester + CX700 based system I
> > experience the following panic using a config obtained with make
> > oldconfig from working 2.6.26 config.
> > 
> > Looking at the traces and when it happens it looks like it could be
> > libATA or SCSI related...
> > 
> > 
> > Note: the kernel is patched with viafb patches sent yesterday ([y]) and
> > squashfs (<m>)
> 
> Could you retest without these two, please?

There'a another fun candidate: lazy allocation of fpu state.  Do you have
padlock-aes/padlock-sha/via-rng in use?

  reply	other threads:[~2008-08-09 22:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09 20:51 [2.6.27-rc2-git4] Kernel panic on VIA Ester+VIA CX700 Bruno Prémont
2008-08-09 22:00 ` Rafael J. Wysocki
2008-08-09 22:00   ` Rafael J. Wysocki
2008-08-09 22:01   ` Al Viro [this message]
2008-08-09 22:13     ` Bruno Prémont
     [not found]     ` <E1KS2KD-0000he-00@gondolin.me.apana.org.au>
     [not found]       ` <20080810133056.2fd69a20@neptune.home>
2008-08-10 23:39         ` H. Peter Anvin
2008-08-11 18:17           ` Suresh Siddha
2008-08-11 20:16             ` Bruno Prémont

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=20080809220154.GO28946@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=bonbons@linux-vserver.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.