I've now upgraded to 2.6.14-rc1 and can still trigger the oops. But I found out that it is dependant on which modules are loaded.
(I rebooted w/o running make install_modules w/o an oops, but when I fixed that and rebooted again, I got the oops.) My autoloaded modules are: e100 uhci-hcd snd_maestro3 snd_mixer_oss snd_pcm_oss i8k plus thier dependancies. All of the dependencies are alsa; I beleive the full list of dependencies is: soundcore snd snd_seq_device snd_timer snd_seq snd_page_alloc snd_pcm snd_ac97_codec snd_rtctimer snd_seq_oss I have to go back and try each one at a time, but I wanted to get this out first. There has been an alsa merge since -rc1, so if it is alsa that triggers the difference I'll have to upgrade and test yet again.... But with all of those modules loaded the oops is reproducable, and w/o them it (so far) is not. Also, as long as I reboot right away and fsck, it seems that I can avoid any data loss. But if I let it run anything written (or perhaps anything written after the log gets full) is lost. (As an example I discovered only after the first two notes, mozilla lost its cookie permissions file, but other files that it updates were OK.) -JimC -- James H. Cloos, Jr. <[EMAIL PROTECTED]> ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
