From: Pedro Francisco <pedrogfrancisco@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: ath5k misbehaving affecting other kernel parts unrelated?
Date: Fri, 23 Apr 2010 08:06:13 +0100 [thread overview]
Message-ID: <201004230806.13628.pedrogfrancisco@gmail.com> (raw)
Greetings!
Is it possible a faulty ath5k module to affect diverse parts of kernel causing
different oopses to happen referencing things as different as cdrom_ioctl,
find_vma, i915_gem_object_get_pages, get_vfs_caps_from_disk,
warn_slowpath_common (ath5k_tasklet_rx), proc_lookup_de and
_spin_lock(ext4_getattr) [soft lookup]?
The task in which such errors happen is capturing packets with kismet during
the night. The errors aren't easy to create, sometimes they've already
happened when I check the computer in the morning and sometimes they require
stirring up the computer a bit such as starting X.
I memtested the machine during 7h and no error was detected.
I've been trying different kernels but main one is 2.6.32-21-generic, Ubuntu
flavour, with linux-backports-modules-wireless-lucid-generic installed. I would
use 2.6.34-rc5 vanilla if shutdown and suspend worked ;)
As such:
a) is it "normal"? I thought modules were somewhat isolated these days.
b) any advices for debugging? I've yet to have two oopses that are similar....
Thank you in Advance,
--
Pedro
next reply other threads:[~2010-04-23 7:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 7:06 Pedro Francisco [this message]
2010-04-23 13:48 ` ath5k misbehaving affecting other kernel parts unrelated? John W. Linville
2010-04-23 16:37 ` me
2010-04-23 16:43 ` Maciej Żenczykowski
2010-04-24 8:59 ` Pedro Francisco
2010-04-24 8:56 ` Pedro Francisco
2010-04-24 12:05 ` me
2010-04-24 12:09 ` Vegard Nossum
2010-04-24 17:28 ` Pedro Francisco
2010-04-25 19:22 ` me
2010-04-25 20:29 ` Jiri Slaby
2010-04-25 21:24 ` Pedro Francisco
2010-04-27 11:04 ` Pedro Francisco
2010-04-28 21:52 ` Pedro Francisco
2010-04-29 7:17 ` Vegard Nossum
2010-04-29 10:25 ` Pedro Francisco
2010-04-23 19:13 ` Dan Carpenter
2010-04-24 9:27 ` Pedro Francisco
2010-04-24 12:13 ` Dan Carpenter
2010-04-24 13:13 ` Pedro Francisco
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=201004230806.13628.pedrogfrancisco@gmail.com \
--to=pedrogfrancisco@gmail.com \
--cc=linux-kernel@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