From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 536] New: snd_ens1371 does not load anymore
Date: Thu, 03 Apr 2003 06:45:28 -0800 [thread overview]
Message-ID: <42120000.1049381128@[10.10.2.4]> (raw)
http://bugme.osdl.org/show_bug.cgi?id=536
Summary: snd_ens1371 does not load anymore
Kernel Version: 2.5.66
Status: NEW
Severity: high
Owner: bugme-janitors@lists.osdl.org
Submitter: ctron@dentrassi.de
Distribution: redhat-80-i386
Hardware Environment: Ensoniq ES1371 [AudioPCI-97] (rev 6).
Software Environment: linux-kernel, module
Problem Description: The snd_ens1371 module does not load although the card is
working under 2.4.19
Steps to reproduce:
insmod snd_ens1371
See the attachment of /var/log/messages!
Apr 1 08:54:21 segfault kernel: Badness in kobject_register at lib/kobject.c:152
Apr 1 08:54:21 segfault kernel: Call Trace:
Apr 1 08:54:21 segfault kernel: [<e0951c38>] driver+0x58/0xa0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<c024e718>] kobject_register+0x58/0x70
Apr 1 08:54:21 segfault kernel: [<e0951c28>] driver+0x48/0xa0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<c0275ca7>] bus_add_driver+0x57/0xf0
Apr 1 08:54:21 segfault kernel: [<e0951c28>] driver+0x48/0xa0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<e0951c80>] +0x0/0x4e0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<c0253bcd>] pci_register_driver+0x4d/0x60
Apr 1 08:54:21 segfault kernel: [<e0951c08>] driver+0x28/0xa0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<e08c501a>] +0x1a/0x5a [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<e0951be0>] driver+0x0/0xa0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<e0951c80>] +0x0/0x4e0 [snd_ens1371]
Apr 1 08:54:21 segfault kernel: [<c01378e1>] sys_init_module+0x171/0x260
Apr 1 08:54:21 segfault kernel: [<c010968f>] syscall_call+0x7/0xb
Apr 1 08:54:21 segfault kernel:
reply other threads:[~2003-04-03 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='42120000.1049381128@[10.10.2.4]' \
--to=mbligh@aracnet.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
all inboxes | Powered by JetHome®