[please cc:, I am not a subscriber]
Hello,
I recently tried 2.6.0-test1, 2.6.0-test2, 2.4.22-pre6 and 2.4.22-pre8,
and via-rhine seems broken in all of them. Network connection doesn't
work, and only the timeout messages appear:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.
2.4.21 still works fine.
lspci -v:
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge
Subsystem: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge
Flags: bus master, 66Mhz, medium devsel, latency 8
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00
[Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: e0000000-e1ffffff
Prefetchable memory behind bridge: d8000000-dfffffff
Capabilities: [80] Power Management version 2
00:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
Subsystem: Creative Labs CT4850 SBLive! Value
Flags: bus master, medium devsel, latency 32, IRQ 18
I/O ports at a000 [size=32]
Capabilities: [dc] Power Management version 1
00:0c.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
(rev 08)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32
I/O ports at a400 [size=8]
Capabilities: [dc] Power Management version 1
00:0d.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at e3001000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
00:0d.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at e3000000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
00:0e.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
Subsystem: Triones Technologies, Inc.: Unknown device 0001
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 17
I/O ports at a800 [size=8]
I/O ports at ac00 [size=4]
I/O ports at b000 [size=8]
I/O ports at b400 [size=4]
I/O ports at b800 [size=256]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
00:0e.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
Subsystem: Triones Technologies, Inc.: Unknown device 0001
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 17
I/O ports at bc00 [size=8]
I/O ports at c000 [size=4]
I/O ports at c400 [size=8]
I/O ports at c800 [size=4]
I/O ports at cc00 [size=256]
Capabilities: [60] Power Management version 2
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00
[UHCI])
Subsystem: Unknown device 1695:3005
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00
[UHCI])
Subsystem: Unknown device 1695:3005
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00
[UHCI])
Subsystem: Unknown device 1695:3005
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if
20 [EHCI])
Subsystem: Unknown device 1695:3005
Flags: bus master, medium devsel, latency 32, IRQ 19
Memory at e3002000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus
Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: Unknown device 1695:3005
Flags: bus master, medium devsel, latency 32
I/O ports at dc00 [size=16]
Capabilities: [c0] Power Management version 2
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 74)
Subsystem: Unknown device 1695:3005
Flags: bus master, medium devsel, latency 32, IRQ 23
I/O ports at e000 [size=256]
Memory at e3003000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2
MX/MX 400] (rev b2) (prog-if 00 [VGA])
Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 16
Memory at e0000000 (32-bit, non-prefetchable) [size=16M]
Memory at d8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
--
Jindrich Makovicka
On Mon, 28 Jul 2003 14:22:58 +0200, Jindrich Makovicka wrote:
> I recently tried 2.6.0-test1, 2.6.0-test2, 2.4.22-pre6 and 2.4.22-pre8,
> and via-rhine seems broken in all of them. Network connection doesn't
> work, and only the timeout messages appear:
Does that mean no traffic at all? No ping, no nothing?
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
> eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.
>
> 2.4.21 still works fine.
Same .config? Is APIC and/or ACPI enabled? Are you running half-duplex?
What other modules do you loaded?
Roger
Hello!
i had the same problem.
It works fine if ACPI is diabled.
I have IO-APIC enabled.
Regards, claas
Hello,
> 2.4.21 still works fine.
I do have watchdog complaints (no resets) with 2.4.21 too. I do not have
access to the box atm, but I suspect NFS since I did experience I/O
errors on copying large files (there was a discussion on lkml about NFS
problems, but I have not followed it)
regards
Stefan