From: "Florian D." <flockmock@gmx.at>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: how to track down strange bug
Date: Thu, 19 Oct 2006 11:37:06 +0200 [thread overview]
Message-ID: <45374742.4010604@gmx.at> (raw)
In-Reply-To: <eh6h7m$vi0$1@sea.gmane.org>
Duncan wrote:
> So make sure you have the right one running, and aren't loading a bunch of
> others, and that DMA is active (merge hdparm and read the manpage).
that is already the case.
>
> The problem in this case would be slow non-DMA I/O interfering with video
> DMA as well.
>
> The problem could also be a non-optimally configured xorg or extensions,
> or selecting a type of video transfer that your particular video hardware
> and xorg driver don't support.
hmm.. NVIDIA card with nv driver, but I'll have a look.
>
> Finally, flaky memory, overclocking and/or overheating, or an unstable
> power supply chain (from the wall outlet thru the UPS if you have one,
> thru the PSU) can do it. Of course, these are likely to show up in other
> areas as well, such as when merging on Gentoo.
my hardware should be ok. thank you for your commentary, but I think
it is a kernel issue. perhaps I can find one, which does not show the
issue and then start a bisect or something, or is there any other
method to track this down?
>
> I've had all those problems at one time or another.
would be boring without it, no? ;)
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-19 9:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 22:30 [gentoo-amd64] how to track down strange bug Florian D.
2006-10-18 23:46 ` Peter Davoust
2006-10-19 0:35 ` [gentoo-amd64] " Duncan
2006-10-19 9:37 ` Florian D. [this message]
2006-10-19 10:27 ` Rob Lesslie
2006-10-19 20:51 ` Duncan
2006-10-19 22:48 ` Neil Bothwick
2006-10-20 10:41 ` Duncan
2006-10-20 11:09 ` Neil Bothwick
2006-10-20 11:39 ` Duncan
2006-10-20 15:02 ` Paul de Vrieze
2006-10-20 15:11 ` Rob Lesslie
2006-10-20 15:25 ` Neil Bothwick
2006-10-20 14:58 ` [gentoo-amd64] " Paul de Vrieze
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=45374742.4010604@gmx.at \
--to=flockmock@gmx.at \
--cc=gentoo-amd64@lists.gentoo.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