From: yhager at yhager.com <yhager@yhager.com>
To: b43-dev@lists.infradead.org
Subject: System freezes with 2.6.33
Date: Sun, 18 Apr 2010 00:19:33 -0700 [thread overview]
Message-ID: <20100418071932.GB15229@happy.exit> (raw)
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).
[yuval at happy ~]$ uname -a
Linux happy 2.6.33-ARCH #1 SMP PREEMPT Mon Apr 5 05:57:38 UTC 2010 i686 VIA C7-M Processor 1600MHz CentaurHauls GNU/Linux
[yuval at happy ~]$ lspci -vvn|grep 43 -A7
00:00.4 0600: 1106:4364
Subsystem: 103c:3030
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
00:00.5 0800: 1106:5364 (prog-if 20 [IO(X)-APIC])
Subsystem: 103c:3030
--
02:00.0 0280: 14e4:4312 (rev 02)
Subsystem: 103c:1371
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 24
Region 0: Memory@fdffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge
07:03.0 0200: 14e4:169c (rev 03)
Subsystem: 103c:3030
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (16000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
next reply other threads:[~2010-04-18 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 7:19 yhager at yhager.com [this message]
2010-04-18 16:16 ` System freezes with 2.6.33 Larry Finger
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=20100418071932.GB15229@happy.exit \
--to=yhager@yhager.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox