linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm2 Kernel panic, possibly network related
Date: Wed, 07 May 2003 12:10:40 +0200	[thread overview]
Message-ID: <3EB8DBA0.7020305@aitel.hist.no> (raw)
In-Reply-To: <20030506232326.7e7237ac.akpm@digeo.com>

2.5.69-mm1 is fine, 2.5.69-mm2 panics after a while even under very
light load.

Machine: 2.4GHz Pentium IV UP,
network card: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
video: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

Kernel config details:
UP, no module support, devfs, preempt, console on radeonfb

I got the OOPS this way:
boot normally (with X and network), switch to console
and log in, play nethack on the console until it oopses.
It will oops while in X too, but then there's nothing
visible to write down.

This is what I managed to write down. The first part scrolled
off screen with no scrollback - and no logfiles due to the
"not syncing" part:

<lost information>
ip_local_deliver
ip_local_deliver _finish
ip_recv_finish
ip_recv_finish
nf_hook_slow
ip_rcv_finish
ip_rcv
ip_rcv_finish
netif_receive_sub
process_backlog
net_rx_action
do_softirq
do_IRQ
default_idle
default_idle
common_interrupt
default_idle
default_idle
default_idle
cpu_idle
rest_init
start_kernel
unknown_bootoption
<0>Kernel panic: Fatal exception in interrupt
in interrupt handler - not syncing

Helge Hafting


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-05-07 10:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07  6:23 2.5.69-mm2 Andrew Morton
2003-05-07 10:10 ` Helge Hafting [this message]
2003-05-07 10:40   ` 2.5.69-mm2 Kernel panic, possibly network related David S. Miller
2003-05-07 10:49     ` Helge Hafting
2003-05-07  9:56       ` David S. Miller
2003-05-07 14:41         ` William Lee Irwin III, Helge Hafting
2003-05-07 13:40           ` David S. Miller
2003-05-07 21:54             ` Helge Hafting
2003-05-07 23:24               ` Ed Tomlinson
2003-05-08  1:38               ` William Lee Irwin III
2003-05-08  6:54                 ` Helge Hafting
2003-05-08  7:30                   ` Helge Hafting
2003-05-08  8:01                   ` William Lee Irwin III
2003-05-08 10:07                     ` William Lee Irwin III
2003-05-08 11:04                       ` Helge Hafting
2003-05-11 15:06                         ` William Lee Irwin III
2003-05-08 11:53                       ` Helge Hafting
2003-05-08 12:04                         ` Jens Axboe
2003-05-08 17:21                 ` David S. Miller
2003-05-08 21:34                   ` Ed Tomlinson
2003-05-08 21:53                     ` David S. Miller
2003-05-07 15:20           ` Steven Cole
2003-05-07 15:33             ` William Lee Irwin III
2003-05-09 12:57     ` Bill Davidsen
2003-05-07 12:06   ` William Lee Irwin III
     [not found] <fa.f4fihqc.4kq986@ifi.uio.no>
     [not found] ` <fa.clherio.l2of82@ifi.uio.no>
2003-05-10 12:18   ` Ed Tomlinson

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=3EB8DBA0.7020305@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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