linux-kernel - Marvel based pcie gbit controller on nForce 630i mainboard

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <47AF27D5.4000308@auby.no>
Date:	Sun, 10 Feb 2008 17:35:33 +0100
From:	Christian Auby <christian@...y.no>
To:	linux-kernel@...r.kernel.org
Subject: Marvel based pcie gbit controller on nForce 630i mainboard

I recently acquired an XFX nForce 630i based motherboard, and have been 
experiencing hard freezes from time to time that I originally had no 
idea why happened. With hard freeze I mean exactly that; no log messages 
that I know of (though there might be some I don't know of), picture and 
input frozen.

After a bit I tried the following 64-bit kernels and found the culprit:

2.6.18-6 (debian stable)
2.6.22-14 (ubuntu server)
2.6.24-2 (debian unstable)

All of them crash when transferring files over samba, a hard freeze 
requiring shutdown.

I added a PCI network card, and without changing anything else things 
now work fine. The faulting network card is detected as:

---
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E 
Gigabit Ethernet Controller (rev 14)
---

Or more detailed:

---
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E 
Gigabit Ethernet Controller (rev 14)
Subsystem: Marvell Technology Group Ltd. Unknown device 00ba
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: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at efbfc000 (64-bit, non-prefetchable) [size=16K]
Region 2: I/O ports at bf00 [size=256]
[virtual] Expansion ROM at efa00000 [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: 0000000000000000 Data: 0000
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 1
Link: Latency L0s <256ns, L1 unlimited
Link: ASPM Disabled RCB 128 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
---

Is this a simple case of unsupported new hardware (atm all devices are 
listed as unknown with lspci, IDs pending according to the lspci page), 
or is there something more sinister afoot? If any more information is 
required (I'm sure there is), I will do my best to provide it with my 
limited Linux knowledge.

Regards,

Christian

PS: Please CC me on reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/