Messages in this thread | | | Date | Fri, 18 Jul 2003 10:34:58 +0200 | Subject | 2.6.0-test1 gets corrupted data when loading init | From | Anders Gustafsson <> |
| |
Hi,
with 2.6.0-test1 I get error like unresolved symbol in libs used by init or bad elf-file. Sometimes init manages to start and there are same type of errors in bash when it tries to run initscripts. This is on a dual xeon, no highmem (512M), ServerWorks chipset, aic79xx scsi, / on scsi.
It breaks between 2.5.70 and 2.5.70-bk1, which contains a update in the aic79xx-drivers, so my guess is related to that.
Scsi-related hardware in machine:
scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.0 <Adaptec AIC7902 Ultra320 SCSI adapter> aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs
scsi1 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.0 <Adaptec AIC7902 Ultra320 SCSI adapter> aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs
(scsi1:A:0): 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Vendor: SEAGATE Model: ST373307LW Rev: 0002 Type: Direct-Access ANSI SCSI revision: 03
-- Anders Gustafsson - andersg@0x63.nu - http://0x63.nu/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |