[intrepid] HP Compaq 6715s very slow - need to be blacklisted?

[Oibaf]

In 2.6.27-rc9 I noticed a fix/blacklist (commit e84956f92a846246b09b34f2a728329c386d250f) for two ATI laptop that set thermal trip points to insanely low values. A more general fix for some HP machine was later merged on upstream 2.6.27.2:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=commit;h=e87898fdba90f9a270ae6bdb8ce98da91338a951
Unfortunately this fix does not cover 6715s.

I am using current Ubuntu LiveCD which ships kernel 2.6.27-6.9 and I noticed a similar problem on my HP Compaq 6715s (with latest BIOS F.0D 08/20/2008).

Steps to reproduce: run current LiveCD (downloaded from http://cdimage.ubuntu.com/daily-live/). The system is really slow, the fan is always active, but ouput fresh air.

If can be useful, running the following command as found here:
http://marc.info/?l=linux-acpi&m=121396447214047&w=4
I get:
$ cat /proc/acpi/thermal_zone/TZ*/trip_points
critical (S5): 105 C
passive: 16 C: tc1=1 tc2=2 tsp=100 devices=C000 C001
active[0]: 16 C: devices=C39B
active[1]: 16 C: devices=C39C
active[2]: 16 C: devices=C39D
active[3]: 16 C: devices=C39E

There is a patch available at http://bugzilla.kernel.org/show_bug.cgi?id=11516#c52

See also http://bugzilla.kernel.org/show_bug.cgi?id=11719

Thanks

[Ivo Mans (ivomans)]

I've got also the HP Compaq 6715s and experience same problem with fan always active and extreme slow CPU performance.

[kulight (kulight)]

i have the same problem on the same machine
cpu performance is very poor making the laptop unusable

fix is already knows please fix it quickly

[Fume (fume)]

i have the same problem on HP Compaq 6715s.
When I print the "apic=off" option in the grub menu.lst then
it runs much faster.

[kulight (kulight)]

"
i have the same problem on HP Compaq 6715s.
When I print the "apic=off" option in the grub menu.lst then
it runs much faster.
"

can u write detailed instructions on how to do that?

thank u very much

[Fume (fume)]

Enter to Terminal

sudo gedit /boot/grub/menu.lst

then go to the kernel line and insert "apic=off" see here:

title Ubuntu 8.10, kernel 2.6.27-7-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=a2dd92fe-4444-44fe-994a-dd45857b05f0 apic=off ro quiet splash
initrd /boot/initrd.img-2.6.27-7-generic
quiet

With this option its possible to use the laptop until the bug is fixed.

[kulight (kulight)]

thank you endlessly
it did the trick and also fixed the restart and shutdown problem i had

[Ivo Mans (ivomans)]

I just tried the 'apic=off' addition as per Fume's explanation, but after reboot I don't notice any improvement: fan is still blowing cold air like crazy and system still very slow.

[Michael (mijobe)]

instead of apic=off use noapic

[Ivo Mans (ivomans)]

Thanks! 'noapic' works for me.

Nevertheless a fix in the kernel for this machine would still be the real solution, so that new users can work with this type of laptop just from a normal install.

[knuutsen (peter-vornberg)]

Hey there,

same as me. Also have 6715s and noapic works for me. But standby or hibernation are critical. Perhaps it has something to do with this noapic function. Besides some probs still out there that makes ubuntu not funny working on a 6715s. Which problems that are? Too much and the USB - Hub combined with this incredible SB600 in my opinion is one of them and it still has something to do with this bug here.

Ahh did i forget the audio probs...ok thats another story...and at least my lovely elisa won't work with the grafic drivers (both: fglrx and radeonhd)....

Hopefully this gets a fix soon... knuutsen

[Crispin Kirchner (kcrispin)]

Hey guys!

For me neither 'apic=off' nor 'noapic' worked. Try 'nolapic'! it did the trick for me.

@knuutsen: did you try the 'radeon' driver which is automatically loaded? Since 8.10 it also supports 3D-acceleration for the RS690 Chip (which is in my 6715s)

greetings,

Crispin

[knuutsen (peter-vornberg)]

Hey Crispin,
i changed back to radeon but can this driver really support 3d now?! I verified that this wasn't the case while i tried openarena and elisa. These programs need 3 d . And the compiz effects in gnome are running with these 2d engine or do i miss something? I will check it out!

Thanks for this advise - please can you tell me the exact radeon driver you use ... thx.

[knuutsen (peter-vornberg)]

So forget my entry before, Crisp, you are right it function well...wow i'm impressed; just tried openarena and it's nice yet.
Elisa won't start, but thats a bug out of ubuntu.. i read.

Thx and the next is to try this ibex with a beamer... i cannot await this. If this works i will totally change to ubuntu! Hopefully it goes....

thx Crisp and cya knuutsen

[J. (jose-manuel-rodriguez-moreno)]

I confirm the same issue on hp Compaq 6715b

The 'noapic' workaround has also worked on this machine.

Thanks a lot for sharing,
J.

[Tim Gardner (timg-tpi)]

Sounds like there is a fix pending in 2.6.26.8

[Oibaf (oibaf)]

This should be fixed in current jaunty kernel (2.6.28 based). Leaving opened for Intrepid.

[Oibaf (oibaf)]

Apparently, the fix was applied to 2.6.27.8:
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27.8

[kulight (kulight)]

so there is a fix...
how would i install the fixed version on my laptop ???
i have no system installed now and installing with this bug is impossible

[Stefan Friesel (stefan-friesel)]

The fix is only in vanilla kernel and ubuntu jaunty right now. Using the noapic or nolapic boot parameter (s.a.) should work at least for installing. I then installed the current jaunty kernel under intrepid, which works afaics.

[kulight (kulight)]

how do i add these parameter (noapic) on the live cd ?

[knuutsen (peter-vornberg)]

Hey kulight (hey Friesel),

if you see the picture for installing you have below the changes F1 till (i guess) F4 or F6. One of the F buttons lets you change the boot parameters... go to the end of the boot line i think you should read "splash" as the last word. After that enter noapic and press Enter or B . Than it should work.

Hope i recognize it right... if not i will proof it.

cya knuutsen

Hey Friesel,

do i need the repositories of jaunty and which one edit in sources.lst ?

cu knuutsen

[Stefan Friesel (stefan-friesel)]

@knuutsen:
You should not add the jaunty repositories to your sources list (unless you want to switch to jaunty which is far from being stable yet). Instead you can download the single package [1] and install it manually. But I cannot guarantee this will work for you and surely there is a much better way to get the fix (maybe from a PPA). Also you should look out for the next kernel update in intrepid and switch back to to the official intrepid kernel asap.
Hope this helps but you should post any follow-up question on a forum (e.g. ubuntuforums.org) as there are quite a few people subscribed to this bug.

[1] http://packages.ubuntu.com/jaunty/base/linux-image-2.6.28-2-generic

[knuutsen (peter-vornberg)]

Hey Friesel,
thx it worked for me, but after deinstalling the fglrx cause it needs the linux-headers to work properly. Using the radeon driver is no problem with the 2.6.28-2 kernel out from jaunty. To have the Wlan as well you must also install linux-restricted 2.6.28-2 from jaunty if you prefer the STA Broadcom Wireless driver.

I also tried to activate the linux-headers 2.6.28-2.3 (devel) (there is 2.6.28-2 included) for reactivating fglrx. But it doesn`t work.

Any ideas?

Thx to all here; in short - the problem is solved - see Stefan Friesel - with the new kernel in jaunty.

My laptop is a dual amd HP 6715s.

[Oibaf (oibaf)]

Should have been fixed in 2.6.27-11.21 (intrepid proposed).

[Stefan Friesel (stefan-friesel)]

Fix confirmed on intrepid x86_64

Kudos to everyone involved in getting this fixed.

[Oibaf (oibaf)]

There is a new BIOS for the HP 6715s: F.0E (25 Nov 2008):
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?&prodTypeId=321957&prodSeriesId=3368539&swItem=ob-67085-1&prodNameId=3356623&swEnvOID=2103&swLang=24&taskId=135&mode=5

Maybe someone could try if the new BIOS fixes the issue also with the original 8.10 kernel (previous F.0D BIOS still had this issue).

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Oibaf (oibaf)]

(Note that the F.0E BIOS still doesn't fix the problem)

[Oibaf (oibaf)]

This is no longer needed on jaunty and nobody appears to care to fix the 8.10 release notes.

[Steve Langasek (vorlon)]

nevertheless, let's correctly document this as 'wontfix'.

[Stefan Friesel (stefan-friesel)]

Just because nobody cares to fix them (yet) doesn't mean the release notes are fixed.

[Steve Langasek (vorlon)]

no, but it does mean they're unlikely to get further attention now that another release is upon us.

[Stefan Friesel (stefan-friesel)]

Sorry, I wrote parallel to Steve, so my answer only refered to Fabio. Anyway I think the bug shouldn't be closed just because it isn't solved yet (mark any bug older than x months as won't fix!?). It's not an overwhelming task for someone having write access ;-)

[Oibaf (oibaf)]

> Sorry, I wrote parallel to Steve, so my answer only refered to Fabio.
> Anyway I think the bug shouldn't be closed just because it isn't solved
> yet (mark any bug older than x months as won't fix!?). It's not an
> overwhelming task for someone having write access ;-)

I closed it not because it isn't fixed in 8.10, but because it is fixed on jaunty ;) (since the kernel has the fix the release notes doesn't need to mention it). The right way to manage it should be to left it closed and nominate it for intrepid, but Ubuntu release notes apparently can't be nominated for older releases. Leaving it opened may also confuse developers/user that are managing/searching Ubuntu release notes bugs for jaunty.