Comment 24 for bug 489712

For some reason this message did not seem to go through, so I resend it.

Olof Staffans wrote:
> Dear Jeremy,
>
> Indeed, the problem still exists to some extend. I stopped using the
> default Radeon video card driver, since it did not work, and changed to
> the vesa driver. At the moment the amd64 installation on my primary
> computer works more or less OK. The i386 version crashes more or less
> regularly. I just apport-collect on the i386 partition.
>
> The second i386 partion now contains a prerelease version of the jaunty
> kernel, which I installed a couple of weeks ago. I was able to start it
> up a couple of times, but at some point it started to freeze during the
> startup, so I am no longer able to start it. The latest kernel that I
> succeeded to upgrade to was 2.6.32-19-generic, but I was never able to
> get that one up and running. I can still access that partition from my
> other installations, so if you are interested in the boot logs I can
> send them to you. The boot loader in that partition works, and I use
> that loader as the default one.
>
> Here I only enclose the menu.lst, so that you can see which partitions I
> have.
>
>
>
> no longer exists, since I some time ago replaced that one with the new
>
> Jeremy Foshee wrote:
>> Hi Olof,
>>
>> 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? Can you
>> try 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 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 489712
>> 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.]
>>
>> ** Tags added: needs-kernel-logs
>>
>> ** Tags added: needs-upstream-testing
>>
>> ** Tags added: kj-triage
>>
>> ** Changed in: linux (Ubuntu)
>> Status: New => Incomplete
>>