From: "Rob Hussey" <robjhussey@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Kernel panic with rt2500pci built-in
Date: Wed, 5 Sep 2007 23:06:57 -0400 [thread overview]
Message-ID: <6b8cef970709052006q43d5602ewde0cea45500deede@mail.gmail.com> (raw)
I receive a kernel panic with rt2500pci built-in, but if built as a
module, I can insmod it without problem. I don't have a serial
console, and I tried to capture the panic with netconsole (using a
different interface of course) but the panic happens immediately after
rt2500pci is initialized, or in other words, too soon for netconsole.
I'd rather not copy over everything unless necessary. Here's the first portion:
ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 18
phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0201, rf: 0003,
rev: 00000004
WARNING: at lib/kref.c:33 kref_get()
[<c0229da9>] kref_get+0x3d/0x44
next reply other threads:[~2007-09-06 3:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 3:06 Rob Hussey [this message]
2007-09-06 3:25 ` Kernel panic with rt2500pci built-in Rob Hussey
2007-09-06 3:53 ` Rob Hussey
2007-09-06 12:12 ` Johannes Berg
2007-09-07 0:45 ` Johannes Berg
2007-09-07 19:31 ` Rob Hussey
2007-09-07 19:37 ` Johannes Berg
2007-09-07 21:38 ` Rob Hussey
2007-09-07 22:00 ` Johannes Berg
2007-09-08 4:29 ` Rob Hussey
2007-09-08 4:40 ` Rob Hussey
2007-09-08 7:49 ` Johannes Berg
2007-09-08 8:26 ` Rob Hussey
2007-09-08 9:36 ` Johannes Berg
2007-09-08 15:57 ` Rob Hussey
2007-09-08 16:16 ` Ivo van Doorn
2007-09-08 16:39 ` Rob Hussey
2007-09-08 17:18 ` Ivo van Doorn
2007-09-08 17:16 ` Rob Hussey
2007-09-08 17:39 ` Ivo van Doorn
2007-09-08 18:28 ` Rob Hussey
2007-09-10 10:31 ` Johannes Berg
2007-09-10 11:05 ` Johannes Berg
2007-09-10 20:40 ` Rob Hussey
2007-09-10 21:25 ` Rob Hussey
2007-09-11 10:17 ` Johannes Berg
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=6b8cef970709052006q43d5602ewde0cea45500deede@mail.gmail.com \
--to=robjhussey@gmail.com \
--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).