From: Pavel Machek <pavel@ucw.cz>
To: Nuno Ferreira <nuno.ferreira@graycell.biz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: problem with suspend and usb
Date: Wed, 22 Sep 2004 19:50:58 +0200 [thread overview]
Message-ID: <20040922175058.GA14891@elf.ucw.cz> (raw)
In-Reply-To: <1095870490.3809.3.camel@taz.graycell.biz>
Hi!
> Well, turns out that the lastest -mm kernel is much worse.
Hmm, well, I'm not going to debug -vanilla when there's better
codebase pending in -mm, so -mm is better because it has chance to get
debugged.
> Found several problems:
> * Shutdown is very slow. After the message "acpi_power_off called"
> appears, it taken ~30s for the laptop to shutdown. Using 2.6.8 it shuts
> down immediately after that message is printed.
Insert printk's to see what is slow, then contact acpi list.
> * Suspend with ohci_hcd hangs. Removing the ohci_hcd module suspend
> works.
> Here's what's printed on the screen before hanging (I hand-write it so
> there could be some typos)
>
> Freeing memory.... done (54077 pages freed)
> usbhid1-1:1.0: resume is unsafe!
> usb1-1: no poweroff yet, suspending instead.
> usb usb1: no poweroff yet, suspending instead.
> ............. swsusp: Need to copy 9776 pages
> ............. swsusp: critical section/: done (9840 pages copied)
Can you insert printks to ohci_hcd to see what went wrong there?
> * Network doesn't work after resuming. I'm using 8139cp. I tried "ifdown
> eth0 && ifup eth0" and network stil. doesn't work after suspend.
> Even tried "ifdown eth0 && modprobe -r 8139cp && modprobe 8139cp && ifup
> eth0" and network still doesn't work. Only started to work after reboot
> Here are the logs from the suspend request
This looks like interrupt problem. Can you try noapic and/or disabling
acpi for irq routing?
> Sep 22 15:29:42 taz kernel: ** PCI interrupts are no longer routed automatically. If this
> Sep 22 15:29:42 taz kernel: ** causes a device to stop working, it is probably because the
> Sep 22 15:29:42 taz kernel: ** driver failed to call pci_enable_device(). As a temporary
> Sep 22 15:29:42 taz kernel: ** workaround, the "pci=routeirq" argument restores the old
> Sep 22 15:29:42 taz kernel: ** behavior. If this argument makes the device work again,
> Sep 22 15:29:42 taz kernel: ** please email the output of "lspci" to bjorn.helgaas@hp.com
> Sep 22 15:29:42 taz kernel: ** so I can fix the driver.
Hmm, also try pci=routeirq.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-09-22 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 13:04 Nuno Ferreira
2004-09-21 0:59 ` Nuno Ferreira
2004-09-22 9:48 ` Pavel Machek
2004-09-22 16:28 ` Nuno Ferreira
2004-09-22 17:50 ` Pavel Machek [this message]
2004-09-23 23:19 ` Nuno Ferreira
2004-09-24 20:22 ` [ACPI] " 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=20040922175058.GA14891@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.ferreira@graycell.biz \
/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
all inboxes | Powered by JetHome®