linux-kernel - Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging."

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 2 Feb 2010 12:59:13 +0100
From:	Jerome Glisse <glisse@...edesktop.org>
To:	Dave Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.sf.net
Subject: Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off
 switch out of staging."

On Tue, Feb 02, 2010 at 09:58:20AM +0100, Domenico Andreoli wrote:
> On Tue, Feb 02, 2010 at 09:17:27AM +0100, Ingo Molnar wrote:
> > 
> > * Dave Airlie <airlied@...ux.ie> wrote:
> > 
> > > > Hi Linus,
> > > > 
> > > > Please pull the 'drm-linus' branch from
> > > > ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus
> > > > 
> > 
> > FYI, this drm pull into mainline has triggered quick boot crashes in -tip 
> > testing (even with the above fix applied), on an Athlon64 whitebox PC with:
> 
> boot broke also here where unfortunately i have not a serial line
> to see what's happening. anyway disabling KMS restores a working
> 2.6.33-rc6-00072-gab65832 kernel.  here is the broken config.
> 
> in the next days i should be able to test it with a RV770.
> 
> >  01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
> >  01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
> 
> 01:00.0 VGA compatible controller: ATI Technologies Inc RV515 [Radeon X1300]
> 01:00.1 Display controller: ATI Technologies Inc RV515 [Radeon X1300] (Secondary)
> 
> 

Can you boot in runlevel 3 and with radeon.modeset=0. Then modprobe radeon modeset=1
(you might need to rmmod first), this should allow you capture dmesg log with the failure.
(Do the modprobe/rmmod through ssh as you won't have a console in the process).

Note that here RV515 works like a charm :)

Cheers,
Jerome
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/