Pavel Machek wrote:
Hi!
Seeing a couple of MSI changes in there, on a hunch I booted latest tree with
pci=nomsi, and it resumed again.
Any ideas how to further debug this?
I'll try backing out individual changes from that merge tomorrow.
Thanks.
Of those msi patches you have identified I
Hi!
> > Seeing a couple of MSI changes in there, on a hunch I booted latest tree
> > with
> > pci=nomsi, and it resumed again.
> >
> > Any ideas how to further debug this?
> > I'll try backing out individual changes from that merge tomorrow.
>
> Thanks.
>
> Of those msi patches you have
Hi!
Seeing a couple of MSI changes in there, on a hunch I booted latest tree
with
pci=nomsi, and it resumed again.
Any ideas how to further debug this?
I'll try backing out individual changes from that merge tomorrow.
Thanks.
Of those msi patches you have identified I don't
Pavel Machek wrote:
Hi!
Seeing a couple of MSI changes in there, on a hunch I booted latest tree with
pci=nomsi, and it resumed again.
Any ideas how to further debug this?
I'll try backing out individual changes from that merge tomorrow.
Thanks.
Of those msi patches you have identified I
On Thu, Mar 15, 2007 at 12:45:20PM -0700, Jeremy Fitzhardinge wrote:
> Dave Jones wrote:
> > I just did a build of top of tree, including those commits, and
> > it's still broken. Booting with pci=nomsi no longer 'fixes' it
> > though, which may indicate that the MSI changes were a red
Dave Jones wrote:
> I just did a build of top of tree, including those commits, and
> it's still broken. Booting with pci=nomsi no longer 'fixes' it
> though, which may indicate that the MSI changes were a red herring.
> (Or that the subsequent changes have regressed it even more,
> which seems
Dave Jones <[EMAIL PROTECTED]> writes:
> I just did a build of top of tree, including those commits, and
> it's still broken. Booting with pci=nomsi no longer 'fixes' it
> though, which may indicate that the MSI changes were a red herring.
> (Or that the subsequent changes have regressed it even
On Thu, Mar 15, 2007 at 10:11:01AM -0600, Eric W. Biederman wrote:
> Dave Jones <[EMAIL PROTECTED]> writes:
>
> > On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
> > > > I spent considerable time over the last day
On Thu, Mar 15, 2007 at 10:11:01AM -0600, Eric W. Biederman wrote:
> I haven't heard anything more on this thread.
Sorry, I've been stuck in meetings the last two days..
> I just wanted to double check. The tree that failed did it include
> commits:
>
Dave Jones <[EMAIL PROTECTED]> writes:
> On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
> > On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
> > > I spent considerable time over the last day or so bisecting to
> > > find out why an X60 stopped resuming somewhen between
Dave Jones [EMAIL PROTECTED] writes:
On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and
On Thu, Mar 15, 2007 at 10:11:01AM -0600, Eric W. Biederman wrote:
I haven't heard anything more on this thread.
Sorry, I've been stuck in meetings the last two days..
I just wanted to double check. The tree that failed did it include
commits:
392ee1e6dd901db6c4504617476f6442ed91f72d
On Thu, Mar 15, 2007 at 10:11:01AM -0600, Eric W. Biederman wrote:
Dave Jones [EMAIL PROTECTED] writes:
On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
I spent considerable time over the last day or so
Dave Jones [EMAIL PROTECTED] writes:
I just did a build of top of tree, including those commits, and
it's still broken. Booting with pci=nomsi no longer 'fixes' it
though, which may indicate that the MSI changes were a red herring.
(Or that the subsequent changes have regressed it even more,
Dave Jones wrote:
I just did a build of top of tree, including those commits, and
it's still broken. Booting with pci=nomsi no longer 'fixes' it
though, which may indicate that the MSI changes were a red herring.
(Or that the subsequent changes have regressed it even more,
which seems
On Thu, Mar 15, 2007 at 12:45:20PM -0700, Jeremy Fitzhardinge wrote:
Dave Jones wrote:
I just did a build of top of tree, including those commits, and
it's still broken. Booting with pci=nomsi no longer 'fixes' it
though, which may indicate that the MSI changes were a red herring.
On Tue, Mar 13, 2007 at 12:08:28AM -0400, Dave Jones wrote:
> I spent considerable time over the last day or so bisecting to
> find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
> (Total lockup, black screen of death).
>
> The bisect log looked like this.
>
...
> Any
On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
> On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
> > I spent considerable time over the last day or so bisecting to
> > find out why an X60 stopped resuming somewhen between 2.6.20 and current
> > -git.
> > (Total lockup,
On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
> I spent considerable time over the last day or so bisecting to
> find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
> (Total lockup, black screen of death).
Do you have CONFIG_TICK_ONESHOT or CONFIG_NO_HZ set? If
Dave Jones <[EMAIL PROTECTED]> writes:
> I spent considerable time over the last day or so bisecting to
> find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
> (Total lockup, black screen of death).
>
> The bisect log looked like this.
>
> git-bisect start
> # bad:
Dave Jones [EMAIL PROTECTED] writes:
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
(Total lockup, black screen of death).
The bisect log looked like this.
git-bisect start
# bad:
On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
(Total lockup, black screen of death).
Do you have CONFIG_TICK_ONESHOT or CONFIG_NO_HZ set? If you
On Tue, Mar 13, 2007 at 10:22:53AM +0100, Rafael J. Wysocki wrote:
On Tuesday, 13 March 2007 05:08, Dave Jones wrote:
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and current
-git.
(Total lockup, black
On Tue, Mar 13, 2007 at 12:08:28AM -0400, Dave Jones wrote:
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
(Total lockup, black screen of death).
The bisect log looked like this.
...
Any ideas
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
(Total lockup, black screen of death).
The bisect log looked like this.
git-bisect start
# bad: [c8f71b01a50597e298dc3214a2f2be7b8d31170c] Linux
I spent considerable time over the last day or so bisecting to
find out why an X60 stopped resuming somewhen between 2.6.20 and current -git.
(Total lockup, black screen of death).
The bisect log looked like this.
git-bisect start
# bad: [c8f71b01a50597e298dc3214a2f2be7b8d31170c] Linux
26 matches
Mail list logo
