On Mon, 2 Jul 2012 07:06:59 +0900 Mattia Dongili <malattia at linux.it> wrote:
> On Thu, Jun 21, 2012 at 06:19:25AM +0900, Mattia Dongili wrote: > > On Tue, Jun 19, 2012 at 07:56:52PM +0900, Mattia Dongili wrote: > > > On Mon, Jun 18, 2012 at 10:04:00PM +0200, Patrik Jakobsson wrote: > > > > On Sun, Jun 17, 2012 at 12:03 PM, Mattia Dongili > > > > <malattia at linux.it> wrote: > > ... > > > > If possible, add drm.debug=7 to your boot line and send a dmesg > > > > of 3.5-rc3. > > > > > > attached the dmesg on rc3 with drm.debug=7. > > > In addition I have a black screen and 3 modprobe processes stuck > > > that udev tried to kill for a bit... then the console went blank > > > and I can't tell if it's still trying: > > > > > > 359 ? R 11:08 /sbin/modprobe -b > > > pci:v00008086d00008108sv0000104Dsd0000905Fbc03sc00i00 > > > 361 ? D 0:00 /sbin/modprobe -b > > > pci:v00008086d0000811Bsv0000104Dsd0000905Fbc04sc03i00 > > > 422 ? D 0:00 /sbin/modprobe -b > > > pci:v00008086d00008119sv0000104Dsd0000905Fbc06sc01i00 > > > > for the record, here below is where the screen flickers a bit and > > booting gets stuck until udev starts trying to kill the modprobe > > calls. > > I gave 3.5-rc4 a try, no significant change but by comparing 3.4 and > 3.5 logs I have this difference that may mean something: > > [ 0.000000] Linux version 3.5.0-rc4... > [ 5.712020] gma500 0000:00:02.0: Backlight lvds set brightness > 74367436 > > while with 3.4 > > [ 5.525296] gma500 0000:00:02.0: Backlight lvds set brightness > 74407440 > > a did put some printks here and there and psb_driver_init seems to > never return from gma_backlight_init. Is it ok if you just comment out gma_backlight_init (at which point it should just skip backlight handling and leave the firmware configured one) Alan
