I tested with 2.6.37-rc3.
Nothing changes. Still the same kind of crashes. I also played with all
combinations of ACPI and APM but no change.
I searched a while and noticed the error already exists:
Bug#454747
Bug#11663
Bug#584724
As pointed out though, the original scheduling while atomics oops o
Network just crashed again.
I will compile/install the new kernel first and try copying again.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cf13f71.2030...@gmx
> I think that is needed. If it works with mainline kernel then we can
> start looking for the patch that fixed it. If it doesn't work then you
> can report the bug upstream.
I guess I will then. Thanks for sharing. Nice to know, there are others
with the same rare issues.
Marcel
--
To UNSUB
Marcel Langner writes:
> Does a report exists for this transmit timeout problem already?
I don't know. I have hit the issue only twice and it is difficult to
debug so I did not report it yet.
> No I have not. Do you think it makes sense to try it? It's a long time
> since I compiled my own kerne
Marcel Langner writes:
> Bug seems to exist for a long time now. Should be fixed before Squeeze
> gets out officially!
1) Are the "scheduling while atomic" and "transmit timed out"
different bugs?
2) Have you tried if this occurs with mainline kernel from kernel.org?
I have a geode box with
$
dmesg output
[ 861.86] WARNING: at
/build/buildd-linux-2.6_2.6.32-27-i386-c5N4Hf/linux-2.6-2.6.32/debian/build/source_i386_none/net/sched/sch_generic.c:261
dev_watchdog+0xdb/0x170()
[ 861.000115] NETDEV WATCHDOG: eth1 (via-rhine): transmit queue 0 timed out
[ 861.000129] Modules linked in:
6 matches
Mail list logo
