i'm experiencing this bug with my "ACER Aspire Easystore H340" running
ubuntu natty.

this happens after the box switches to UP code (i do not know if this is
actually related, but i notice that it *always* happens after the
switch).

please find the syslog file attached.

cheers,
raoul

excerpt from /var/log/syslog:

Apr  9 12:12:53 media kernel: [ 2356.741312] CPU 1 is now offline
Apr  9 12:12:53 media kernel: [ 2356.741323] SMP alternatives: switching to UP 
code
Apr  9 12:12:54 media kernel: [ 2357.383713] EXT4-fs (sda1): re-mounted. Opts: 
errors=remount-ro,commit=600
Apr  9 12:12:54 media kernel: [ 2357.392752] EXT4-fs (dm-0): re-mounted. Opts: 
errors=remount-ro,commit=600
Apr  9 12:12:54 media kernel: [ 2357.443081] WARNING! power/level is 
deprecated; use power/control instead
Apr  9 12:12:57 media kernel: [ 2360.420810] sky2 0000:09:00.0: eth0: Link is 
up at 100 Mbps, full duplex, flow control both
Apr  9 12:17:01 media CRON[27193]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Apr  9 12:19:15 media kernel: [ 2739.050015] ------------[ cut here 
]------------
Apr  9 12:19:15 media kernel: [ 2739.050033] WARNING: at 
/build/buildd/linux-2.6.38/net/sched/sch_generic.c:256 
dev_watchdog+0x2a0/0x2b0()
Apr  9 12:19:15 media kernel: [ 2739.050040] Hardware name: Aspire easyStore 
H340 
Apr  9 12:19:15 media kernel: [ 2739.050046] NETDEV WATCHDOG: eth0 (sky2): 
transmit queue 0 timed out
Apr  9 12:19:15 media kernel: [ 2739.050050] Modules linked in: ufs qnx4 
hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs dm_crypt 
psmouse serio_raw dme1737 hwmon_vid coretemp lp parport raid10 raid1 raid0 
multipath linear btrfs zlib_deflate libcrc32c raid456 async_pq async_xor xor 
async_memcpy async_raid6_recov raid6_pq async_tx usb_storage pata_marvell uas 
i915 ahci drm_kms_helper libahci sky2 drm i2c_algo_bit video
Apr  9 12:19:15 media kernel: [ 2739.050140] Pid: 0, comm: swapper Not tainted 
2.6.38-7-server #39-Ubuntu
Apr  9 12:19:15 media kernel: [ 2739.050145] Call Trace:
Apr  9 12:19:15 media kernel: [ 2739.050150]  <IRQ>  [<ffffffff81065d1f>] ? 
warn_slowpath_common+0x7f/0xc0
Apr  9 12:19:15 media kernel: [ 2739.050170]  [<ffffffff81065e16>] ? 
warn_slowpath_fmt+0x46/0x50
Apr  9 12:19:15 media kernel: [ 2739.050179]  [<ffffffff81500e80>] ? 
dev_watchdog+0x2a0/0x2b0
Apr  9 12:19:15 media kernel: [ 2739.050189]  [<ffffffff81013a79>] ? 
sched_clock+0x9/0x10
Apr  9 12:19:15 media kernel: [ 2739.050198]  [<ffffffff8108e318>] ? 
sched_clock_cpu+0xa8/0x110
Apr  9 12:19:15 media kernel: [ 2739.050206]  [<ffffffff81500be0>] ? 
dev_watchdog+0x0/0x2b0
Apr  9 12:19:15 media kernel: [ 2739.050216]  [<ffffffff81074614>] ? 
call_timer_fn+0x44/0x130
Apr  9 12:19:15 media kernel: [ 2739.050224]  [<ffffffff81500be0>] ? 
dev_watchdog+0x0/0x2b0
Apr  9 12:19:15 media kernel: [ 2739.050233]  [<ffffffff81075c64>] ? 
run_timer_softirq+0x134/0x280
Apr  9 12:19:15 media kernel: [ 2739.050243]  [<ffffffff8102c58d>] ? 
lapic_next_event+0x1d/0x30
Apr  9 12:19:15 media kernel: [ 2739.050252]  [<ffffffff8106d398>] ? 
__do_softirq+0xa8/0x1c0
Apr  9 12:19:15 media kernel: [ 2739.050261]  [<ffffffff81097c3f>] ? 
tick_program_event+0x1f/0x30
Apr  9 12:19:15 media kernel: [ 2739.050270]  [<ffffffff8100cedc>] ? 
call_softirq+0x1c/0x30
Apr  9 12:19:15 media kernel: [ 2739.050278]  [<ffffffff8100ea05>] ? 
do_softirq+0x65/0xa0
Apr  9 12:19:15 media kernel: [ 2739.050286]  [<ffffffff8106d5b5>] ? 
irq_exit+0x85/0x90
Apr  9 12:19:15 media kernel: [ 2739.050295]  [<ffffffff815df670>] ? 
smp_apic_timer_interrupt+0x70/0x9b
Apr  9 12:19:15 media kernel: [ 2739.050304]  [<ffffffff8100c993>] ? 
apic_timer_interrupt+0x13/0x20
Apr  9 12:19:15 media kernel: [ 2739.050310]  <EOI>  [<ffffffff813353ca>] ? 
intel_idle+0xca/0x120
Apr  9 12:19:15 media kernel: [ 2739.050326]  [<ffffffff813353a9>] ? 
intel_idle+0xa9/0x120
Apr  9 12:19:15 media kernel: [ 2739.050336]  [<ffffffff814b5f3a>] ? 
cpuidle_idle_call+0xaa/0x1b0
Apr  9 12:19:15 media kernel: [ 2739.050347]  [<ffffffff8100a266>] ? 
cpu_idle+0xa6/0xf0
Apr  9 12:19:15 media kernel: [ 2739.050356]  [<ffffffff815ba335>] ? 
rest_init+0x75/0x80
Apr  9 12:19:15 media kernel: [ 2739.050365]  [<ffffffff81ae1c90>] ? 
start_kernel+0x3f5/0x400
Apr  9 12:19:15 media kernel: [ 2739.050374]  [<ffffffff81ae1388>] ? 
x86_64_start_reservations+0x132/0x136
Apr  9 12:19:15 media kernel: [ 2739.050383]  [<ffffffff81ae145d>] ? 
x86_64_start_kernel+0xd1/0xe0
Apr  9 12:19:15 media kernel: [ 2739.050390] ---[ end trace d435fbd2dc4262db 
]---
Apr  9 12:19:15 media kernel: [ 2739.050398] sky2 0000:09:00.0: eth0: tx timeout
Apr  9 12:19:15 media kernel: [ 2739.050492] sky2 0000:09:00.0: eth0: transmit 
ring 58 .. 17 report=58 done=58
Apr  9 12:19:19 media kernel: [ 2742.408382] sky2 0000:09:00.0: eth0: Link is 
up at 100 Mbps, full duplex, flow control both

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/488153/+attachment/2005253/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/488153

Title:
  NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to