Hi,
I have several machines here, with either onboard aic7880 or with
AHA2940 (I don't recall) sitting on the PCI bus, which share the same
problem: they fail to detect the first disk (Id #0). The information
below is from lspci and /proc/scsi/scsi of Linux 2.2.19, in that order,
all Kernels have been compiled on a Duron/800 SuSE 7.0 Linux box
(running gcc 2.95.2).
Machine #1:
Pentium-II (Klamath)
00:09.0 SCSI storage controller: Adaptec AIC-7881U
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST34572W Rev: 0718
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST39140W Rev: 1498
Type: Direct-Access ANSI SCSI revision: 02
Machine #2:
Pentium-II (Deschutes)
00:09.0 SCSI storage controller: Adaptec AIC-7881U
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST34572N Rev: 0784
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: DCAS-32160 Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
These have further devices (CD writer, CD-ROM drive), and these machines
are 100% in 2.2.19. With 2.4.3 and 2.4.4-pre8, I get this problem
(pencil & paper copy for Machine #2, DO NOT "grep"):
AIC 7XXX EISA/VLB/PCI SCSI HBA DRIVER 6.1.5
aic7880: wide Channel A, SCSI ID=7, 16/255 SCBs
scsi0: SCSI host adapter emulation for IDE devices
PCI: found IRQ 5 for dev 00:09.0
scsi1:0:0:0: Attempting to queue an abort message.
Command found on device queue
aic7xxx_abort returns 8194
Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
(Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
would mount that as sda). Regretfully, my root partition is on the
FIRST SCSI disk, so the kernel panicks since it cannot mount /.
That's all I copied in a hurry, maybe it's sufficient to debug, if not,
I can try to grab a null modem cable and catch the full sequence; I'd be
glad if someone could mention the "canonical" aic7xxx LILO append
parameters for a full debug trace in that case.
Bottom line: I'm not buying Adaptec SCSI host adaptors ever again.
--
Matthias Andree
On Sat, Apr 28, 2001 at 08:22:25PM +0200, Matthias Andree wrote:
> These have further devices (CD writer, CD-ROM drive), and these machines
> are 100% in 2.2.19. With 2.4.3 and 2.4.4-pre8, I get this problem
> (pencil & paper copy for Machine #2, DO NOT "grep"):
>
> AIC 7XXX EISA/VLB/PCI SCSI HBA DRIVER 6.1.5
> aic7880: wide Channel A, SCSI ID=7, 16/255 SCBs
> scsi0: SCSI host adapter emulation for IDE devices
> PCI: found IRQ 5 for dev 00:09.0
> scsi1:0:0:0: Attempting to queue an abort message.
> Command found on device queue
> aic7xxx_abort returns 8194
Getting the same errors here, but only a few seconds after my adaptec gets initialized and all disks/cdrs/zips get attached + mounted. On 2.4.3-ac14 it only gives these errors and happily runs afterwards. But on 2.4.4 it panics after $random time.
My setup is a P2B-S motherboard with a Quantum Fireball ST 6.4 GB HDD
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.11
<Adaptec aic7890/91 Ultra2 SCSI adapter>
aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs
Vendor: QUANTUM Model: FIREBALL ST6.4S Rev: 0F0C
Type: Direct-Access ANSI SCSI revision: 02
(scsi0:A:0): 20.000MB/s transfers (20.000MHz, offset 15)
And the specific errors are
scsi0:0:0:0: Attempting to queue a TARGET RESET message
scsi0:0:0:0: Command not found
aic7xxx_dev_reset returns 8194
Device not ready. Make sure there is a disc in the drive.
> Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
> (Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
> would mount that as sda). Regretfully, my root partition is on the
> FIRST SCSI disk, so the kernel panicks since it cannot mount /.
>
> That's all I copied in a hurry, maybe it's sufficient to debug, if not,
> I can try to grab a null modem cable and catch the full sequence; I'd be
> glad if someone could mention the "canonical" aic7xxx LILO append
> parameters for a full debug trace in that case.
--
Cliff Albert | IRCNet: #linux.nl, #ne2000, #linux, #freebsd.nl
[email protected] | #openbsd, #ipv6, #cu2.nl
-[ICQ: 18461740]--------| 6BONE: CA2-6BONE RIPE: CA3348-RIPE
Howdy,
I've got an "Adaptec AHA-2940UW Pro Ultra SCSI host adapter" using
the aic7xxx driver (the new one, not the old one), and have had no
problems, I have a zip drive on ID5, and a 12X Smart & Friendly CD-RW on
ID6, haven't had any problems on 2.4.3-ac14, or 2.4.4, just an FYI.
Matthew S. Hallacy
> Getting the same errors here, but only a few seconds after my adaptec gets initialized and all disks/cdrs/zips get attached + mounted. On 2.4.3-ac14 it only gives these errors and happily runs afterwards. But on 2.4.4 it panics after $random time.
>
> My setup is a P2B-S motherboard with a Quantum Fireball ST 6.4 GB HDD
>
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.11
> <Adaptec aic7890/91 Ultra2 SCSI adapter>
> aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs
>
> Vendor: QUANTUM Model: FIREBALL ST6.4S Rev: 0F0C
> Type: Direct-Access ANSI SCSI revision: 02
> (scsi0:A:0): 20.000MB/s transfers (20.000MHz, offset 15)
>
> And the specific errors are
>
> scsi0:0:0:0: Attempting to queue a TARGET RESET message
> scsi0:0:0:0: Command not found
> aic7xxx_dev_reset returns 8194
> Device not ready. Make sure there is a disc in the drive.
>
> > Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
> > (Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
> > would mount that as sda). Regretfully, my root partition is on the
> > FIRST SCSI disk, so the kernel panicks since it cannot mount /.
> >
> > That's all I copied in a hurry, maybe it's sufficient to debug, if not,
> > I can try to grab a null modem cable and catch the full sequence; I'd be
> > glad if someone could mention the "canonical" aic7xxx LILO append
> > parameters for a full debug trace in that case.
No problems here... with 2.4.3
Here is the dump from dmesg.
regards,
Royans
-------------
SCSI subsystem driver Revision: 1.00
aacraid raid driver version, Apr 28 2001
percraid device detected
Device mapped to virtual address 0xf8806000
percraid:0 device initialization successful
percraid:0 AacHba_ClassDriverInit complete
scsi0 : percraid
Vendor: DELL Model: PERCRAID Mirror Rev: 0001
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 35544577 512-byte hdwr sectors (18199 MB)
sda: Write Protect is off
Partition check:
sda: sda1 sda2 < sda5 sda6 >
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.5
<Adaptec aic7899 Ultra160 SCSI adapter>
aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs
-----------------
bash-2.04$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 6
cpu MHz : 993.400
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse
bogomips : 1979.18
-----------------
-----Original Message-----
From: Matthias Andree [mailto:[email protected]]
Sent: Saturday, April 28, 2001 11:22 AM
To: Linux-Kernel mailing list
Subject: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
Hi,
I have several machines here, with either onboard aic7880 or with
AHA2940 (I don't recall) sitting on the PCI bus, which share the same
problem: they fail to detect the first disk (Id #0). The information
below is from lspci and /proc/scsi/scsi of Linux 2.2.19, in that order,
all Kernels have been compiled on a Duron/800 SuSE 7.0 Linux box
(running gcc 2.95.2).
Machine #1:
Pentium-II (Klamath)
00:09.0 SCSI storage controller: Adaptec AIC-7881U
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST34572W Rev: 0718
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST39140W Rev: 1498
Type: Direct-Access ANSI SCSI revision: 02
Machine #2:
Pentium-II (Deschutes)
00:09.0 SCSI storage controller: Adaptec AIC-7881U
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST34572N Rev: 0784
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: DCAS-32160 Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
These have further devices (CD writer, CD-ROM drive), and these machines
are 100% in 2.2.19. With 2.4.3 and 2.4.4-pre8, I get this problem
(pencil & paper copy for Machine #2, DO NOT "grep"):
AIC 7XXX EISA/VLB/PCI SCSI HBA DRIVER 6.1.5
aic7880: wide Channel A, SCSI ID=7, 16/255 SCBs
scsi0: SCSI host adapter emulation for IDE devices
PCI: found IRQ 5 for dev 00:09.0
scsi1:0:0:0: Attempting to queue an abort message.
Command found on device queue
aic7xxx_abort returns 8194
Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
(Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
would mount that as sda). Regretfully, my root partition is on the
FIRST SCSI disk, so the kernel panicks since it cannot mount /.
That's all I copied in a hurry, maybe it's sufficient to debug, if not,
I can try to grab a null modem cable and catch the full sequence; I'd be
glad if someone could mention the "canonical" aic7xxx LILO append
parameters for a full debug trace in that case.
Bottom line: I'm not buying Adaptec SCSI host adaptors ever again.
--
Matthias Andree
Howdy Matthias,
Well, under 2.4.4, I can't even get the driver to load due to unresolved
symbols... So I know I won't be much help... :-(
Later,
Steve
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Matthias Andree
Sent: Saturday, April 28, 2001 1:22 PM
To: Linux-Kernel mailing list
Subject: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
Hi,
I have several machines here, with either onboard aic7880 or with
AHA2940 (I don't recall) sitting on the PCI bus, which share the same
problem: they fail to detect the first disk (Id #0). The information
below is from lspci and /proc/scsi/scsi of Linux 2.2.19, in that order,
all Kernels have been compiled on a Duron/800 SuSE 7.0 Linux box
(running gcc 2.95.2).
Machine #1:
Pentium-II (Klamath)
00:09.0 SCSI storage controller: Adaptec AIC-7881U
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST34572W Rev: 0718
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST39140W Rev: 1498
Type: Direct-Access ANSI SCSI revision: 02
Machine #2:
Pentium-II (Deschutes)
00:09.0 SCSI storage controller: Adaptec AIC-7881U
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST34572N Rev: 0784
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: DCAS-32160 Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
These have further devices (CD writer, CD-ROM drive), and these machines
are 100% in 2.2.19. With 2.4.3 and 2.4.4-pre8, I get this problem
(pencil & paper copy for Machine #2, DO NOT "grep"):
AIC 7XXX EISA/VLB/PCI SCSI HBA DRIVER 6.1.5
aic7880: wide Channel A, SCSI ID=7, 16/255 SCBs
scsi0: SCSI host adapter emulation for IDE devices
PCI: found IRQ 5 for dev 00:09.0
scsi1:0:0:0: Attempting to queue an abort message.
Command found on device queue
aic7xxx_abort returns 8194
Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
(Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
would mount that as sda). Regretfully, my root partition is on the
FIRST SCSI disk, so the kernel panicks since it cannot mount /.
That's all I copied in a hurry, maybe it's sufficient to debug, if not,
I can try to grab a null modem cable and catch the full sequence; I'd be
glad if someone could mention the "canonical" aic7xxx LILO append
parameters for a full debug trace in that case.
Bottom line: I'm not buying Adaptec SCSI host adaptors ever again.
--
Matthias Andree
On 04.29 Steve 'Denali' McKnelly wrote:
> Command found on device queue
> aic7xxx_abort returns 8194
>
I have seen blaming for this error to aic7xxx new driver prior to version
6.1.11. It was included in the 2.4.3-ac series, but its has not got into
main 2.4.4 (there is still 6.1.5). Everything needs its time.
Grab the updated patch from people.freebsd.org/~gibbs/linux.
BTW (Alan?) new version is 6.1.12 (just patched 2.4.4 after offset
engineering and works fine).
Candidate for 2.4.4-ac1 or 2.4.5-pre1 ?
--
J.A. Magallon # Let the source
mailto:[email protected] # be with you, Luke...
Linux werewolf 2.4.4 #1 SMP Sat Apr 28 11:45:02 CEST 2001 i686
On Sat, 28 Apr 2001, Royans Tharakan wrote:
> SCSI subsystem driver Revision: 1.00
> aacraid raid driver version, Apr 28 2001
> percraid device detected
> Device mapped to virtual address 0xf8806000
> percraid:0 device initialization successful
> percraid:0 AacHba_ClassDriverInit complete
> scsi0 : percraid
> Vendor: DELL Model: PERCRAID Mirror Rev: 0001
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sda: 35544577 512-byte hdwr sectors (18199 MB)
> sda: Write Protect is off
> Partition check:
> sda: sda1 sda2 < sda5 sda6 >
> scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.5
> <Adaptec aic7899 Ultra160 SCSI adapter>
> aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs
Your sda disk is attached to your RAID card, isn't it?
On Sat, 28 Apr 2001, poptix wrote:
> Howdy,
>
> I've got an "Adaptec AHA-2940UW Pro Ultra SCSI host adapter" using
> the aic7xxx driver (the new one, not the old one), and have had no
> problems, I have a zip drive on ID5, and a 12X Smart & Friendly CD-RW on
> ID6, haven't had any problems on 2.4.3-ac14, or 2.4.4, just an FYI.
You're not using SCSI hard disks, are you?
Howdy J.A.,
Let me ask a possibly stupid question... How do you tell
what version of the Gibbs Adaptec driver you're using? Did I
misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
Also, did I understand you to say the 6.1.12 version will fix
my unresolved symbol problem?
Thanks,
Steve
-----Original Message-----
From: J . A . Magallon [mailto:[email protected]]
Sent: Sunday, April 29, 2001 5:26 AM
To: Steve 'Denali' McKnelly
Cc: Matthias Andree; Linux-Kernel mailing list
Subject: Re: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect
sda
On 04.29 Steve 'Denali' McKnelly wrote:
> Command found on device queue
> aic7xxx_abort returns 8194
>
I have seen blaming for this error to aic7xxx new driver prior to version
6.1.11. It was included in the 2.4.3-ac series, but its has not got into
main 2.4.4 (there is still 6.1.5). Everything needs its time.
Grab the updated patch from people.freebsd.org/~gibbs/linux.
BTW (Alan?) new version is 6.1.12 (just patched 2.4.4 after offset
engineering and works fine).
Candidate for 2.4.4-ac1 or 2.4.5-pre1 ?
--
J.A. Magallon # Let the source
mailto:[email protected] # be with you,
Luke...
Linux werewolf 2.4.4 #1 SMP Sat Apr 28 11:45:02 CEST 2001 i686
At 12:17 PM 4/29/01, Steve 'Denali' McKnelly wrote:
>Howdy J.A.,
>
> Let me ask a possibly stupid question... How do you tell
>what version of the Gibbs Adaptec driver you're using? Did I
>misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
>Also, did I understand you to say the 6.1.12 version will fix
>my unresolved symbol problem?
>
>Thanks,
>Steve
Steve,
A message saying (roughly) AIC7XXX 6.1.xxx appears while the kernel is
loading. You can also grep the aic7xxx.c source file or run the strings
command ( strings /lib/modules/2.4.4/kernel/drivers/scsi/aic7xxx ).
I'm not sure about your undefined symbols problem, but I was able to build
2.4.4 with 6.1.11 with no trouble.
David
--------------------------------------------------------
David Relson Osage Software Systems, Inc.
[email protected] Ann Arbor, MI 48103
http://www.osagesoftware.com tel: 734.821.8800
On 04.29 Steve 'Denali' McKnelly wrote:
> Howdy J.A.,
>
> Let me ask a possibly stupid question... How do you tell
> what version of the Gibbs Adaptec driver you're using? Did I
You can look at the kernel boot messages for a line like:
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.12
After boot, you car look at them with 'dmesg'.
And you can also do a 'head -1 /proc/scsi/aic7xxx/*'
> misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
Yes, vanilla 2.4.4 uses 6.1.5.
> Also, did I understand you to say the 6.1.12 version will fix
> my unresolved symbol problem?
>
No, i was answering what you quoted, did not see the original message.
The 6.1.11 driver solved problems about the 'abort' messages. Dunno
about the build. I use the driver but built-in.
--
J.A. Magallon # Let the source
mailto:[email protected] # be with you, Luke...
Linux werewolf 2.4.4 #1 SMP Sat Apr 28 11:45:02 CEST 2001 i686
On Sun, 29 Apr 2001, Steve 'Denali' McKnelly wrote:
> Let me ask a possibly stupid question... How do you tell
> what version of the Gibbs Adaptec driver you're using? Did I
> misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
> Also, did I understand you to say the 6.1.12 version will fix
> my unresolved symbol problem?
Try: dmesg | grep -i aic7xxx
Some distributions store the boot dmesg output in a file, since if the
kernel spews a lot of messages, the older ones get lost if the buffer is
full; SuSE e. g. have been using /var/log/boot.msg for quite some time
now.
Other systems throw the entire boot message output into the normal
syslog. (Seen than one on FreeBSD 4.3, but I don't remember Debian 1.x
and Red Hat 6.0 Sparc.)
Ahh... It doesn't even get that far... It just dies with the
undefined symbols...
-----Original Message-----
From: David Relson [mailto:[email protected]]
Sent: Sunday, April 29, 2001 11:32 AM
To: Steve 'Denali' McKnelly
Cc: Linux-Kernel mailing list
Subject: RE: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect
sda
At 12:17 PM 4/29/01, Steve 'Denali' McKnelly wrote:
>Howdy J.A.,
>
> Let me ask a possibly stupid question... How do you tell
>what version of the Gibbs Adaptec driver you're using? Did I
>misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
>Also, did I understand you to say the 6.1.12 version will fix
>my unresolved symbol problem?
>
>Thanks,
>Steve
Steve,
A message saying (roughly) AIC7XXX 6.1.xxx appears while the kernel is
loading. You can also grep the aic7xxx.c source file or run the strings
command ( strings /lib/modules/2.4.4/kernel/drivers/scsi/aic7xxx ).
I'm not sure about your undefined symbols problem, but I was able to build
2.4.4 with 6.1.11 with no trouble.
David
--------------------------------------------------------
David Relson Osage Software Systems, Inc.
[email protected] Ann Arbor, MI 48103
http://www.osagesoftware.com tel: 734.821.8800
On Sun, 29 Apr 2001, J . A . Magallon wrote:
> > Command found on device queue
> > aic7xxx_abort returns 8194
>
> I have seen blaming for this error to aic7xxx new driver prior to version
> 6.1.11. It was included in the 2.4.3-ac series, but its has not got into
> main 2.4.4 (there is still 6.1.5). Everything needs its time.
Since the official aic7xxx site doesn't carry a patch against 2.4.4 yet
(just 2.4.3) which has cosmetic issues when being patched, I made a
patch against 2.4.4: I took the 2.4.3-aic7xxx-6.1.12 patch, applied to
2.4.4, bumped the version to read -ma1 in EXTRAVERSION, and made a new
patch against vanilla 2.4.4, to be found at:
*** WARNING BELOW ***
http://mandree.home.pages.de/kernelpatches/v2.4/v2.4.4/
72k linux-2.4.4-aic7xxx-to-6.1.12.patch.gz
Apply with patch -p1.
NOTE: Do not expect this patch to last until after either Justin has a
patch against 2.4.4 available or 2.4.5 has been released.
*** WARNING *** I did not yet try to boot it, that will have to wait
until later.
Matthias,
I tried pretty much the same thing, and I also tried your patch.
Unhappily when I access my zip drive using the aic7xxx driver my system
becomes pretty much unresposive, just short of locking up completely.
ie at least the emergency alt-sysrq keys still work.
I guess we'll just have to wait for Justin to come out with the real patch...
-- todd --
> X-Apparently-To: [email protected] via web13607.mail.yahoo.com
> X-Track: 1: 40
> Date: Mon, 30 Apr 2001 01:39:56 +0200
> From: Matthias Andree <[email protected]>
> Mail-Followup-To: Linux-Kernel mailing list <[email protected]>
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> User-Agent: Mutt/1.2.5i
> Sender: [email protected]
> Precedence: bulk
> X-Mailing-List: [email protected]
>
> On Sun, 29 Apr 2001, J . A . Magallon wrote:
>
> > > Command found on device queue
> > > aic7xxx_abort returns 8194
> >
> > I have seen blaming for this error to aic7xxx new driver prior to version
> > 6.1.11. It was included in the 2.4.3-ac series, but its has not got into
> > main 2.4.4 (there is still 6.1.5). Everything needs its time.
>
> Since the official aic7xxx site doesn't carry a patch against 2.4.4 yet
> (just 2.4.3) which has cosmetic issues when being patched, I made a
> patch against 2.4.4: I took the 2.4.3-aic7xxx-6.1.12 patch, applied to
> 2.4.4, bumped the version to read -ma1 in EXTRAVERSION, and made a new
> patch against vanilla 2.4.4, to be found at:
>
> *** WARNING BELOW ***
>
> http://mandree.home.pages.de/kernelpatches/v2.4/v2.4.4/
> 72k linux-2.4.4-aic7xxx-to-6.1.12.patch.gz
>
> Apply with patch -p1.
>
> NOTE: Do not expect this patch to last until after either Justin has a
> patch against 2.4.4 available or 2.4.5 has been released.
>
> *** WARNING *** I did not yet try to boot it, that will have to wait
> until later.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
**********************************************************************
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**********************************************************************
Matthias,
I tried 2.4.4 with the old aic7xxxx driver and it worked fine.
I have no control over that stupid, stupid mime-sweeper message.
Thats our anal-retentive network administrators work....
-- todd --
--
.~. Todd Roy, Senior Database Administrator .~.
/V\ Holstein Association, U.S.A. Inc. /V\
// \\ [email protected] // \\
/( )\ 1-802-254-4551x4230 /( )\
^^-^^ ^^-^^
**********************************************************************
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**********************************************************************
On Mon, Apr 30, 2001 at 10:36:53AM -0400, Todd M. Roy wrote:
> I tried 2.4.4 with the old aic7xxxx driver and it worked fine.
>
> I have no control over that stupid, stupid mime-sweeper message.
> Thats our anal-retentive network administrators work....
2.4.4 with old aic7xxx still crashes my box, but doesn't give the warnings. 2.4.3-ac14 still works fine. even under high load on the scsi bus.
--
Cliff Albert | IRCNet: #linux.nl, #ne2000, #linux, #freebsd.nl
[email protected] | #openbsd, #ipv6, #cu2.nl
-[ICQ: 18461740]--------| 6BONE: CA2-6BONE RIPE: CA3348-RIPE