SUSE 9.0 lockup on Intel D875PBZ
Further to my previous post (GRUB, SATA etc) my D875PBZ-based box is hanging on boot. I have: 1 PATA drive (pri master), 1 DVD (sec master) and 2 SATA drives. I am booting off the first SATA drive (SATA0). It gets to runlevel 5 and starts various things (lots of green done messages) but then stops. The last two lines on screen are: Starting hardware scan on bootStarting CRON daemon done Starting Name Service Cache Daemon done I tried booting with the failsafe args(no dma, apm, acpi, smp, apic etc) but that hung earlier in the boot. The last line is: hde: attached ide-disk driver. I don't see anything wrong in the log before that. Does anybody have any suggestions what may be wrong or where to look for more diagnostics? This is the same m/b that 'root' says works fine (and indeed my box works under SuSE 8.2 with an earlier Mantel .21 kernel) Cheers, Dave
Hello Dave, Wednesday, January 28, 2004, 10:09:23 AM, you wrote: DH> Further to my previous post (GRUB, SATA etc) my D875PBZ-based box is DH> hanging on boot. I have: DH> 1 PATA drive (pri master), 1 DVD (sec master) and 2 SATA drives. DH> I am booting off the first SATA drive (SATA0). It gets to runlevel 5 and DH> starts various things (lots of green done messages) but then stops. The DH> last two lines on screen are: DH> Starting hardware scan on bootStarting CRON daemon done DH> Starting Name Service Cache Daemon done DH> I tried booting with the failsafe args(no dma, apm, acpi, smp, apic etc) DH> but that hung earlier in the boot. The last line is: DH> hde: attached ide-disk driver. DH> I don't see anything wrong in the log before that. DH> Does anybody have any suggestions what may be wrong or where to look for DH> more diagnostics? I didn't want to mention this in my previous post, but now that you seem to be able to boot to a point... The board I installed Suse 9.0 on had both the Intel ICH5 SATA controller and a Silicon Image Sil3112a SATA controller. I managed to get Suse installed to the drives connected to the SI interface w/o too much trouble. However, when I tried to move the boot disk from the SI controller to the ICH5 controller (and make the necessary changes in BIOS), I experienced the exact same problems that you're describing, using the latest Suse 2.4 kernel. I attributed this problem to a driver issue with the controller in the kernel and left the drives on the SI SATA ports. I've been reading related posts regarding SATA interfaces, but it seems everyone is avoiding the ICH5 controller in preference for their secondary SATA controllers. I know I avoided the ICH5 controller since my research stated that there wasn't support for it in the default Suse kernel at the time. I wish you the best of luck in solving this problem as I would like to know the answer also (if there is one). -- Best regards, Brian Curtis
Dave Howorth wrote:
Further to my previous post (GRUB, SATA etc) my D875PBZ-based box is hanging on boot. I have:
1 PATA drive (pri master), 1 DVD (sec master) and 2 SATA drives.
I am booting off the first SATA drive (SATA0). It gets to runlevel 5 and starts various things (lots of green done messages) but then stops. The last two lines on screen are:
Starting hardware scan on bootStarting CRON daemon done Starting Name Service Cache Daemon done
I tried booting with the failsafe args(no dma, apm, acpi, smp, apic etc) but that hung earlier in the boot. The last line is:
hde: attached ide-disk driver.
I don't see anything wrong in the log before that.
Does anybody have any suggestions what may be wrong or where to look for more diagnostics?
This is the same m/b that 'root' says works fine (and indeed my box works under SuSE 8.2 with an earlier Mantel .21 kernel)
Cheers, Dave
Hi Dave, I recently posted about my attempt to install 9.0 to SATA on a D875PBZ. I tried the installation exactly the same way you did, by not bringing the PATA into the drive selection. Whenever I booted from DVD I got the same message that you're getting now: 'hde: attached ide-disk driver.' then it freezes. At lease you were able to load onto a SATA whereas I was not. I'm curious if you're running the same BIOS version. Mine is BZ87510A.86A.0083.P18. I'm also curious as to which kernel was installed onto your system. Mine shows the smp4G kernel. Dmesg shows CPU0 and CPU1 despite there being only 1 CPU on the system. Dan - wo6m
Dan wrote:
I recently posted about my attempt to install 9.0 to SATA on a D875PBZ. I tried the installation exactly the same way you did, by not bringing the PATA into the drive selection. Whenever I booted from DVD I got the same message that you're getting now: 'hde: attached ide-disk driver.' then it freezes. At lease you were able to load onto a SATA whereas I was not.
So you see the problem when you're in Legacy mode whereas I see it in Enhanced? That's curious. Things have moved on since. I rebooted the machine a couple more times and eventually it came all the way up. I was able to do some more configuration and then it locked up (I was formatting the second SATA drive at the time). After rebooting, it runs again and I've completed the disk setup. As I write, I've just fsck'ed one of the new partitions on that drive and the system has locked up when I tried to fsck the second partition :( Anybody got any ideas on tracking this down?
I'm curious if you're running the same BIOS version. Mine is BZ87510A.86A.0083.P18. I'm also curious as to which kernel was installed onto your system. Mine shows the smp4G kernel. Dmesg shows CPU0 and CPU1 despite there being only 1 CPU on the system.
My BIOS version is BZ87510A.86A.0038.P08. The kernel is smp4G. You see CPU0 and CPU1 because it's a hyperthreading processor, it's normal. And that's also why the SMP kernel is chosen.
Dan - wo6m
Glad you've got a name, Dan :) Cheers, Dave
I wrote:
As I write, I've just fsck'ed one of the new partitions on that drive and the system has locked up when I tried to fsck the second partition :(
Anybody got any ideas on tracking this down?
OK. That time I tried several reboots and it locked up at the same place each time. So I switched it off and had lunch. Now it's working again and I'm running some fscks with bad block tests. It seems to me that the 2.4 kernel shipped with SUSE 9 is not stable on this hardware (unless there's a hardware bug!). Does anybody know of any other 2.4 versions (or compile options) that might help? How stable is the 2.6 kernel that ships with SUSE 9 - is that safe to use for a normal user's desktop machine? Cheers, Dave
On Thu, 2004-01-29 at 08:15, Dave Howorth wrote:
OK. That time I tried several reboots and it locked up at the same place each time. So I switched it off and had lunch. Now it's working again and I'm running some fscks with bad block tests.
It seems to me that the 2.4 kernel shipped with SUSE 9 is not stable on this hardware (unless there's a hardware bug!). Does anybody know of any other 2.4 versions (or compile options) that might help? How stable is the 2.6 kernel that ships with SUSE 9 - is that safe to use for a normal user's desktop machine?
Cheers, Dave
This looks more like a hardware problem, most likely the PS. I had a similar problem recently and it was the PS. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Kenneth Schneider wrote:
OK. That time I tried several reboots and it locked up at the same place each time. So I switched it off and had lunch. Now it's working again and I'm running some fscks with bad block tests.
It seems to me that the 2.4 kernel shipped with SUSE 9 is not stable on this hardware (unless there's a hardware bug!). Does anybody know of any other 2.4 versions (or compile options) that might help? How stable is the 2.6 kernel that ships with SUSE 9 - is that safe to use for a normal user's desktop machine?
This looks more like a hardware problem, most likely the PS. I had a similar problem recently and it was the PS.
I don't think so because (a) somebody else has the same problem on another machine (b) I don't seem to get the problem with the BIOS in Legacy mode, or (c) in W2000 or (d) in SuSE8.2 or (e) in Knoppix, all of which are on the machine. Cheers, Dave
Hi, You should use newer kernel from SuSE ftp. The last one I supppose is 2.4.21-166. Additionally, I found that Netatalk completely freeze machine if it has 2 network cards (I have 875Wp-1S m/b). On Jan 29, 2004, at 16:12, Dave Howorth wrote:
Kenneth Schneider wrote:
OK. That time I tried several reboots and it locked up at the same place each time. So I switched it off and had lunch. Now it's working again and I'm running some fscks with bad block tests.
It seems to me that the 2.4 kernel shipped with SUSE 9 is not stable on this hardware (unless there's a hardware bug!). Does anybody know of any other 2.4 versions (or compile options) that might help? How stable is the 2.6 kernel that ships with SUSE 9 - is that safe to use for a normal user's desktop machine? This looks more like a hardware problem, most likely the PS. I had a similar problem recently and it was the PS.
I don't think so because (a) somebody else has the same problem on another machine (b) I don't seem to get the problem with the BIOS in Legacy mode, or (c) in W2000 or (d) in SuSE8.2 or (e) in Knoppix, all of which are on the machine.
********************************************* * Best Regards --- Andrei Verovski * * Personal Home Page * http://snow.prohosting.com/guru4mac/ * Mac, Linux, DTP, Development, IT WEB Site *********************************************
On Thursday 29 January 2004 14.15, Dave Howorth wrote:
How stable is the 2.6 kernel that ships with SUSE 9 - is that safe to use for a normal user's desktop machine?
Don't use the one that ships, it's just a test kernel, it was outdated even before the boxes hit the stores. If you're going to try 2.6 it's better to get the later builds from $YOUR_FAVOURITE_SUSE_MIRROR/people/kraxel/ I've been running 2.6.1 from there for a while now and it's been 100% stable so far under "average" desktop use
participants (6)
-
Anders Johansson -
Andrei Verovski -
Brian Curtis -
Dave Howorth -
Kenneth Schneider -
root