From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, chris@linuxepos.com,
Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [Bugme-new] [Bug 9386] New: sis190 network driver crash
Date: Thu, 15 Nov 2007 11:58:41 -0800 [thread overview]
Message-ID: <20071115115841.30d43003.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9386-10286@http.bugzilla.kernel.org/>
On Thu, 15 Nov 2007 07:30:53 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9386
>
> Summary: sis190 network driver crash
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.23.1
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: chris@linuxepos.com
> CC: romieu@fr.zoreil.com
>
>
> I have a problem where I can lock up a number of machines by
> changing the link state on a sis190 Ethernet port. For example, during
> a data transfer such as FTP if I unplug the Ethernet cable and plug it
> back in, the Ethernet interface will stop responding and the machine
> will lock up after a minute or so. This behaviour is repeatable. I have the
> sis190 driver loaded as a module.
>
> I haven't found a kernel version where this doesn't happen. It happens with
> kernel 2.6.20.15, for example.
>
next parent reply other threads:[~2007-11-15 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9386-10286@http.bugzilla.kernel.org/>
2007-11-15 19:58 ` Andrew Morton [this message]
2007-11-15 23:00 ` [Bugme-new] [Bug 9386] New: sis190 network driver crash David Miller
2007-11-15 23:36 ` Francois Romieu
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=20071115115841.30d43003.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=chris@linuxepos.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).