From: Zoltan Boszormenyi <zboszor@dunaweb.hu>
To: linux-kernel@vger.kernel.org
Subject: Oops in au8830 driver on x86-64
Date: Thu, 11 May 2006 01:05:42 +0200 [thread overview]
Message-ID: <446271C6.9050509@dunaweb.hu> (raw)
Hi,
I bought a used sound card for secondary uses, it happens to be
a Diamond Sound Monster MX300 with an Aureal Vortex2 chip.
Unfortunately, after putting it into the machine, it doesn't boot up,
I get an oops that prevents booting further. I have hand-copied
the relevant info:
RIP: {:snd_au8830:snd_vortex_probe+411}
...
Call Trace: {sprintf+81} {__wake_up+56}
{pci_device_probe+256} {driver_probe_device+82}
{__driver_attach+142} {__driver_attach+0}
{bus_for_each_dev+67} {bus_add_driver+118}
{__pci_register_driver+142} {stop_machine_run+58}
{sys_init_module+278} {system_call+126}
The kernel is not tainted.
$ uname -a
Linux xxxxxx 2.6.16-1.2111_FC5 #1 SMP Thu May 4 21:16:04 EDT 2006 x86_64
x86_64 x86_64 GNU/Linux
System is an FC5/x86-64 updated to the latest erratas.
There is only one sprintf() call in the whole au88x0 driver source,
line 328 in au88x0.c. Why it fails for x86-64 is beyond my understanding.
This is the code in question:
327: strcpy(card->shortname, CARD_NAME_SHORT);
328: sprintf(card->longname, "%s at 0x%lx irq %i",
card->shortname, chip->io, chip->irq);
Pointer "card" exists or the driver would have failed earlier allocating
or dereferencing it.
card->longname is 80 byte large, length of the string is at most 44 byte:
12 byte (format string fillings + terminating NULL) +
6 byte (CARD_NAME_SHORT) +
6 byte (unsigned long written in hex) +
10 byte (unsigned int written in dec)
I couldn't seek further, I put the card away for now. :-)
Best regards,
Zoltán Böszörményi
next reply other threads:[~2006-05-10 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 23:05 Zoltan Boszormenyi [this message]
2006-05-10 23:07 ` Oops in au8830 driver on x86-64 Zoltan Boszormenyi
2006-05-11 18:35 ` Andi Kleen
2006-05-11 19:23 ` Zoltan Boszormenyi
2006-05-11 19:24 ` Andi Kleen
2006-05-11 19:46 ` Zoltan Boszormenyi
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=446271C6.9050509@dunaweb.hu \
--to=zboszor@dunaweb.hu \
--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.