netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	bluesloth600@gmail.com
Subject: Re: [Bugme-new] [Bug 11855] New: kernel BUG when bringing down ppp connection
Date: Mon, 27 Oct 2008 20:24:07 -0700	[thread overview]
Message-ID: <20081027202407.7e390191.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11855-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sat, 25 Oct 2008 17:34:16 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=11855
> 
>            Summary: kernel BUG when bringing down ppp connection
>            Product: Networking
>            Version: 2.5
>      KernelVersion: 2.6.27.3
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Other
>         AssignedTo: acme@ghostprotocols.net
>         ReportedBy: bluesloth600@gmail.com
> 
> 
> Latest working kernel version: 2.6.26.6
> Earliest failing kernel version: 2.6.27

A regression.

> Distribution: Debian sid
> Hardware Environment: Dell Inspiron 1721, AMD x86-64 SMP
> Software Environment:
> Gnu C                  4.3.2
> Gnu make               3.81
> binutils               2.18.0.20080103
> util-linux             2.13.1.1
> mount                  2.13.1.1
> module-init-tools      found
> Linux C Library        2.7
> Dynamic linker (ldd)   2.7
> Procps                 3.2.7
> Console-tools          0.2.3
> Sh-utils               6.10
> udev                   125
> 
> Problem Description: I connect to my dialup service with a Zoom model 3048
> modem connected via a Radio Shack 26-183 USB/serial converter cable.  When I
> log off (using poff), sometimes it works perfectly, but usually after the modem
> disconnects I get:
> 
> kernel BUG at drivers/char/tty_ldisc.c:199!
> invalid opcode: 0000 [1] PREEMPT SMP
> CPU 1

This has an Alany feel to it?

> and then 12 screenfuls of stack traces and stuff, with a bunch of "scheduling
> while atomic" BUGs.. none of it ever managed to get in any logs, so I'll be
> attaching photos of the screen.
> 
> At this point, sometimes the magic SysRq key combinations work, but usually
> they don't, and I have to just turn the computer off.
> 
> I reproduced this with 2.6.27.2 and 2.6.27.3, and then with 2.6.27 using a
> configuration closer to the one I use for 2.6.26.6.
> 
> I set the severity to high because this makes 2.6.27 unusable for me.
> 
> Steps to reproduce: hmm, guess I already said that.

Additional details are attached to the bugzilla report.

       reply	other threads:[~2008-10-28  3:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11855-10286@http.bugzilla.kernel.org/>
2008-10-28  3:24 ` Andrew Morton [this message]
2008-10-28  9:44   ` [Bugme-new] [Bug 11855] New: kernel BUG when bringing down ppp connection Alan Cox
2008-10-29 11:16     ` Jason Cassell

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=20081027202407.7e390191.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bluesloth600@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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).