> On Sat, Oct 03, 2009 at 02:28:50PM +0300, Matti Aarnio wrote:> > On Sat, Oct 03, 2009 at 01:00:03PM +0200, Frederic Weisbecker wrote:> > > On Sat, Oct 03, 2009 at 01:53:18PM +0300, Matti Aarnio wrote:> > > > This is perhaps already fixed, as I have two a bit newer kernels than this one,> > > > but reporting is better than being silent..> > > > > > > > > Hi,> > > > > > Which kernel is this? Does it happen in the current 2.6.32-rc1 ?> > > > I do know that reading the trace is difficult, but the asked for information> > is down in there. Intentionally put there by the kernel-oops coders, I presume.> > > Ah ok. It's just that I'm not that familiar with fedora's kernels naming :-)> > > > I do use vendor kernels, and Fedora 12 beta program has not yet made> > 2.6.32-rc1 kernel available.> > > > However this does not appear in 2.6.31.1-56.fc12.x86_64 kernel that > > is lattest from vendor, but there I have some other troubles why I > > took a bit older kernel. (Other troubles with the xfs filesystem > > lock handling.)> > So this looks based on a 2.6.31.1 kernel, more stable. And if it > doesn't happen with it, then it's fine.> > That said, it's all about fedora based kernel so it's a bit hard to > tell if it came from fedora adds or vanilla kernel code.