All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Bob Copeland <me@bobcopeland.com>,
	Jiri Slaby <jirislaby@gmail.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Ath5k on 2.6.32 suddenly fails
Date: Fri, 15 Jan 2010 23:29:59 +0100	[thread overview]
Message-ID: <201001152330.00470.mb@bu3sch.de> (raw)
In-Reply-To: <201001112336.50125.mb@bu3sch.de>

On Monday 11 January 2010 23:36:49 Michael Buesch wrote:
> I currently have one and a half days of uptime. I think I'll first
> continue running .32 to check whether it happens again or if this was just
> some random hardware burp.
> I think it should be likely to trigger again within one or two days, if this is a bug.

mb@quimby:~$ uptime
 23:23:34 up 5 days, 11:49,  1 user,  load average: 0.00, 0.00, 0.00

So, it didn't trigger, yet.
I think I will assume for now that we had a hardware burp and this
is not caused by a software bug. The AP is used a lot and it currently
is rock-stable on 2.6.32.

The card is a minipci connected through a minipci->pci converter card.
I know that the converter does not have high quality contact pins, so I
currently blame the converter card for flipping a bit.
I think I'll replace it by something better soon.

So let's close this, unless I come back to you guys with new results.

-- 
Greetings, Michael.

  reply	other threads:[~2010-01-15 22:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 10:52 Ath5k on 2.6.32 suddenly fails Michael Buesch
2010-01-11 16:11 ` Luis R. Rodriguez
2010-01-11 16:35   ` Larry Finger
2010-01-11 16:43     ` Luis R. Rodriguez
2010-01-11 22:36   ` Michael Buesch
2010-01-15 22:29     ` Michael Buesch [this message]
2010-01-15 22:40       ` Michael Buesch
2010-01-15 22:47         ` Luis R. Rodriguez
2010-01-15 22:50           ` Michael Buesch
2010-01-21 12:05             ` Michael Buesch
2010-01-21 15:57               ` Bob Copeland

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=201001152330.00470.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=rjw@sisk.pl \
    /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.