Coach-X wrote:
Is it possible to disable the hw/scsi scan on suse 10.2, or would this cause the system not to boot?
This is related to my issue with raid/scsi drives here:
http://lists.opensuse.org/opensuse/2007-04/msg03328.html
I believe I have isolated the problem to the scsi scan and the megaraid driver.
A proper boot on suse 9.3 finds the raid, then processor:
<6>scsi0 : LSI Logic MegaRAID E 254 commands 16 targs 5 chans 7 luns <5>scsi0: scanning scsi channel 0 for logical drives. <5> Vendor: MegaRAID Model: LD0 RAID5 34730R Rev: E <5> Type: Direct-Access ANSI SCSI revision: 02
<5>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 <5>scsi0: scanning scsi channel 4 [P0] for physical devices. <5> Vendor: HP Model: SAFTE; U160/M BP Rev: 1021 <5> Type: Processor ANSI SCSI revision: 02
Suse 10.2 finda the raid and then the other attached drives, no processor:
<6>scsi0 : LSI Logic MegaRAID E 254 commands 16 targs 5 chans 7 luns <5>scsi0: scanning scsi channel 0 for logical drives. <5> Vendor: MegaRAID Model: LD0 RAID5 34730R Rev: E <5> Type: Direct-Access ANSI SCSI revision: 02
<5>scsi0: scanning scsi channel 4 [P0] for physical devices. <5> Vendor: HP Model: 18.2GB C 80-D94N Rev: D94N <5> Type: Direct-Access ANSI SCSI revision: 02
I have opened a bug report on this as well:
Uh, why would a SCSI scan cause the problems with CPU reporting? They're not related in the slightest. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org