Ubuntu
linux package

freeze when starting X (intel) from the recovery console

Bug #668017 reported by Roman Gröger on 2010-10-28

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Medium	Unassigned

Bug Description

The screen goes blank when I start the X server from the recovery console. The computer is SONY VAIO VPCY2 with the integrated Intel graphics (i915). If I boot into the recovery console and use the intel driver on xorg.conf, the X windows do not even start. The screen goes blank and the computer freezes. I saw some complaints when booting about intel_agp:
  "unknown symbol intel_agp_enabled (err -16)"
  "gave up waiting for init of module intel_agp"
  "unknown symbol intel_max_stolen (err -16)"
Somebody on the web suggested to blacklist intel_agp by adding a line
  blacklist intel_agp
in /etc/modprobe.d/blacklist.conf
and updating the initramfs by
  sudo update-initramfs -u
This removed the error messages about intel_agp but the computer still freezes. I am attaching Xorg.0.log that was generated during this freeze.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic-pae 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 3 2010-10-28 21:20 seq
crw-rw----+ 1 root audio 116, 2 2010-10-28 21:20 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices: aplay: device_list:235: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:235: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Oct 28 21:27:10 2010
HibernationDevice: RESUME=UUID=f0a94758-e232-47f0-96c3-ff7fc7a4ac31
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: Sony Corporation VPCY21S1E
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=d8799835-d288-4c17-85a5-23ebde743a39 ro single i8042.nopnp
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 06/14/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: R0170H2
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnINSYDE:bvrR0170H2:bd06/14/2010:svnSonyCorporation:pnVPCY21S1E:pvrC9003JV1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCY21S1E
dmi.product.version: C9003JV1
dmi.sys.vendor: Sony Corporation

Tags:

Revision history for this message

Roman Gröger (xalbert76) wrote on 2010-10-28:

Xorg.0.log Edit (5.8 KiB, text/plain)
AcpiTables.txt Edit (230.3 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (53.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (40.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (517 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (15.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (374 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (575 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (308 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (103.2 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (238.4 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (5.2 MiB, text/plain; charset="utf-8")

Revision history for this message

Johan Euphrosine (proppy) wrote on 2010-11-02:

Adding blacklist intel_ips to modprobe blacklist solved the issue for me, as pointed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665097/comments/1

Brad Figg (brad-figg) on 2011-04-06

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2012-10-16:

Roman Gröger, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this 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 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER