From: lists@sapience.com
To: linux-kernel@vger.kernel.org
Cc: gibbs@scsiguy.com
Subject: Re: aic7xxx 6.1.10 and 2.4.4-pre1
Date: Sun, 8 Apr 2001 00:11:32 -0400 [thread overview]
Message-ID: <20010408001132.A28840@sapience.com> (raw)
In-Reply-To: <20010407195031.B25801@sapience.com> <200104080139.f381dZs92143@aslan.scsiguy.com>
In-Reply-To: <200104080139.f381dZs92143@aslan.scsiguy.com>; from gibbs@scsiguy.com on Sat, Apr 07, 2001 at 07:39:35PM -0600
I used 5000ms. I still freeze up with 2.4.3 + 6.1.10.
Unfortunately i could not see any messages and nothing got logged.
This time an fsck allowed me to boot back to 2.4.1.
The visible symptoms were the same as before (2.4.3 + 6.1.8) but this time I was
unable to flip virtual consoles before the freeze so I dont even
know 100% what is causing it - it boots fine - and the scsi driver
makes no complaints - it all looks normal. X starts up and I can login.
it starts ok and windows start popping up - shortly thereafter it freezes
- just like before.
I will try investigate further and see if I can get any more log messages.
Is there any debug boot option or compile flag that will help me find out more
what is going on?
/var/log/messages says this about scsi.
Apr 7 19:56:13 snap kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.10
Apr 7 19:56:13 snap kernel: <Adaptec 2940 Ultra2 SCSI adapter>
Apr 7 19:56:13 snap kernel: aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs
Apr 7 19:56:13 snap kernel:
Apr 7 19:56:13 snap kernel: Vendor: YAMAHA Model: CRW8424S Rev: 1.0d
Apr 7 19:56:13 snap kernel: Type: CD-ROM ANSI SCSI revision: 02
Apr 7 19:56:13 snap kernel: Vendor: SEAGATE Model: ST318275LW Rev: 0001
Apr 7 19:56:13 snap kernel: Type: Direct-Access ANSI SCSI revision: 02
Apr 7 19:56:13 snap kernel: (scsi0:A:5): 80.000MB/s transfers (40.000MHz, offset 15, 16bit)
Apr 7 19:56:13 snap kernel: Vendor: SEAGATE Model: ST318275LW Rev: 0001
Apr 7 19:56:13 snap kernel: Type: Direct-Access ANSI SCSI revision: 02
Apr 7 19:56:13 snap kernel: (scsi0:A:6): 80.000MB/s transfers (40.000MHz, offset 15, 16bit)
Apr 7 19:56:13 snap kernel: scsi0:0:5:0: Tagged Queuing enabled. Depth 253
Apr 7 19:56:13 snap kernel: scsi0:0:6:0: Tagged Queuing enabled. Depth 253
next parent reply other threads:[~2001-04-08 4:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010407195031.B25801@sapience.com>
[not found] ` <200104080139.f381dZs92143@aslan.scsiguy.com>
2001-04-08 4:11 ` lists [this message]
2001-04-08 4:42 ` aic7xxx 6.1.10 and 2.4.4-pre1 lists
2001-04-09 21:19 ` Justin T. Gibbs
2001-04-10 12:33 ` aic7xxx and newer kernels lists
2001-04-10 14:00 ` Justin T. Gibbs
2001-04-10 21:37 ` lists
2001-04-07 21:55 aic7xxx 6.1.10 and 2.4.4-pre1 lists
2001-04-07 23:24 ` Justin T. Gibbs
2001-04-08 0:22 ` J . A . Magallon
2001-04-08 1:41 ` Justin T. Gibbs
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=20010408001132.A28840@sapience.com \
--to=lists@sapience.com \
--cc=gibbs@scsiguy.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.