From: Ingo Brunberg <ingo_brunberg@web.de>
To: linux-kernel@vger.kernel.org
Subject: BUG in rt2x00lib_txdone() with 2.6.37-rc8
Date: Thu, 13 Jan 2011 13:36:16 +0100 [thread overview]
Message-ID: <m31v4hkmkf.fsf@ingo.homenetwork> (raw)
I also suffer from this bug with 2.6.37. The first time the following
trace made it into my logs. Hopefully it might help.
BUG: unable to handle kernel NULL pointer dereference at 0000000000000090
IP: [<ffffffffa00983e4>] rt2x00lib_txdone+0x31/0x259 [rt2x00lib]
PGD a7011067 PUD ab9b2067 PMD 0
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:13.2/usb2/2-3/2-3.4/2-3.4:1.0/firmware/2-3.4:1.0/loading
CPU 3
Modules linked in: aes_generic af_packet w83627ehf hwmon_vid ipv6 fbcon font bitblit softcursor dm_mod arc4 ecb crypto_blkcipher cryptomgr aead crypto_algapi rt73usb rt2x00usb rt2x00lib mac80211 cfg80211 usbhid hid radeon snd_hda_codec_realtek ttm r8169 drm_kms_helper sr_mod drm cdrom firewire_ohci snd_hda_intel i2c_piix4 bitrev 8250_pnp processor snd_hda_codec ohci_hcd thermal_sys ehci_hcd usbcore crc32 8250 i2c_algo_bit firewire_core i2c_core sg pata_atiixp crc_itu_t rtc button k10temp evdev hwmon snd_pcm snd_timer cfbcopyarea cfbimgblt snd floppy cfbfillrect serial_core mii nls_base soundcore snd_page_alloc
Pid: 3069, comm: kworker/3:0 Not tainted 2.6.37 #1 M3A785GXH/128M/To Be Filled By O.E.M.
RIP: 0010:[<ffffffffa00983e4>] [<ffffffffa00983e4>] rt2x00lib_txdone+0x31/0x259 [rt2x00lib]
RSP: 0018:ffff880094ad3d30 EFLAGS: 00010286
RAX: 0000000000000030 RBX: ffff88011df79980 RCX: 0000000000000014
RDX: 0000000000000101 RSI: ffff880094ad3d90 RDI: 0000000000000000
RBP: ffff88011ec37af8 R08: 0000000000000002 R09: ffffffff00000002
R10: 0000000000000286 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000028 R14: ffff880094ad3d90 R15: ffff88011df79c10
FS: 00007fc5bad23710(0000) GS:ffff8800cfd80000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000090 CR3: 00000000ab985000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kworker/3:0 (pid: 3069, threadinfo ffff880094ad2000, task ffff88011ff08b20)
Stack:
ffff88011fc7e420 0000000000011000 0000000000000030 0000000000004000
ffff88011ec37af8 ffff88011dcb3af0 ffff88011df79980 ffff88011dcb3b40
ffff88011dcb3b40 0000000000000003 ffff88011df79c10 ffffffffa009862e
Call Trace:
[<ffffffffa009862e>] ? rt2x00lib_txdone_noinfo+0x22/0x27 [rt2x00lib]
[<ffffffffa0016316>] ? rt2x00usb_work_txdone+0x3e/0x6d [rt2x00usb]
[<ffffffffa0016a0d>] ? rt2x00usb_watchdog+0x69/0xe0 [rt2x00usb]
[<ffffffffa009aed9>] ? rt2x00link_watchdog+0x0/0x4a [rt2x00lib]
[<ffffffffa009af00>] ? rt2x00link_watchdog+0x27/0x4a [rt2x00lib]
[<ffffffff8104256e>] ? process_one_work+0x20e/0x34e
[<ffffffff81042a45>] ? worker_thread+0x1c9/0x340
[<ffffffff8102612e>] ? __wake_up_common+0x41/0x78
[<ffffffff8104287c>] ? worker_thread+0x0/0x340
[<ffffffff8104287c>] ? worker_thread+0x0/0x340
[<ffffffff810455a9>] ? kthread+0x7a/0x82
[<ffffffff81002cd4>] ? kernel_thread_helper+0x4/0x10
[<ffffffff8104552f>] ? kthread+0x0/0x82
[<ffffffff81002cd0>] ? kernel_thread_helper+0x0/0x10
Code: f6 41 55 41 54 55 48 89 fd 53 48 83 ec 28 4c 8b 67 10 48 8b 47 08 48 8b 18 49 8d 44 24 30 4c 89 e7 4d 8d 6c 24 28 48 89 44 24 10 <41> 8b 94 24 90 00 00 00 66 89 54 24 1e e8 1b 16 14 00 48 89 ef
RIP [<ffffffffa00983e4>] rt2x00lib_txdone+0x31/0x259 [rt2x00lib]
RSP <ffff880094ad3d30>
CR2: 0000000000000090
---[ end trace 2c6843a38ee68ff0 ]---
next reply other threads:[~2011-01-13 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 12:36 Ingo Brunberg [this message]
2011-01-13 13:23 ` BUG in rt2x00lib_txdone() with 2.6.37-rc8 Helmut Schaa
2011-01-15 13:34 ` Ivo Van Doorn
2011-01-16 1:59 ` Helmut Schaa
2011-01-16 2:58 ` Ingo Brunberg
2011-01-17 20:36 ` Ivo Van Doorn
-- strict thread matches above, loose matches on Subject: below --
2011-01-12 22:34 Michele Ballabio
2010-12-31 10:23 Stephen Boyd
2011-01-01 10:28 ` Heinz Diehl
2011-01-01 21:35 ` Stephen Boyd
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=m31v4hkmkf.fsf@ingo.homenetwork \
--to=ingo_brunberg@web.de \
--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 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.