From: Geert Uytterhoeven <geert@thomas.kotnet.org>
To: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Crash when early load of cs4236 module
Date: Wed, 13 Jan 1999 23:15:04 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.05.9901132310180.341-100000@callisto.thomas.kotnet.org> (raw)
To make my sound module load automatically at boot time, I put
cs4232 io=0x530 irq=5 dma=1 dma2=5
in /etc/modules (I'm using Debian `sid' on a CHRP box with cs4236 sound).
This works fine, except that I get a kernel crash later when the boot
scripts are initializing the network daemons:
NIP: cc831bb0
bad access address: 0000ac44
backtrace: cc8319b0 ???
cc8303dc ???
c003438c (c0034154 T sys_ioctl)
c0003898 (c0003898 T syscall_ret_1)
<garbage>
It happens in both 2.2.0pre6 and 2.2.0pre4 and is reproducible (I hate
file system checks on 2 GB partitions on slow disks :-(.
If I remove the cs4232 line from /etc/modules again and load the module by
hand later
modprobe cs4232 io=0x530 irq=5 dma=1 dma2=5
I have no problems at all. Really weird...
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be
Linux/m68k on Amiga, Wavelets http://www.cs.kuleuven.ac.be/~geert/
KotNET@Thomas Network Administration -- Make you bed part of Cyberspace!!
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-01-13 22:15 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=Pine.LNX.4.05.9901132310180.341-100000@callisto.thomas.kotnet.org \
--to=geert@thomas.kotnet.org \
--cc=linuxppc-dev@lists.linuxppc.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.