public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <disposable1@telefonica.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Weird SCSI subsystem behaviour (ISA related?????)
Date: Tue, 7 Sep 2004 13:50:03 +0200	[thread overview]
Message-ID: <20040907115003.GA1412@DervishD> (raw)

    Hi all :)

    I recently upgraded to 2.4.27 and finally remove ISA support
(CONFIG_ISA is now not set). This may be important because the kernel
threads named 'usb-storage-0' and 'scsi_eh_0' are both stuck in a
very high address, namely e086e736 and e086d279. But my ksyms says
this:

[...]
e086b944  scsi_hostlist                     [scsi_mod]
e086b948  scsi_devicelist                   [scsi_mod]
e086b94c  scsi_hosts                        [scsi_mod]
e086b964  scsi_dma_free_sectors             [scsi_mod]
e086b968  scsi_need_isa_buffer              [scsi_mod]

    As far as I can tell, this means that both kernel threads are
stuck somewhere in the code of 'scsi_need_isa_buffer'. Does this mean
that I must set CONFIG_ISA? If the answer is yes: then why
CONFIG_SCSI doesn't depend on CONFIG_ISA? Is all that not related to
ISA in any way (I suppose this is the correct answer) and the problem
is just that both threads are stuck in a wrong address caused by
only-god-knows?

    I use scsi for my card reader, that works without problem
usually. Right now I cannot test if the problem was a loose cable,
bad insertion of the card, etc. but anyway that shouldn't cause
kernel threads to get stuck...

    Thanks in advance :) If anyone wants additional info, just tell.
I'm going to reboot ASAP to see if this problem is persistent or if I
just had bad luck.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

                 reply	other threads:[~2004-09-07 11:48 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=20040907115003.GA1412@DervishD \
    --to=disposable1@telefonica.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