mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob Tracy)
To: linux-kernel@vger.kernel.org
Subject: 2.6.22-rc6 bad page error (followup)
Date: Fri, 6 Jul 2007 16:29:10 -0500 (CDT)	[thread overview]
Message-ID: <20070706212910.BEAA8DBA1@gherkin.frus.com> (raw)

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
rct@frus.com            |  sucked into jet engines."       --Anon
-----------------------------------------------------------------------

                 reply	other threads:[~2007-07-06 21:29 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=20070706212910.BEAA8DBA1@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®