Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-12-19 Thread Julian Gilbey
reopen 681280 thanks Oh dear. Even with a patched kernel, it's started doing the same thing again. So even though this seemed to help, it's not actually fully fixed the problem :-/ It certainly seems to be the case, though, that this problem only appears when the computer is powered by

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-11-03 Thread Jonathan Nieder
Uwe Kleine-König wrote: On Mon, Oct 29, 2012 at 11:49:37PM -0700, Jonathan Nieder wrote: Uwe Kleine-König wrote: For DEBIAN_KERNEL_DISABLE_DEBUG it might even be worth to default to no debug packages and use -d to enable them?! Sounds sane. How about something like this? Looks good,

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-30 Thread Uwe Kleine-König
On Mon, Oct 29, 2012 at 04:50:30PM -0700, Jonathan Nieder wrote: Uwe Kleine-König wrote: It would be nice to get support for DEBIAN_KERNEL_USE_CCACHE and DEBIAN_KERNEL_DISABLE_DEBUG info test-patches. Hm, don't they work? I guess they do, but their existence isn't obvious for the random

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-30 Thread Jonathan Nieder
Uwe Kleine-König wrote: I guess they do, but their existence isn't obvious for the random Debian user who is willing to test a patch for us. For reference: the implied documentation bug is now filed at http://bugs.debian.org/691816 Something like this would be nice: $

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-30 Thread Julian Gilbey
On Mon, Oct 29, 2012 at 11:49:37PM -0700, Jonathan Nieder wrote: Sounds sane. How about something like this? Nice; one tiny suggestion: Index: debian/bin/test-patches === --- debian/bin/test-patches (révision 19472) +++

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-30 Thread Uwe Kleine-König
On Mon, Oct 29, 2012 at 11:49:37PM -0700, Jonathan Nieder wrote: Uwe Kleine-König wrote: I guess they do, but their existence isn't obvious for the random Debian user who is willing to test a patch for us. For reference: the implied documentation bug is now filed at

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-30 Thread Julian Gilbey
On Tue, Oct 30, 2012 at 10:46:29AM +0100, Uwe Kleine-König wrote: -eval set -- $(getopt -n $0 -- f:j:s: $@) +if [ -z ${DEBIAN_KERNEL_DISABLE_DEBUG+set} ]; then I don't know that construct, only :+, but + seems to do the same without me finding it in the manpage of neither bash nor dash. In

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-29 Thread Jonathan Nieder
Uwe Kleine-König wrote: It would be nice to get support for DEBIAN_KERNEL_USE_CCACHE and DEBIAN_KERNEL_DISABLE_DEBUG info test-patches. Hm, don't they work? Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-26 Thread Uwe Kleine-König
Hello, On Wed, Oct 24, 2012 at 10:52:48PM +0100, Julian Gilbey wrote: Oh, it just finished this time! I now understand why it took so long - the -dbg package is *huge*! It would be nice to get support for DEBIAN_KERNEL_USE_CCACHE and DEBIAN_KERNEL_DISABLE_DEBUG info test-patches. Best regards

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-25 Thread Jonathan Nieder
tags 681280 + upstream patch forwarded 681280 http://thread.gmane.org/gmane.linux.network/235795/focus=247154 quit Julian Gilbey wrote: Jonathan Nieder wrote: A 3.6.y kernel should be hitting experimental this weekend, or if you'd like to try the patch before then, see [1]. [...] Yes, that

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-25 Thread Julian Gilbey
On Wed, Oct 24, 2012 at 11:27:51PM +0100, Julian Gilbey wrote: The only interesting recent sky2 patch I can find upstream is v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How does a kernel with that patch applied behave? A 3.6.y kernel should be hitting experimental

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-24 Thread Julian Gilbey
On Sat, Oct 20, 2012 at 10:50:02PM -0700, Jonathan Nieder wrote: The only interesting recent sky2 patch I can find upstream is v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How does a kernel with that patch applied behave? A 3.6.y kernel should be hitting experimental

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-24 Thread Julian Gilbey
On Wed, Oct 24, 2012 at 10:42:53PM +0100, Julian Gilbey wrote: On Sat, Oct 20, 2012 at 10:50:02PM -0700, Jonathan Nieder wrote: The only interesting recent sky2 patch I can find upstream is v3.6-rc1~125^2~264 (sky2: Fix for interrupt handler, 2012-07-03). How does a kernel with that patch

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-24 Thread Julian Gilbey
On Sat, Oct 20, 2012 at 10:50:02PM -0700, Jonathan Nieder wrote: Jonathan Nieder wrote: Julian Gilbey wrote [regarding sky2 tx stalls]: I think this may be a hardware fault: I have now identified what appears to be the physical situation under which this bug manifests itself: it

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-20 Thread Julian Gilbey
On Tue, Jul 17, 2012 at 08:12:10AM +0100, Julian Gilbey wrote: On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote: I've had numerous occasions in at least the last month (from kernel 3.2.19-1 or earlier - that's as far back as my logs go) when my machine has given a kernel error

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-20 Thread Jonathan Nieder
Hi, Julian Gilbey wrote [regarding sky2 tx stalls]: I think this may be a hardware fault: I have now identified what appears to be the physical situation under which this bug manifests itself: it reliably occurs when I attempt to connect to an ethernet without my power supply connected

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-10-20 Thread Jonathan Nieder
Jonathan Nieder wrote: Julian Gilbey wrote [regarding sky2 tx stalls]: I think this may be a hardware fault: I have now identified what appears to be the physical situation under which this bug manifests itself: it reliably occurs when I attempt to connect to an ethernet without my power

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-07-17 Thread Julian Gilbey
On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote: I've had numerous occasions in at least the last month (from kernel 3.2.19-1 or earlier - that's as far back as my logs go) when my machine has given a kernel error when trying to connect to a Windows-driven ethernet. (I hadn't

Bug#681280: kernel warning at .../net/sched/sch_generic.c:255 dev_watchdog - eth0 (sky2) transmit queue 0 timed out

2012-07-17 Thread Julian Gilbey
On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote: I've had numerous occasions in at least the last month (from kernel 3.2.19-1 or earlier - that's as far back as my logs go) when my machine has given a kernel error when trying to connect to a Windows-driven ethernet. (I hadn't