aic7xxx dump_card_state not reentrant?

aic7xxx dump_card_state not reentrant?

[random1]

I'm trying to get suspend and resume working for a 2.4 kernel with
scsi devices, and I'm running into trouble saving and restoring the
card state.  One thing that I've discovered in the process of looking
into this is that the ahc_dump_card_state routine is called at both
process level and interrupt level.  If I read it correctly, it alters
the card state while dumping the list of SCBs.  If a sequencer
interrupt occurs in the meantime, bad stuff happens.  Doesn't it?
Well, I'm seeing panics in which ahc_dump_card_state is running in
both contexts "simultaneously."

Re: aic7xxx dump_card_state not reentrant?

[Justin T. Gibbs]

> I'm trying to get suspend and resume working for a 2.4 kernel with
> scsi devices, and I'm running into trouble saving and restoring the
> card state.  One thing that I've discovered in the process of looking
> into this is that the ahc_dump_card_state routine is called at both
> process level and interrupt level.  If I read it correctly, it alters
> the card state while dumping the list of SCBs.  If a sequencer
> interrupt occurs in the meantime, bad stuff happens.  Doesn't it?
> Well, I'm seeing panics in which ahc_dump_card_state is running in
> both contexts "simultaneously."

You must hold the ahc_lock() before calling most routines in the driver.
It is tha ahc_lock() that protects against reentrancy.

--
Justin

sym53c8xx message d sent on bad reselection

[Daryl Zero]

Hi.. I'm new to this list and somewhat new to linux. I tend to be
technical in nature but I do not have a lot of experience with linux. I
have recently upgraded my home firewall box to Redhat 7.3. Everything
seems to work fine, except I am now having one problem with the SCSI disk
system.

The computer is a Compaq Professional Workstation 7000 with dual Pentium
Pro 200 processors (overclocked to 233). It has a sym53c875 SCSI
controller in the motherboard, and the factory Western Digital WDE2170W
2GB SCSI drive install internally. I have externally attached 4 Seagate
ST410800N 10GB SCSI drives, mounted on /disk1 thru /disk4 under linux. The
internal drive and the /disk4 external drive are terminated via jumper
settings on the drives.

The problem I'm having is that now it seems that if I start to copy or
write things to /disk2, it will work for awhile but then hang, and the
following message appears on the console:

> sym53c875-0:2: message d sent on bad reselection.
> scsi: aborting command due to timeout : pid 4125, scsi0, channel 0, id 2, lun 0
> Write (10) 00 00 0a 12 10 00 01 10 00
> sym53c8xx_abort: pid=4125 serial_number 4126
> serial_number_at_timeout=4126
> sym53c875-0:2: message d sent on bad reselection.
> scsi: aborting command due to timeout : pid 4199, scsi0, channel 0, id 2, lun 0
> Write (10) 00 00 0a 12 10 00 01 10 00
> sym53c8xx_abort: pid=4199 serial_number 4200
> serial_number_at_timeout=4200
> sym53c875-0:2: message d sent on bad reselection.
> SCSI host 0 abort (pid 4213) timed out - resetting
> SCSI bus is being reset for host 0 channel 0.
> sym53c8xx_reset: pid=4213 reset_flags=2 serial_number=4214
> serial_number_at_timeout=4214

Then the write operation finishes (I think). So I do something else on
that drive, and I get a similar set of console messages again. Then, the
console starts spitting out:

> sym53c875-0: SCSI phase error fixup: CCB already dequeued.

This message repeats about once ever second or two and just keeps on
repeating.

Can anyone tell me what might be wrong and what I ought to try?

David Bradford
Information Services Director, LPA, Inc.
Home: (503) 203-1043
Cell: (503) 341-9519

Re: sym53c8xx message d sent on bad reselection

[Daryl Zero]

On Sat, 17 Aug 2002, Daryl Zero wrote:

> The problem I'm having is that now it seems that if I start to copy or
> write things to /disk2, it will work for awhile but then hang, and the
> following message appears on the console:

I also should mention that this "message d sent on bad reselection" error
did NOT occur when I did an SSH file transfer of about 200MB of tar files
over 10Mbit/sec ethernet to that same disk!

Also, on bootup, I get the following messages:

> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2

then later,

> modprobe: modprobe: Can't locate module block-major-30

I've no idea what these mean?

Dave