kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #67785
[Bug 1269412] Re: via-rhine kernel module: PHY status 786d, resetting
I`ve been testing another Kernels, even 2.6.32 and the trouble is the same, so I think the problem is related to SystemD.
Some help?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269412
Title:
via-rhine kernel module: PHY status 786d, resetting
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
kernel version: 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:16:27 UTC 2013 i686 athlon i686 GNU/Linux
the mainboard is asus A8V-VM SE
if i receive for half hour at 100Mbit full speed with partimage the network card hangs and this is the dmesg output:
[ 2022.004060] WARNING: CPU: 0 PID: 3435 at /build/buildd/linux-3.11.0/net/sched/sch_generic.c:260 dev_watchdog+0x1ef/0x200()
[ 2022.004066] NETDEV WATCHDOG: eth1 (via-rhine): transmit queue 0 timed out
[ 2022.004069] Modules linked in: usblp pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables bridge stp llc snd_hda_codec_realtek snd_hda_intel ppdev snd_hda_codec rfcomm bnep bluetooth snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq nouveau nfsd binfmt_misc auth_rpcgss nfs_acl snd_seq_device nfs lockd sunrpc fscache mxm_wmi snd_timer wmi video snd serio_raw ttm k8temp soundcore drm_kms_helper drm i2c_viapro i2c_algo_bit parport_pc mac_hid asus_atk0110 shpchp lp parport hid_generic usbhid hid pata_acpi usb_storage via_rhine mii floppy pata_via sata_via
[ 2022.004162] CPU: 0 PID: 3435 Comm: firefox Tainted: GF O 3.11.0-15-generic #23-Ubuntu
[ 2022.004167] Hardware name: System manufacturer System Product Name/A8V-VM SE, BIOS 0702 05/21/2007
[ 2022.004171] 00000000 00000000 f580bec0 c1627228 f580bf00 f580bef0 c105267e c188f6cc
[ 2022.004182] f580bf1c 00000d6b c188f708 00000104 c1568a3f c1568a3f f68f0000 00000000
[ 2022.004193] 000691a5 f580bf08 c10526d3 00000009 f580bf00 c188f6cc f580bf1c f580bf40
[ 2022.004203] Call Trace:
[ 2022.004213] [<c1627228>] dump_stack+0x41/0x52
[ 2022.004222] [<c105267e>] warn_slowpath_common+0x7e/0xa0
[ 2022.004229] [<c1568a3f>] ? dev_watchdog+0x1ef/0x200
[ 2022.004235] [<c1568a3f>] ? dev_watchdog+0x1ef/0x200
[ 2022.004242] [<c10526d3>] warn_slowpath_fmt+0x33/0x40
[ 2022.004248] [<c1568a3f>] dev_watchdog+0x1ef/0x200
[ 2022.004260] [<c105d9ed>] call_timer_fn+0x2d/0xe0
[ 2022.004268] [<c14321fc>] ? scsi_finish_command+0xac/0x110
[ 2022.004277] [<c1437d10>] ? scsi_decide_disposition+0x180/0x1b0
[ 2022.004284] [<c10dd32c>] ? rcu_report_qs_rnp+0xac/0x110
[ 2022.004291] [<c1568850>] ? dev_deactivate_queue.constprop.35+0x50/0x50
[ 2022.004298] [<c105e8e9>] run_timer_softirq+0x179/0x220
[ 2022.004305] [<c1045128>] ? default_spin_lock_flags+0x8/0x10
[ 2022.004312] [<c1568850>] ? dev_deactivate_queue.constprop.35+0x50/0x50
[ 2022.004321] [<c10573f1>] __do_softirq+0xc1/0x1d0
[ 2022.004329] [<c1057330>] ? remote_softirq_receive+0xb0/0xb0
[ 2022.004332] <IRQ> [<c1057665>] ? irq_exit+0x95/0xa0
[ 2022.004344] [<c1635198>] ? smp_apic_timer_interrupt+0x38/0x50
[ 2022.004351] [<c162dbbc>] ? apic_timer_interrupt+0x34/0x3c
[ 2022.004356] ---[ end trace 031fe02290c75deb ]---
[ 2022.004525] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2026.004199] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2032.004214] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2036.004191] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2042.004188] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2048.004205] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2058.004197] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2068.004202] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2076.004214] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2082.004220] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2092.004204] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2102.004204] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2112.004198] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2122.004198] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2130.004192] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2140.004202] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2150.004206] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
[ 2160.004191] via-rhine 0000:00:12.0 eth1: Transmit timed out, status 0003, PHY status 786d, resetting...
modprobe -r and modprobe the module don't solve the problem, i must
reset the pc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269412/+subscriptions