From: Alex Deucher <alexdeucher@gmail.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: Linux 2.6.39-rc3
Date: Tue, 12 Apr 2011 10:15:11 -0400 [thread overview]
Message-ID: <BANLkTimSgAmT5a1s0ciBr2jsE-Nu7n4buQ@mail.gmail.com> (raw)
In-Reply-To: <20110412090207.GE19819@8bytes.org>
On Tue, Apr 12, 2011 at 5:02 AM, Joerg Roedel <joro@8bytes.org> wrote:
> On Mon, Apr 11, 2011 at 05:40:11PM -0700, Linus Torvalds wrote:
>> Let's hope the release cycle continues like this. I _like_ it when
>> people really seem to follow the whole "big changes during the merge
>> window" rules.
>
> Sorry for disturbing the silence, but radeon seems to have issues. I
> tested -rc3 (and after that -rc1 which also has the issue) on my Laptop
> and it just reboots after (or while?) GFX initialization. The last lines
> of dmesg are:
>
> Freeing unused kernel memory: 624k freed
> Write protecting the kernel read-only data: 8192k
> Freeing unused kernel memory: 1456k freed
> Freeing unused kernel memory: 16k freed
> udev: starting version 151
> udevd (62): /proc/62/oom_adj is deprecated, please use /proc/62/oom_score_adj instead.
> [drm] Initialized drm 1.1.0 20060810
> [drm] radeon defaulting to kernel modesetting.
> [drm] radeon kernel modesetting enabled.
> radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [drm] initializing kernel modesetting (RS880 0x1002:0x9712).
> [drm] register mmio base: 0xD6400000
> [drm] register mmio size: 65536
> ATOM BIOS: HP_TAG
> radeon 0000:01:05.0: VRAM: 320M 0x00000000C0000000 - 0x00000000D3FFFFFF (320M used)
> radeon 0000:01:05.0: GTT: 512M 0x00000000A0000000 - 0x00000000BFFFFFFF
> [drm] Detected VRAM RAM=320M, BAR=256M
> [drm] RAM width 32bits DDR
> [TTM] Zone kernel: Available graphics memory: 1896512 kiB.
> usb 7-2: new full speed USB device number 2 using ohci_hcd
> [TTM] Initializing pool allocator.
> [drm] radeon: 320M of VRAM memory ready
> [drm] radeon: 512M of GTT memory ready.
> [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [drm] Driver supports precise vblank timestamp query.
> [drm] radeon: irq initialized.
> [drm] GART: num cpu pages 131072, num gpu pages 131072
> [drm] Loading RS780 Microcode
> radeon 0000:01:05.0: WB enabled
> [drm] ring test succeeded in 1 usecs
> [drm] radeon: ib pool ready.
>
> The card is a Radeon Mobility 4200:
>
> 01:05.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200]
> Subsystem: Hewlett-Packard Company Device 307e
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 18
> Region 0: Memory at c0000000 (32-bit, prefetchable) [size=256M]
> Region 1: I/O ports at 6000 [size=256]
> Region 2: Memory at d6400000 (32-bit, non-prefetchable) [size=64K]
> Region 5: Memory at d6300000 (32-bit, non-prefetchable) [size=1M]
> Capabilities: [50] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
> Address: 0000000000000000 Data: 0000
> Kernel driver in use: radeon
> Kernel modules: radeon
>
> The problem does not happen with 2.6.38. I try to bisect this further down to a
> commit. Alex, please let me know if you need any further information.
If you can bisect it, that would be great. Thanks,
Alex
>
> Joerg
>
>
next prev parent reply other threads:[~2011-04-12 14:15 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 0:40 Linux 2.6.39-rc3 Linus Torvalds
2011-04-12 9:02 ` Joerg Roedel
2011-04-12 14:15 ` Alex Deucher [this message]
2011-04-12 18:44 ` Joerg Roedel
2011-04-13 1:27 ` David Rientjes
2011-04-13 6:46 ` Ingo Molnar
2011-04-13 17:21 ` Joerg Roedel
2011-04-13 18:39 ` H. Peter Anvin
2011-04-13 19:26 ` Joerg Roedel
2011-04-13 18:51 ` H. Peter Anvin
2011-04-13 19:24 ` Joerg Roedel
2011-04-13 19:14 ` Yinghai Lu
2011-04-13 19:34 ` Joerg Roedel
2011-04-13 20:48 ` Yinghai Lu
2011-04-13 20:54 ` Linus Torvalds
2011-04-13 21:23 ` Yinghai Lu
2011-04-13 23:39 ` Linus Torvalds
2011-04-14 0:10 ` Yinghai Lu
2011-04-14 2:03 ` H. Peter Anvin
2011-04-14 2:27 ` Linus Torvalds
2011-04-14 2:33 ` Linus Torvalds
2011-04-14 4:03 ` Tejun Heo
2011-04-14 9:36 ` Joerg Roedel
2011-04-14 8:09 ` Alan Cox
2011-04-15 13:11 ` Joerg Roedel
2011-04-15 13:16 ` Ingo Molnar
2011-04-15 14:33 ` Joerg Roedel
2011-04-15 16:11 ` Alex Deucher
2011-04-15 15:46 ` Joerg Roedel
2011-04-15 16:11 ` Jerome Glisse
2011-04-16 16:35 ` Joerg Roedel
2011-04-16 18:54 ` Jerome Glisse
2011-04-17 14:09 ` Joerg Roedel
2011-04-18 1:12 ` Jerome Glisse
2011-04-18 15:23 ` Alex Deucher
2011-04-18 15:29 ` Jerome Glisse
2011-04-18 15:33 ` Alex Deucher
2011-04-18 15:59 ` Jerome Glisse
2011-04-18 16:35 ` Alex Deucher
2011-04-15 14:04 ` Andreas Herrmann
2011-04-15 14:28 ` Joerg Roedel
2011-04-15 14:16 ` Alexandre Demers
2011-04-15 14:27 ` Joerg Roedel
2011-04-15 18:59 ` Alexandre Demers
2011-04-15 19:06 ` Ingo Molnar
2011-04-15 19:18 ` Yinghai Lu
2011-04-15 20:22 ` H. Peter Anvin
2011-04-16 12:01 ` Joerg Roedel
2011-04-16 12:00 ` Joerg Roedel
2011-04-16 12:21 ` Ingo Molnar
2011-04-16 0:03 ` [tip:x86/urgent] x86, amd: Disable GartTlbWlkErr when BIOS forgets it tip-bot for Joerg Roedel
2011-05-06 21:17 ` Linux 2.6.39-rc3 Linus Torvalds
2011-04-13 21:50 ` Joerg Roedel
2011-04-13 21:59 ` Yinghai Lu
2011-04-13 22:11 ` H. Peter Anvin
2011-04-13 22:01 ` H. Peter Anvin
2011-04-13 22:22 ` Joerg Roedel
2011-04-13 22:31 ` H. Peter Anvin
2011-04-14 8:59 ` Joerg Roedel
2011-04-13 19:48 ` Alex Deucher
2011-04-14 1:58 ` H. Peter Anvin
2011-04-14 2:07 ` Dave Airlie
2011-04-14 6:10 ` H. Peter Anvin
2011-04-14 8:56 ` Joerg Roedel
2011-04-14 9:07 ` Dave Airlie
2011-04-14 9:11 ` Ingo Molnar
2011-04-14 14:31 ` H. Peter Anvin
2011-04-14 14:28 ` Alex Deucher
2011-04-14 21:09 ` Joerg Roedel
2011-04-14 21:34 ` Alex Deucher
2011-04-15 6:50 ` Joerg Roedel
2011-04-15 14:49 ` Andreas Herrmann
2011-04-15 8:26 ` Michel Dänzer
2011-04-15 8:55 ` Joerg Roedel
2011-04-12 19:09 ` Dave Jones
2011-04-12 19:21 ` Dave Jones
2011-04-12 19:55 ` Linus Torvalds
2011-04-12 20:13 ` Dave Jones
2011-04-14 8:20 ` Aneesh Kumar K.V
2011-04-18 22:57 ` Kay Sievers
2011-04-18 23:02 ` Dave Jones
2011-04-18 23:14 ` Kay Sievers
2011-04-19 11:42 ` Ted Ts'o
2011-04-19 8:23 ` Aneesh Kumar K.V
2011-04-19 8:37 ` Steven Whitehouse
2011-04-19 9:55 ` Kay Sievers
2011-04-12 20:20 ` Eric Sandeen
2011-04-12 20:27 ` Karel Zak
2011-04-12 20:33 ` Linus Torvalds
2011-04-14 20:24 ` Borislav Petkov
2011-04-14 20:55 ` Linus Torvalds
2011-04-15 4:14 ` Christoph Hellwig
2011-04-20 20:12 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2011-04-13 4:32 George Spelvin
2011-04-13 14:54 ` Linus Torvalds
2011-04-14 18:28 ` Pavel Machek
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=BANLkTimSgAmT5a1s0ciBr2jsE-Nu7n4buQ@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).