From: "John W. Linville" <linville@tuxdriver.com>
To: Priit Laes <plaes@plaes.org>
Cc: netdev@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: iwl3945: HARDWARE GONE??
Date: Fri, 2 Jul 2010 12:26:50 -0400 [thread overview]
Message-ID: <20100702162650.GC2381@tuxdriver.com> (raw)
In-Reply-To: <1278086575.2889.8.camel@chi>
On Fri, Jul 02, 2010 at 07:02:55PM +0300, Priit Laes wrote:
> Heya!
>
> Bumped my kernel to version 2.6.35-rc3-00391-g97e0214 and ran into
> HARDWARE GONE error message..
>
> Hardware is Lenovo x60s and wireless card is intel 3945:
>
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
> Subsystem: Intel Corporation ThinkPad R60e/X60s
> Flags: bus master, fast devsel, latency 0, IRQ 47
> Memory at edf00000 (32-bit, non-prefetchable) [size=4K]
> Capabilities: [c8] Power Management version 2
> Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [e0] Express Legacy Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [140] Device Serial Number 00-xx-xx-xx-xx-xx-xx-xx
> Kernel driver in use: iwl3945
> Kernel modules: iwl3945
>
> I have attached dmesg error message...
>
> Cheers,
> Priit :)
> [13813.347617] Uhhuh. NMI received for unknown reason a1 on CPU 0.
> [13813.347617] You have some hardware problem, likely on the PCI bus.
> [13813.347617] Dazed and confused, but trying to continue
> [13813.347617] iwl3945 0000:03:00.0: HARDWARE GONE?? INTA == 0xffffffff
We've been seeing this sort of thing a lot -- somehow the iwl3945 gets
disconnected from the PCI bus. Anyone have any clue how that happens?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-07-02 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 16:02 iwl3945: HARDWARE GONE?? Priit Laes
2010-07-02 16:26 ` John W. Linville [this message]
2010-07-02 16:48 ` Stephen Hemminger
2010-07-06 0:18 ` Robert Hancock
2010-07-06 12:48 ` Priit Laes
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=20100702162650.GC2381@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=plaes@plaes.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.