1969:2062 [STAGING] Locks up logging in

Bug #765241 reported by qamelian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Netbook locks up immediately after logging in to default Ubuntu 11.04 desktop. this happens 100% of the time with the default 11.04 kernel, both on the 32-bit and 64-bit releases. If I install 10.10 and use the update-manager to upgrade to 11.04, this doesn't happen with the 2.6.35 series of kernels. It has happened with each release to date of the 2.6.38 kernel.

The netbook is setup to dual boot with windows 7 Home Premium. If I boot into Windows 7 immediately after one of these lockups, then immediately reboot into Natty, the lockup after logging in does not occur. This can also be reproduced 100% of the time.

This only occurs on an installed system. Booting 11.04 from a "live" thumb drive does not result in a lockup.

WORKAROUND: It looks like this is an issue with a kernel module (atl1c). After blacklisting this module, Ubuntu 11.04 boots with the 2.6.38 series kernel without needing a preceeding Windows 7 boot.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: carl 1378 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0x90544000 irq 41'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0x90540000 irq 16'
   Mixer name : 'Conexant CX20584'
   Components : 'HDA:14f15068,10250543,00100302'
   Controls : 9
   Simple ctrls : 9
Date: Mon Apr 18 18:47:58 2011
HibernationDevice: RESUME=UUID=605dc6c5-4bf3-43fe-927a-eccb414a9ec5
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 0402:9665 ALi Corp.
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire One 522
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=94e2285e-bb00-4cf8-9995-b26381ed8435 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.50
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: brcm80211
Title: [STAGING]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.03
dmi.board.name: Aspire One 522
dmi.board.vendor: Acer
dmi.board.version: V1.03
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrV1.03:bd12/09/2010:svnAcer:pnAspireOne522:pvrV1.03:rvnAcer:rnAspireOne522:rvrV1.03:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire One 522
dmi.product.version: V1.03
dmi.sys.vendor: Acer

Revision history for this message
qamelian (carl-godfrey) wrote :
Revision history for this message
qamelian (carl-godfrey) wrote :

It looks like this is an issue with a kernel module (atl1c). After blacklisting this module, Ubuntu 11.04 boots with the 2.6.38 series kernel without needing a preceeding Windows 7 boot. This should not be necessary, however, since the 2.6.25 series kernel boots fine without blacklisting this module.

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

qamelian, 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 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? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

summary: - [STAGING]
+ 1969:2062 [STAGING] Locks up logging in locks up
summary: - 1969:2062 [STAGING] Locks up logging in locks up
+ 1969:2062 [STAGING] Locks up logging in
description: updated
Changed in linux (Ubuntu):
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.