mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>,
	Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [2.2.17] yes: oops again in /proc/scsi/scsi
Date: Mon, 27 Nov 2000 15:26:35 +0100	[thread overview]
Message-ID: <20001127152635.K18517@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <20001122020618.A1411@emma1.emma.line.org> <20001123010712.C32555@garloff.etpnet.phys.tue.nl> <20001127091005.A2973@emma1.emma.line.org>
In-Reply-To: <20001127091005.A2973@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Mon, Nov 27, 2000 at 09:10:05AM +0100

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]

On Mon, Nov 27, 2000 at 09:10:05AM +0100, Matthias Andree wrote:
> My previous mail was a tad too early. After I moved the bus back to the
> Tekram DC-390U (sym53c8xx driver), I caught an oops again, and
> rescan-scsi-bus.sh caught a SIGSEGV. There seems to be a kernel bug somewhere
> in that SCSI handling stuff:
> 
> Unable to handle kernel NULL pointer dereference at virtual address 00000052
> current->tss.cr3 = 07106000, %%cr3 = 07106000
> *pde = 00000000
> Oops: 0002
> CPU:    0
> EIP:    0010:[sr_finish+112/388]
> EFLAGS: 00010206
> eax: 00000000   ebx: 00000054   ecx: 00000005   edx: c7f9cc00
> esi: c629bd50   edi: c7f9cc40   ebp: 00000001   esp: c629bd3c
> ds: 0018   es: 0018   ss: 0018
> Process rescan-scsi-bus (pid: 2846, process nr: 23, stackpage=c629b000)
> Stack: 00000000 c7f88340 c02a9960 c629bd4c 00307273 c01fedaf c7f88700 c7555de0
>        c629becc c01fedf3 00000000 00000000 c7f88340 00000000 c6e132c0 c02cb0e0
>        c6e132c8 c0132793 c6e132c0 c629bda4 c629bda4 c0001a00 00020000 c63532c0
> Call Trace: [scan_scsis+491/1076] [scan_scsis+559/1076] [get_new_inode+147/312] [iget4+121/132] [vsprintf+720/764] [wake_up_process+64/76] [__wake_up+59/68]
> Code: 80 48 52 20 a1 8c 99 2a c0 80 4c 18 16 08 a1 8c 99 2a c0 80
> Using defaults from ksymoops -t elf32-i386 -a i386

This time, I do not suspect the low-level driver. It mey very well be, that
there's a subtile bug WRT add/remove-single-device housekeeping in the SCSI
layer.
You told that you did parallel rescan-scsi-bus.sh calls. That may have
confused the kernel. Did the above oops happen without such abuse?

Regards,
-- 
Kurt Garloff                   <kurt@garloff.de>         [Eindhoven, NL]
Physics: Plasma simulations <k.garloff@phys.tue.nl>   [TU Eindhoven, NL]
Linux: SCSI, Security          <garloff@suse.de>   [SuSE Nuernberg, FRG]
 (See mail header or public key servers for PGP2 and GPG public keys.)

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2000-11-27 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  1:06 [2.2.17] oops " Matthias Andree
2000-11-23  0:07 ` Kurt Garloff
2000-11-27  7:57   ` Matthias Andree
2000-11-27 14:22     ` Kurt Garloff
2000-11-27  8:10   ` [2.2.17] yes: oops again " Matthias Andree
2000-11-27 14:26     ` Kurt Garloff [this message]

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=20001127152635.K18517@garloff.etpnet.phys.tue.nl \
    --to=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    /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

all inboxes | Powered by JetHome®