All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maciek Zarzycki <zarzych@gmail.com>
To: sedat.dilek@gmail.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: Possible bug in iwlwifi
Date: Sun, 27 Jan 2013 22:49:20 +0100	[thread overview]
Message-ID: <5643712.YXEVgUjzFG@zarzych> (raw)
In-Reply-To: <CA+icZUWfjE4CWU9k9DRyQhDxB1MbgaL5WfR_B=viTLKWN5YCxg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

On Sunday 27 of January 2013 22:25:16 Sedat Dilek wrote:

> I can't say much to the call-traces, but in general you should add
> your kernel-config and dmesg at least.
> An 'lspci -nnvv' (or lsusb) wouldn't hurt, too.
> 
> Check <wireless.kernel.org> on how to debug iwlwifi driver
> (documentation websites).
> 
> If you are fit in kernel-building you can try the pending patches in
> Greg's linux-stable GIT [2].
> Before that I would try the pending patch from iwlwifi-fixes GIT [1],
> it's for 3.7-stable as well.
> 
> Can you try and report?
> 
> Regards,
> - Sedat -
> 
> P.S.: IIRC iwlwifi folks have an own mailing-list?

Thanks for your answer. The iwlwifi page mentions this mailing list for bug reports. 

I'm using arch kernel. I'll compile a vanilla kernel tomorrow and also check it with the two sets of patches that you mentioned and report back. I've also just stumbled upon docs on how to report wireless related bugs. Sorry for not following them with my first email.

-- 
Maciek Zarzycki

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-01-27 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 20:51 Possible bug in iwlwifi Maciek Zarzycki
2013-01-27 20:59 ` Maciek Zarzycki
2013-01-27 21:25   ` Sedat Dilek
2013-01-27 21:27     ` Sedat Dilek
2013-01-27 21:49     ` Maciek Zarzycki [this message]
2013-01-27 21:59       ` Sedat Dilek
2013-01-29 19:32         ` Maciek Zarzycki
2021-05-05 12:05 Michael Yartys
2021-05-05 12:09 ` Johannes Berg
2021-05-05 12:25   ` Michael Yartys
2021-05-05 12:36     ` Michael Yartys
2021-05-05 13:06       ` Michael Yartys
2021-05-05 16:48         ` Johannes Berg

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=5643712.YXEVgUjzFG@zarzych \
    --to=zarzych@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    /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.