[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#275302: kernel-image-2.6.8-1-686-smp: 2.6.8-2 worked fined



On Monday 18 October 2004 11:25, Horms wrote:
> On Fri, Oct 08, 2004 at 01:57:05AM +0300, Stefanos Harhalakis wrote:
> > Package: kernel-image-2.6.8-1-686-smp
> > Version: 2.6.8-3
> > Followup-For: Bug #275302
> >
> > I've the same problem. On two identical machines I tested 2.6.8-2 and
> > 2.6.8-3. -2 worked fine. -3 could not boot no matter what I did. It
> > worked fine when I overwrote the vmlinuz and initrd of 2.6.8-3 with
> > 2.6.8-2 from the second machine.
>
> Ok, that sounds pretty crazy, though I still suspect a modules problem.
> What type of hardware is your root partition on, what modules are loaded
> on a successful boot, can you examine the initrd images to find out
> if there is a difference in the modules included in each initrd -
> they are cramfs images and you can mount them using the loopback device.

aix78xxx, scsi drives only. While booting the initrd image no scsi disks are 
detected at all and thus the mounting of the root partition fails.

The dmesg messages from the working (-2) kernel:

SCSI subsystem initialized
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec aic7899 Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Using anticipatory io scheduler
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
(scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
  Vendor: IBM       Model: DDYS-T18350N      Rev: S96H
  Type:   Direct-Access                      ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled.  Depth 8
  Vendor: IBM       Model: DDYS-T18350N      Rev: S96H
  Type:   Direct-Access                      ANSI SCSI revision: 03
scsi0:A:1:0: Tagged Queuing enabled.  Depth 8
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec aic7899 Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs

SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB)
SCSI device sda: drive cache: write back
 /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 35843670 512-byte hdwr sectors (18352 MB)
SCSI device sdb: drive cache: write back
 /dev/scsi/host0/bus0/target1/lun0: p1 p2 p3 p4

the -3 kernel reports 'no scsi devices' or something simillar if i remember 
correctly.

> mkdir /tmp/img
> mount -o loop,ro /boot/blah.img /tmp/img
I'm sorry but I don't have the -3 kernel. From the -2 version:

-rw-r--r--  1 root root 251651 Jan  1  
1970 /mnt/1/lib/modules/2.6.8-1-686-smp/kernel/drivers/scsi/aic7xxx/aic7xxx.ko

md5sum:
59526545107e173cd3301b741dfdabb3  /mnt/1/lib/modules/2.6.8-1-686-smp/kernel/drivers/scsi/aic7xxx/aic7xxx.ko

Also, please have a look at other comments since someone confirmed a problem 
with aic7xxx.

<<V13>>

Attachment: pgpnTHF9hkXCw.pgp
Description: signature


Reply to: