mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John covici <covici@ccs.covici.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Dave Airlie <airlied@gmail.com>, Jon Smirl <jonsmirl@gmail.com>,
	covici@ccs.covici.com,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result
Date: Fri, 21 Jan 2005 13:49:58 -0500	[thread overview]
Message-ID: <16881.20182.831343.763236@ccs.covici.com> (raw)
In-Reply-To: <20050121182656.GA24167@hh.idb.hist.no>

Makes sense to me -- I went from 6.8 to 6.9rc2 and that is I think
when my X died.  Now mine is an APG not PCI, but it may be related.
 
on Friday 01/21/2005 Helge Hafting(helgehaf@aitel.hist.no) wrote
 > On Sun, Jan 16, 2005 at 10:41:23PM +1100, Dave Airlie wrote:
 > > > 
 > > > I'm fine with adding this code, but we still don't know if this is the
 > > > cause of his problem. The debug output can determine if this really is
 > > > the source of the problem or if it is somewhere else.
 > > > 
 > > 
 > > I actually doubt it is this stuff.. my guess is that it is something
 > > nasty like ACPI breaking int10 for X or something like that... it
 > > seems a lot more subtle than the usually things that break when we
 > > mess with the DRM :-)
 > > 
 > The search was a short one.  
 > 2.6.9-rc1 works fine, just like 2.6.8.1
 > 2.6.9-rc2 crashes.  I didn't find any kernel revisions between those two.
 > 
 > It is interesting to note that the 2.6.9 crash was a bit different.
 > X got a bit further according to the log.
 > During the test, everything stopped, but the machine wasn't completely
 > dead like it usually is.  Numlock actually toggled the LED, but the screen was 
 > black and I could not break out of X with ctrl+alt+backspace. So I tried to 
 > switch consoles, and the kernel died a bit more.  No more numlock LED
 > toggling, but sysrq+S+U+B actually worked.  The discs synced and
 > the thing booted.  Hm, perhaps  X always got a bit further, but
 > now the disc sync preserved more of the log?
 > 
 > Here is how it ended (I have all of it if necessary):
 > 
 > (==) RADEON(0): Write-combining range (0xe0000000,0x8000000)
 > (II) RADEON(0): Wrote: rd=12, fd=120, pd=1
 > drmOpenDevice: minor is 0
 > drmOpenDevice: node name is /dev/dri/card0
 > drmOpenDevice: open result is -1, (Unknown error 999)
 > drmOpenDevice: open result is -1, (Unknown error 999)
 > drmOpenDevice: Open failed
 > drmOpenDevice: minor is 0
 > drmOpenDevice: node name is /dev/dri/card0
 > drmOpenDevice: open result is -1, (Unknown error 999)
 > drmOpenDevice: open result is -1, (Unknown error 999)
 > drmOpenDevice: Open failed
 > drmOpenDevice: minor is 0
 > drmOpenDevice: node name is /dev/dri/card0
 > drmOpenDevice: open result is 6, (OK)
 > drmGetBusid returned ''
 > (II) RADEON(0): [drm] loaded kernel module for "radeon" driver
 > (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:0:8:0"
 > (II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0920000
 > (II) RADEON(0): [drm] mapped SAREA 0xe0920000 to 0xafd8c000
 > (II) RADEON(0): [drm] framebuffer handle = 0xe0000000
 > (II) RADEON(0): [drm] added 1 reserved context for kernel
 > (II) RADEON(0): [pci] 8192 kB allocated with handle 0xe097d000
 > (II) RADEON(0): [pci] ring handle = 0xe097d000
 > (II) RADEON(0): [pci] Ring mapped at 0xafc8b000
 > (II) RADEON(0): [pci] Ring contents 0x00000000
 > (II) RADEON(0): [pci] ring read ptr handle = 0xe0a7e000
 > (II) RADEON(0): [pci] Ring read ptr mapped at 0xafc8a000
 > (II) RADEON(0): [pci] Ring read ptr contents 0x00000000
 > (II) RADEON(0): [pci] vertex/indirect buffers handle = 0xe0a7f000
 > (II) RADEON(0): [pci] Vertex/indirect buffers mapped at 0xafa8a000
 > (II) RADEON(0): [pci] Vertex/indirect buffers contents 0x00000000
 > (II) RADEON(0): [pci] GART texture map handle = 0xe0c7f000
 > (II) RADEON(0): [pci] GART Texture map mapped at 0xaf5aa000
 > (II) RADEON(0): [drm] register handle = 0xf6000000
 > (II) RADEON(0): [dri] Visual configs initialized
 > (II) RADEON(0): CP in BM mode
 > (II) RADEON(0): Using 8 MB GART aperture
 > (II) RADEON(0): Using 1 MB for the ring buffer
 > (II) RADEON(0): Using 2 MB for vertex/indirect buffers
 > (II) RADEON(0): Using 5 MB for GART textures
 > (II) RADEON(0): Memory manager initialized to (0,0) (1280,8191)
 > (II) RADEON(0): Reserved area from (0,1024) to (1280,1026)
 > (II) RADEON(0): Largest offscreen area available: 1280 x 7165
 > (II) RADEON(0): Will use back buffer at offset 0x1400000
 > (II) RADEON(0): Will use depth buffer at offset 0x1900000
 > (II) RADEON(0): Will use 100352 kb for textures at offset 0x1e00000
 > (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
 >         Screen to screen bit blits
 >         Solid filled rectangles
 >         8x8 mono pattern filled rectangles
 >         Indirect CPU to Screen color expansion
 >         Solid Lines
 >         Scanline Image Writes
 >         Offscreen Pixmaps
 >         Setting up tile and stipple cache:
 >                 32 128x128 slots
 >                 32 256x256 slots
 >                 16 512x512 slots
 > (II) RADEON(0): Acceleration enabled
 > (==) RADEON(0): Backing store disabled
 > (==) RADEON(0): Silken mouse enabled
 > (II) RADEON(0): Using hardware cursor (scanline 1026)
 > (II) RADEON(0): Largest offscreen area available: 1280 x 7161
 > (**) Option "dpms"
 > (**) RADEON(0): DPMS enabled
 > (WW) RADEON(0): Option "DynamicClocks" is not used
 > (II) RADEON(0): X context handle = 0x00000001
 > (II) RADEON(0): [drm] installed DRM signal handler
 > (II) RADEON(0): [DRI] installation complete
 > (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
 > 
 > 
 > I hope this can be of help,
 > Helge Hafting
 > -
 > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
 > the body of a message to majordomo@vger.kernel.org
 > More majordomo info at  http://vger.kernel.org/majordomo-info.html
 > Please read the FAQ at  http://www.tux.org/lkml/

-- 
Your life is like a penny -- how are you going to spend it?

         John Covici
         covici@ccs.covici.com

  reply	other threads:[~2005-01-21 18:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 10:30 2.6.10 dies when X tries to initialize PCI radeon 9200 SE Helge Hafting
2005-01-13 11:00 ` John covici
2005-01-13 21:06   ` Dave Airlie
2005-01-15 18:57     ` Helge Hafting
2005-01-16 10:08       ` Dave Airlie
2005-01-16 10:33         ` Jon Smirl
2005-01-16 10:37           ` Dave Airlie
2005-01-16 10:35         ` Jon Smirl
2005-01-16 10:50         ` Helge Hafting
2005-01-16 11:04           ` Jon Smirl
2005-01-16 11:07             ` Dave Airlie
2005-01-16 11:34               ` Jon Smirl
2005-01-16 11:41                 ` Dave Airlie
2005-01-21 18:26                   ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Helge Hafting
2005-01-21 18:49                     ` John covici [this message]
2005-01-16 12:26                 ` 2.6.10 dies when X tries to initialize PCI radeon 9200 SE John covici
2005-01-16 12:18             ` Helge Hafting
2005-01-16 20:25               ` Mike Houston
2005-01-16 22:08               ` Jon Smirl
2005-01-16 22:24                 ` Helge Hafting
2005-01-17 17:19                 ` Helge Hafting
2005-01-14  2:20   ` David Lang
2005-01-14 10:35     ` Helge Hafting
2005-01-14 12:41       ` John covici
2005-01-15  8:23         ` Dave Airlie
     [not found] <fa.jfkohta.1il0fq0@ifi.uio.no>
     [not found] ` <fa.hh8592m.qji2ie@ifi.uio.no>
2005-01-21 20:05   ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Andreas Hartmann
2005-01-21 22:09     ` Helge Hafting
     [not found] <fa.ks44mbo.ljgao4@ifi.uio.no>
     [not found] ` <fa.hinb9iv.s38127@ifi.uio.no>
2005-01-22  9:40   ` Andreas Hartmann
2005-01-22 13:01     ` Dave Airlie

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=16881.20182.831343.763236@ccs.covici.com \
    --to=covici@ccs.covici.com \
    --cc=airlied@gmail.com \
    --cc=helgehaf@aitel.hist.no \
    --cc=jonsmirl@gmail.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

Powered by JetHome