[Compaq Presario R3200 CTO] Kernel regression.... boot param acpi=off now NEEDED

[Israel Dahl]

Currently running 10.04 and no boot param needed.

WORKAROUND: From 10.10 and onward I have needed kernel parameter acpi=off

Which is of course a bad idea to run a system without acpi. I have tried numerous boot parameters and none work consistantly. acpi_osi Windows 2006 (2001 SP1/SP2) worked occasionally. This affects other distros as well. Lucid puppy 5.25 works perfectly, but the current slacko puppy does not. all ubuntu derivatives are commonly affected, as well as debian. I have tried running some other live CDs of others (Arch, etc..) all with the newer kernels are affected. This is related to other bugs

626622
633596
and probably more than that.
Maverick is where the issue began.

I am absolutely sure it is the kernel because of running non Ubuntu OS with the later kernels and needing the param acpi=off.
I would like to use the modern systems for my computer, as they have much better features, and some of the newer programs are something I really want to use.
Any other information needed I will provide
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-14-generic 3.0.0-14.23
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic i686
AcpiTables:

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: test 1197 F.... xfce4-volumed
                      test 1201 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 33
   Simple ctrls : 22
Date: Tue Dec 13 15:31:01 2011
HibernationDevice: RESUME=UUID=178007cb-6931-4c28-bd05-83cb7e7a4f3f
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 002: ID 04b3:310b IBM Corp. Red Wheel Mouse
MachineType: Hewlett-Packard Presario R3200 (PF153UA#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=22ff7388-e573-44ce-9842-c6434ddd3bd6 ro acpi=off
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-14-generic N/A
 linux-backports-modules-3.0.0-14-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2004
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.11
dmi.board.name: 08A0
dmi.board.vendor: Compal
dmi.board.version: 32.22
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.11:bd04/30/2004:svnHewlett-Packard:pnPresarioR3200(PF153UA#ABA):pvrF.11:rvnCompal:rn08A0:rvr32.22:cvnCompal:ct10:cvr:
dmi.product.name: Presario R3200 (PF153UA#ABA)
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard
---
AcpiTables:

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: love 1530 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'nForce3'/'NVidia nForce3 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 33
   Simple ctrls : 22
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=dd870a3f-02fe-4195-b2c9-f85eb37a1140
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Presario R3200 (PF153UA#ABA)
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-6-generic root=UUID=0d668b39-80f8-4eb0-b84f-555e2d724418 ro acpi=off
ProcVersionSignature: Ubuntu 3.5.0-6.6~precise1-generic 3.5.0
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-6-generic N/A
 linux-backports-modules-3.5.0-6-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.5.0-6-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/30/2004
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.11
dmi.board.name: 08A0
dmi.board.vendor: Compal
dmi.board.version: 32.22
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.11:bd04/30/2004:svnHewlett-Packard:pnPresarioR3200(PF153UA#ABA):pvrF.11:rvnCompal:rn08A0:rvr32.22:cvnCompal:ct10:cvr:
dmi.product.name: Presario R3200 (PF153UA#ABA)
dmi.product.version: F.11
dmi.sys.vendor: Hewlett-Packard

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[Israel Dahl (israeldahl)]

https://wiki.ubuntu.com/MaverickMeerkat/ReleaseNotes

"With 10.10 we have also dropped support for i586 and lower processors, as well as i686 processors without cmov support. "

Does this latest Kernel re include support? Because this may be the issue I am facing? I will try the newest one and post back my findings.

[uski (ba-cykian)]

Hello,

Tested today on a Presario R3200 with kernel 3.3-rc1.
Bug exists as decribed on Ubuntu 11.10; it needs acpi=off to boot properly both with the current 3.0.0-15 kernel package and with the 3.3-rc1 package.

Hope this feedback helps.

[Israel Dahl (israeldahl)]

Oh good, I am glad someone else can confirm it. I hope this bug gets fixed, as I would like to run 12.04 on the Presario. Still have a few months to get a fix before it is out

[penalvch (penalvch)]

Israel Dahl, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Israel Dahl (israeldahl)]

I have tested the Quantal ports to precise with it, and still not working.... however I will boot into it and run apport-collect -p linux 903961 when I have the opportunity. Currently I have been able to run precise with the OLD Lucid Kernel (which makes it run slowly and makes it somewhat useless...)

[Israel Dahl (israeldahl)]

Ok, That is more info for you!!
I changed the 'needs-upstream-testing' to 'kernel-bug-exists-upstream-linux-3.5.0-6-generic'
I obviously am testing the quantal kernel in Precise, as I thought it may have been fixed WAY up stream, but this isn't the case. The problem developed in the switch from lucid to maverick. I have wiped the hard drive and reinstalled. I've tried numerous OS. All linux kernels past the 2.6.3(something) mark are affected.

[penalvch (penalvch)]

Israel Dahl, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903961/comments/27 :
<"I changed the 'needs-upstream-testing' to 'kernel-bug-exists-upstream-linux-3.5.0-6-generic' I obviously am testing the quantal kernel in Precise..."

Unfortunately, testing the quantal kernel is not testing the mainline kernel as requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903961/comments/6 .

In addition to testing the mainline, the next step is to perform a kernel bisect from Lucid to Maverick, in order to identify the offending commit(s). Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Israel Dahl (israeldahl)]

Oh, ok... well I will download the latest non quantal kernel and rerun the apport command.
Before I commit to bisect the kernel, is there someway I can test it without causing my computer to hang during the boot process? or some ultra secret thing i can do to get out of a frozen and locked up boot process and simply reboot back to grub. Can I do this in a VM and it still produce the accurate results?

[penalvch (penalvch)]

Israel Dahl, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903961/comments/29 :
>"well I will download the latest non quantal kernel and rerun the apport command."

You will not be able to apport in a non-Ubuntu repository kernel, such as a mainline kernel. Hence, please do not worry about apport'ing it, as we trust you if you say you tested it. :D

>"Before I commit to bisect the kernel, is there someway I can test it without causing my computer to hang during the boot process? or some ultra secret thing i can do to get out of a frozen and locked up boot process and simply reboot back to grub."

Unfortunately, some things in the debugging process are more involving then others, and bisecting is one of them. I know of no way to test for the computer to hang, other than to hang it via the bisect process. However, bisecting is one of the most helpful debugging steps to provide to get your bug fixed as soon as possible.

>"Can I do this in a VM and it still produce the accurate results?"

You are welcome to test for the problem in a VM to provide hardware disparate datapoint(s). However, the issue is not a matter of accuracy. In a very high majority of linux (Ubuntu) kernel problems are hardware dependent. As the VM is virtualizing hardware via software, that is notably different from your host hardware, this will only further validate this is issue is dependent on your hardware. As well, we would have already received a rash of Launchpad bug reports noting, "XYZ virtualization platform(s) will not boot Ubuntu guests unless one does acpi=off."

[Israel Dahl (israeldahl)]

I have never bisected a kernel before, so I am checking out your recomended reading, and I have the latest precise 3.4.0-030400rc6, installed (rc7 only contained the 'all headers' file.... so I will only test rc6) I also downloaded the last lucid 2.6.33-020635rc1 and first maverick 2.6.33-02063306-generic to narrow it down and find the regression.

I really don't know anything about bisecting, except the little I have read so far. I had assumed I would have to reboot into every kernel to test it, so I was hoping to be able not to freeze my computer during the boot process.

[Israel Dahl (israeldahl)]

booting into 3.4.0-030400rc6 kernel hangs the boot process

so bug still exists upstream

[Israel Dahl (israeldahl)]

I am testing the kernels to find where the regression occured. And I am keeping my notes here to keep track of them

WORKING
The very first listed Maverick Kernel works.
2.6.33-02063306-generic_2.6.33-02063306
2.6.33-020633_2.6.33-020633
2.6.34-020634-generic_2.6.34-020634

NOT WORKING
LUCID
2.6.35-rc1-lucid... which is the last Lucid kernel in mainline (2.6.35-020635rc1)
MAVERICK
2.6.34-02063412-generic_2.6.34-02063412.201205172135
2.6.34-02063401-generic_2.6.34-02063401

[Israel Dahl (israeldahl)]

OK!!! The LAST working Kernel is
2.6.34-020634rc1-generic_2.6.34-020634rc1
the FIRST broken Kernel is
2.6.34-02063401-generic_2.6.34-02063401

@Christopher Penalver If I need some help bisecting can I contact you? If not who could assist me if I have questions. I am wondering if i can use git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git or if I need to use something else.

since i have to run acpi=off for it to work, what can I type to locate that specific part...
ex.' git log --oneline Ubuntu-2.6.35-24.42..Ubuntu-2.6.35-25.43 drivers/gpu/drm/radeon/'

[penalvch (penalvch)]

Israel Dahl, thank you for narrowing down the kernel version this regression occurs in.

As I am presently packing all my belongings and moving from one coast in the US to another (taking well needed micro breaks to help triage!), I will not be a great person to directly contact for a few weeks. Instead, it would be best if you need more immediate, granular help to contact the Ubuntu Kernel Team directly via IRC or mailinglist -> https://wiki.ubuntu.com/KernelTeam#Contacts .
You may also seek support via http://www.ubuntu.com/support .

Thank you for your understanding.

[Israel Dahl (israeldahl)]

Wow, thanks for helping me despite the huge move!!! I hope it all goes well for you! I have contacted the manager of the Kernel Team, and hopefully I can be put in touch with the right person to help. Thanks again, I had kinda given up on fixing this bug (as I am not a kernel programmer, and know very little about the kernel). I really appreciate your help in all sincerity.

[Joseph Salisbury (jsalisbury)]

Hi Israel,

I would be happy to help you with a bisect. Just to confirm we are starting the bisect in the right place, can you confirm the following:

Does NOT have the bug: v2.6.34-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc1/

First kernel that DOES have the bug: v2.6.34.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34.1-maverick/

[Israel Dahl (israeldahl)]

Thank you so much!!!
Yes that is absolutely correct.
Thank you (in advance) for your help!!

[Joseph Salisbury (jsalisbury)]

I started a kernel bisect between v2.6.34-rc1 and v2.6.34.1.

The first test kernel is available and is built up to commit:
6f063aea557f66eea8c35034a25df85cae5ced33

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test that kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

I just booted into your rc2 Kernel, and it works perfectly!!!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
5e31877b647bf41ad080adad6100a617ed4c6be4

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033568

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

http://people.canonical.com/~jsalisbury/lp1033568/
doesn't show
5e31877b647bf41ad080adad6100a617ed4c6be4

but i see this
http://people.canonical.com/~jsalisbury/lp903961/5e31877b647bf41ad080adad6100a617ed4c6be4/
Should I test that one??

Well, anyway the kernel from
http://people.canonical.com/~jsalisbury/lp1033568/
3.4.0-030400rc2-generic

Does NOT work
It hangs up when I boot

[Israel Dahl (israeldahl)]

I guess I will not be testing the one at
http://people.canonical.com/~jsalisbury/lp903961/5e31877b647bf41ad080adad6100a617ed4c6be4/
I am running the i386 not 64bit, though my computer does have AMD, and I have used a 64bit on it before....

[Joseph Salisbury (jsalisbury)]

Hi Israel,

The long directory names are the SHA1 of the test kernel. The kernels in those directories are the ones already tested. I just put them there to keep them around.

The latest test kernel is in the top level directory:
http://people.canonical.com/~jsalisbury/lp1033568/

There should be a 32-bit kernel available there with the name:
linux-image-3.4.0-030400rc2-generic_3.4.0-030400rc2.201208080008_i386.deb

Is that the one you tested in comment #43 that has this bug?

[Israel Dahl (israeldahl)]

Sorry for being confusing... I just noticed the directory name 'lp1033568' was different than the directory name 'lp903961' for the FIRST kernel I tested in comment #39.
 I was going to test both just incase you had accidentally mixed up two directories (as I am sure you are very busy with more important bugs than mine).
To clarify, YES I tested the linux-image-3.4.0-030400rc2-generic_3.4.0-030400rc2.201208080008_i386.deb
and YES it had the bug. and Thank you so much for taking the time to help me, and being so patient with me as well.

[Joseph Salisbury (jsalisbury)]

Sorry for the typos in comment #39 and #45. The test kernel to test is at:
http://people.canonical.com/~jsalisbury/lp903961

Is that the kernel you tested for comment #46, which has the bug?

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
84db18bbeb5c9c1a9c86e38a89d76ee526fd2c6f

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

No problem, thanks for spending so much time on this!!
I just tested 2.6.34-020634rc3_2.6.34-020634rc3.201208142104
and YES it WORKED!!!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
baa06775e224e9f74e5c2de894c95cd49678beff

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

Ok, I just tested
2.6.34-020634rc4_2.6.34-020634rc4.201208151835
and YES it BOOTED!!!

[Israel Dahl (israeldahl)]

I encountered the same bug on a totally different machine, a Gateway. I will have to boot the machine, connect and post more detailed info, though it maybe a different bug, though acpi=off did allow it to boot properly.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
1f829825f21755c48de075cd7722fcd19438f587

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

Ok, I hada hiccup trying to test it.... I was running the previous rc4 when I tried dpkg it. I got it all sorted out, and installed.
And 2.6.34-020634rc4.201209242136

WORKS!!!!
It booted just fine, thanks again!!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
9b030e2006546366c832911ca5eb9e785408795b

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

It booted just fine!!
2.6.34-020634rc4-generic_2.6.34-020634rc4.201209261745
Thank you!!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
2545cf6e94b4eb5a2c48dd55751aa9a70ff1ff9d

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

Just tried it and it worked just fine!!! This is great! I'm glad they have all worked so far!!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
9befb55ef51ad69dd67e279b0533d4cbc5e4c6c0

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

We should run into a kernel that has the bug again, if the bisect is working properly.

[Israel Dahl (israeldahl)]

I'm very sorry that is only the amd64bit kernels..... the bug is for the i386 type.

[Israel Dahl (israeldahl)]

This morning I booted the old machine up and found that the previous rc5 does have the bug. I remember now that it would be intermittant sometimes. I usually try to always boot into the latest kernel we are bisecting just to make sure it works well. And since I couldn't download/install the one you posted (comment #59) I booted into the previous one (comment #57 ) So apparently the bug actually was there, it just happened to boot fine the very first time. I am sure it is not in the previous one (rc4 from comment #55) as I have booted this one multiple times. So you were absolutely right, we did run into the bug again, which IS present in the kernel from comment #57. To be clear:

2.6.34-020634rc5.201209272045_i386 HAS the bug
 http://people.canonical.com/~jsalisbury/lp903961/2545cf6e94b4eb5a2c48dd55751aa9a70ff1ff9d/

2.6.34-020634rc4.201209261745_i386 does NOT have the bug
http://people.canonical.com/~jsalisbury/lp903961/9b030e2006546366c832911ca5eb9e785408795b/

[Joseph Salisbury (jsalisbury)]

Thanks for the update, Israel. It would be great if you can test the old machine, so we ensure we are telling the the bisect which kernels are good and bad.

Based on your results from comment #61, I built the next test kernel, which is up to commit:
ac8bf564307962a763a52b34e771205c58b76ec8

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

I will test it later, and report the results. I do use the older machine quite often, but I'm also testing the quantal kernel in precise as well as Beta testing 12.10 on this machine. Thank you so much for all your attention to this bug!!

[Israel Dahl (israeldahl)]

Ok, the bug is present again in this latest one. It froze up, and the caps lock key blinked.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
186837ca3a6dd6b422a5ea316ed38eea183dca5d

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

Ok, I booted into it twice, so I can say it works! I will default to this one until the next kernel is built.

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
34388d1c4feae50d61d6f4ec7594b9076d6d24db

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

On my first boot it WORKS!!
If anything changes I will post again.
Thanks!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
28a1f533ae8606020238b840b82ae70a3f87609e

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp903961

Can you test this latest kernel and report back if it has the bug or not?

[Israel Dahl (israeldahl)]

Ok, I booted into the newest rc4 Kernel you built. No problems with it, I will default to this one until the next one is built. Thanks!

[Joseph Salisbury (jsalisbury)]

The latest v3.7 kernel is now available. Can you test v3.7-rc1 to see if this bug got fixed upstream:

 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc1-quantal/

[Israel Dahl (israeldahl)]

I'm sorry but, doesn't there need to be a
linux-headers-***-generic-*****-.deb
linux-headers-**************-all.deb
linux-image-***-generic-*****-.deb
linux-image-extra-***-generic-*****-.deb

there is no
linux-headers-**************-all.deb
at that link. How do I install it? a normal sudo dpkg -i *.deb in my sub directory results in errors.... what am I missing?

[Joseph Salisbury (jsalisbury)]

You shouldn't need the headers package. However, there may be an issue with the v3.7-rc1 build. Can you test the latest v3.6.2 stable release instead:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.2-quantal/

[Israel Dahl (israeldahl)]

Ok, I'm downloading them now, and I will test it out, and let you know the results, thank you.

[Israel Dahl (israeldahl)]

No, that just hung the computer up right off the bat. I will see if I can get the 3.7 to install. If it works, I'll let you know

[Israel Dahl (israeldahl)]

No, it had the same error again when I tried to install the 3.7... just ended up with a broken package.

[Israel Dahl (israeldahl)]

Ok, so I have been trying the 64 bit build, and that seems to work perfectly. I had tried the 64 bit (11.04, and 11.10 and both did not work), and so far 12.04.1 64 bit doesn't have the bug. So, if you want to fix the bug for the 32 bit (just because it is a regression) we can, I will continue to test. If you'd rather close this bug without fixing it, that is fine as well.

[penalvch (penalvch)]

Israel Dahl, as per http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=228&lc=en&cc=us&dlc=en&sw_lang=&product=425664#N642 an upgrade is available for your BIOS (F.45). If you upgrade to this, does this change anything?

[Israel Dahl (israeldahl)]

I am not sure how to go about upgrading BIOS in Linux (I also do not think it is ever recommended), but as I said the 64bit version works quite well. I have no windows CDs of any sort.

[Launchpad Janitor (janitor)]

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

[LaurensV (laurens-daemon)]

Is there still interest in getting this issue fixed for 32-bit?

I got here via the links http://askubuntu.com/questions/204905/compaq-presario-r3000-randomly-fails-to-boot-on-11-10-12-04-12-10 and http://askubuntu.com/questions/87187/11-10-randomly-fails-to-boot-on-compaq-presario-r3000

I'm having the intermittent boot issue on a Compaq Presario R3000 now with Lubuntu 13.04. The CPU in this laptop doesn't have 64-bit extensions... acpi=off does not fix the issue.

What can I provide to help debugging this issue?

Thanks!

[penalvch (penalvch)]

LaurensV, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Israel Dahl (israeldahl)]

Also, I had some major issues with 13.04 and stuck with 12.04 because it runs flawlessly. All the core will be kept up to date, only the LXDE components will not be updated. I had to change a parameter with my graphics card to get mine to boot with 13.04... but I agree that it might be best to file a new bug on this issue.
A few last things: people will likely ask if you have updated your firmware, you will need windows to do this (win XP) freeDos doesn't work for this computer :(
Make sure you don't have an AMD processor. running `lspci` from the terminal will list components look for lines containing
"Advanced Micro Devices [AMD]" if those exist, use the 64 Bit version, as AMD makes 64 Bit processors.
I hope your issue is resolved, my old R3000 was thought to be a gonner until I put GNU/Linux on it(Sometimes I use puppy on it as well as Ubuntu)!

[LaurensV (laurens-daemon)]

Hey Israel,

My processor is an AMD Athlon XP-M, which doesn't support 64-bit as far as I can see... Yes, I have the latest BIOS version installed :)

[penalvch (penalvch)]

LaurensV, please see the comment already posted to you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903961/comments/82 .