public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Glenn Johnson <glennpj@charter.net>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-rc1-mm1 oops with X
Date: Mon, 26 Jan 2004 22:47:57 -0600	[thread overview]
Message-ID: <20040127044757.GA5400@gforce.johnson.home> (raw)
In-Reply-To: <20040127040446.GA2445@srv-lnx2600.matchmail.com>

On Mon, Jan 26, 2004 at 08:04:46PM -0800, Mike Fedyk wrote:

> On Fri, Jan 23, 2004 at 10:33:27PM -0600, Glenn Johnson wrote:
>
> > On Fri, Jan 23, 2004 at 01:56:24PM -0800, Mike Fedyk wrote:
> >
> > > How far does it get through, and at what point in X startup does
> > > the kernel oops?
> >
> > I would say fairly early on but I do not know how to quantify that.
>
> Post your log file, and show where in the log the oops occours...

Okay, below is the XFree log file.  It is truncated at the point where
the oops occurs.  I sent an e-mail to Andrew confirming that backing out
sysfs-class-10-vc.patch fixes the problem for me.

---begin X log for kernel oops---

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.1-mm5 i686 [ELF] 
Build Date: 20 January 2004
	Before reporting problems, check http://www.XFree86.Org/
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jan 26 22:33:10 2004
(==) Using config file: "/etc/X11/XF86Config"
(==) ServerLayout "XFree86 Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to "unix/:-1"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(**) ModulePath set to "/usr/X11R6/lib/modules"
(++) using VT number 8

---end X log for kernel oops

The VT number it tries to use jumps around.  Sometimes it is VT10, VT11,
etc.  It should be using VT7 however.

Cheers,

Glenn

      reply	other threads:[~2004-01-27  6:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  6:19 2.6.2-rc1-mm1 oops with X Glenn Johnson
2004-01-23  7:18 ` Andrew Morton
2004-01-23  9:03   ` David Woodhouse
2004-01-23  9:11     ` Andrew Morton
2004-01-23  9:36       ` David Woodhouse
2004-01-23  9:44         ` Andrew Morton
2004-01-23 16:42           ` Glenn Johnson
2004-01-23 17:05           ` Glenn Johnson
2004-01-23 21:56             ` Mike Fedyk
2004-01-24  4:33               ` Glenn Johnson
2004-01-27  4:04                 ` Mike Fedyk
2004-01-27  4:47                   ` Glenn Johnson [this message]

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=20040127044757.GA5400@gforce.johnson.home \
    --to=glennpj@charter.net \
    --cc=akpm@osdl.org \
    --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