From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Adam Belay <ambx1@neo.rr.com>
Cc: David Brownell <david-b@pacbell.net>, linux-pm@lists.osdl.org
Subject: Re: A reference implementation of PCI suspend/resume?
Date: Wed, 18 May 2005 19:40:08 +0200 [thread overview]
Message-ID: <200505181940.09407.rjw@sisk.pl> (raw)
In-Reply-To: <20050518012604.GC11189@neo.rr.com>
Hi,
On Wednesday, 18 of May 2005 03:26, Adam Belay wrote:
> On Tue, May 17, 2005 at 09:28:10PM +0200, Rafael J. Wysocki wrote:
> > On Tuesday, 17 of May 2005 20:35, David Brownell wrote:
> > > On Tuesday 17 May 2005 2:10 am, Rafael J. Wysocki wrote:
> > >
> > > > Could you please have a look at http://bugzilla.kernel.org/show_bug.cgi?id=4416
> > >
> > > Sorry, I don't have much time for such things; especially for
> > > problems that only appear in the MM tree (with so many non-USB
> > > changes) ... and which already appear to be board-specific, and
> > > tied to ACPI changes.
> >
> > Never mind. :-)
> >
> > > > There seems to be a problem with OHCI and EHCI drivers wrt suspend/resume
> > > > (swsusp) in the current -mm on that box.
> > >
> > > Is that with or without those ACPI fixes?
> >
> > Both ...
> >
> > Rafael
> >
>
> Have you checked which of these device drivers are calling free_irq() in
> their suspend routines.
AFAICS, the EHCI and OHCI drivers do, but the snd_intel8x0 driver does not.
Anyway this does not seem to be relevant, as the box hangs when the
drivers' resume routines are called (ie on resume-during-resume).
All of the drivers that cause the problem are compiled as modules, so their
suspend routines are not called during swsusp resume.
> Also could I see /proc/interrupts (with an offending
> combination of drivers loaded) and a list of the hardware you think might be
> involved.
The offending devices are (from lspci):
0000:00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2)
IOW, it's the nForce3 chipset.
Also, there are multiple configurations in which the problem appears (please
see below).
> Have you been able to find a pair of drivers that will cause this
> problem?
The drivers that cause this problem (on this particular box) are:
ehci_hcd
ohci_hcd
snd_intel8x0
If any of them is loaded on suspend, the box hangs solid during resume (please
note that I was unable to reproduce the problem on a different box, using the
same drivers with the AMD chipset and the NEC USB 2.0).
Here go various /proc/interrupts that correspond to the "hanging" driver
configurations:
1) whith snd_intel8x0
CPU0
0: 1145893 XT-PIC timer
1: 1187 XT-PIC i8042
2: 0 XT-PIC cascade
8: 0 XT-PIC rtc
9: 428 XT-PIC acpi
10: 4898 XT-PIC NVidia nForce3
11: 0 XT-PIC yenta, yenta
12: 119 XT-PIC i8042
14: 9787 XT-PIC ide0
15: 7294 XT-PIC ide1
NMI: 0
LOC: 1145536
ERR: 0
MIS: 0
2) with EHCI
CPU0
0: 146184 XT-PIC timer
1: 243 XT-PIC i8042
2: 0 XT-PIC cascade
5: 5 XT-PIC ehci_hcd:usb1
8: 0 XT-PIC rtc
9: 76 XT-PIC acpi
11: 0 XT-PIC yenta, yenta
12: 119 XT-PIC i8042
14: 759 XT-PIC ide0
15: 7240 XT-PIC ide1
NMI: 0
LOC: 146005
ERR: 0
MIS: 0
3) with OHCI
CPU0
0: 152128 XT-PIC timer
1: 205 XT-PIC i8042
2: 0 XT-PIC cascade
8: 0 XT-PIC rtc
9: 77 XT-PIC acpi
11: 25 XT-PIC yenta, yenta, ohci_hcd:usb1, ohci_hcd:usb2
12: 119 XT-PIC i8042
14: 813 XT-PIC ide0
15: 7310 XT-PIC ide1
NMI: 0
LOC: 151961
ERR: 0
MIS: 0
Of course any combination of the three causes the problem.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-05-18 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 5:06 A reference implementation of PCI suspend/resume? Fabrice Gautier
2005-05-16 4:53 ` David Brownell
2005-05-16 8:55 ` Shaohua Li
2005-05-16 20:16 ` Adam Belay
2005-05-16 20:56 ` Rafael J. Wysocki
2005-05-16 21:19 ` Jordan Crouse
2005-05-17 0:26 ` David Brownell
2005-05-17 9:10 ` Rafael J. Wysocki
2005-05-17 18:35 ` David Brownell
2005-05-17 19:28 ` Rafael J. Wysocki
2005-05-18 1:26 ` Adam Belay
2005-05-18 17:40 ` Rafael J. Wysocki [this message]
2005-05-18 18:32 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 19:02 Fabrice Gautier
2005-05-16 19:39 ` David Brownell
2005-05-12 1:24 Shaohua Li
2005-05-12 6:21 ` Adam Belay
2005-05-12 7:03 ` Shaohua Li
2005-05-27 6:49 ` Shaohua Li
2005-05-27 7:20 ` Pavel Machek
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=200505181940.09407.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ambx1@neo.rr.com \
--cc=david-b@pacbell.net \
--cc=linux-pm@lists.osdl.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