wierd patching experience

[Jon P. deOng]

i had almost the exact same results with any 2.1 kernel. I can get
2.1.anything on all the PII 233mhz machines we run. However, I tried 2.1.x
with my 400mhz PII with the 100mhz bus and it hangs at
>scsi : 1 host.
>(scsi1:0:-1:-1) Scanning channel for devices.
>(scsi0:-1:-1:-1) Allocating initial 30 SCB structures
pressing <Ctrl>+<scrollLock> shows the swapper task in hung. I have posted
a couple of messages to the linux kernel list but have had very little
response. So if you find a fix for this I'd appreciate hearing about it.

jpd

At 04:04 PM 5/13/98 +0200, OLK wrote:
>Here's the story:
>
>Dnl'ded linux-tarball 2.1.95 which ran not bad.
>Patched one by one up to .99 running stable too.
>Was brave enough to patch for 100, scsi hang at boot
>went upto 101 -> exactly the same result
>
>Here's the bootmsg:
>
>(scsi1) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 14/0
>(scsi1) Wide Channel, SCSI ID=7, 16/255 SCBs
>(scsi1) BIOS enabled, IO Port 0xec00, IRQ 16
>(scsi1) IO Memory at 0xfebfb000, MMAP Memory at 0xc880a000
>(scsi1) Resetting channel
>(scsi1) Downloading sequencer code... 413 instructions downloaded
>scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.0.13/3.2.4
>       <Adaptec AHA-294X Ultra SCSI host adapter>
>scsi : 1 host.
>(scsi1:0:-1:-1) Scanning channel for devices.
>(scsi0:-1:-1:-1) Allocating initial 30 SCB structures
>(scsi0: 0: 0: 0) Invalid SCB during SEQINT 0x71, SCB_TAG 61.
>(scsi0:-1:-1:-1) CMDCMPLT with invalid SCB index 61
>
>booting with 2.1.100 and 2.1.101 
>(486 and pentium both with AHA-2940 BIOS v1.16 PCI/NARROW-BUS)
>
>pls. ignore (scsi1/0) in the beginning, because its shamelessly
>stolen by somebody who had exactly the same problem like me ;-((
>
>Well,
>then looked up the src and found in
> ftp://ftp.dialnet.net/pub/linux/aic7xxx/
>the patch 5.0.14, glancing through krnl-src (101)
>i had 5.0.13, aplying this went almost fine
>except of a reject of 3 Hunks #(2,4,51) in aic7xxx.c,
>which were already there in the krnl-src.
>So 101 contains already 3 Hunks of 5.0.14 and reports
>aic7xxx as 5.0.13...Huh?
>
>However, Result -> kernel 101 hangs at boot again at same
>place with same see above error msgs.
>
>There seemes to be very little traffic here,
>is this normal?
>
>OLK (who wants to use the 101 kernel)
>-- 
>eMail : delise at online-club.de
>
>
>To Unsubscribe: send mail to majordomo at FreeBSD.org
>with "unsubscribe aic7xxx" in the body of the message
>

To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message