From: Ben Hutchings <ben@decadent.org.uk>
To: Simon L'nu <simon.lnu@gmail.com>
Cc: 635770@bugs.debian.org, Daniele Venzano <venza@brownhat.org>,
netdev <netdev@vger.kernel.org>
Subject: TX watchdog warning for sis900
Date: Sun, 28 Aug 2011 21:38:24 +0100 [thread overview]
Message-ID: <1314563913.9176.55.camel@deadeye> (raw)
In-Reply-To: <CAPC6j9mg7vuOtVWQf-SyuQjaDQ3zD2Oz5AUFmP26S8CsHUw_0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
[Bug log is at <http://bugs.debian.org/635770>.]
On Tue, 2011-08-02 at 16:25 -0400, Simon L'nu wrote:
> On Sun, Jul 31, 2011 at 1:25 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Thu, 2011-07-28 at 13:42 -0400, Simon L'nu wrote:
> >> Package: linux-2.6
> >> Version: 3.0.0-1
> >> Severity: important
> >> Tags: experimental
> >>
> >> hi,
> >>
> >> so at random times, the driver will just oops with (below), and then the
> >> network just conks out, unable to do anything. when i remove it (modprobe -r) after bringing
> >> it down, and back up, it's extremely slow (see below kernel oops message).
> > [...]
> >
> > Did this happen with any previous version of the kernel package? What
> > is the last version where this did not happen?
> >
> > Ben.
> >
> >
>
> no, and only started happening recently. i also tried 2.6.39.2, and it
> started happening there. made me suspect an hardware or firmware
> issue. the PXE firmware option was enabled in BIOS (it's the built-in
> NIC).
Do you mean that you recently enabled PXE boot and that this has started
happening since then?
Ben.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
parent reply other threads:[~2011-08-28 20:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAPC6j9mg7vuOtVWQf-SyuQjaDQ3zD2Oz5AUFmP26S8CsHUw_0Q@mail.gmail.com>]
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=1314563913.9176.55.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=635770@bugs.debian.org \
--cc=netdev@vger.kernel.org \
--cc=simon.lnu@gmail.com \
--cc=venza@brownhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).