From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc5 bad page with fglrx on Radeon X300
Date: Sat, 10 Dec 2005 16:23:43 -0500 [thread overview]
Message-ID: <439B475F.2050901@ens-lyon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0512032155290.3099@g5.osdl.org>
Linus Torvalds wrote:
>There's a rc5 out there now, largely because I'm going to be out of email
>contact for the next week, and while I wish people were religiously
>testing all the nightly snapshots, the fact is, you guys don't.
>
>So making the current state available as an -rc makes sense, even though
>not a lot has changed since -rc4.
>
>That said, if you didn't test -rc4 _either_ - shame on you, and please
>do test -rc5.
>
>
Does anybody out there have ATI drivers working on Radeon X300
on 2.6.15-rc5 (or -rc[234]) ? They released fglrx 8.20.8 on december 8th.
I thought they would have fixed the driver for 2.6.15.
But, I still get bad page and X programs freezing.
Thanks,
Brice
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies,
Starnberg, GERMANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 169
[fglrx] module loaded - fglrx 8.20.8 [Dec 6 2005] on minor 0
[fglrx] ACPI power management is initialized.
[<c0140817>] bad_page+0x87/0xc0
[<c01410f8>] free_hot_cold_page+0x48/0x110
[<c014b62c>] zap_pte_range+0x10c/0x250
[<c014b866>] unmap_page_range+0xf6/0x130
[<c014b97b>] unmap_vmas+0xdb/0x200
[<c0150163>] unmap_region+0x93/0x130
[<c01504f7>] do_munmap+0x107/0x150
[<c015058c>] sys_munmap+0x4c/0x70
[<c0103105>] syscall_call+0x7/0xb
[fglrx] free PCIe = 54804480
[fglrx] max PCIe = 54804480
[fglrx] free LFB = 47099904
[fglrx] max LFB = 47099904
[fglrx] free Inv = 0
[fglrx] max Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
[fglrx] total FB = 0
[fglrx] total PCIe = 16384
next prev parent reply other threads:[~2005-12-10 21:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 6:03 Linux 2.6.15-rc5: off-line for a week Linus Torvalds
2005-12-04 15:34 ` Gene Heskett
2005-12-04 18:50 ` Michael Krufky
2005-12-04 20:47 ` Gene Heskett
2005-12-04 21:14 ` Michael Krufky
2005-12-05 0:16 ` Gene Heskett
2005-12-04 16:56 ` Jesper Juhl
2005-12-04 17:26 ` Michal Piotrowski
2005-12-04 18:35 ` Jesper Juhl
2005-12-04 22:25 ` Andrea Arcangeli
2005-12-04 23:43 ` Linux 2.6.15-rc5: sk98lin broken Johannes Stezenbach
2005-12-05 19:00 ` [PATCH linux-2.6.15-rc5] sk98lin: rx checksum offset not set Stephen Hemminger
2005-12-05 19:22 ` Johannes Stezenbach
2005-12-05 19:13 ` Linux 2.6.15-rc5: sk98lin broken Bill Davidsen
2005-12-07 21:59 ` Linux 2.6.15-rc5: off-line for a week Rich Walker
2005-12-10 16:27 ` Linux 2.6.15-rc5: multiuser scheduling trouble Helge Hafting
2005-12-12 0:09 ` Linus Torvalds
2005-12-12 6:51 ` Ingo Molnar
2005-12-12 11:18 ` Helge Hafting
2005-12-12 11:30 ` Nix
2005-12-12 12:31 ` Helge Hafting
2005-12-12 10:51 ` Helge Hafting
2005-12-10 21:23 ` Brice Goglin [this message]
2005-12-10 21:43 ` Linux 2.6.15-rc5 bad page with fglrx on Radeon X300 Lee Revell
2005-12-11 10:49 ` Hugh Dickins
[not found] <5fVeA-714-27@gated-at.bofh.it>
[not found] ` <5iksa-2mf-3@gated-at.bofh.it>
2005-12-10 21:46 ` ldonesty
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=439B475F.2050901@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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