From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: alangrimes@starpower.net
Subject: [Bugme-new] [Bug 1893] New: running Mozilla's update routine causes kernel oops, reliably! (fwd)
Date: Fri, 16 Jan 2004 14:44:21 -0800 [thread overview]
Message-ID: <22640000.1074293061@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=1893
Summary: running Mozilla's update routine causes kernel oops,
reliably!
Kernel Version: 2.6.1
Status: NEW
Severity: normal
Owner: acme@conectiva.com.br
Submitter: alangrimes@starpower.net
Distribution: N/A, _VERY_ old installation, mostly a source distro at this point
in time.
Hardware Environment: Athlon SMP, 1gb of ECC ram, (ECC enabled).
Software Environment: ppp 2.4.1, mozilla.
Problem Description: updating mozilla causes dialup connection to drop + kernel
oops,
Steps to reproduce:
1. I beleive that this is a SMP related bug related to the recient preemptive
kernel enhancements...
2. it might be in either the kernel "softirq.c" file or the ppp driver, I don't
know which.
3. I'm using wvdial to dial the modem.
4. I run, in the mozilla source directory, "gmake client.mk checkout" as per the
instructions. This command runs a while then stalls.
5. soon thereafter I get a "peer not responding" error in the wvdial window
associated with this kernel oops:
Badness in local_bh_enable at kernel/softirq.c:121
Call Trace:
[<c012c6dc>] local_bh_enable+0x8c/0x90
[<c02a3f69>] ppp_async_push+0xb9/0x1a0
[<c02a384e>] ppp_asynctty_wakeup+0x2e/0x70
[<c026faa4>] uart_flush_buffer+0x84/0x90
[<c02503ee>] do_tty_hangup+0x40e/0x4b0
[<c0250534>] disassociate_ctty+0x64/0x210
[<c012aa44>] do_exit+0x2b4/0x450
[<c012acb2>] do_group_exit+0x42/0xe0
[<c010b59b>] syscall_call+0x7/0xb
6. this problem is extremely reproducable.
7. versions:
bash-2.05$ ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux (none) 2.6.1 #2 SMP Sun Jan 11 12:30:36 EST 2004 i686 unknown unknown GNU/
Linux
Gnu C 3.3.2
Gnu make 3.79.1
util-linux 2.11n
mount 2.11n
module-init-tools 0.9.14
e2fsprogs 1.26
jfsutils 1.0.15
reiserfsprogs 3.6.9
pcmcia-cs 3.1.31
nfs-utils 0.3.3
Linux C Library 2.3.2
Dynamic linker (ldd) 2.3.2
Linux C++ Library 5.0.5
Procps 2.0.7
Net-tools 1.60
Kbd 1.08
Sh-utils 5.0
bash-2.05$
reply other threads:[~2004-01-16 22:44 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=22640000.1074293061@flay \
--to=mbligh@aracnet.com \
--cc=alangrimes@starpower.net \
--cc=linux-kernel@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