From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: System freezes with 2.6.33
Date: Sun, 18 Apr 2010 11:16:49 -0500 [thread overview]
Message-ID: <4BCB3071.8030500@lwfinger.net> (raw)
In-Reply-To: <20100418071932.GB15229@happy.exit>
On 04/18/2010 02:19 AM, yhager at yhager.com wrote:
> Hi,
>
> After upgrading my system to 2.6.33
> (http://www.archlinux.org/packages/core/i686/kernel26/) I am
> experiencing complete system lockups.
>
> I confirmed that this happens when the b43 drives is on ahd I try to
> connect to the network. When I remove the module, the system works fine
> for hours. When it is on, I have a few minutes, till a complete freeze.
>
> There is nothing in the kernel logs, or dmesg, or anywhere I could
> find. I tried reinstalling the firmware, but it didn't change anything.
>
> The hardware is HP-2133 (mini note).
Yours is the first report of such freezes. As there is a possibility of
info being logged, but not being written and saved on disk, I would like
you to switch to the logging console (Ctrl+Alt+F10) immediately after
bringing the system up and starting the connection. Does anything show
there? I do not have access to a card like yours, but I have tested with
a 14e4:4311, which is similar.
Larry
next prev parent reply other threads:[~2010-04-18 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 7:19 System freezes with 2.6.33 yhager at yhager.com
2010-04-18 16:16 ` Larry Finger [this message]
2010-04-20 14:34 ` yhager at yhager.com
2010-04-20 15:51 ` Peter Stuge
2010-04-20 16:07 ` Daniel Kuehn
2010-04-20 16:27 ` Peter Stuge
2010-04-20 17:07 ` Larry Finger
2010-04-22 16:12 ` yhager at yhager.com
2010-04-22 17:21 ` Larry Finger
2010-04-22 18:59 ` yhager at yhager.com
2010-05-01 23:28 ` Yuval Hager
2010-04-19 16:54 ` Peter Stuge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BCB3071.8030500@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.