Recent i386 karmic kernels crash, amd64 kernels are OK

[Olof Staffans]

After upgrading to Karmic my amd64 partition still works,OK, but my two i386 partitions crash if I use the most recent kernels.

Typically 2.6.31-15 and 2.6.31-14 become totally irresponsible within a minute or two. The kernel 2.6.28-15 can work for some time, but sometimes the graphic is messed up, and I have to switch to one of the other processes (Alt-Ctl-F1) and back to get back a graphic window. In this kernel only the X-server crashes, and the keyboard still works, so that I can switch to a terminal window. Kernel 2.6.27-11 typically does not crash until I log out.

After upgrading to Karmic the sound stopped to work in kernels 2.6.28-15 and 2.6.27-11. This applies also to the amd_64 version.

But as I said, I do not have these crashes in the 64 bit verson.

[Victor Vargas (kamus)]

reassigned to linux kernel package

[Olof Staffans (olof-staffans)]

I have now traced the problem to the graphics card driver. The reason
why the 64 bit installation did not crash was that it used the vesa
driver instead of the default Radeon driver. I have a Radeon graphics
card installed (the following is a piece of the log produced by the
Radeon driver):

(II) RADEON(0): EDID for output VGA-0
(II) RADEON(0): Manufacturer: VSC Model: f14 Serial#: 16843009
(II) RADEON(0): Year: 2003 Week: 27
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) RADEON(0): Signal levels configurable
(II) RADEON(0): Sync: Separate CompositeSerration on. V.Sync Pulse
req. if CompSync or SyncOnGreen
(II) RADEON(0): Max Image Size [cm]: horiz.: 32 vert.: 24
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.626 redY: 0.338 greenX: 0.278 greenY: 0.601
(II) RADEON(0): blueX: 0.150 blueY: 0.068 whiteX: 0.096 whiteY: 0.109

I now use it by means of the vesa driver:

(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
 compiled for 1.6.3, module version = 2.2.1
 Module class: X.Org Video Driver
 ABI class: X.Org Video Driver, version 5.0
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 01@00:00:0

In other words, I edited xorg.conf and replaced the default

Section "Device"
 Identifier "Configured Video Device"
EndSection

by

Section "Device"
 Identifier "Generic Video Card"
 Driver "vesa"
 BusID "PCI:1:0:0"
EndSection

and everything seems to work fine now.

[Olof Staffans (olof-staffans)]

More precisely, this is my graphics card:

(--) PCI:*(0:1:0:0) 1002:5960:17ee:2801 ATI Technologies Inc RV280
[Radeon 9200 PRO] rev 1, Mem @ 0xf0000000/134217728, 0xfbf00000/65536,
I/O @ 0x0000e000/256, BIOS @ 0x????????/131072

[Jeremy Foshee (jeremyfoshee)]

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.]

[Olof Staffans (olof-staffans)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: staffans 2012 F.... kmix
 /dev/snd/controlC0: staffans 1992 F.... knotify4
                      staffans 2012 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with ALC850 at 0xd800, irq 22'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 49
   Simple ctrls : 30
Card1.Amixer.info:
 Card hw:1 'DVC100'/'Pinnacle Systems GmbH DVC100 at usb-0000:00:10.4-1.3, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB2304:021a'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Line',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 16
   Mono: Capture 0 [0%] [-16.00dB] [off]
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=628172e2-d54b-48b9-b31c-4d16e6d5ea40
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcCmdLine: root=UUID=6339b283-19ff-41fa-b65d-355724881e1e ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-20-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
WpaSupplicantLog:

XsessionErrors:
 (firefox:2028): GLib-WARNING **: g_set_prgname() called multiple times
 (polkit-gnome-authentication-agent-1:2058): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (thunderbird-bin:2093): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:2180): GLib-WARNING **: g_set_prgname() called multiple times
dmi.bios.date: 11/14/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1017.002
dmi.board.name: A8V Deluxe
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017.002:bd11/14/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Olof Staffans (olof-staffans)]

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
>

[Olof Staffans (olof-staffans)]

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
>>

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.