Hello, I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down or reboot on their own. I always have to physically power them off and then back on. They are SMP machines and I am using ACPI. There are no other apparent problems although one machine did panic today and as a result I had to drive in and power cycle it. I saw some posts about this in mail archives, but they were very old. Has anyone else experienced this problem? What should I look for to fix this? -Will
> -----Original Message----- > From: Peter Jeremy [mailto:peter.jeremy@alcatel.com.au] > Sent: Sunday, January 16, 2005 6:56 PM > To: Will Saxon > Cc: stable@freebsd.org > Subject: Re: Machine(s) not able to reboot > > > > [Please wrap your mail before 80 columns]Sorry, have to do it manually and I forgot.> > On 2005-Jan-16 18:39:41 -0500, Will Saxon > <WillS@housing.ufl.edu> wrote: > >I have two HP Proliant DL360G3 servers which I recently upgraded from > >5.2.1-R to 5.3-R. Since the upgrade, I am not able to cause the > >machines to shut down or reboot on their own. I always have to > >physically power them off and then back on. > > I have this problem with some DL380's. I have been unable to work out > what the root cause is but I've found that the problem is triggered by > kldload(8). If I don't use any modules other than acpi.ko (which is > loaded by /boot/loader) then I don't have the problem. >This works for me also. I had not added device vlan to my kernel config and was also loading the sysvipc stuff, usb and linux/linprocfs. Thanks! -Will
On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon <WillS@housing.ufl.edu> wrote:> Hello, > > I have two HP Proliant DL360G3 servers which I recently upgraded from 5.2.1-R > to 5.3-R. Since the upgrade, I am not able to cause the machines to shut down > or reboot on their own. I always have to physically power them off and then back > on. They are SMP machines and I am using ACPI. There are no other apparent > problems although one machine did panic today and as a result I had to drive in > and power cycle it.I haven't heard of this problem before, and I was wondering if today's 5.3-R errata notice (more than one IPI per APIC causes deadlock) might have something to do with it. Are these machines running SMP? - John
> -----Original Message----- > From: jmc [mailto:jcagle@gmail.com] > Sent: Sunday, January 16, 2005 11:39 PM > To: Will Saxon > Cc: stable@freebsd.org > Subject: Re: Machine(s) not able to reboot > > > On Sun, 16 Jan 2005 18:39:41 -0500, Will Saxon > <WillS@housing.ufl.edu> wrote: > > Hello, > > > > I have two HP Proliant DL360G3 servers which I recently > upgraded from 5.2.1-R > > to 5.3-R. Since the upgrade, I am not able to cause the > machines to shut down > > or reboot on their own. I always have to physically power > them off and then back > > on. They are SMP machines and I am using ACPI. There are no > other apparent > > problems although one machine did panic today and as a > result I had to drive in > > and power cycle it. > > I haven't heard of this problem before, and I was wondering if today's > 5.3-R errata notice (more than one IPI per APIC causes deadlock) might > have something to do with it. Are these machines running SMP? > > - John >They are. I believe the panic could be related to the problem announced today also, as the panicked machine occasionally sees bursts of high load caused by multiple hungry processes. The other email response to this issue, about this happening when using loaded modules, fixed the problem for me. I compiled new kernels with linux emulation, etc. in kernel and the problem stopped. What a relief. I have verified that at least on one machine the hangup problem will continue even when only usb and acpi are loaded via module. This will happen by default on the Proliant servers since by default usbd is loaded at boot. -Will