More insight into GUS problems

Andrew J. Anderson (andrew@db.erau.edu)
Sat, 28 Mar 1998 01:19:29 -0500 (EST)

I am able to reproduce an oops if I build the GUS drivers with support for
the GUS MAX. After loading the ad1848 module, it will oops when loading
the GUS module. The panic occurs inside gus.o, which loads parially, but
no symbols are loaded into /proc/ksyms to trace it. What is the best way
to trace a panic in a module?

If I build the GUS drivers without support for the MAX, it does not load
the ad1848 module, and does not cause a panic.

Also, the memory detection for the Interwave isn't quite right -- it won't
detect more than 256k. I'm working on comparing the Linux UltraSound
Project's memory detection code with the OSS code to see why one can see
all of the memory and the other can't.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Andrew Anderson http://amelia.db.erau.edu/~andrew/
if(!(family_tree=fork())){redneck=TRUE;}

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu