system unstable

[Wayne R. Knight]

I have a desktop system with an ECS 945GCT-M motherboard, an Intel E2200 Pentium Dual Core CPU running at 1.8 GHz and 4 GB DDR2/667 RAM. This system is completely stable under Ubuntu 9.04 and Windows 7. Under Ubuntu 10.04 the system seizes after anywhere from 20 seconds to 15 minutes. There are no warnings and the only indication is that stops whatever it was doing and the mouse and keyboard cease to have any input. I have let the system stand for over half an hour to see if it would recover and it didn't. The only actions available are to turn the power switch off or press the reboot button on the chassis. This behavior is unpredictable and is independent of any application or utility being used.

[Jeremy Foshee (jeremyfoshee)]

Hi Wayne,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 584325

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Wayne R. Knight (wrkbear)]

Thanks for the feedback. I installed the latest version from the link you provided with the same results. The system continues to seize shortly after booting up and logging in. I repartitioned the hard drive, checked it for bad sectors (didn't find any) and reinstalled lucid and this time made a note of the messages at the end of the installation.

At the end of the installation, it gave the message to reboot. I allowed it to reboot itself and in the process of shutting down it ejected the CD and gave the following messages:

casper is resynching snapshots and caching reboot files
end request I/O error device sr0 logical block 452948
buffer I/O error on device sr0 logical block 113237
(this was repeated for blocks ending in 38, 39, 40, 41, 42, 43, and 44)
SQUASHFS error read data failed to read block 0xda71f0e
err unexpectedly disconnected from boot daemon
init: plymouth post-start process (20428) terminated with status 2
Please remove disc and close tray
end request I/O err 452956
init: plymouth main proc (20427) killed by BUS signal
(more end request messages)
init: plymouth-splash main process (20691) terminated with status 1

At this point, the system seized and would not auto-restart. I manually rebooted (reboot switch on chassis) and the system booted, logged me in and after about 1 minute as I was opening the "System" menu, it seized.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Wayne R. Knight (wrkbear)]

This problem still persists with 10.04 and 10.10. We have isolated the
problem to compiz (the version running on gnome). If we shut down
compiz, the problem disappears. The graphics processor is an intel chip
(on board). I forget the number, but someone told me that there is a
problem with compiz and that particular graphics coprocessor.

Unfortunately, I don't think the problem is unique to the intel graphics
coprocessor as my other 64 bit intel system uses an nVidia (GeForce
7300) graphics card and has the same problem.

W. Knight

On Thu, 2010-09-23 at 03:37 +0000, Jeremy Foshee wrote:
> This bug report was marked as Incomplete and has not had any updated
> comments for quite some time. As a result this bug is being closed.
> Please reopen if this is still an issue in the current Ubuntu
> development release http://cdimage.ubuntu.com/daily-live/current/ .
> Also, please be sure to provide any requested information that may have
> been missing. To reopen the bug, click on the current status under the
> Status column and change the status back to "New". Thanks.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kj-expired
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Expired
>