Ubuntu
linux package

Ubuntu crashes with CapsLk blinking on Lenovo T500

Bug #318600 reported by max on 2009-01-18

12

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

This bug similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/312262/
and this is continue to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/316566

I installed Ubuntu 8.1 on Lenovo T500. It is randomly crash too. If ubuntu 9.04 after crash can save report (Alt+SysRg+1, t) and can be rebooted by (Alt+SysRg+RSEIUB) than ubuntu 8.1 just crash with blinking CapsLk.
Ubuntu 8.1 can be rebooted only by switch of power (Press and hold power button).

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: linux-image-2.6.27-9-generic 2.6.27-9.19
ProcCmdLine: root=UUID=982071a8-715d-4cf4-9306-fd67d9e15e51 ro quiet nosplash
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-9.19-generic
SourcePackage: linux

Tags:

Revision history for this message

max (mikhmv) wrote on 2009-01-18:

#1

BootDmesg.gz Edit (13.2 KiB, application/x-gzip)
CurrentDmesg.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")
HalComputerInfo.txt Edit (2.6 KiB, text/plain; charset="utf-8")
LsUsb.txt Edit (684 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (19.5 KiB, text/plain; charset="utf-8")
ProcCpuInfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.7 KiB, text/plain; charset="utf-8")

Revision history for this message

max (mikhmv) wrote on 2009-01-18:

#2

dmesg.log Edit (55.0 KiB, application/octet-stream)

Revision history for this message

max (mikhmv) wrote on 2009-01-18:

#3

lspci-vnvn.log Edit (33.5 KiB, text/plain)

Revision history for this message

max (mikhmv) wrote on 2009-01-18:

#4

uname-a.log Edit (90 bytes, text/plain)

Revision history for this message

max (mikhmv) wrote on 2009-01-18:

#5

version.log Edit (27 bytes, text/plain)

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2009-01-19:

#6

Hi Max,

You mention if you run Jaunty 9.04 (which has a 2.6.28 based kernel), you are able to save a log/report of the crash. Could you attach that report to this bug report? All I currently notice here are logs from the 2.6.27 kernel that's used in Intrepid 8.04. Thanks.

Changed in linux:
status:	New → Incomplete

Revision history for this message

max (mikhmv) wrote on 2009-01-19:

#7

Hi Leann,
You can see all my bug reports for jaunty in the thread: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/316566
If it will be helpful I can create new report on jaunty by ubuntu-bug. I have one computer with jaunty now and one with 8.1. They have similar configuration except wireless (8.1 with Intel 5300, jaunty with Intel 5350). Both of them had problem with jaunty.
8.1 I tried only on one computer. It is freeze not so often compare with jaunty. Jaunty crash once per hour or even often. This crash once per day.
If it will be helpful I can perform any tests on computer with jaunty.

thanks,
Max.

Revision history for this message

max (mikhmv) wrote on 2009-01-28:

#8

I added Pre-released and unsupported updates in software Sources. And after update Intrepid start work normally. Look like new drivers or new kernel don't have this bug.

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2009-01-29:

#9

Thanks max. Just to clarify, you enabled the intrepid-proposed repository? and this then appears to be resolved? If so, then once the packages in intrepid-proposed move to -updates this should be resolved. Thanks.

Revision history for this message

max (mikhmv) wrote on 2009-01-29:

#10

Yes. I think this bug already resolved but solution not released for regular update yet.

Changed in linux:
status:	Incomplete → Fix Committed

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2009-02-18:

#11

Marking Fix Released now that 2.6.27-11 is available as an update. Thanks.

Changed in linux:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #316566

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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