From: Thibault Roulet <tr@omch.ch>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Diego Giagio <diego@giagio.com>,
647513@bugs.debian.org, netdev <netdev@vger.kernel.org>
Subject: Bug#647513: TX watchdog fires for ipheth after phone upgraded to iOS 5
Date: Thu, 03 Nov 2011 16:09:31 +0100 [thread overview]
Message-ID: <4EB2AEAB.6010603@omch.ch> (raw)
In-Reply-To: <1320331171.3079.31.camel@deadeye>
On 11/03/2011 03:39 PM, Ben Hutchings wrote:
> On Thu, 2011-11-03 at 14:52 +0100, darx wrote:
>> Package: linux-2.6
>> Version: 3.0.0-3
>> Severity: important
>> Tags: upstream
>>
>> Hi,
>>
>> After IOS5 update on my iphone when I plug it on my Debian, it crashes.
>
> No it doesn't.
well, "crash" is a bit strong. It looks like a kernel hickups
>
>> As I'm using it as a modem it's quite problematic.
>>
>>
>> Nov 3 14:16:51 thib kernel: [ 371.824017] ------------[ cut here
>> ]------------
>> Nov 3 14:16:51 thib kernel: [ 371.824024] WARNING: at /build/buildd-
>> linux-2.6_3.0.0-3-amd64-9ClimQ/linux-2.6-3.0.0/debian/build/source_amd64_none/net/sched/sch_generic.c:255
>> dev_watchdog+0xe9/0x148()
>> Nov 3 14:16:51 thib kernel: [ 371.824027] Hardware name: OptiPlex 780
>> Nov 3 14:16:51 thib kernel: [ 371.824029] NETDEV WATCHDOG: eth1 (ipheth):
>> transmit queue 0 timed out
> [...]
>
> Diego, please can you investigate this.
>
Oh and I can add that I tested on this DELL Optiplex 780 machine and also a small HP mini 5101 laptop (same debian
version). Same error.
Thanks
Thib
prev parent reply other threads:[~2011-11-03 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111103135222.3555.69704.reportbug@thib.infomaniak.ch>
2011-11-03 14:39 ` TX watchdog fires for ipheth after phone upgraded to iOS 5 Ben Hutchings
2011-11-03 15:09 ` Thibault Roulet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB2AEAB.6010603@omch.ch \
--to=tr@omch.ch \
--cc=647513@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=diego@giagio.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.