From: Marcel Holtmann <marcel@holtmann.org>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel D945GNT crashes with AGP enabled
Date: Sat, 29 Oct 2005 13:27:47 +0200 [thread overview]
Message-ID: <1130585267.5360.12.camel@blade> (raw)
In-Reply-To: <1130518160.5372.6.camel@blade>
Hi Dave,
> > > The problematic part is the Intel AGP module (intel_agp), because if I
> > > don't compile it the system works fine. There is an oops coming, but so
> > > far I wasn't able to get it out. Does anyone have seen this problem
> > > before and have some patches for me to try? Otherwise I need to try to
> > > get this oops message.
> >
> > You never mentioned what kernel you're running.
> > If it's a recent -mm, there's an AGP optimisation patch to do less
> > frequent TLB flushes, which may be worth backing out.
> >
> > If you're running mainline, I'm puzzled.
>
> basically I am running mainline, but I also tried your agpgart tree and
> both are having problems.
I also checked a non-SMP and non-preempt kernel. Both make my system
crash when killing the X server.
> > It'd be useful to see that oops.
>
> I am working on it and actually it is enough to just kill the X process
> to crash the system. I saw parts of the oops and it seems that there are
> some RCU calls in the backtrace, but this might not help at all. So it
> seems that I really need that oops.
So getting the oops is really hard. I can't get it via serial port and
the netconsole (it uses an e100) is also not working. I tried to run
framebuffer, but I can only use vesafb and the resolution is nothing
better than any text console and I wasn't able to change it. So taking a
picture of the oops is also not an option. What other possible ways I
have to finally get the oops out of the system?
And btw why can't I compile the intelfb on x86_64? I use the internal
graphics card (8086:2772) of the D945GNT motherboard.
0000:00:02.0 VGA compatible controller: Intel Corporation 945G Integrated Graphics Controller (rev 02)
The Kconfig file makes it unselectable on x86_64 system.
config FB_INTEL
tristate "Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)"
depends on FB && EXPERIMENTAL && PCI && X86 && !X86_64
It seems that the most recent support in this driver is for the 915G and
not for the 945G. Are they so different that we need a complete new
driver or is the !X86_64 a relict from old times?
Regards
Marcel
next prev parent reply other threads:[~2005-10-29 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 13:38 Intel D945GNT crashes with AGP enabled Marcel Holtmann
2005-10-28 14:52 ` Alejandro Bonilla
2005-10-28 16:28 ` Dave Jones
2005-10-28 16:49 ` Marcel Holtmann
2005-10-29 11:27 ` Marcel Holtmann [this message]
2005-10-29 12:27 ` Marcel Holtmann
2005-10-29 13:44 ` Alan Hourihane
2005-10-29 13:55 ` Marcel Holtmann
2005-10-29 14:49 ` Alan Hourihane
2005-10-29 14:56 ` Marcel Holtmann
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=1130585267.5360.12.camel@blade \
--to=marcel@holtmann.org \
--cc=davej@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.