On Sun, 2010-03-21 at 18:19 -0600, Pete Zaitcev wrote:
> On Wed, 17 Mar 2010 08:26:59 -0700
> Bjorn Helgaas wrote:
>
> > > > > http://bugzilla.kernel.org/show_bug.cgi?id=15533
> >
> > Any luck testing the patch from the bugzilla? I'd really like to get
> > this figured out so we can get the fix
On Wed, 17 Mar 2010 08:26:59 -0700
Bjorn Helgaas wrote:
> > > > http://bugzilla.kernel.org/show_bug.cgi?id=15533
>
> Any luck testing the patch from the bugzilla? I'd really like to get
> this figured out so we can get the fix in the next -rc and move on
> to the next _CRS issue :-)
I was on v
On Monday 15 March 2010 11:51:01 am Bjorn Helgaas wrote:
> On Saturday 13 March 2010 08:02:24 pm Bjorn Helgaas wrote:
> > On Sat, 2010-03-13 at 13:46 -0700, Pete Zaitcev wrote:
> > > On Fri, 12 Mar 2010 22:37:56 -0700
> > > Bjorn Helgaas wrote:
> > >
> > > > Thanks for the report. Would you mind
On Saturday 13 March 2010 08:02:24 pm Bjorn Helgaas wrote:
> On Sat, 2010-03-13 at 13:46 -0700, Pete Zaitcev wrote:
> > On Fri, 12 Mar 2010 22:37:56 -0700
> > Bjorn Helgaas wrote:
> >
> > > Thanks for the report. Would you mind posting the entire dmesg
> > > log, /proc/iomem contents, and "lspci
On Sat, 2010-03-13 at 13:46 -0700, Pete Zaitcev wrote:
> On Fri, 12 Mar 2010 22:37:56 -0700
> Bjorn Helgaas wrote:
>
> > Thanks for the report. Would you mind posting the entire dmesg
> > log, /proc/iomem contents, and "lspci -vv" output somewhere (maybe in
> > bugzilla)?
>
> Done, new bug:
> h
On Fri, 2010-03-12 at 23:40 -0700, Pete Zaitcev wrote:
> On Fri, 12 Mar 2010 22:37:56 -0700
> Bjorn Helgaas wrote:
>
> > Thanks for the report. Would you mind posting the entire dmesg
> > log, /proc/iomem contents, and "lspci -vv" output somewhere (maybe in
> > bugzilla)?
> >
> > The quote belo
On Fri, 12 Mar 2010 22:37:56 -0700
Bjorn Helgaas wrote:
> Thanks for the report. Would you mind posting the entire dmesg
> log, /proc/iomem contents, and "lspci -vv" output somewhere (maybe in
> bugzilla)?
Done, new bug:
http://bugzilla.kernel.org/show_bug.cgi?id=15533
-- Pete
---
On Fri, 2010-03-12 at 22:37 -0700, Bjorn Helgaas wrote:
> On Fri, 2010-03-12 at 18:25 -0700, Pete Zaitcev wrote:
> > On Thu, 11 Mar 2010 00:33:58 -0700, Pete Zaitcev wrote:
> >
> > I apologise for answering to myself, but while there was no answer,
> > git bisect found the offending commit and I
On Fri, 2010-03-12 at 18:25 -0700, Pete Zaitcev wrote:
> On Thu, 11 Mar 2010 00:33:58 -0700, Pete Zaitcev wrote:
>
> I apologise for answering to myself, but while there was no answer,
> git bisect found the offending commit and I verified that it was
> the culprit. Also, I am adding Bjorn and Je
On Fri, 12 Mar 2010 22:37:56 -0700
Bjorn Helgaas wrote:
> Thanks for the report. Would you mind posting the entire dmesg
> log, /proc/iomem contents, and "lspci -vv" output somewhere (maybe in
> bugzilla)?
>
> The quote below isn't enough for me to see the problem, but
> http://bugzilla.kernel.
On Thu, 11 Mar 2010 00:33:58 -0700, Pete Zaitcev wrote:
I apologise for answering to myself, but while there was no answer,
git bisect found the offending commit and I verified that it was
the culprit. Also, I am adding Bjorn and Jesse to cc:.
> I seem to hit a sudden regression in 2.6.34-rc1: t
Dear Dave and others:
I seem to hit a sudden regression in 2.6.34-rc1: the modeset fails.
On this box it also means, no way to start X, which is unfortunate.
Here's a quote from bad dmesg (truncated front and back for brievity):
Linux agpgart interface v0.103
agpgart-intel :00:00.0: Intel HD
12 matches
Mail list logo
