Cannot reboot the system. Last message seen on the console is "Uptime: 1d2h33m". At this time the keyboard is unresponsive and a physical power cycle is needed to complete the reboot. Hardware is: Dell R815, Four AMD 12 Core CPUs, 64GB RAM. How-To-Repeat: Use Dell r815.
Are you eventually able to make some tests on that machine if I send you some instruction/patches? Is the problem 100% reproducible? Can you try by starting with showing "sysctl hw.acpi.handle_reboot" and force it to 0 (and see what happens)?
On Apr 20, 2012, at 6:17 PM, Attilio Rao wrote: > Are you eventually able to make some tests on that machine if I send > you some instruction/patches? Is the problem 100% reproducible? > Can you try by starting with showing "sysctl hw.acpi.handle_reboot" > and force it to 0 (and see what happens)? Hello Attillio, I have hardware dedicated to resolving this problem. The problem is 100% reproducible. The sysctl you asked for is already set to zero. sysctl -a |grep handle_reboot hw.acpi.handle_reboot: 0 --RX
2012/5/1, RX <rx@sigint.ws>: > On Apr 20, 2012, at 6:17 PM, Attilio Rao wrote: > >> Are you eventually able to make some tests on that machine if I send >> you some instruction/patches? Is the problem 100% reproducible? >> Can you try by starting with showing "sysctl hw.acpi.handle_reboot" >> and force it to 0 (and see what happens)? > > > Hello Attillio, > > I have hardware dedicated to resolving this problem. > > The problem is 100% reproducible. > > The sysctl you asked for is already set to zero. > > sysctl -a |grep handle_reboot > hw.acpi.handle_reboot: 0 Can you try to update your BIOS to latest available version and see if handle_reboot changes its value? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein
On 05/01/12 15:29, Attilio Rao wrote: > Can you try to update your BIOS to latest available version and see if > handle_reboot changes its value? Thanks, Attilio The system is already running the current bios version, 2.3.0. What relation does handle_reboot have here ? All systems I've checked have this set to '0'. --RX
2012/5/2 RX <rx@sigint.ws>: > On 05/01/12 15:29, Attilio Rao wrote: >> >> Can you try to update your BIOS to latest available version and see if >> handle_reboot changes its value? Thanks, Attilio > > > The system is already running the current bios version, 2.3.0. > > What relation does handle_reboot have here ? =C2=A0All systems I've check= ed have > this set to '0'. It means that your ACPI FADT doesn't likely have RESET_REG on. However, maybe you don't even get to the cpu stopping part, can you apply the following patch and tell me if you see more output before to stop? http://www.freebsd.org/~attilio/shutdowncheck.patch Also do you have a serial console you can use on any of those machines? Attilio --=20 Peace can only be achieved by understanding - A. Einstein
On May 12, 2012, at 9:18 AM, Attilio Rao wrote: > It means that your ACPI FADT doesn't likely have RESET_REG on. > However, maybe you don't even get to the cpu stopping part, can you > apply the following patch and tell me if you see more output before to > stop? > http://www.freebsd.org/~attilio/shutdowncheck.patch Thanks. Both checkpoints are reached. The last line is "Rebooting...". > Also do you have a serial console you can use on any of those machines? I'll make it happen. --RX
While working at setting up the serial console I noticed the system will = reboot at the boot menu by hitting option #3. --RX
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped