Lenovo X61 hangs with flashing caps lock LED.

[fcolcord]

The caps lock LED is flashing often when I boot up or reactivate after a suspend.
If I turn off x61 then reboot in safe mode, then it doesn't happen until I leave it.
I have a wireless N router.

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: frank 1520 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8220000 irq 45'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20d6,00100400'
   Controls : 31
   Simple ctrls : 19
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7MHT25WW-1.03'
   Mixer name : 'ThinkPad EC 7MHT25WW-1.03'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 11.10
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: LENOVO 7673H7G
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=fb420329-0902-4e4c-9ffb-537236618d8d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-13-generic N/A
 linux-backports-modules-3.0.0-13-generic N/A
 linux-firmware 1.60
Tags: oneiric running-unity
Uname: Linux 3.0.0-13-generic i686
UpgradeStatus: Upgraded to oneiric on 2011-10-16 (29 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/01/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETB6WW (2.16 )
dmi.board.name: 7673H7G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7NETB6WW(2.16):bd07/01/2008:svnLENOVO:pn7673H7G:pvrThinkPadX61:rvnLENOVO:rn7673H7G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7673H7G
dmi.product.version: ThinkPad X61
dmi.sys.vendor: LENOVO

[Fabio Marconi (fabiomarconi)]

Please run in a terminal
apport-collect 888341
Thanks
Fabio

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 888341

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

apport information

[fcolcord (fcolcord)]

It looks like apport worked.

Just for context, I started up laptop this morning to do something
quickly. Can't remember what I was running when I last shut down.

In the past few days, the laptop has been running fine. This is the
first event since I got the email asking me to run apport. I start
laptop about once a day.

Skype has been crashing on my machine regularly. Now that I see bugs
are attended to regularly, I will look up other skype bugs and if
necessary file one. I think skype crashes due to wireless network
problems.

I have a strong signal. I'm not far away from router on the same floor.

My hunch is that this is a wireless driver issue.

I am running a Belkin N router. I can find model number if you want
when I get home.

I also run firefox and chrome regularly.

When I started up this morning, got flashing capslock light. Couldn't
do anything.
Turned off by holding down power button. Grub menu on restart. Chose
rescue option. Then said continue.
After login, couldn't find "terminal" in unity menu.
Realized I should do a clean shutdown.
After rebooting, no grub, ran apport fine.

Let me know if there is anything else you need me to do to help debug.

I'm happy to install other drivers if you want.

Thanks to the volunteers and everyone at Ubuntu for producing software
that gives life to old machines.

Yours

Frank

On 2011-11-12, Fabio Marconi <email address hidden> wrote:
> Please run in a terminal
> apport-collect 888341
> Thanks
> Fabio
>
> ** Package changed: ubuntu => linux (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/888341
>
> Title:
> Lenovo X61 hangs with flashing caps lock LED.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/888341/+subscriptions
>

--
Sent from my mobile device

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

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'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

[fcolcord (fcolcord)]

So, I should follow the instructions in:

start quote

Installing Mainline KernelsTo use the mainline kernel as-is you only
only need to download and install the *image*.deb package that
corresponds to your architecture, however if you need to build any
external modules you also need the correct *header*.deb and
*source*.deb packages.
To install, download the common headers, architecture specific
headers, and the architecture specific image. For example for
2.6.27.15 we have the following files, for i386 you would need those
marked with B and C, amd64 take those marked A & C:
A       linux-headers-2.6.27-02062715-generic_2.6.27-02062715_amd64.debB
      linux-headers-2.6.27-02062715-generic_2.6.27-02062715_i386.debC
     linux-headers-2.6.27-02062715_2.6.27-02062715_all.debA
linux-image-2.6.27-02062715-generic_2.6.27-02062715_amd64.debB
linux-image-2.6.27-02062715-generic_2.6.27-02062715_i386.debOnce you
have those downloaded they will need to be installed using dpkg:
sudo dpkg -i *.debWhen this process completes you should have a new
entry on your boot menu representing the mainline kernel. This will
appear as an entry like this:
Ubuntu Intrepid, kernel 2.6.27-02062715-generic

end quote
and go to this directory, for example,

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc2-oneiric/

and download these files

 linux-headers-3.2.0-030200rc2-generic_3.2.0-030200rc2.201111151435_i386.deb 15-Nov-2011
19:51 893K
 linux-headers-3.2.0-030200rc2_3.2.0-030200rc2.201111151435_all.deb 15-Nov-2011
19:35 11M
 linux-image-3.2.0-030200rc2-generic_3.2.0-030200rc2.201111151435_i386.deb 15-Nov-2011
19:51 35M

and execute the last instructions quoted above.

(I've never done this before, so I'm just checking I understand your
request correctly.)

regards,

Frank

On 17 November 2011 15:00, Joseph Salisbury
<email address hidden> wrote:
> Would it be possible for you to test the latest upstream kernel?  It
> will allow additional upstream developers to examine the issue. Refer to
> https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test
> the latest v3.2-rcN kernel (Not a kernel in the daily directory).  Once
> you've tested the upstream kernel, please remove the 'needs-upstream-
> testing' tag(Only that one tag, please leave the others). 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.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'.  For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> 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'.  If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
>       Status: Incomplete => Conf...

[fcolcord (fcolcord)]

OK. I've done those steps.

The only error I had following the instructions is that I don't have a boot
menu, and I can't figure out how to get one.
I installed startup manager, and put in a longer pause, but that didn't
help.

I did the command (can't remember which) to show which kernel I'm running,
and it said 3.2.
So I think the steps went through fine.

I will let you know if the error with being unable to boot up comes up
again.

regards,

Frank

On 17 November 2011 16:59, Frank Colcord <email address hidden> wrote:

> So, I should follow the instructions in:
>
> start quote
>
> Installing Mainline KernelsTo use the mainline kernel as-is you only
> only need to download and install the *image*.deb package that
> corresponds to your architecture, however if you need to build any
> external modules you also need the correct *header*.deb and
> *source*.deb packages.
> To install, download the common headers, architecture specific
> headers, and the architecture specific image. For example for
> 2.6.27.15 we have the following files, for i386 you would need those
> marked with B and C, amd64 take those marked A & C:
> A linux-headers-2.6.27-02062715-generic_2.6.27-02062715_amd64.debB
> linux-headers-2.6.27-02062715-generic_2.6.27-02062715_i386.debC
> linux-headers-2.6.27-02062715_2.6.27-02062715_all.debA
> linux-image-2.6.27-02062715-generic_2.6.27-02062715_amd64.debB
> linux-image-2.6.27-02062715-generic_2.6.27-02062715_i386.debOnce you
> have those downloaded they will need to be installed using dpkg:
> sudo dpkg -i *.debWhen this process completes you should have a new
> entry on your boot menu representing the mainline kernel. This will
> appear as an entry like this:
> Ubuntu Intrepid, kernel 2.6.27-02062715-generic
>
> end quote
> and go to this directory, for example,
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc2-oneiric/
>
>
> and download these files
>
>
>
> linux-headers-3.2.0-030200rc2-generic_3.2.0-030200rc2.201111151435_i386.deb
> 15-Nov-2011
> 19:51 893K
> linux-headers-3.2.0-030200rc2_3.2.0-030200rc2.201111151435_all.deb
> 15-Nov-2011
> 19:35 11M
>
> linux-image-3.2.0-030200rc2-generic_3.2.0-030200rc2.201111151435_i386.deb
> 15-Nov-2011
> 19:51 35M
>
>
> and execute the last instructions quoted above.
>
> (I've never done this before, so I'm just checking I understand your
> request correctly.)
>
> regards,
>
> Frank
>
>
> On 17 November 2011 15:00, Joseph Salisbury
> <email address hidden> wrote:
> > Would it be possible for you to test the latest upstream kernel? It
> > will allow additional upstream developers to examine the issue. Refer to
> > https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test
> > the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once
> > you've tested the upstream kernel, please remove the 'needs-upstream-
> > testing' tag(Only that one tag, please leave the others). 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.
> >
> > If this bug is fixed by the mainline kernel, plea...

[fcolcord (fcolcord)]

Hi,

Thanks to everyone who contributed to fixing this bug so promptly.

I did the mainline kernel thing as requested above.

Have been testing since 22 Nov, and haven't had a repeat of behaviour.

3.2.0-030200rc2

Not sure I edited the tag right, but that string was in the name of the files I downloaded.

thanks again,

Frank

[fcolcord (fcolcord)]

btw you might want to change the instructions on

https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds

quote
When this process completes you should have a new entry on your boot menu representing the mainline kernel. This will appear as an entry like this:

Ubuntu Intrepid, kernel 2.6.27-02062715-generic
end quote

because I didn't see a boot menu, and can't figure out how to.

thanks,

Frank

[penalvch (penalvch)]

fcolcord, 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test 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. 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.11-rc5

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.

[Launchpad Janitor (janitor)]

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