Kernel 2.2.21 aic7xxx lockup or kernel lockup

Kernel 2.2.21 aic7xxx lockup or kernel lockup

[John L. Males]

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

Hello,

**** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****

Could somone advise me what I need to do to obtain the details of a
aic7xxx module lockup that happens when using insmod?  I am not sure
what would be helpful data to report here and assist in determining
what is the problem, beyond the obvious system details?

I am now using kernel 2.2.21, and it is a tad better in terms of not
locking up the kernel hard in the different device connected
conditions.  The lockup does not always occur, much depends on if
something is connected to the 2930 or not.  In all cases with a device
connected a hard kernel lockup or module load lockup occur.  In the
latter I can ctrl-c or close the xterm to kill the load.  I tried an
strace but this appears not to provide any detail, at least in my
limited knowledge of the kernel and my techncial read of the strace
data.

The 2930 has no problem with seeing the devices.  The devices work
just fine as I changed to a BusLogic 930 and both scanner and CDWriter
work just fine.  The primary SCSI is a Buslogic 958 that the hard
drives boot off.  I was using the 2930 for external and slow devices. 
The 958 remained in, I just swapped the 2930 for the 930.  The
buslogic.o is loaded at boot time from the Initial RAM disk, and there
is no compiled in SCSI driver support, all are modules.

I really appreciate if you bcc me in on your reply so I can avoid the
big SPAM problems that have been snowballing me lately.


Regards,

John L. Males
Willowdale, Ontario
Canada
29 June 2002 16:04


==================================================================


"Boooomer ... Boom Boom, how are you Boom Boom" Boomer 1985 -
February/2000


***** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****


Please BCC me by replacing after the "@" as follows:
TLD =         The last three letters of the word "internet"
Domain name = The first four letters of the word "software",
              followed by the first four letters of the word
              "homeless".
My appologies in advance for the jumbled eMail address
and request to BCC me, but SPAM has become a very serious
problem.  The eMail address in my header information is
not a valid eMail address for me.  I needed to use a valid
domain due to ISP SMTP screen rules.

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

Re: Kernel 2.2.21 aic7xxx lockup or kernel lockup

[John L. Males]

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

Hello,

***** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****

Trying to ask this again please.


Regards,

John L. Males
Willowdale, Ontario
Canada
01 July 2002 17:56

On Sat, 29 Jun 2002 16:04:23 -0400
On (Sat) 2002-06-29 16:04:23 -0400 
John L. Males wrote in Message-ID:
20020629160423.2cfc6be7.jlmales@yahoo.com

To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
From: "John L. Males" <jlmales@yahoo.com>
Subject: Kernel 2.2.21 aic7xxx lockup or kernel lockup
Date: Sat, 29 Jun 2002 16:04:23 -0400

> Hello,
> 
> **** Please BCC me in on any reply, not CC me.
> Two reasons, I am not on the Mailing List,
> and second I am suffering BIG time with SPAM
> from posting to mailing lists/Newsgroups.
> Instructions on real address at bottom.
> Thanks in advance. *****
> 
> Could somone advise me what I need to do to obtain the details of a
> aic7xxx module lockup that happens when using insmod?  I am not sure
> what would be helpful data to report here and assist in determining
> what is the problem, beyond the obvious system details?
> 
> I am now using kernel 2.2.21, and it is a tad better in terms of not
> locking up the kernel hard in the different device connected
> conditions.  The lockup does not always occur, much depends on if
> something is connected to the 2930 or not.  In all cases with a
> device connected a hard kernel lockup or module load lockup occur. 
> In the latter I can ctrl-c or close the xterm to kill the load.  I
> tried an strace but this appears not to provide any detail, at least
> in my limited knowledge of the kernel and my techncial read of the
> strace data.
> 
> The 2930 has no problem with seeing the devices.  The devices work
> just fine as I changed to a BusLogic 930 and both scanner and
> CDWriter work just fine.  The primary SCSI is a Buslogic 958 that
> the hard drives boot off.  I was using the 2930 for external and
> slow devices. The 958 remained in, I just swapped the 2930 for the
> 930.  The buslogic.o is loaded at boot time from the Initial RAM
> disk, and there is no compiled in SCSI driver support, all are
> modules.
> 
> I really appreciate if you bcc me in on your reply so I can avoid
> the big SPAM problems that have been snowballing me lately.
> 
> 
> Regards,
> 
> John L. Males
> Willowdale, Ontario
> Canada
> 29 June 2002 16:04
> 

[snip]


==================================================================


"Boooomer ... Boom Boom, how are you Boom Boom" Boomer 1985 -
February/2000


***** Please BCC me in on any reply, not CC me.
Two reasons, I am not on the Mailing List,
and second I am suffering BIG time with SPAM
from posting to mailing lists/Newsgroups.
Instructions on real address at bottom.
Thanks in advance. *****


Please BCC me by replacing after the "@" as follows:
TLD =         The last three letters of the word "internet"
Domain name = The first four letters of the word "software",
              followed by the first four letters of the word
              "homeless".
My appologies in advance for the jumbled eMail address
and request to BCC me, but SPAM has become a very serious
problem.  The eMail address in my header information is
not a valid eMail address for me.  I needed to use a valid
domain due to ISP SMTP screen rules.

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