From: Florian Lohoff <flo@rfc822.org>
To: netdev <netdev@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: 2.6.20-rc4 sky2 unsupported chip type 0xff / phy write timeout
Date: Wed, 10 Jan 2007 10:55:28 +0100 [thread overview]
Message-ID: <20070110095528.GA14947@paradigm.rfc822.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4126 bytes --]
Hi,
i have random problems after fresh boot with the onboard sky2 on an
Fujitsu Siemens Lifebook E8110. With 2.6.18-686-3 from the Debian repository i see
random crashes on boot - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404107
With a
Linux machine 2.6.20-rc4 #0 SMP PREEMPT Mon Jan 8 15:18:15 CET 2007 i686 GNU/Linux
i dont see crashes now but instead i see on random boots:
[ 12.412000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 12.412000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 12.412000] sky2 v1.10 addr 0xf0000000 irq 16 Yukon-EC Ultra (0xb4) rev 2
[ 12.412000] sky2 eth0: addr 00:17:42:13:45:8c
[ 24.548000] sky2 eth1: enabling interface
[ 24.552000] sky2 eth1: phy write timeout
[ 24.556000] sky2 eth1: phy write timeout
[ 24.556000] sky2 eth1: phy write timeout
[ 24.560000] sky2 eth1: phy write timeout
[ 24.560000] sky2 eth1: phy write timeout
[ 24.564000] sky2 eth1: phy write timeout
[ 24.564000] sky2 eth1: phy write timeout
[ 24.568000] sky2 eth1: phy write timeout
[ 24.568000] sky2 eth1: phy write timeout
[ 24.572000] sky2 eth1: phy write timeout
[ 24.572000] sky2 eth1: ram buffer 1020K
Afterwards the interface is not usable as one would have expected. rmmod/modprobe later:
[ 186.536000] sky2 eth1: disabling interface
[ 186.536000] sky2 eth1: phy write timeout
[ 186.564000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
[ 190.464000] PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
[ 190.464000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 190.464000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 190.464000] sky2 0000:02:00.0: unsupported chip type 0xff
[ 190.464000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
[ 190.464000] sky2: probe of 0000:02:00.0 failed with error -95
On a working boot i see:
[ 12.236000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[ 12.236000] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 12.236000] sky2 v1.10 addr 0xf0000000 irq 16 Yukon-EC Ultra (0xb4) rev 2
[ 12.240000] sky2 eth1: addr 00:17:42:13:45:8c
[ 24.552000] sky2 eth1: enabling interface
[ 24.556000] sky2 eth1: ram buffer 0K
[ 26.200000] sky2 eth1: Link is up at 100 Mbps, full duplex, flow control none
lspci -vvvn
02:00.0 0200: 11ab:4363 (rev 12)
Subsystem: 10cf:139a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 220
Region 0: Memory at f0000000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at 2000 [size=256]
[virtual] Expansion ROM at 38000000 [disabled] [size=128K]
Capabilities: [48] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 4142
Capabilities: [e0] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s unlimited, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <256ns, L1 unlimited
Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [100] Advanced Error Reporting
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-01-10 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 9:55 Florian Lohoff [this message]
2007-01-10 20:08 ` 2.6.20-rc4 sky2 unsupported chip type 0xff / phy write timeout Stephen Hemminger
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=20070110095528.GA14947@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).