From: Stephen Hemminger <stephen@networkplumber.org>
To: Chas Williams <chas@cmf.nrl.navy.mil>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Fw: [Bug 55951] New: usbatm BUG when killing pppd or br2684ctl
Date: Sat, 30 Mar 2013 17:06:01 -0700 [thread overview]
Message-ID: <20130330170601.621bda4f@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Fri, 29 Mar 2013 17:45:31 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 55951] New: usbatm BUG when killing pppd or br2684ctl
https://bugzilla.kernel.org/show_bug.cgi?id=55951
Summary: usbatm BUG when killing pppd or br2684ctl
Product: Networking
Version: 2.5
Kernel Version: 3.8.2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
AssignedTo: shemminger@linux-foundation.org
ReportedBy: jd.girard@sysnux.pf
Regression: Yes
Created an attachment (id=96631)
--> (https://bugzilla.kernel.org/attachment.cgi?id=96631)
Kernel BUG
The system is an alix2d2 acting as my Internet router through an USB ADSL modem
(DLink DSL200); xusbatm is driving the modem, but it needs a patched version of
usbatm (patch was written by Roman Kagan). I've been using this setup since
November 2011 (kernel 2.6.36 or 2.6.37), regularly updating the kernel without
trouble, so I think this is a regression.
The problem only occurs when killing pppd or br2684ctl (done in a script when
connection is lost), otherwise the system works fine:
[xxxxx@ix100 ~]$ uptime
14:34:36 up 9 days, 8:48, 1 user, load average: 0.20, 0.13, 0.14
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
reply other threads:[~2013-03-31 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130330170601.621bda4f@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=linux-atm-general@lists.sourceforge.net \
--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 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).