public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Valette <eric.valette@free.fr>
To: flamingice@sourmilk.net, andreamrl@tiscali.it
Cc: linux-kernel@vger.kernel.org
Subject: rtl8187 driver in 2.6.23-rc6-git5: kernel panic if not used as a module. Works as a module.
Date: Sat, 15 Sep 2007 16:07:08 +0200	[thread overview]
Message-ID: <46EBE70C.2040201@free.fr> (raw)

First let me start by a thanks: it was the last piece of my P5W de luxe
machine based that has not its driver from stock kernel.

It works like a charm when used as a module:

lsusb
Bus 005 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 0bda:8187 Realtek Semiconductor Corp.  <=========
Bus 001 Device 005: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB
2.0 Hub
Bus 001 Device 004: ID 03f0:c202 Hewlett-Packard
Bus 001 Device 006: ID 058f:6362 Alcor Micro Corp. Hi-Speed Internal
Multi-Card Reader/Writer
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 003: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB
2.0 Hub
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB
2.0 Hub


wlan0     IEEE 802.11g  ESSID:"xxxxxxxx"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:18:E7:15:2B:2A
          Bit Rate=11 Mb/s
          Retry min limit:7   RTS thr:off   Fragment thr=2346 B
          Encryption key:xxxxxxxxx
          Link Quality=43/64  Signal level=39/65
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


wlan0     Lien encap:Ethernet  HWaddr 00:15:AF:0A:BE:A9
          inet adr:192.168.1.11  Bcast:192.168.1.255  Masque:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:637 errors:0 dropped:0 overruns:0 frame:0
          TX packets:562 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:373558 (364.8 KiB)  TX bytes:88216 (86.1 KiB)


However, when I compile it directly inside the kernel, I get a panic
with a backtrace at usb initilialisation. The backtrace points to
registering things in /proc (make-directory or something)!

I can probably take a picture of the backtrace if you want.

Config: Asus P5W de luxe, Intel(R) Core(TM)2 CPU 6600  @ 2.40GHz, pure
64 bits install.

-- eric


             reply	other threads:[~2007-09-15 14:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 14:07 Eric Valette [this message]
2007-09-15 14:27 ` rtl8187 driver in 2.6.23-rc6-git5: kernel panic if not used as a module. Works as a module Eric Valette
2007-09-15 15:38   ` Paul Rolland
2007-09-15 16:28   ` Rob Hussey
2007-09-15 17:41     ` Paul Rolland
2007-09-15 18:30     ` Eric Valette
2007-09-15 18:51       ` Paul Rolland
2007-09-15 19:00         ` Eric Valette
2007-09-17  9:48           ` Johannes Berg
2007-09-17 11:44             ` Eric Valette
2007-09-15 21:19         ` Rob Hussey
2007-09-25  8:05           ` Eric Valette

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=46EBE70C.2040201@free.fr \
    --to=eric.valette@free.fr \
    --cc=andreamrl@tiscali.it \
    --cc=flamingice@sourmilk.net \
    --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