public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@pobox.com>
To: J Sloan <jjs@lexus.com>
Cc: Robert Love <rml@tech9.net>, Linux kernel <linux-kernel@vger.kernel.org>
Subject: preempt-patch cleared of blame
Date: Wed, 07 Nov 2001 19:48:08 -0800	[thread overview]
Message-ID: <3BEA0078.F938623B@pobox.com> (raw)
In-Reply-To: <3BE8B460.A23E1A67@pobox.com> <1005109646.884.0.camel@phantasy> <3BE9A506.82D64AE4@lexus.com>

Hi All,

I'd reported a disaster with 2.4.14+preempt,
but I have just reproduced it with 2.4.14
vanilla - (to recap, "dbench 16" hangs the
system hard, it doesn't even respond to
pings, and must be power cycled)

Again, since I am seeing the problem with
2.4.14 vanilla, the preempt patch is NOT at
fault here -

However I am concerned with this latest
twist, as I want linux to be extremely stable,
and this sort of thing is discouraging.

I think there may be a problem with the
compaq smart/2p raid drivers, since
the "do_ida_intr" code keeps showing
up in the oops, and I have not seen a
problem with 2.4.14 on any other system.

I am going to try and reproduce the oops
elsewhere, and hopefuly I will not be able
to - in any event, the oops follows:

Compaq 6500
4XPPRO 200
1.2 GB RAM
compaq "smart" raid controller

-----------------------------------------------------------

ksymoops 2.4.1 on i686 2.4.14.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.14/ (default)
     -m /boot/System.map-2.4.14 (default)

case login: Unable to handle kernel NULL pointer dereference at virtual
address
00000000
*pde = 00000000
Oops: 0000
CPU:    3
EIP:    0010:[<00000000>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010082
eax: f1c29480   ebx: f1ec17e0   ecx: 00000001   edx: f0509540
esi: f7b93fc4   edi: f7bb7000   ebp: 00000001   esp: f569de80
ds: 0018   es: 0018  ss: 0018
Process dbench (pid:1360, stackpage=f569d000)
Stack: c0182b3f f1c29480 00000001 00000012 00004812 00178a3c 00001000
c1abb7c0
       f7bc2ca0 00000003 24000001 0000000b c01089d4 0000000b f7bb7000
f569def8
       f569def8 c0298960 0000000b 00000003 c01089d4 0000000b f569def8
f7bc2ca0
Call Trace:  [<c0182b3f>] [<c01087ce>] [<c01089d4>] [<c0120018>]
[<c0127631>]
[<c0133266>] [<c0132dd0>] [<c0132fce>] [<c0106f66>]
Code: Bad EIP Value.

>>EIP; 00000000 Before first symbol
Trace; c0182b3f <do_ida_intr+20f/280>
Trace; c01087ce <handle_IRQ_event+5e/90>
Trace; c01089d4 <do_IRQ+a4/f0>
Trace; c0120018 <exec_usermodehelper+38/400>
Trace; c0127631 <generic_file_write+4e1/610>
Trace; c0133266 <sys_write+96/d0>
Trace; c0132dd0 <generic_file_llseek+0/b0>
Trace; c0132fce <sys_lseek+be/d0>
Trace; c0106f66 <system_call+2e/38>

 <0> Kernel panic: Aiee, killing interrupt handler!






  parent reply	other threads:[~2001-11-08  3:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07  4:11 disaster with 2.4.14+preempt J Sloan
2001-11-07  5:07 ` Robert Love
2001-11-07  6:52   ` J Sloan
2001-11-07 21:17   ` J Sloan
2001-11-07 22:30     ` Robert Love
2001-11-08  3:48     ` J Sloan [this message]
2001-11-08 10:36       ` preempt-patch cleared of blame Jens Axboe
2001-11-08 12:23         ` Ingo Molnar
2001-11-08 11:38           ` Jens Axboe
2001-11-08 11:41             ` [patch] cciss dequeue race fix (was Re: preempt-patch cleared of blame) Jens Axboe
2001-11-08 12:05             ` AMD761Agpgart+Radeon64DDR+kernel+2.4.14...no go Cyrus
2001-11-08 17:14               ` Robert Love
2001-11-09  0:45                 ` David S. Miller
2001-11-08 22:04               ` Jussi Laako
2001-11-08 23:28                 ` Alan Cox
2001-11-09 21:04                   ` Jussi Laako
2001-11-15 23:25                     ` Stephen C. Tweedie
2001-11-11  7:59             ` AMD761Agpgart+Radeon64DDR+kernel+2.4.15-pre2...still testing Cyrus
2001-11-09  1:35         ` Success with 2.4.14 on Compaq 6500 J Sloan

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=3BEA0078.F938623B@pobox.com \
    --to=jjs@pobox.com \
    --cc=jjs@lexus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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