From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Kamil Grzebien <ciptok@gmail.com>
Cc: Kamil Grzebien <ciptok@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Initializing iwl3945 error
Date: Wed, 4 Apr 2012 18:13:19 +0200 [thread overview]
Message-ID: <20120404161317.GB14078@redhat.com> (raw)
In-Reply-To: <CAErSpo6t-cVBdJfyARi3ifEuBUvopbG5GQSP5YywrvumDK8HFA@mail.gmail.com>
On Thu, Mar 15, 2012 at 03:08:43PM -0600, Bjorn Helgaas wrote:
> The bug report (http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2143)
> has a lot of logs, but they're pretty old and I can't tell how
> applicable they are to your situation.
>
> It would be useful to see a complete dmesg log, /proc/iomem, and
> "lspci -vv" output from your machine after the problem occurs, and
> also the same information when it works (when using the noapic flag).
Kamil, ping, can you provide requested information?
Stanislaw
next prev parent reply other threads:[~2012-04-04 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 17:43 Initializing iwl3945 error Kamil Grzebien
2012-03-13 8:12 ` Stanislaw Gruszka
2012-03-15 21:08 ` Bjorn Helgaas
2012-04-04 16:13 ` Stanislaw Gruszka [this message]
2012-04-05 8:24 ` Kamil Grzebien
2012-04-08 11:51 ` Kamil Grzebien
2012-05-28 14:04 ` Stanislaw Gruszka
2012-05-28 18:21 ` Bjorn Helgaas
2012-05-29 9:21 ` Stanislaw Gruszka
2012-06-22 3:30 ` Bjorn Helgaas
2012-07-01 18:01 ` Kamil Grzebien
2012-07-02 5:31 ` Stanislaw Gruszka
2012-07-02 20:49 ` Kamil Grzebien
2012-07-06 20:38 ` Bjorn Helgaas
2012-07-06 21:34 ` Yinghai Lu
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=20120404161317.GB14078@redhat.com \
--to=sgruszka@redhat.com \
--cc=bhelgaas@google.com \
--cc=ciptok@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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.