All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Yuval Hager <yuval@avramzon.net>
Cc: Michael Buesch <mb@bu3sch.de>,
	LKML <linux-kernel@vger.kernel.org>,
	wireless <linux-wireless@vger.kernel.org>,
	bcm43xx-dev@lists.berlios.de
Subject: Re: BCM4312 Fails when xdm is started
Date: Mon, 24 Nov 2008 10:11:53 -0600	[thread overview]
Message-ID: <492AD249.3020309@lwfinger.net> (raw)
In-Reply-To: <200811241155.47079.mb@bu3sch.de>

Michael Buesch wrote:
> On Monday 24 November 2008 09:49:38 Yuval Hager wrote:
>> * Now check this out - the output of lspci -d 14e4:4312 -x
>> 02:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev ff)
>> 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>
>> (I double checked this)
>>
>> huh?
> 
> Hah, interesting. I think your hardware may be faulty, in fact.
> To me it really seems like the mainboard has power failures on the PCI bus.
> 
> This is a laptop, so you can't pull random hardware? Can you run some
> hardware burn-in tests like mprime (http://mersenne.org/freesoft/) or memtest?
> If that doesn't help, can you try with another operating system?
> 

I also think you are seeing a hardware failure. Another test to try is
http://freshmeat.net/projects/cpuburn/?topic_id=146, which will exercise the system.

Larry

  reply	other threads:[~2008-11-24 16:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200811151801.02369.yuval@avramzon.net>
     [not found] ` <491EFB9D.3040002@lwfinger.net>
     [not found]   ` <200811151907.05636.yuval@avramzon.net>
     [not found]     ` <20081115174623.27321.qmail@stuge.se>
2008-11-21 16:25       ` BCM4312 Fails when xdm is started Larry Finger
2008-11-21 17:42         ` Michael Buesch
2008-11-21 18:28           ` Larry Finger
2008-11-22  6:39             ` Yuval Hager
2008-11-22 15:13               ` Michael Buesch
2008-11-22 15:32                 ` Larry Finger
2008-11-22 15:54                   ` Michael Buesch
2008-11-23  7:26                     ` Yuval Hager
2008-11-23 11:49                     ` Yuval Hager
2008-11-23 12:20                       ` Michael Buesch
2008-11-23 15:42                         ` Larry Finger
2008-11-23 17:42                           ` Michael Buesch
     [not found]                             ` <200811231955.41722.yuval@avramzon.net>
2008-11-23 18:08                               ` Michael Buesch
2008-11-23 20:46                         ` Peter Stuge
2008-11-23 21:09                           ` Larry Finger
2008-11-24  8:49                             ` Yuval Hager
2008-11-24 10:55                               ` Michael Buesch
2008-11-24 16:11                                 ` Larry Finger [this message]
2008-11-25  5:43                                   ` Yuval Hager
2008-11-25  7:18                                     ` Peter Stuge
2008-12-07  9:29                                       ` Yuval Hager
2008-12-07 16:15                                         ` Larry Finger
2008-11-25 11:05                                     ` Michael Buesch

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=492AD249.3020309@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=yuval@avramzon.net \
    /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.