From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S263195AbVG3XsY@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S263195AbVG3XsY (ORCPT <rfc822;willy@w.ods.org>);
	Sat, 30 Jul 2005 19:48:24 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263196AbVG3XsY
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sat, 30 Jul 2005 19:48:24 -0400
Received: from mustang.oldcity.dca.net ([216.158.38.3]:39623 "HELO
	mustang.oldcity.dca.net") by vger.kernel.org with SMTP
	id S263195AbVG3XsN (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 30 Jul 2005 19:48:13 -0400
Subject: Simple question re: oops
From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Content-Type: text/plain
Date: Sat, 30 Jul 2005 19:48:11 -0400
Message-Id: <1122767292.4464.1.camel@mindpipe>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.0 
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with "Aieee, killing interrupt handler".

How do I get the output to stop after the first Oops?

Lee