mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: corbet@lwn.net (Jonathan Corbet)
Cc: ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: [MICROPATCH] Make x86_64 build work without GART_IOMMU
Date: Fri, 30 Apr 2004 15:08:28 -0700	[thread overview]
Message-ID: <20040430150828.1594ad6a.akpm@osdl.org> (raw)
In-Reply-To: <20040430214040.25268.qmail@lwn.net>

corbet@lwn.net (Jonathan Corbet) wrote:
>
> > > My Radeon 9200SE goes nuts if I build a GART-enabled
> > > kernel.  Haven't figured out why...
> > 
> > Define 'nuts' and supply full boot log (with GART enabled)
> 
> Oops, sorry for the technical term...:)

"No User Time Scheduled".  Silly Andi.

> Andrew asked for a profile to help track down where the kernel loop is.  I
> just did one, but the results are less than illuminating:
> 
> 	105219 total                                      0.0448
> 	 85232 __delay                                  2663.5000
> 	 14076 default_idle                             293.2500
> 	  4679 __do_softirq                              26.5852
> 	   474 check_poison_obj                           1.0216
> 	   197 handle_IRQ_event                           2.0521
> 	    91 kmem_cache_free                            0.1034

Yup, that's the one.  There are various loops where the driver spins on a
hardware register, with an mdelay() in the loop.

Can you get a sysrq-p trace?



  parent reply	other threads:[~2004-04-30 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1QMlc-5kS-39@gated-at.bofh.it>
2004-04-30 21:00 ` Andi Kleen
2004-04-30 21:40   ` Jonathan Corbet
2004-04-30 22:07     ` Andi Kleen
2004-05-03 15:09       ` Jonathan Corbet
2004-05-03 16:23         ` Roland Dreier
2004-05-03 16:33         ` Andi Kleen
2004-04-30 22:08     ` Andrew Morton [this message]
2004-04-30 19:57 Jonathan Corbet

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=20040430150828.1594ad6a.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@muc.de \
    --cc=corbet@lwn.net \
    --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

all inboxes | Powered by JetHome®