[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080810001325.383a9ade@neptune.home>
Date: Sun, 10 Aug 2008 00:13:25 +0200
From: Bruno Prémont <bonbons@...ux-vserver.org>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: [2.6.27-rc2-git4] Kernel panic on VIA Ester+VIA CX700
On Sat, 09 August 2008 Al Viro <viro@...IV.linux.org.uk> wrote:
> 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?
>
They are compiled into the kernel and initialize with 2.6.26.2, though
I have no idea if the kernel uses them more than that...
The crash happens long enough before userspace gets started, as such
except kernel-side users there should be no users of them.
I will check tomorrow without these to determine which one might be the
offending one:
- no crypto,padlock/viarng
- no viafb
- no squashfs (though it should be pretty inoffensive)
Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists