All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Cheek <joseph@cheek.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
Date: Mon, 02 Feb 2009 23:01:11 -0500	[thread overview]
Message-ID: <4987C187.9090904@cheek.com> (raw)
In-Reply-To: <43e72e890902021550q60103e5an2a56d3cc4cd8f4dd@mail.gmail.com>

looks like i was a little hasty.  checking syslog I see:

Feb  2 22:49:31 harrisburg ath9k: received PCI FATAL interrupt
Feb  2 22:49:36 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29
 - assume out of range

can I assume that the lack of a ProbeResp is because of the fatal
interrupt 5 seconds earlier?

Joseph Cheek

Luis R. Rodriguez wrote:
> On Mon, Feb 2, 2009 at 2:21 PM, Joseph Cheek <joseph@cheek.com> wrote:
>   
>> I've been trying git tip for a week and no more kernel OOPS!  great job,
>> thanks!
>>     
>
> Good to hear :)
>
>   
>> I also did NOT have to change IEEE_MONITORING_INTERVAL to stay
>> connected.  *But* I still lose connectivity for several seconds during a
>> large file transfer (most often transferring 50M or more via scp or
>> rsync -e ssh).
>>     
>
> Check the logs for reason given for the disassociation, see another
> thread recently where I posted the reason number to reason
> description.
>
>   Luis
>
>   

  reply	other threads:[~2009-02-03  4:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  6:14 [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
2009-01-21 18:49 ` Luis R. Rodriguez
2009-01-21 19:54   ` Joseph Cheek
2009-01-21 22:18     ` Joseph Cheek
2009-01-22 19:19       ` Joseph Cheek
2009-01-22 19:44         ` Luis R. Rodriguez
2009-01-25  0:32           ` Joseph Cheek
2009-01-25  2:23             ` Luis R. Rodriguez
2009-01-25  2:27             ` Stephen Gutknecht
2009-02-02 22:21             ` Joseph Cheek
2009-02-02 23:50               ` Luis R. Rodriguez
2009-02-03  4:01                 ` Joseph Cheek [this message]
2009-02-03  5:04                   ` Luis R. Rodriguez
2009-02-03 11:11                     ` [ath9k-devel] Problem with 80211n Speed and packet drop Amit Sood
2009-02-04 20:58                       ` Pavel Roskin
2009-02-04 23:21                         ` Amit Sood
2009-02-05  4:37                           ` Pavel Roskin
2009-02-08  3:14                     ` [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
  -- strict thread matches above, loose matches on Subject: below --
2009-04-06  7:36 Masashi Honma
2009-04-06  7:43 Masashi Honma

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=4987C187.9090904@cheek.com \
    --to=joseph@cheek.com \
    --cc=ath9k-devel@lists.ath9k.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.