All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olver Eduardo Ramos <olver.ramos@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel bug
Date: Sat, 29 Mar 2008 04:05:01 -0500	[thread overview]
Message-ID: <47EE063D.3050000@gmail.com> (raw)

------------[ cut here ]------------
kernel BUG at net/mac80211/ieee80211.c:966!
invalid opcode: 0000 [#1] SMP
Modules linked in: iwl3945 mac80211 cfg80211 cryptomgr ecb arc4
blkcipher crypto_algapi snd_seq_oss snd_seq_device snd_seq_midi_event
snd_seq snd_pcm_oss snd_mixer_oss nvidia(P) snd_hda_intel snd_pcm
snd_timer snd snd_page_alloc

Pid: 4472, comm: insmod Tainted: P        (2.6.24 #4)
EIP: 0060:[<f9982867>] EFLAGS: 00210246 CPU: 1
EIP is at ieee80211_alloc_hw+0x5a/0x2af [mac80211]
EAX: f3ea8d80 EBX: fc226d60 ECX: c029cd19 EDX: f3ea8040
ESI: fc226c80 EDI: f3ea8180 EBP: f7cc58e4 ESP: f3ea5dbc
 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process insmod (pid: 4472, ti=f3ea4000 task=f3c8d110 task.ti=f3ea4000)
Stack: f78583d8 f3ea8040 fc226cb0 fc226c80 f7cc5800 f7cc58e4 fc2110cc
f5772180
       00000000 f7ccdc90 c019c69e f3c81780 f3c81780 00200296 c03eb51d
f7ccdc90
       f7cc5800 f7cc58c4 c021fb2d fc226cb0 fc226c80 f7cc5800 f7cc58e4
c022d84d
Call Trace:
 [<fc2110cc>] iwl3945_pci_probe+0x9e/0xcfd [iwl3945]
 [<c019c69e>] sysfs_create_link+0xb7/0xf9
 [<c03eb51d>] netlink_broadcast+0x261/0x2a1
 [<c021fb2d>] kobject_get+0xf/0x13
 [<c022d84d>] pci_device_probe+0x36/0x57
 [<c029f010>] driver_probe_device+0xde/0x15c
 [<c02205ff>] kobject_uevent_env+0x350/0x374
 [<c029f125>] __driver_attach+0x0/0x87
 [<c029f177>] __driver_attach+0x52/0x87
 [<c029e5c5>] bus_for_each_dev+0x33/0x55
 [<c029ee77>] driver_attach+0x16/0x18
 [<c029f125>] __driver_attach+0x0/0x87
 [<c029e8ab>] bus_add_driver+0x6d/0x197
 [<c022d989>] __pci_register_driver+0x48/0x74
 [<f93c9030>] iwl3945_init+0x30/0x74 [iwl3945]
 [<c014229f>] sys_init_module+0x14bd/0x15e0
 [<c0169f8d>] do_sync_read+0xc7/0x10a
 [<c0150936>] __alloc_pages+0x61/0x2cf
 [<f998d2d1>] ieee80211_rx_irqsafe+0x0/0x4f [mac80211]
 [<c017b7e4>] mntput_no_expire+0x11/0x56
 [<c0104e5a>] syscall_call+0x7/0xb
 [<c0450000>] rpc_sleep_on+0x11d/0x224
 =======================
Code: 4c 9f 99 f9 89 d7 89 42 08 89 d0 81 c7 40 01 00 00 05 40 0d 00 00
89 57 2c 89 47 38 83 3b 00 75 04 0f 0b eb fe 83 7b 04 00 75 04 <0f> 0b
eb fe 83 7b 08 00 75 04 0f 0b eb fe 83 7b 14 00 75 04 0f
EIP: [<f9982867>] ieee80211_alloc_hw+0x5a/0x2af [mac80211] SS:ESP
0068:f3ea5dbc
---[ end trace 0378acc020bdab15 ]---

             reply	other threads:[~2008-03-30  0:05 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  9:05 Olver Eduardo Ramos [this message]
2008-03-30  1:06 ` kernel bug Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2018-07-31 17:02 Kernel bug Sergiy Vovk
2011-09-24 19:26 kernel bug Roman Kapusta
2011-09-24 19:45 ` Roman Kapusta
2011-09-26  0:50 ` Li Zefan
2010-12-23 18:12 kernel BUG Dipl.-Ing. Michael Niederle
2010-12-23 19:43 ` Chris Ball
2010-12-23 20:55   ` Michael Niederle
2010-12-24  0:19     ` Chris Ball
2010-12-24  0:32       ` Michael Niederle
2010-12-24  0:51         ` Chris Ball
2010-12-25  9:50           ` Michael Niederle
2010-12-25 11:46             ` Christian Thaeter
     [not found] <200907311139.55095.christoph.thielecke@gmx.de>
2009-07-31 16:01 ` kernel bug Linus Torvalds
2009-07-31 16:26   ` Eric Paris
     [not found] <150c16850812011409hf507ac6m5b168571ee6b453e@mail.gmail.com>
2008-12-02 21:06 ` Kernel BUG Justin Maggard
2008-12-02 23:38   ` Neil Brown
2008-12-11 21:23     ` Dan Williams
2008-09-10 20:35 kernel bug Todor Gyumyushev
2008-09-11  3:21 ` Aaron Straus
2008-04-13 16:06 monte
2008-04-13 18:20 ` Jesper Juhl
2008-04-13 18:33 ` Alan Cox
2007-09-19 21:43 Kernel bug Branislav Bozgai
2007-09-24 15:33 ` Mel Gorman
2007-08-19 18:33 kernel bug Costas Sismanis
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 11:59 ` Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2006-12-22 13:42   ` Peter Zijlstra
2006-12-22 23:46   ` Rudy Zijlstra
2005-11-26  1:23 Kernel bug Vympel
2005-11-27 12:51 ` Hugh Dickins
2005-11-03 18:10 Kernel BUG Mark Fortescue
2005-11-03 18:59 ` Trond Myklebust
2005-11-03 23:15   ` Mark Fortescue
2005-11-04 10:08   ` Mark Fortescue
2005-09-26  8:59 Haavard Bjerke
2005-04-07 21:26 kernel BUG christophe varoqui
2005-02-18 19:38 kernel bug Steve Felt
2004-07-06 15:06 Kernel BUG Teuling, Sieme
2004-07-06 20:21 ` Thomas Gleixner
2003-03-26 23:57 Perez-Gonzalez, Inaky
2003-03-27 14:23 ` Hugh Dickins
2003-03-26 13:13 kasper_k_jensen
2003-01-25 22:56 Kernel bug Massimiliano C. - Uf0On|in3
2003-01-19 18:01 Christophe Dupre
2003-01-07  9:17 kernel BUG Sönke Ruempler
2002-12-07 10:09 Kernel BUG Henrik Steffen
2002-12-08  1:47 ` Alan Cox
2002-11-27 11:31 kernel bug sanket rathi
2002-11-27 10:45 sanket rathi
2002-11-27  9:50 sanket rathi
2002-11-27 10:10 ` Arjan van de Ven
2002-06-28 19:54 kernel BUG Eric Weiss
2002-06-28 19:26 ew
2002-06-27 19:23 Chaoyang Deng
2002-06-28  5:58 ` Austin Gonyou
2002-06-28 14:00   ` Mike Black
2002-05-21 14:01 kernel bug Chen Hao
2001-11-25 18:03 Kernel Bug gonzalo.ab
2001-11-25 23:59 ` Adam Schrotenboer
2001-05-13 16:46 Kernel bug Tomas Jura
2001-05-13 17:12 ` Olaf Hering
2001-05-13 17:48   ` Tomas Jura
2001-05-14 15:27     ` Olaf Hering
2001-03-06 19:55 kernel bug ernte23

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=47EE063D.3050000@gmail.com \
    --to=olver.ramos@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 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.