public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben@splentec.com>
To: nahshon@actcom.co.il, Marcelo Tosatti <marcelo@conectiva.com.br>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Fwd: Patch - SCSI host numbers - please apply
Date: Tue, 18 Jun 2002 17:18:16 -0400	[thread overview]
Message-ID: <3D0FA398.8DA6C959@splentec.com> (raw)
In-Reply-To: 200206181514.52827.nahshon@actcom.co.il

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

Itai,

After applying your patch to 2.4.18, I see the following
problems:

1. ide-scsi does NOT work. /proc/scsi/scsi shows NO
   devices and /proc/scsi/ide-scsi is empty.

2. /proc/scsi/{scsi, ide-scsi, scsi_test} are all empty!

3. After ``rmmod scsi_test'' and ``ls /proc/scsi''
   the kernel OOPS-es.

NONE of those problems exist with a non-patched kernel.

I used kernel 2.4.18, but doubt there'd difference for
2.5.x since the host_no stuff hasn't changed (2.5.22).

I've attached the OOPS and the tgz of my testing
module scsi_test.o.

Interested parties: this is in regards to the
scsi subsystem assigning _repeating_ host numbers
to hosts registered! See my message 
``/proc/scsi/driver/hosts with same numeric???''
dated 2002/05/29 on linux-scsi ML.

To repeat the problem:
$ insmod scsi_reg.o
$ rmmod scsi_reg
$ insmod scsi_req.o MaxHosts=20
$ ls /proc/scsi/scsi_test

Voila!

Here is the OOPS:
----------------------------
Jun 18 16:49:23 canoe kernel: Unable to handle kernel paging request at virtual address e5a59010
Jun 18 16:49:23 canoe kernel:  printing eip:
Jun 18 16:49:23 canoe kernel: c0150c68
Jun 18 16:49:23 canoe kernel: *pde = 1d58c067
Jun 18 16:49:23 canoe kernel: *pte = 00000000
Jun 18 16:49:23 canoe kernel: Oops: 0002
Jun 18 16:49:23 canoe kernel: CPU:    0
Jun 18 16:49:23 canoe kernel: EIP:    0010:[proc_get_inode+152/256]    Not tainted
Jun 18 16:49:23 canoe kernel: EIP:    0010:[<c0150c68>]    Not tainted
Jun 18 16:49:23 canoe kernel: EFLAGS: 00010286
Jun 18 16:49:23 canoe kernel: eax: e5a59000   ebx: dc921880   ecx: 00000001   edx: 00000003
Jun 18 16:49:23 canoe kernel: esi: dc337c80   edi: dc9218d5   ebp: dc06e600   esp: dc31de4c
Jun 18 16:49:23 canoe kernel: ds: 0018   es: 0018   ss: 0018
Jun 18 16:49:23 canoe kernel: Process ls (pid: 1151, stackpage=dc31d000)
Jun 18 16:49:23 canoe kernel: Stack: dff83800 dc06e665 c0152721 dff83800 000011bb dc921880 ffffffea
00000000 
Jun 18 16:49:23 canoe kernel:        dc62f400 c0145569 c1787100 000001f0 dc06e600 fffffff4 dc660580
dc62f400 
Jun 18 16:49:23 canoe kernel:        c013cc33 dc660580 dc06e600 dc31df64 00000000 dc660580 dc31df9c
c013d3ec 
Jun 18 16:49:23 canoe kernel: Call Trace: [proc_lookup+161/176] [d_alloc+25/368]
[real_lookup+163/208] [link_path_walk+1708/2000] [filldir64+239/352] 
Jun 18 16:49:23 canoe kernel: Call Trace: [<c0152721>] [<c0145569>] [<c013cc33>] [<c013d3ec>]
[<c014132f>] 
Jun 18 16:49:23 canoe kernel:    [do_page_fault+764/1239] [getname+109/176] [__user_walk+58/80]
[sys_lstat64+20/112] [error_code+52/60] [system_call+51/56] 
Jun 18 16:49:23 canoe kernel:    [<c011431c>] [<c013c90d>] [<c013d8ca>] [<c013a804>] [<c010705c>]
[<c0106f6b>] 
Jun 18 16:49:23 canoe kernel: 
Jun 18 16:49:23 canoe kernel: Code: ff 40 10 8b 43 24 83 48 14 18 8b 43 18 85 c0 74 06 89 86 88
------------------------------------

-- 
Luben

[-- Attachment #2: scsi_reg.tar.gz --]
[-- Type: application/x-gzip, Size: 1480 bytes --]

       reply	other threads:[~2002-06-18 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200206171604.57115.nahshon@actcom.co.il>
     [not found] ` <3D0E4F4F.1D3D68B3@splentec.com>
     [not found]   ` <200206181514.52827.nahshon@actcom.co.il>
2002-06-18 21:18     ` Luben Tuikov [this message]
2002-06-19  0:03       ` Fwd: Patch - SCSI host numbers - please apply Itai Nahshon
2002-06-19 16:26         ` Luben Tuikov

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=3D0FA398.8DA6C959@splentec.com \
    --to=luben@splentec.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=nahshon@actcom.co.il \
    /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