From: Dave Airlie <airlied@gmail.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Jon Smirl <jonsmirl@gmail.com>,
Andreas Hartmann <andihartmann@01019freenet.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.10 dies when X uses G550
Date: Sun, 6 Feb 2005 21:10:04 +1100 [thread overview]
Message-ID: <21d7e9970502060210251815fb@mail.gmail.com> (raw)
In-Reply-To: <21d7e997050203215715f32c3@mail.gmail.com>
https://bugs.freedesktop.org/show_bug.cgi?id=2431
might have something to do with this...
Dave.
On Fri, 4 Feb 2005 16:57:50 +1100, Dave Airlie <airlied@gmail.com> wrote:
> > The logs with secondary radeon used to end like this:
> > (II) LoadModule: "int10"
> > (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
> > (II) RADEON(0): initializing int10
> > (**) RADEON(0): Option "InitPrimary" "on"
> > (II) Truncating PCI BIOS Length to 53248
> >
> > The logs for secondary G550 ends like this, with or without int10
> > (--) MGA(0): Pseudo-DMA transfer window at 0xF3000000
> > (==) MGA(0): BIOS at 0xC0000
> > (WW) MGA(0): Video BIOS info block not detected!
> > (II) MGA(0): MGABios.RamdacType = 0x0
> > (==) MGA(0): Write-combining range (0xf0000000,0x2000000)
> > (--) MGA(0): VideoRAM: 2048 kByte
> > (II) Loading sub module "ddc"
> > (II) LoadModule: "ddc"
> > (II) Reloading /usr/X11R6/lib/modules/libddc.a
> > (II) Loading sub module "i2c"
> > (II) LoadModule: "i2c"
> > (II) Loading /usr/X11R6/lib/modules/libi2c.a
> > (II) Module i2c: vendor="The XFree86 Project"
> > compiled for 4.3.0.1, module version = 1.2.0
> > ABI class: XFree86 Video Driver, version 0.6
> > (==) MGA(0): Write-combining range (0xf0000000,0x200000)
> > (II) MGA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
> > (II) MGA(0): I2C bus "DDC" initialized.
> > (II) MGA(0): I2C device "DDC:ddc2" registered at address 0xA0.
> > (II) MGA(0): I2C device "DDC:ddc2" removed.
> > (II) MGA(0): I2C Monitor info: (nil)
> > (II) MGA(0): end of I2C Monitor info
> >
> > The video bios is apparently not detected at all, and therefore not run.
> >
> > The kernel doesn't actually hang, only X gets stuck. sysrq+T
> > dumped stack traces for all tasks except the xserver. For X,
> > there was only one line identifying the xserver process and the fact
> > that it was Running. No stack dump. I managed to kill all tasks
> > and have init proceeding into init 2.
> >
> > So I wonder - is Debians X 4.3.0.1 buggy, or the kernel?
> > The fact remains that the newer kernels locks up while trying to use the
> > secondary radeon, while it actually works with 2.6.8.1.
>
> I've had some luck in reproducing this, however I've had to retask my
> test machine to find some hangs in my real life application (can run
> for 5 or 6 days without crashing :-), so I might get back to looking
> for this at some stage but when is anybodys guess, all I did was take
> a Radeon AGP card, and a PCI SiS crappy card and ran X on 2.6.10 and
> it hung....
>
> Dave.
>
next prev parent reply other threads:[~2005-02-06 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ks44mbo.ljgao4@ifi.uio.no>
[not found] ` <fa.hinb9iv.s38127@ifi.uio.no>
2005-01-22 9:40 ` 2.6.10 dies when X uses PCI radeon 9200 SE, binary search result Andreas Hartmann
2005-01-22 13:01 ` Dave Airlie
2005-01-26 10:05 ` 2.6.10 dies when X uses PCI radeon 9200 SE, further " Helge Hafting
2005-01-30 11:16 ` Helge Hafting
2005-01-30 11:22 ` Dave Airlie
2005-01-30 14:43 ` Jon Smirl
2005-01-30 15:05 ` Jon Smirl
2005-01-30 16:32 ` Helge Hafting
2005-01-30 17:05 ` Jon Smirl
2005-01-30 21:56 ` Helge Hafting
2005-02-04 3:43 ` 2.6.10 dies when X uses G550 Helge Hafting
2005-02-04 4:47 ` Jon Smirl
2005-02-04 5:57 ` Dave Airlie
2005-02-06 10:10 ` Dave Airlie [this message]
2005-01-30 15:07 ` 2.6.10 dies when X uses PCI radeon 9200 SE, further binary search result Jon Smirl
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=21d7e9970502060210251815fb@mail.gmail.com \
--to=airlied@gmail.com \
--cc=andihartmann@01019freenet.de \
--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