All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Allan Duncan <allan.d@bigpond.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	faith@valinux.com
Subject: Re: Linux 2.4.20-pre4 blows away Xwindows with Matrox G400 and DRM
Date: Fri, 30 Aug 2002 19:54:00 -0700	[thread overview]
Message-ID: <20020831025400.GA457@matchmail.com> (raw)
In-Reply-To: <3D677F5B.7AD0D472@bigpond.com>

On Sat, Aug 24, 2002 at 10:43:07PM +1000, Allan Duncan wrote:
> I have done some more digging, including the same kernel on a second host.
> The second box has a K6, VIA MVP3 chipset, and a G200 with 8M, otherwise
> the software versions are the same.  It works fine.  Taking the .config
> used for that, I redid the kernel on the AthlonXP / VIA KT266a / G400,
> almost instant reboot.
> 
> 
> One of the crashes was a touch later, and the last few lines from
> /var/log/messages was:
> Aug 21 20:46:32 localhost login(pam_unix)[1063]: session opened for user alland by LOGIN(uid=0)
> Aug 21 20:46:32 localhost  -- alland[1063]: LOGIN ON tty1 BY alland
> Aug 21 20:50:22 localhost modprobe: modprobe: Can't locate module char-major-226
> Aug 21 20:50:22 localhost modprobe: modprobe: Can't locate module char-major-226
> Aug 21 20:50:22 localhost kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
> Aug 21 20:50:22 localhost kernel: agpgart: Maximum main memory to use for agp memory: 439M
> Aug 21 20:50:22 localhost kernel: agpgart: Detected Via Apollo Pro KT266 chipset
> Aug 21 20:50:22 localhost kernel: agpgart: AGP aperture is 128M @ 0xd0000000
> Aug 21 20:50:22 localhost kernel: [drm] AGP 0.99 on VIA Apollo KT133 @ 0xd0000000 128MB
> Aug 21 20:50:22 localhost kernel: [drm] Initialized mga 3.0.2 20010321 on minor 0
> Aug 21 20:57:29 localhost syslogd 1.4.1: restart.
> 
> The "char-major-226" corresponds to the /dev/dri/card0 above, and the failure point
> seems to be when the drmOpenDevice succeeds on the third attempt.
> 
> I tried unsetting CONFIG_DRM, but it still fails.

I have seen something similar on 2.4.19-pre8-aa3, but I haven't tried to
debug the setup.  I did a hardware reset (software reset would just reboot
after X started again) and was able to avoid the problem.  A few days later
I upgraded it to 2.4.19.  I haven't seen the problem since then, but it has
only been a few days.

00:00.0 Host bridge: Intel Corp. 82820 820 (Camino) Chipset Host Bridge
(MCH) (rev 03)
00:01.0 PCI bridge: Intel Corp. 82820 820 (Camino) Chipset PCI to AGP Bridge
(rev 03)
00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02)
00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02)
00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation Riva TnT2 [NV5] (rev 11)

Mike

      reply	other threads:[~2002-08-31  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 10:37 Linux 2.4.20-pre4 blows away Xwindows with Matrox G400 and DRM Allan Duncan
2002-08-20 12:42 ` Alan Cox
2002-08-20 21:46   ` Allan Duncan
2002-08-24 12:43 ` Allan Duncan
2002-08-31  2:54   ` Mike Fedyk [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=20020831025400.GA457@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=allan.d@bigpond.com \
    --cc=faith@valinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.