kernel 2.6.15-25-k7 smp version crashes after few minutes use

[digimars]

I have Ubuntu Dapper Drake 6.06 (with all of the updates that come across) installed on a machine with an AMD X2 4400+ dual core processor. I downloaded and installed all of the packages (the kernel image file, restricted modules, etc.) from the Synaptic package manager and I later did it again through sudo apt-get.

I can boot into the 2.6.15-25-k7 kernel setup fine after I first installed this kernel. The computer ran fine for about 2-5 minutes when I tried to access another page in firefox when the whole computer locked up. I couldn't move my mouse, keyboard input was non-existent, and there was no activity on my hdd light.

I hard rebooted by the power switch on my tower, and tried again. This time, again after about 2-5 minutes of use, I clicked on the window title bar for my terminal window, and again the computer locked up. I hard rebooted again.

Thinking that maybe my mouse was causing this, this time when I logged in, I brought up a terminal and waited a few moments. Then, without moving my mouse, I typed in glxgears into the terminal then hit enter, then the computer locked up again.

Thinking there was something wrong with this kernel altogether, I tried to download and install the previous (2.6.15-23-k7) kernel, along with the smp packages as I had before, however, It would not let me have anything else specific to the -23 kernel, everything was updated for the -25 kernel. So when I tried to boot into that one, X failed to start because the restricted modules would not configure for the -23 kernel, only the -25 one.

I did a memtest on my machine, and it passed both full tests that I ran it through (2GB DDR2 memory).

I am currently working out of a 386 kernel, but I much prefer to have both of my cores on my processor working.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Any news on this ?

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.