Kernel update broke graphics driver due to gcc segfault

Bug #868498 reported by Kasper Dupont
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

After upgrading from 2.6.32-33-generic to 2.6.32-34-generic X was no longer working on my system. During install an alert had appeared in the Gnome status bar indicating an install error for the psb-kernel-source driver for the graphics chip in this machine. The alert did not provide any information on where to find logs from the failing install, thus making further debugging hard. Moreover the button to report the bug directly from the alert was not functional.

After a bit of searching I found out that I could run the driver build manually by running this command as root:
dkms ^Cild -k 2.6.32-34-generic -m psb-kernel-source -v 4.42.0

This also failed, but at least pointed at the logfile in /var/lib/dkms/psb-kernel-source/4.42.0/build/make.log

In this logfile I could see that the reason for the failure was that gcc was segfaulting during the build. The segfault would happen at different points during the build.

The following workaround worked for me:
1. Add "kernel.randomize_va_space = 0" to /etc/sysctl.conf
2. Reboot
3. Uninstall linux-image-2.6.32-34-generic
4. Install linux-image-2.6.32-34-generic again
5. Reboot

This is a regression as no such problems happened during earlier kernel upgrades. The kernel has been upgraded a few times already on this machine without problems. The last upgrade that worked without problems was to 2.6.32-33-generic, which worked flawless and would also have performed a build of this driver.

I don't know which component is responsible for the gcc segfaults, so I am reporting this against my best guess.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19
Uname: Linux 2.6.32-34-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: kasperd 1782 F.... pulseaudio
 /dev/snd/controlC0: kasperd 1782 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'MID'/'HDA Intel MID at 0xb0050000 irq 22'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,10ec0662,00100101'
   Controls : 33
   Simple ctrls : 19
Card1.Amixer.info:
 Card hw:1 'Audio'/'USB Audio at usb-0000:00:1d.0-2, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB0d8c:0006'
   Controls : 12
   Simple ctrls : 7
Date: Wed Oct 5 17:56:55 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e14584e1-caed-4150-9e25-e364d27bebe3
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
MachineType: CompuLab CM-iAM/SBC-FITPC2i
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-34-generic root=UUID=8bf29c49-594d-41b8-8513-ac3cf4bf4e1b ro crashkernel=384M-2G:64M,2G-:128M rootdir=lucid
ProcEnviron:
 PATH=(custom, user)
 LANG=en_DK.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:

SourcePackage: linux
dmi.bios.date: 09/14/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: NAPA0001.86C.0000.D.1009141059
dmi.board.name: CM-iAM/SBC-FITPC2i
dmi.board.vendor: Intel Corporation
dmi.board.version: 1.x
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: OEM
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrNAPA0001.86C.0000.D.1009141059:bd09/14/2010:svnCompuLab:pnCM-iAM/SBC-FITPC2i:pvrNotApplicable:rvnIntelCorporation:rnCM-iAM/SBC-FITPC2i:rvr1.x:cvnOEM:ct1:cvrN/A:
dmi.product.name: CM-iAM/SBC-FITPC2i
dmi.product.version: Not Applicable
dmi.sys.vendor: CompuLab

Revision history for this message
Kasper Dupont (ubuntu-launchpad-feb) wrote :
Revision history for this message
Kasper Dupont (ubuntu-launchpad-feb) wrote :

Here is the end of /var/lib/dkms/psb-kernel-source/4.42.0/build/make.log from one of the runs:

  CC [M] /var/lib/dkms/psb-kernel-source/4.42.0/build/drm_scatter.o
  CC [M] /var/lib/dkms/psb-kernel-source/4.42.0/build/drm_memory_debug.o
  CC [M] /var/lib/dkms/psb-kernel-source/4.42.0/build/ati_pcigart.o
  CC [M] /var/lib/dkms/psb-kernel-source/4.42.0/build/drm_sman.o
  CC [M] /var/lib/dkms/psb-kernel-source/4.42.0/build/drm_hashtab.o
cc1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[2]: *** [/var/lib/dkms/psb-kernel-source/4.42.0/build/drm_hashtab.o] Error 1
make[1]: *** [_module_/var/lib/dkms/psb-kernel-source/4.42.0/build] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-34-generic'
make: *** [modules] Error 2

Sam_ (and-sam)
affects: ubuntu → linux (Ubuntu)
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Kasper Dupont, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.