Kernel 3.0.0-18 - Unitiy does not start (Lifebook T4220)

[Thomas T.]

I just downloaded the new kernel and rebooted, but Unity does not start anymore...

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-17-generic 3.0.0-17.30
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc800000 irq 47'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,10cf0100,00100202'
   Controls : 15
   Simple ctrls : 10
Date: Mon Apr 2 19:39:20 2012
HibernationDevice: RESUME=UUID=8514a1d8-a43a-4651-ab78-a06e17965cc2
MachineType: FUJITSU SIEMENS LIFEBOOK T4220
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   product info: "O2Micro", "SmartCardBus Reader", "V1.0", ""
   manfid: 0xffff, 0x0001
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   5.0V 16-bit PC Card
   Subdevice 0 (function 0) [unbound]
ProcKernelCmdLine: root=UUID=ef1a90b6-f404-4102-9989-f5fc3e7d513e ro quiet splash
PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-17-generic N/A
 linux-backports-modules-3.0.0-17-generic N/A
 linux-firmware 1.60.1
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-10-13 (172 days ago)
UserAsoundrc:
 pcm.pulse { type pulse }
 ctl.pulse { type pulse }
dmi.bios.date: 05/15/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.16
dmi.board.name: FJNB1D4
dmi.board.vendor: FUJITSU
dmi.board.version: CP336664-01
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: T42__
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd05/15/2008:svnFUJITSUSIEMENS:pnLIFEBOOKT4220:pvr:rvnFUJITSU:rnFJNB1D4:rvrCP336664-01:cvnFUJITSUSIEMENS:ct10:cvrT42__:
dmi.product.name: LIFEBOOK T4220
dmi.sys.vendor: FUJITSU SIEMENS

[Joseph Salisbury (jsalisbury)]

Does Unity start if you reboot back into the previous kernel?

[Thomas T. (dontpanic)]

Yes, with 3.0.0-17 it's working...
When I boot with 3.0.0-18, I can log in using the terminal (i mean STRG+ALT+F1)...
Sometimes my fingerprint is working as well, sometimes I can only use password authentification (don't know if this information helps...)

[Luis Henriques (henrix)]

I have build a test kernel that we would like you to test if possible. The only addition commit on this test kernel is 93dc6107a76daed81c07f50215fa6ae77691634f "Don't limit non-nested epoll paths".

Could you please check if it solves the issues you're having and report back? You can get this kernel here:

http://people.canonical.com/~henrix/lp972529/

[Thomas T. (dontpanic)]

Seems to work! Thank you very much!

[Brad Figg (brad-figg)]

Anyone experiencing this issue, please try the kernel at: http://people.canonical.com/~herton/fpu_bug/

[Herton R. Krzesinski (herton)]

Thomas, can you confirm that kernel 3.0.0-19 in -proposed fixes this bug, or do you still have issues?

[Thomas T. (dontpanic)]

Yes, the new kernel fixes the bug. Thank you!

Am 2012-04-23 22:46, schrieb Herton R. Krzesinski:
> Thomas, can you confirm that kernel 3.0.0-19 in -proposed fixes this
> bug, or do you still have issues?
>