keyboard / log off / shutdown stop working intermittently (bcm43xx related?)

uname -a:
2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Same specs as head of post except I use 64-bit Gutsy. I removed the bcm43xx and used ndiswrapper to access wireless instead though.

Bug confimed by Checho (and 2 others on Ubuntuforums.org)

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Same problem, but I get this in dmesg when the keyboard stops working:

[1270.000000] NETDEV WATCHDOG: eth1: transmit timed out
[1270.000000] bcm43xx: Controller RESET (TX timeout) ...

Sometimes I can do fine for hours at a time, sometimes it happens 5 minutes after I turn my laptop on.

BTW, I use wifi-radar (as a daemon). I don't use knetwork manager.

I don't seem to have that one but I do have a lot of:

[17503.548000] APIC error on CPU1: 40(40)
[17503.548000] APIC error on CPU0: 40(40)

Type errors (on this dual core AMD machine)

I'm on a dell inspiron 1501. Randomly my keyboard stops reacting, if I try to shut down it hangs on a black screen with som cryptic signs on it. If I want to turn it of, then I have to hold the power button in.

I read a comment on ubuntuforums that indicated there was something wrong with the way ubuntu used unfree drivers. So I uninstalled the unfree driver for bcm43xx, rebooted and so I installed the package found here:

http://www.linux-geek.org/2007/04/22/dell-1390-native-linux-driver-how-to-updated/

Package: http://ubuntu.cafuego.net/pool/feisty-cafuego/bcm43xx/bcm43xx-firmware_1.3-1ubuntu2_all.deb

Then I rebooted, and the wifi was functioning without the unfree driver. I still havent confirmed that machine won't lock up on me, but I'm hoping it will do the trick! Time will tell.

Didn't seem to make a difference.

Well,

This one's nearly 100% reproducable here, and yet the strange thing is that
when I created a new user and logged in with that this bug doesn't seem to
occur. I've taken to logging in with the new user, connecting to the
internet (which is an instant keyboard hang on user 1), then starting a new
session with my original user. That way I have internet *and* keyboard and
still get to use the same account. Unfortunately, this is a dog of a process
to go through *every single login* so I'm hoping we can do something to get
this fixed here soon.

Is this still happening in Hardy (b43 drivers)?

Can't say at the moment as the system is still running Gutsy, and it's
my computer instability hating wife's laptop, so no upgrade to a beta
OS. :( Did a complete re-install (of Gutsy) a few weeks back though
and I haven't seen this problem since. This is no guarantee though as
I've done complete re-installs on it before only to have the problem
resurface a few weeks later. Could be that a kernel upgrade did the
job for us though...

I'll make sure I report back here if the problem happens again.

On 3/24/08, Leonardo Gastón De Luca <email address hidden> wrote:
> Is this still happening in Hardy (b43 drivers)?
>
> --
> keyboard / log off / shutdown stop working intermittently (bcm43xx related?)
> https://bugs.launchpad.net/bugs/174015
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "linux-source-2.6.22" in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: linux-source-2.6.22
>
> There's a few similar experiences that have been mentioned in the comments
> of various other bugs, but this bug differs from the following bug
> descriptions as I describe below.
>
> The basic pattern is that most of the time my keyboard, shutdown and
> internet work fine. Sometimes though for a few days at a time, regardless of
> shutdowns etc I can either have knetwork manager running, but keyboard does
> nothing and shutdown hangs, or I can turn off knetworkmanager autostarting
> and the keyboard/shutdown work fine. Often after a few days it seems to go
> away for a month or so by itself and the keyboard *always* works for kdm
> login. A number of other people (in Ubuntu / Xubuntu) have the same problem
> as discussed here:
>
> http://ubuntuforums.org/showthread.php?p=3726423#post3726423
>
> The problem seems to be a kernel meets bcm43xx issue although it seems more
> common on Dell AMD (x2) based machines.
>
> My system is:
> Kubuntu Gutsy final (32 bit)
> 2.6.22-14-generic i686
> bcm43xx-fwcutter
> lspci and dmesg are below
>
> A number of similar looking bugs exist, but are different in the following
> ways:
> bug 59432 - This bug is reporting for Edgy using Ndiswrapper
> bug 61388 - Very similar comments by Michael Head, Xamusk and b, however
> this bug claims to have been fixed back in Feisty in kernel 2.6.20.
> bug 138094 - Problems discussed here seem to be around compiz. Compiz /
> Desktop Effects are not installed here (Kubuntu) and their Desktop freezes
> too.
> bug 108225 - Very similar, but on Feisty using Atheros. Comments by Severn
> Clay and Arkan (also using bcm43xx) match perfectly
> bug 159398 - Similar, but on 2.6.20 kernel and desktop also hangs (not just
> keyboard).
> bug 85099 - again this refers to an older kernel (2.6.20-8) and hard
> lockups, not just keyboard/shutdown problems.
> bug 151370 - Same kernel, but different symptoms. No keyboard problems.
>

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Hmmm... haven't looked at this one in a while. And in fact, I haven't seen this bug in almost as long. I have a feeling that the upgrade to Hardy (final) may have fixed it already.

Sorry I missed marking it as resolved, but it was very intermittent and so without going a few months I couldn't have said with any certainty if it was fixed anyway. Now I can. =)

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I'd say b43 solved all this.

Setting this to Fix Released.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.