Same type of "stuff" happening with 2.6.22-rc7. I've managed to narrow it down somewhat. The page corruption happens only when I've got the sound driver loaded: might be a DMA kind of thing that's killing me. Anyone got any ideas how I might narrow it down further? The sound modules loaded include ALSA's "snd_es18xx" with all the various OSS-compatibility modules. At the risk of making an inflammatory comment, I don't recall this kind of thing happening when I was using the equivalent OSS driver. N.B.: the ALSA driver only recently (in the past few months) became usable on the Alpha, and I made the switch to ALSA as soon as it was feasible to do so. I may try going back to the OSS driver (if it's still available) to see if the problem goes away. That would at least confirm my suspicions as to where the problem lies.
Original message excerpted below: >This happened on an Alpha computer (433au) running 2.6.22-rc6. The >error was triggered when I started up a NX KDE session, which I've >done successfully on all occasions prior to this one. In other words, >I wasn't doing anything out of the ordinary... >Bad page state in process 'gnome-terminal' >(...) >Bad page state in process 'syslogd' -- ----------------------------------------------------------------------- Bob Tracy | "Eagles may soar, but weasels don't get [EMAIL PROTECTED] | sucked into jet engines." --Anon ----------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
