From: reinette chatre <reinette.chatre@intel.com>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn preventing hibernation with TuxOnIce
Date: Tue, 07 Apr 2009 10:23:43 -0700 [thread overview]
Message-ID: <1239125023.16010.33.camel@rc-desk> (raw)
In-Reply-To: <8ccc1dbe0904061216m1e31aaf4j53b0c067b9e19999@mail.gmail.com>
Mathias,
On Mon, 2009-04-06 at 12:16 -0700, Mathias Bur=C3=A9n wrote:
> Hi,
>=20
> I think I've found a bug. Either it's iwlagn or it's TuxOnIce, I'll
> try here first. Whenever my wlan0 interfaces is up, TuxOnIce causes a
> kernel panic=20
Does this mean you do not get a kernel panic if your wlan0 interface is
down? Does it matter whether iwlagn module is loaded or not, or just
interface being up or down? Does it happen during hibernate or when you
resume?
> when it's 'writing kernel and process information', after
> a while I get a backtrace (?) about something with sda (my SSD). I wa=
s
> first using iwlagn from 2.6.29 but I just installed
> compat-wireless-2009-04-06 and it made no difference.
>=20
> Hardware being used:
> Dell Inspiron 1520
>=20
> iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
> iwlagn: Copyright(c) 2003-2009 Intel Corporation
> iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> iwlagn 0000:0c:00.0: setting latency timer to 64
> iwlagn 0000:0c:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=3D=
0x4
> iwlagn 0000:0c:00.0: Tunable channels: 13 802.11bg, 19 802.11a channe=
ls
> iwlagn 0000:0c:00.0: irq 29 for MSI/MSI-X
> phy0: Selected rate control algorithm 'iwl-agn-rs'
> iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-4965-2.ucode
> iwlagn 0000:0c:00.0: loaded firmware version 228.57.2.23
> Registered led device: iwl-phy0::radio
> Registered led device: iwl-phy0::assoc
> Registered led device: iwl-phy0::RX
> Registered led device: iwl-phy0::TX
>=20
> Vanilla 2.6.29.1 kernel with TuxOnIce patch, fs for / is ext4, using
> the deadline scheduler. Kernel configuration at [1]. dmesg at [2].
The dmesg does not contain any panic or errors related to iwlagn that I
can see.=20
>=20
> Is there any way you could help me debug this? Thanks,
We can start with iwlagn debugging. Please recompile your driver with
debugging enabled and then load it with "modprobe iwlagn
debug=3D0x43fff".=20
>=20
> Mathias
>=20
>=20
> [1] http://rafb.net/p/qWvmzl19.html
> [2] http://rafb.net/p/3c2Nuw14.html
> --
Reinette
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-07 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8ccc1dbe0904061150w18d38193v772492e480f0aa15@mail.gmail.com>
2009-04-06 19:16 ` iwlagn preventing hibernation with TuxOnIce Mathias Burén
2009-04-07 17:23 ` reinette chatre [this message]
[not found] ` <8ccc1dbe0904071409k61daaf47t2261e3cfc48615be@mail.gmail.com>
2009-04-07 23:14 ` reinette chatre
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=1239125023.16010.33.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.buren@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox