From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Cc: Pavel Machek <pavel@suse.cz>, linux1394-devel@lists.sourceforge.net
Subject: ACPI S3 and ieee1394 don't get along
Date: Tue, 13 Sep 2005 11:56:31 +0200 [thread overview]
Message-ID: <200509131156.31914.lkml@kcore.org> (raw)
Hello lists,
Running kernel 2.6.13.1, no patches.
Yesterday, after putting my laptop into S3 and reviving it at home, the firewire interface was
unusable, no response when plugging in my external disk, loading sbp2 manually didn't trigger anything.
At this point I unloaded the ohci1394 module, and reloaded it:
Sep 12 16:59:52 precious kernel: ieee1394: Node removed: ID:BUS[0-00:1023] GUID[00c09f00000c8dfa]
Sep 12 16:59:52 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 16:59:53 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 16:59:57 precious kernel: ohci1394: $Rev: 1299 $ Ben Collins <bcollins@debian.org>
Sep 12 16:59:57 precious kernel: ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
Sep 12 16:59:57 precious kernel: PCI: Setting latency timer of device 0000:02:07.0 to 64
Sep 12 16:59:57 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 16:59:57 precious kernel: ohci1394: fw-host0: Runaway loop while stopping context: ...
Sep 12 16:59:58 precious last message repeated 3 times
Sep 12 16:59:58 precious kernel: ohci1394: fw-host0: OHCI-1394 165.165 (PCI): IRQ=[10] MMIO=[d0209000-d02097ff] Max Packet=[65536]
Sep 12 16:59:58 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 17:00:01 precious last message repeated 29 times
Sep 12 17:00:01 precious kernel: ohci1394: fw-host0: Serial EEPROM has suspicious values, attempting to setting max_packet_size to 512 bytes
Sep 12 17:00:02 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 17:00:31 precious last message repeated 2 times
Sep 12 17:00:39 precious kernel: ieee1394: Initialized config rom entry `ip1394'
Sep 12 17:00:39 precious kernel: ohci1394: $Rev: 1299 $ Ben Collins <bcollins@debian.org>
Sep 12 17:00:39 precious kernel: ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
Sep 12 17:00:40 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 17:00:40 precious kernel: ohci1394: fw-host0: Runaway loop while stopping context: ...
Sep 12 17:00:40 precious last message repeated 3 times
Sep 12 17:00:40 precious kernel: ohci1394: fw-host0: OHCI-1394 165.165 (PCI): IRQ=[10] MMIO=[d0209000-d02097ff] Max Packet=[65536]
Sep 12 17:00:40 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
Sep 12 17:00:43 precious last message repeated 29 times
Sep 12 17:00:43 precious kernel: ohci1394: fw-host0: Serial EEPROM has suspicious values, attempting to setting max_packet_size to 512 bytes
Sep 12 17:00:44 precious kernel: ohci1394: fw-host0: Set PHY Reg timeout [0xffffffff/0x00004000/100]
clearly it didn't really got back it's old state when returning from S3. Rebooting helped, but that's
what i'm trying to avoid by using S3 :p
lspci for the firewire interface:
0000:02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: Acer Incorporated [ALI]: Unknown device 001f
Flags: bus master, medium devsel, latency 64, IRQ 10
Memory at d0209000 (32-bit, non-prefetchable) [size=2K]
Memory at d0200000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] Power Management version 2
I saw this thread: http://marc.theaimsgroup.com/?l=linux1394-user&m=111262313930798&w=2 tho I'm not sure if it's relevant to this.
Any patches I might try? The linux1394.org site still is down, so nothing to dig on there ;)
For the firewire maintainers: great job you're doing on it!
Jan
--
Smoking is the leading cause of statistics.
next reply other threads:[~2005-09-13 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 9:56 Jan De Luyck [this message]
2005-09-13 10:20 ` ACPI S3 and ieee1394 don't get along Pavel Machek
2005-09-14 0:20 ` Stefan Richter
2005-09-14 8:46 ` Pavel Machek
2005-09-14 0:17 ` Stefan Richter
2005-09-14 5:08 ` Jan De Luyck
2005-09-14 20:54 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 14:21 Lukas Hejtmanek
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=200509131156.31914.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=pavel@suse.cz \
/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