From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
Linux PCI <linux-pci@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] PCI PM: Restore standard config registers of all devices early (was: Re: EeePC resume failure - timers)
Date: Tue, 20 Jan 2009 12:32:00 -0800 [thread overview]
Message-ID: <200901201232.00966.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200901201215.11559.jbarnes@virtuousgeek.org>
On Tuesday, January 20, 2009 12:15 pm Jesse Barnes wrote:
> On Tuesday, January 20, 2009 12:09 pm Jesse Barnes wrote:
> > On Tuesday, January 20, 2009 11:45 am Linus Torvalds wrote:
> > > On Tue, 20 Jan 2009, Jesse Barnes wrote:
> > > > Hm it's probably not display programming related then... Sounds like
> > > > the i830_update_dri_buffers() call is failing for some reason. The
> > > > kernel driver does do some I/O mapping stuff at enter/leavevt time
> > > > (and therefore suspend/resume time), can you reproduce the issue just
> > > > by VT switching? If so you might be able to see something useful in
> > > > the kernel log...
> > >
> > > I was going to say that I've been VT switching and it has worked, but I
> > > decided to double-check. And yes, I can reproduce it that way. And no,
> > > no kernel messages that are visible that way either.
> >
> > So the machine is alive enough for you to see the logs? Can you get a
> > backtrace (both kernel & userspace)?
>
> Oops, just realized by "no messages visible" you probably meant that it
> really was hung rather than you saw no useful messages. That'll make
> things more difficult. Which 2D driver are you running?
And I assume you've tried keeping an ssh session open on the machine while VT
switching (that's *usually* sufficient for me, in all but the worst of
crashes)...
next prev parent reply other threads:[~2009-01-20 20:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0901161010400.2417-100000@iolanthe.rowland.org>
2009-01-16 15:28 ` [PATCH] PCI PM: Restore standard config registers of all devices early (was: Re: EeePC resume failure - timers) Rafael J. Wysocki
2009-01-16 15:51 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901160733260.29252@localhost.localdomain>
2009-01-16 16:27 ` Rafael J. Wysocki
[not found] ` <200901161727.05026.rjw@sisk.pl>
2009-01-16 16:37 ` Linus Torvalds
2009-01-16 16:40 ` Alan Stern
2009-01-16 16:51 ` [PATCH] irq: provide debug_poll_all_shared_irqs() method under CONFIG_DEBUG_SHIRQ Ingo Molnar
[not found] ` <20090116165123.GB27495@elte.hu>
2009-01-16 17:08 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901160855440.29252@localhost.localdomain>
2009-01-16 17:11 ` Ingo Molnar
[not found] ` <20090116171149.GA14084@elte.hu>
2009-01-16 17:13 ` Ingo Molnar
[not found] ` <20090116171359.GA15538@elte.hu>
2009-01-16 17:31 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901160834380.29252@localhost.localdomain>
2009-01-16 20:48 ` [PATCH] PCI PM: Restore standard config registers of all devices early (was: Re: EeePC resume failure - timers) Rafael J. Wysocki
[not found] ` <200901162148.42357.rjw@sisk.pl>
2009-01-16 20:54 ` Rafael J. Wysocki
[not found] ` <200901162154.44045.rjw@sisk.pl>
2009-01-16 20:59 ` Jesse Barnes
[not found] ` <200901161259.56586.jbarnes@virtuousgeek.org>
2009-01-16 21:11 ` Rafael J. Wysocki
2009-01-19 21:54 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901200850560.3081@localhost.localdomain>
2009-01-19 22:19 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901200917320.2930@localhost.localdomain>
2009-01-19 22:21 ` Jesse Barnes
2009-01-19 23:26 ` Rafael J. Wysocki
[not found] ` <200901191421.56148.jbarnes@virtuousgeek.org>
2009-01-20 4:56 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901201342510.3554@localhost.localdomain>
2009-01-20 17:45 ` Jesse Barnes
[not found] ` <200901200945.37371.jbarnes@virtuousgeek.org>
2009-01-20 19:22 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901210613030.3457@localhost.localdomain>
2009-01-20 19:30 ` Jesse Barnes
[not found] ` <200901201130.17987.jbarnes@virtuousgeek.org>
2009-01-20 19:45 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901210642570.2885@localhost.localdomain>
2009-01-20 20:09 ` Jesse Barnes
[not found] ` <200901201209.37836.jbarnes@virtuousgeek.org>
2009-01-20 20:15 ` Jesse Barnes
2009-01-20 20:15 ` Jesse Barnes
[not found] ` <200901201215.11559.jbarnes@virtuousgeek.org>
2009-01-20 20:32 ` Jesse Barnes [this message]
2009-01-20 20:19 ` Linus Torvalds
[not found] ` <alpine.LFD.2.00.0901210703530.2892@localhost.localdomain>
2009-01-20 20:40 ` Jesse Barnes
[not found] ` <200901201240.53719.jbarnes@virtuousgeek.org>
2009-01-20 21:43 ` Jesse Barnes
2009-01-20 16:21 ` Daniel Qarras
[not found] <200901161040.19222.rjw@sisk.pl>
2009-01-16 15:15 ` Alan Stern
[not found] <alpine.LFD.2.00.0901141236260.6528@localhost.localdomain>
[not found] ` <alpine.LFD.2.00.0901150954390.6528@localhost.localdomain>
[not found] ` <200901152008.50643.rjw@sisk.pl>
2009-01-16 9:40 ` Rafael J. Wysocki
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=200901201232.00966.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=johnstul@us.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox