Hot reboot freeze on HP 8510w - Ubuntu 8.10

[Nikolaj Hansen]

Hi,

My laptop hangs during warm reboot when I reboot the new 8.10 Intepid Ibex. The regular bios is loaded and the system then hangs when trying to load the Intel bios extensions. The system is a newer HP 8510w.

The problem was non existing on 8.04.

My layman guess would be that there is some memory conflict when doing a warm reboot on the system, and the bios extension does not load.

A cold reboot (power off) solves the problem as a work around.

See attached file

regards

Nikolaj Hansen

Update:

I now flashed the laptop with the latest bios and extensions. The fault remains the same.

[Mike (mikeheggy)]

I can also confirm this bug. I also have a HP 8510w, and upgraded from 8.04 to 8.10. This causes the same issue described above.

Regards
Mike

[Sari Luca (sari-luca)]

I have the same issue on my HP 8510w.

[janne5011 (jan-nordin)]

I have the same issue on HP 6910p

[dontpanic (robban-robert-deactivatedaccount)]

Same issue with my Acer Extensa 5220

[asdfred (gurrenfred)]

Also same issue with an extensa 5220.

[Nikolaj Hansen (barnabasdk)]

The issue is also on the latest 9.04.

However I think I accidently solved this. Follow these steps:

1) boot laptop normally.

2) Go into hibernation

3) Start from hibernation

4) reboot pc immediatly after restart from hibernation

5) PC now does not hang, but boots just fine

I am more and more convinced that the Intel VPro chipset is on LSD.

It would be nice to hear if this solves the issue for anyone else.

with regards

Nikolaj Hansen

[Peter Curtis (petedcurtis)]

I know this is an old thread. But I've got this exact same problem on two HP8510w. I just put up with it by letting cool down for 5 minutes. Strange is once it gets into Windows it does keep running OK.
But today I was trying to install a SSD. And both kept cutting out very quickly just could not complete the Ghost restore before it cut off. I raised the keyboard and felt CPU and it was very hot. I placed an ice pack on it and it ran OK. So it seems for some reason the CPU heats up to much very quickly whilst booting, but once running WIN XP it keeps cooler. So I'm guess maybe it is something in the BIOS is setting the CPU to run really hot somehow. So if the CPU is running very hot, it will keep tripping out on a reboot. Of course doing a restore it takes much longer to get to windows via the CD boot. I am running BIOS V14 and there is now a release V20 on the HP driver web site for th HP8510w. But apparently you cannot roll back the BIOS to earlier version once you go to V.20.

BTW: I did clean out the fluff n stuff from the fan and the fans always on. So its not that. I've not yet upgraded to BIOS V.20.
I'll try that next.

Peter

[Peter Curtis (petedcurtis)]

Hi, Tried BIOS V.20 and no change. It seems that the CPU will only run cool if its in WIndows, XP in my case. I also cleaned and replaced the thermal paste on the CPU & GPU and no change except it ran a little bit longer before crashing. When I try to do anything outside windows like booting using EaseUs boot CD it will crash as the CPU it gets hot usually witin two minutes. Placiing a large metal block on the CPU cooling sink on top of the CPU or placing a gel pack on the CPU will keep it running. So it's definitely the CPU overheating. My guess as it never loads WINDOWS OS it has to be a BIOS issue of some sort. Maybe its the overtemp trip in the CPU which is to sensitive, but as it only occurs in BIOS mode seems this could be changed somehow by a change in the BIOS?.
Peter Curtis

[Nikolaj Hansen (barnabasdk)]

I think you misunderstand my initial bug report.

Hot / cold reboot has got nothing to do with the operating temperature of the system.

1) A hot reboot is when you select "reboot" in what ever system you are running.

2) A cold reboot is when you power of the system completely. And then restart.

The temperature of my cpu has never been an issue.

[Sam Gweon (gweon)]

Hi, this bug also affects me with my HP 8510w. I am using Ubuntu 12.04 with the following kernel (see below for the "uname -a" output). This bug has been affecting me for the last several months, but I do not know exactly when it started. I suppose it started after one of those software updates, which I do almost everyday.

I really like to have this bug solved somehow! The main reason is that I am often accessing my laptop remotely with wake-on-lan. If I mistakenly type "sudo reboot" (which I remember not to, these days) then my laptop is no longer accessible from a remote location due to this bug, which makes it hang indefinitely at the BIOS prompt! For this reason, I would call this a very severe bug. In my more than 15 years of using Linux, this is the first time I experience this particular bug, and very disappointingly, it seems very hard to fix, based on what I can search and find on the internet.

# uname -a
Linux xyz 3.2.0-37-generic-pae #58-Ubuntu SMP Thu Jan 24 15:51:02 UTC 2013 i686 i686 i386 GNU/Linux

[penalvch (penalvch)]

Nikolaj Hansen, thank you for reporting this bug to Ubuntu. Jaunty reached EOL on October 23, 2010.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 295512

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]