Hello again:
I have been searching to no avail about this SCSI problem I
am having on a generic p133 SMP system. It has 2 SCSI
controllers
one for the harddrive and one for the external 4 bay
CDrom's.
Kernel 2.2.16-3 rpm update throws my machine into an endless
boot
and I noticed that one of the updates to kernel 2.2.14-5
that
resulted in kernel 2.2.16-3 is "Updated SCSI error
handling".
Does anyone know the details of this so called "Updated SCSI
error
handling" or know of a list or newsgroup that this question
might
be better suited for? I am thinking of jumping to the 2.2.18
kernel but I fear that this Updated SCSI error handling may
still be a feature in it also.
TIA,
Eddie Strohmier
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Eddie Strohmier
> Sent: Saturday, February 03, 2001 3:48 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Kernel upgrade 2.2.16/SCSI probs
>
>
>
>
> That is interesting. I was just looking at the security
> update site and
> it states this:
>
> ----------------------------------------
> A security bug involving setuid programs is fixed in
> this kernel.
>
> Added or updated drivers include:
> Updated AMI MegaRAID driver
> Updated Acenic Gigabit Ethernet driver
> Added Adaptec RAID (aacraid) driver
> Updated to latest 3c90x driver from 3Com
> Updated agpgart handling for latest Intel 810 chipset
> Updated SCSI error handling <<<<<<<**********
>
> ----------------------------------------
>
> Note the updated SCSI error handling. I wonder
> what type of
> update occurred as this must be the difference in the 2
> versions of the stock and the rpm update that is
> causing the
> errors I am receiving. Anyone know the specifics
> behind this
> "Updated SCSI error handling"?
>
>
> Thanks,
>
> Eddie Strohmier
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Eddie Strohmier
> > Sent: Saturday, February 03, 2001 3:34 AM
> > To: [EMAIL PROTECTED]
> > Subject: Kernel upgrade 2.2.16/SCSI probs
> >
> >
> >
> > Hello All:
> >
> > I had no problem updating my two SCSI machines
> > here at home
> > with the rpm version of kernel 2.2.16-3 on my RH 6.2
> > machines but I am having major problems with an
> > SMP machine
> > that has 2 SCSI controllers. This is a generic dual p133
> > running now with the 2.2.14 stock kernel with
> RH 6.2. The
> > installer did fine as far as loading the stock
> SMP kernel
> > and picking up both SCSI controllers. One
> controller feeds
> > the hard drive and the other is a SCSI card
> that feeds a 4
> > bay external CDROM box with is terminated
> > properly. Ok I do
> > my normal rpm -ivh kernel-2.2.16-3smp.rpm and all loads
> > fine. Then I do my mkinitrd image for boot and place the
> > appropriate lines in lilo so I can boot my new kernel or
> > select the old kernel with a different label in case it
> > fails. I also remember to run LILO each attempt at this.
> > Well it sure failed in boot up with a message
> of the sort:
> > SCSI device resetting id 0, resetting SCSI bus. I can't
> > remember the exact line as it never gets written
> > to the logs
> > because it never finishes the boot and that was the only
> > notes I had jotted down to research this on. It
> does this
> > right before it is ready to read init. But this
> error runs
> > continuously "SCSI device failure id 0, resetting
> > SCSI bus,
> > or something along that line and finally I
> either reset or
> > CTL-ALT-DEL and boot back to original kernel with no
> > difficulty. It is my understanding that an RPM
> > kernel update
> > does not change any of the kernel config choices just
> > upgrades the kernel. I am thinking of building 2.2.18 on
> > this machine and trying that unless someone
> > recognizes this
> > error and has a fix for it. I wonder if it has
> > something to
> > do with the two SCSI controllers confusing the
> > boot process
> > as to which is the hard disk controller and the
> > CDrom's but
> > then again they boot fine with the previous
> stock kernel.
> > Anyone seen this behavior before and know a
> fix? Is there
> > some lilo entry I can use to be sure the machine
> > is looking
> > for SCSI id #0 that could clear this up. Very
> frustrating
> > considering I had done my two other machines that
> > by the way
> > only have "one" SCSI controller on board and
> they went so
> > smooth it almost sold me on using RPM for
> kernel updates.
> >
> > Thanks in Advance
> >
> >
> > Eddie Strohmier
> >
> >
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> >
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
