From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-wireless@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: iwl3945 dies (oops) in post 2.6.34 kernels
Date: Tue, 25 May 2010 19:01:56 +0200 [thread overview]
Message-ID: <1274806916.18861.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100525163920.GA2730@core.coreip.homeip.net>
On Tue, 2010-05-25 at 09:39 -0700, Dmitry Torokhov wrote:
> Hi,
>
> I am getting the following crashers in iwl3945 after updating to
> post-2.6.34 kernels. This is with the pull from Linus's tree as of last
> night (the taint is from nvidia module):
>
> [ 3330.630734] general protection fault: 0000 [#1] PREEMPT SMP
> [ 3330.630752] last sysfs file: /sys/devices/platform/dock.0/docked
> [ 3330.630761] CPU 0
> [ 3330.630766] Modules linked in: cryptd aes_x86_64 aes_generic fuse rfcomm sco bnep l2cap autofs4
> coretemp hwmon sunrpc ppdev parport_pc parport acpi_cpufreq mperf uinput nvidia(P) snd_hda_codec_idt
> arc4 snd_hda_intel ecb snd_hda_codec snd_hwdep iwl3945 joydev snd_seq snd_seq_device snd_pcm iwlcore
> mac80211 snd_timer cfg80211 snd psmouse iTCO_wdt dell_wmi iTCO_vendor_support serio_raw tg3 battery
> dell_laptop dcdbas soundcore snd_page_alloc btusb bluetooth video pcspkr mac_hid ac wmi libphy
> firewire_ohci i2c_i801 firewire_core yenta_socket crc_itu_t ohci_hcd [last unloaded: microcode]
> [ 3330.630950]
> [ 3330.630958] Pid: 455, comm: iwl3945 Tainted: P 2.6.35-rc0 #293 0WM416/Latitude D630
> [ 3330.630967] RIP: 0010:[<ffffffffa01e70d3>] [<ffffffffa01e70d3>] iwl3945_get_channels_for_scan+0xe3/0x460 [iwl3945]
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2208
johannes
next prev parent reply other threads:[~2010-05-25 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 16:39 iwl3945 dies (oops) in post 2.6.34 kernels Dmitry Torokhov
2010-05-25 16:55 ` John W. Linville
2010-05-25 17:01 ` Johannes Berg [this message]
2010-05-25 17:08 ` Abhijeet Kolekar
2010-05-25 17:27 ` Dmitry Torokhov
2010-05-25 22:34 ` Sedat Dilek
2010-06-04 5:08 ` Dmitry Torokhov
2010-06-04 5:08 ` Abhijeet Kolekar
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=1274806916.18861.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).