Re: IBM ServerRAID 7 + fsck Crash SLES9_x64
"Weh, Reinhard" <[email protected]>
| Newsgroups | gmane.linux.suse.oracle.general |
|---|---|
| Message-ID | <7351FB26589253418E9C3710393C631E011097C6@FFM-SRV-EXCH-1.sageinternal.de> |
Hello now I have found the solution for this crash. With kernel parameter pci=nommconf a full fsck work well. Also with SP4 and all hotfixes. Config Notes SLES 9: System required the following boot parameter for proper installation/operation: pci=nommconf More Details in the YES Certied document of this hardware http://developer.novell.com/yes/80226.htm regards Reinhard >Message-ID: <[email protected]> >Date: Thu, 22 Dec 2005 08:59:05 +0100 >From: Reinhard Weh <[email protected]> >Subject: [suse-sles-e] IBM ServerRAID 7 + fsck Crash SLES9_x64 + SP2 >Hello, > >last night we have installed the latest kernel-2.6.5-7.202.7-smp on a >IBM x346 SMP, an during the fsck (forced because the last fsck has gone >142 days...) we have got the following CRASH message> > >NMI Watchdog detected LOCKUP on CPU0 >.. >scsi_eh_o Not tainted >... >IPS 0000:08:0e:0: Reset Request - Flushed Cache >... >some Hex-Adresses> > >I have to boot from rescue SLES9 CD (with defaultkernel-smp-2.6.5-7.97) Sage bäurer GmbH Firmensitz: Auf der Steig 6, 78052 Villingen-Schwenningen Registergericht: Amtsgericht Freiburg i. Br., HRB 611793 Geschäftsführer: Franz Bruckmaier, Dr. Thomas Scholtis _______________________________________________ suse-sles-e mailing list [email protected] http://listx.novell.com/mailman/listinfo/suse-sles-e