linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: 2.5.69-mm1
Date: 06 May 2003 08:33:10 -0600	[thread overview]
Message-ID: <1052231590.2166.141.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <20030504231650.75881288.akpm@digeo.com>

On Mon, 2003-05-05 at 00:16, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69-mm1/
> 
> Various random fixups, cleanps and speedups.  Mainly a resync to 2.5.69.
> 
I have one machine for testing which is running X, and a kexec reboot
glitches the video system when initiated from runlevel 5.  Kexec works fine
from runlevel 3.

I was not able to test this until now, due to the "crash on leaving X"
bug which has been fixed in 2.5.69.

The symptoms are a blank screen for the 35 seconds that it takes this
box to do a kexec boot following do-kexec.sh /boot/vmlinuz-2.5.69-mm1
Then, if I had "id:3:initdefault:" in /etc/inittab, I just get a blank screen
at the console, but I can ssh into the box since it does come up fine otherwise.
If I had runlevel 5 instead in the above, then X starts OK (after a blank screen
startup) and all is well.

[steven@spc1 steven]$ /sbin/lspci
00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03)
00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC [Chipset Graphics Controller] (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:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)

snippet from dmesg:

Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel i810 E Chipset.
agpgart: Maximum main memory to use for agp memory: 202M
agpgart: detected 4MB dedicated video ram.
agpgart: AGP aperture is 64M @ 0xf8000000
[drm] Initialized i810 1.2.1 20020211 on minor 0

Steven



  parent reply	other threads:[~2003-05-06 14:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05  6:16 2.5.69-mm1 Andrew Morton
2003-05-05 15:32 ` 2.5.69-mm1 Andrei Ivanov
2003-05-05 16:45   ` 2.5.69-mm1 Greg KH
2003-05-06  9:49     ` 2.5.69-mm1 Andrei Ivanov
2003-05-05 18:44   ` 2.5.69-mm1 Andrew Morton
2003-05-05 21:01 ` 2.5.69-mm1 William Lee Irwin III
2003-05-06 11:09   ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 12:02     ` 2.5.69-mm1 David S. Miller
2003-05-06 15:25       ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 14:20         ` 2.5.69-mm1 David S. Miller
2003-05-06 15:47           ` 2.5.69-mm1 Dipankar Sarma
2003-05-05 21:02 ` 2.5.69-mm1 William Lee Irwin III
2003-05-06 14:33 ` Steven Cole [this message]
2003-05-06 15:33   ` 2.5.69-mm1 Andrew Morton
2003-05-06 15:36     ` 2.5.69-mm1 Eric W. Biederman
2003-05-06 16:35       ` 2.5.69-mm1 Steven Cole

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=1052231590.2166.141.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=akpm@digeo.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --subject='Re: 2.5.69-mm1' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).