public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: florin@iucha.net (Florin Iucha)
To: linux-kernel@vger.kernel.org
Cc: Dave Jones <davej@codemonkey.org.uk>
Subject: Re: Kernels since 2.5.60 upto 2.5.67 freeze when X server terminates
Date: Tue, 15 Apr 2003 13:20:57 -0500	[thread overview]
Message-ID: <20030415182057.GC29143@iucha.net> (raw)
In-Reply-To: <20030415164435.GA6389@rivenstone.net>

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

On Tue, Apr 15, 2003 at 12:44:40PM -0400, Joseph Fannin wrote:
> On Tue, Apr 15, 2003 at 03:06:37PM +0200, Alessandro Suardi wrote:
> <snip>
> > I surely hit bug 543 in 2.5.65 IIRC, and guess what...
> >  ATI Radeon 7500 Mobile - XFree 4.2.1
> > 
> > According to other emails on lkml, it appears that DRM and/or AGP
> >  new kernel code might be at fault. I don't actually remember
> >  seeing non-Radeon cards being hit by such problems though...
> 
>     I've seen this problem too many times, but haven't tried to track
> it down.  The video is ATI Rage 128 Pro.
> 
>     A common bit seems to be ATI cards, judging from this thread.  I'm
> also using the aty128fb framebuffer driver.  My motherboard is Aladdin V
> based and so uses the ali-agp module.

I think it has to do with the interaction between XFree86 4.3.0 and
the AGP code.

I have wdm as my display manager. I am able to login, but when logging
out the system dies. These are the last two messages printed on the
serial console:
   agpgart: Putting AGP V2 device at 00:00.0 into 4x mode
   agpgart: Putting AGP V2 device at 01:00.0 into 4x mode
and then, hard freeze.

These lines do not appear when using XFree86 4.2.1 .

I have a Radeon 8500 and AGP 4x is enabled in BIOS. The motherboard is
ECS K7S5A (SIS 735 chipset).

Dave, if you have any patch to test send it over!

florin

-- 

"NT is to UNIX what a doughnut is to a particle accelerator."

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-15 18:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 11:36 Kernels since 2.5.60 upto 2.5.67 freeze when X server terminates Petr Cisar
2003-04-15 12:03 ` Dave Gilbert (Home)
2003-04-15 12:20 ` Rudmer van Dijk
2003-04-15 12:55 ` Florin Iucha
2003-04-15 13:06   ` Alessandro Suardi
2003-04-15 16:44     ` Joseph Fannin
2003-04-15 18:20       ` Florin Iucha [this message]
2003-04-15 22:43         ` Andrew Morton
2003-04-16  0:45           ` Florin Iucha
2003-04-16  7:58             ` Dave Jones
2003-04-16  8:08               ` Andrew Morton
2003-04-16  8:10                 ` Dave Jones
2003-04-16 11:42             ` Alan Cox
2003-04-16 13:15               ` Florin Iucha
2003-04-16 13:58                 ` Dave Jones
2003-04-16 21:12                   ` Florin Iucha
2003-04-18 15:28                   ` Florin Iucha
2003-04-20  0:00                     ` Dave Jones
2003-04-16 14:28               ` Steven Cole
2003-04-16  4:41         ` Joseph Fannin
2003-04-16  6:09           ` Florin Iucha
2003-04-16  8:25           ` Valdis.Kletnieks
2003-04-16 12:10             ` Steven Cole
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 16:45 Sami Nieminen

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=20030415182057.GC29143@iucha.net \
    --to=florin@iucha.net \
    --cc=davej@codemonkey.org.uk \
    --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