Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Mar 2005 02:30:07 GMT
From:      Chen Zhao <chen@metcomm.net>
To:        freebsd-i386@FreeBSD.org
Subject:   Re: i386/72441: HP Proliant DL380 hangs on reboot with 5.3
Message-ID:  <200503160230.j2G2U7bL034674@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/72441; it has been noted by GNATS.

From: Chen Zhao <chen@metcomm.net>
To: jhb@FreeBSD.org
Cc: freebsd-gnats-submit@FreeBSD.org, PeterJeremy@optushome.com.au
Subject: Re: i386/72441: HP Proliant DL380 hangs on reboot with 5.3
Date: Tue, 15 Mar 2005 21:26:56 -0500

 This problem still occurs with 5.3-RELEASE-p5.
 We were bit by this too with a new server we're trying to put into 
 production.  We have a dual cpu 2.8Ghz system.  Snip from non-verbose dmesg:
 ==
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  6
 MADT: Forcing active-low polarity and level trigger for SCI
 ==
 
 We tried several bios options to change the mp table mapping.
 Aside from the default 'auto', we also tried 'apic' and 'full'.
 We also tried changing the OS selection from 'linux' to 'other'.
 Nothing has made a difference, although it does change the
 output at shutdown a little.
 
 The last two lines displayed on the console after attempting the reboot
 change slightly, depending on the options above, but I don't have it exactly 
 verbatim, and I don't have what changes coincide with which lines, as I was 
 working with someone at the datacenter where the server is located, and we 
 don't have a serial console hook up (yet?).
 
 ==
 cpu_reset called on cpu #0
 cpu_reset: Stopping other CPUs
 ==
 
 ==
 cpu_reset: Restarting BSP
 cpu_reset_proxy: Stop CPU 1
 ==
 
 I'm love to help trouble shoot this, but the difficulty is of course
 needing someone to be at the datacenter when the attempted reboots don't 
 come back.  We may be able to get some integrated lights out management
 going but I don't have an eta on that.
 
 Is there any info I can provide from a running system to help?
 
 My impression is that the initial install rebooted itself correctly, 
 but I could be wrong.  I just know that finding that the system did not
 reboot after a cvsup to -p5 came as a bit of a shock.
 Any attention to this is appreciated, thanks.  This is quite critical 
 to us as well.  
 
 -- 
 | Chen Zhao
 | Chief Cynic
 | WizNix, Inc. :: Solutions for troubled networks.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503160230.j2G2U7bL034674>