From: Carsten Rietzschel <cr7@os.inf.tu-dresden.de>
To: Alexander Gran <alex@zodiac.dnsalias.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI S3 - USB resume problem (kernel 2.6.7)
Date: Fri, 18 Jun 2004 13:41:39 +0200 [thread overview]
Message-ID: <200406181341.39546.cr7@os.inf.tu-dresden.de> (raw)
In-Reply-To: <200406172123.38043@zodiac.zodiac.dnsalias.org>
Hello,
thanks Alex. You're right - the e1000 doesn't work too.
Also all other PCI-devices like firewire, USB and soundcard do not.
So it's not a problem of USB, but of ACPI-PCI.
After reading a few mails of the acpi-mailinglist and some bug reports, I know
now, I'm not alone with this problem :/
I'll have a closer look to acpi-list & bug reports.
Maybe someone here, has found a solution or has some hints what to do next ???
Regards,
Carsten
Am Donnerstag, 17. Juni 2004 21:23 schrieb Alexander Gran:
> Am Donnerstag, 17. Juni 2004 17:44 schrieb Carsten Rietzschel:
> > Noticed that in /proc/interrupts the values for uhci_hcd are not
> > incremented after resume. So are no IRQs where received (is that right
> > ?). What could be reason ?
>
> No Idea. I also tried to get this working, without success (And no more
> time at the moment to dig deeper). The e1000 driver has the same problem.
> No Interrupts on RX. Someone suggested to "Hook the driver to the timer
> interrupt and see if that works at least somehow", however I'm unsure how
> to do that ;)
>
> regards
> Alex
next prev parent reply other threads:[~2004-06-18 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 15:44 Carsten Rietzschel
2004-06-17 19:23 ` Alexander Gran
2004-06-18 11:41 ` Carsten Rietzschel [this message]
2004-06-18 11:50 ` Alexander Gran
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=200406181341.39546.cr7@os.inf.tu-dresden.de \
--to=cr7@os.inf.tu-dresden.de \
--cc=alex@zodiac.dnsalias.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®