I recently had a try at an old 2.0.30 that was still on my HD, and
found out that it works with 2.0.30, where it doesn't with 2.0.33.
It seems however that there were no changes to this driver between .30
and .33, so it must be the side-effect of some other change.
The main symptoms are:
* no problem with CD-ROMs, only with CD-As.
* when using eg. cdplay, the driver most of the time seems to loop
* setting DEBUG gives huge amounts of:
===
May 1 17:46:30 bylbo kernel: Entering handle_sony_cd_attention
May 1 17:46:30 bylbo kernel: Leaving handle_sony_cd_attention at 1018
===
with some variations though - it is sometimes leaving at 992.
That doesn't seem to be a hardware problem, as after booting under
2.0.30 I couldn't reproduce, and all went well.
Using IRQs or polled mode doesn't seem to change anything.
My HW is:
* cdu33a drive
* cd controler on GUS MAX, or on WDH-7001C card (no apparent difference)
* i486 ISA motherboard
Note that I also found out it was possible to rmmod the cdu31a module
before cdplay has exited (ie, when it is looping), and that causes a
kernel OOPS, as well as cdplay segfaulting.
-- Yann Dirson <ydirson@a2points.com> | Stop making M$-Bill richer & richer, alt-email: <dirson@univ-mlv.fr> | support Debian GNU/Linux: debian-email: <dirson@debian.org> | more powerful, more stable ! http://www.a2points.com/homepage/3475232 | Check <http://www.debian.org/>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu