System Locks Up forcing hard boot frequently Ubuntu 8.04.1 Kernel 2.6.24-19-Generic

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

"uname -a" = 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux

it's taken me a long time to get the PC to boot up to get this....I've had to hard reset about 50+ times....recovery mode not working either......Seems that when loading the graphical bar with progress. I nearly always get stuck just before the 3rd hash mark from the left. I counted (out of boredom) there are 20 hash marks if you count the far right end of the bar.

In my latest series of hard resets trying to get Ubuntu to load it
crashed as usual though this time I got the following:

[ 31.927656] Bug: unable to handle kernel paging request at virtual
address 8087df20
[ 31.927751] printing eip: c0172dd7 *p

I don't know if that helps any but there it is....let me know if there
is any other info I can get for you

Gaurish Sharma wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it, because your description
> does not yet have enough information.
>
> Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
> 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
> 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at [WWW]
> https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

No response for 11 days now I see that this bug is not assigned to anyone. I have submitted the requested files. What needs to be done to speed this along? My computer is effectively useless until this is resolved.

Bump added Yeam as subscriber

Sorry for Trouble, i Understand your trouble.
Your system maybe locked up due to IRQ conflicts. but i am not sure.
Please have a look https://help.ubuntu.com/community/DebuggingIRQProblems
and see if any one these listed workarounds solve your problem.
To use this you, you need to edit grub to pass on the arguments at boot time.in choices menu, press "e" and then add the option like "noapic" at end of line.

Then press "b" to boot the system.

Secondly i wanted to ask, Do you have made a Proper SWAP space on a separate partition which should be appox 1.5times your ram?

Thanks

i added noapic nolapic acpi=off pci=noacpi

this improved stability quite a bit so that I can log in now, but it is
still crashing like before just not as frequently.

got any other ideas or suggestions?

Gaurish Sharma wrote:
> Sorry for Trouble, i Understand your trouble.
> Your system maybe locked up due to IRQ conflicts. but i am not sure.
> Please have a look https://help.ubuntu.com/community/DebuggingIRQProblems
> and see if any one these listed workarounds solve your problem.
> To use this you, you need to edit grub to pass on the arguments at boot time.in choices menu, press "e" and then add the option like "noapic" at end of line.
>
> Then press "b" to boot the system.
>
>
> Secondly i wanted to ask, Do you have made a Proper SWAP space on a separate partition which should be appox 1.5times your ram?
>
> Thanks
>
>

seems my last post was a bit premature. i even managed to change it on
the menu.lst ( think that's the name) when I hit esc now and "e" on the
kernel it shows my changes but now it is locking up like before. was
good for about an hour. now it's just as bad as before

Jason T Myrick wrote:
> i added noapic nolapic acpi=off pci=noacpi
>
> this improved stability quite a bit so that I can log in now, but it
> is still crashing like before just not as frequently.
>
> got any other ideas or suggestions?
>
>
>
> Gaurish Sharma wrote:
>> Sorry for Trouble, i Understand your trouble.
>> Your system maybe locked up due to IRQ conflicts. but i am not sure.
>> Please have a look
>> https://help.ubuntu.com/community/DebuggingIRQProblems
>> and see if any one these listed workarounds solve your problem.
>> To use this you, you need to edit grub to pass on the arguments at
>> boot time.in choices menu, press "e" and then add the option like
>> "noapic" at end of line.
>>
>> Then press "b" to boot the system.
>>
>>
>> Secondly i wanted to ask, Do you have made a Proper SWAP space on a
>> separate partition which should be appox 1.5times your ram?
>>
>> Thanks
>>
>>
>
>

now i'm getting Kernel panic - not syncing: Attempted to kill the idle
task! error message

this is driving me crazy...my laptop works great...i don't get it. You
would think the desktop would work with Ubuntu with even less problems

Jason T Myrick wrote:
> seems my last post was a bit premature. i even managed to change it
> on the menu.lst ( think that's the name) when I hit esc now and "e"
> on the kernel it shows my changes but now it is locking up like
> before. was good for about an hour. now it's just as bad as before
>
>
> Jason T Myrick wrote:
>> i added noapic nolapic acpi=off pci=noacpi
>>
>> this improved stability quite a bit so that I can log in now, but it
>> is still crashing like before just not as frequently.
>>
>> got any other ideas or suggestions?
>>
>>
>>
>> Gaurish Sharma wrote:
>>> Sorry for Trouble, i Understand your trouble.
>>> Your system maybe locked up due to IRQ conflicts. but i am not sure.
>>> Please have a look
>>> https://help.ubuntu.com/community/DebuggingIRQProblems
>>> and see if any one these listed workarounds solve your problem.
>>> To use this you, you need to edit grub to pass on the arguments at
>>> boot time.in choices menu, press "e" and then add the option like
>>> "noapic" at end of line.
>>>
>>> Then press "b" to boot the system.
>>>
>>>
>>> Secondly i wanted to ask, Do you have made a Proper SWAP space on a
>>> separate partition which should be appox 1.5times your ram?
>>>
>>> Thanks
>>>
>>>
>>
>>
>
>

ok got the idle task problem solved but comp is still locking up....what is being done to fix these lock up issues...i see many bugs on launchpad about hard lockups. For now I have a completely useless desktop sitting here collecting dust....just waiting for someone to request logs or give more suggestions on how to fix this issue. I'm to the point that I may give a shout on craigslist asking for some local help.

Hi,
Please check your RAM using Memtest, i suspect a faulty Memory

*Turn On or Restart the system

*Use the arrow keys to move to the entry labeled Ubuntu, memtest86+

*Press Enter. The test will run automatically, and continue until you
end it by pressing the Escape key
* Allow the test to run for at least one full pass

Regards,
Gaurish Sharma

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!