gma500 suspend to ram fails (3.4)
On Tue, Jul 03, 2012 at 07:11:31AM +0900, Mattia Dongili wrote: > On Mon, Jul 02, 2012 at 11:43:04AM +0100, Alan Cox wrote: > > On Mon, 2 Jul 2012 07:06:59 +0900 > > Mattia Dongili wrote: > ... > > > 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) > > ha! that gave me a good lead. > The problem is not gma_backlight_init but rather psb_modeset_init that > calls the errata for the chip that in turn sets the brightness before > any initialization is done. > > Commenting out the call to dev_priv->ops->errata in framebuffer.c makes > boot get to the end like it used to on 3.4. It seems to be just an > ordering problem in the end. and back to the original issue, with 3.5 the laptop suspends to ram just fine! finally this vaio X may be of some use!! I can test patches for the errata call issue if you need any confirmation. -- mattia :wq!
gma500 suspend to ram fails (3.4)
On Mon, Jul 02, 2012 at 11:43:04AM +0100, Alan Cox wrote: > On Mon, 2 Jul 2012 07:06:59 +0900 > Mattia Dongili wrote: ... > > 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) ha! that gave me a good lead. The problem is not gma_backlight_init but rather psb_modeset_init that calls the errata for the chip that in turn sets the brightness before any initialization is done. Commenting out the call to dev_priv->ops->errata in framebuffer.c makes boot get to the end like it used to on 3.4. It seems to be just an ordering problem in the end. -- mattia :wq!
Re: gma500 suspend to ram fails (3.4)
On Tue, Jul 03, 2012 at 07:11:31AM +0900, Mattia Dongili wrote: > On Mon, Jul 02, 2012 at 11:43:04AM +0100, Alan Cox wrote: > > On Mon, 2 Jul 2012 07:06:59 +0900 > > Mattia Dongili wrote: > ... > > > 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) > > ha! that gave me a good lead. > The problem is not gma_backlight_init but rather psb_modeset_init that > calls the errata for the chip that in turn sets the brightness before > any initialization is done. > > Commenting out the call to dev_priv->ops->errata in framebuffer.c makes > boot get to the end like it used to on 3.4. It seems to be just an > ordering problem in the end. and back to the original issue, with 3.5 the laptop suspends to ram just fine! finally this vaio X may be of some use!! I can test patches for the errata call issue if you need any confirmation. -- mattia :wq! ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: gma500 suspend to ram fails (3.4)
On Mon, Jul 02, 2012 at 11:43:04AM +0100, Alan Cox wrote: > On Mon, 2 Jul 2012 07:06:59 +0900 > Mattia Dongili wrote: ... > > 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) ha! that gave me a good lead. The problem is not gma_backlight_init but rather psb_modeset_init that calls the errata for the chip that in turn sets the brightness before any initialization is done. Commenting out the call to dev_priv->ops->errata in framebuffer.c makes boot get to the end like it used to on 3.4. It seems to be just an ordering problem in the end. -- mattia :wq! ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
gma500 suspend to ram fails (3.4)
On Mon, 2 Jul 2012 07:06:59 +0900 Mattia Dongili 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 > > > > 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:v8086d8108sv104Dsd905Fbc03sc00i00 > > > 361 ?D 0:00 /sbin/modprobe -b > > > pci:v8086d811Bsv104Dsd905Fbc04sc03i00 > > > 422 ?D 0:00 /sbin/modprobe -b > > > pci:v8086d8119sv104Dsd905Fbc06sc01i00 > > > > 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.00] Linux version 3.5.0-rc4... > [5.712020] gma500 :00:02.0: Backlight lvds set brightness > 74367436 > > while with 3.4 > > [5.525296] gma500 :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
Re: gma500 suspend to ram fails (3.4)
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 > > > 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:v8086d8108sv104Dsd905Fbc03sc00i00 > > 361 ?D 0:00 /sbin/modprobe -b > > pci:v8086d811Bsv104Dsd905Fbc04sc03i00 > > 422 ?D 0:00 /sbin/modprobe -b > > pci:v8086d8119sv104Dsd905Fbc06sc01i00 > > 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.00] Linux version 3.5.0-rc4... [5.712020] gma500 :00:02.0: Backlight lvds set brightness 74367436 while with 3.4 [5.525296] gma500 :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. -- mattia :wq! ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
gma500 suspend to ram fails (3.4)
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 > > > 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:v8086d8108sv104Dsd905Fbc03sc00i00 > > 361 ?D 0:00 /sbin/modprobe -b > > pci:v8086d811Bsv104Dsd905Fbc04sc03i00 > > 422 ?D 0:00 /sbin/modprobe -b > > pci:v8086d8119sv104Dsd905Fbc06sc01i00 > > 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.00] Linux version 3.5.0-rc4... [5.712020] gma500 :00:02.0: Backlight lvds set brightness 74367436 while with 3.4 [5.525296] gma500 :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. -- mattia :wq!
Re: gma500 suspend to ram fails (3.4)
On Mon, 2 Jul 2012 07:06:59 +0900 Mattia Dongili 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 > > > > 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:v8086d8108sv104Dsd905Fbc03sc00i00 > > > 361 ?D 0:00 /sbin/modprobe -b > > > pci:v8086d811Bsv104Dsd905Fbc04sc03i00 > > > 422 ?D 0:00 /sbin/modprobe -b > > > pci:v8086d8119sv104Dsd905Fbc06sc01i00 > > > > 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.00] Linux version 3.5.0-rc4... > [5.712020] gma500 :00:02.0: Backlight lvds set brightness > 74367436 > > while with 3.4 > > [5.525296] gma500 :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 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
gma500 suspend to ram fails (3.4)
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 > > 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:v8086d8108sv104Dsd905Fbc03sc00i00 > 361 ?D 0:00 /sbin/modprobe -b > pci:v8086d811Bsv104Dsd905Fbc04sc03i00 > 422 ?D 0:00 /sbin/modprobe -b > pci:v8086d8119sv104Dsd905Fbc06sc01i00 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. ... > [5.547841] [drm:psb_intel_sdvo_debug_write], SDVOB: W: 1D > (SDVO_CMD_GET_INPUT_PIXEL_CLOCK_RANGE) > [5.560512] [drm:psb_intel_sdvo_read_response], SDVOB: R: (Success) C4 09 > 74 40 > [5.560520] [drm:psb_intel_sdvo_init], SDVOB device VID/DID: 02:42.02, > clock range 25MHz - 165MHz, input 1: Y, input 2: N, output 1: Y, output 2: N > [5.660023] gma500 :00:02.0: Backlight lvds set brightness 74367436 > [ 117.723197] Adding 4883756k swap on /dev/sda2. Priority:-1 extents:1 > across:4883756k SS > [ 117.911192] EXT3-fs (sda1): using internal journal -- mattia :wq!
Re: gma500 suspend to ram fails (3.4)
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 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:v8086d8108sv104Dsd905Fbc03sc00i00 > 361 ?D 0:00 /sbin/modprobe -b > pci:v8086d811Bsv104Dsd905Fbc04sc03i00 > 422 ?D 0:00 /sbin/modprobe -b > pci:v8086d8119sv104Dsd905Fbc06sc01i00 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. ... > [5.547841] [drm:psb_intel_sdvo_debug_write], SDVOB: W: 1D > (SDVO_CMD_GET_INPUT_PIXEL_CLOCK_RANGE) > [5.560512] [drm:psb_intel_sdvo_read_response], SDVOB: R: (Success) C4 09 > 74 40 > [5.560520] [drm:psb_intel_sdvo_init], SDVOB device VID/DID: 02:42.02, > clock range 25MHz - 165MHz, input 1: Y, input 2: N, output 1: Y, output 2: N > [5.660023] gma500 :00:02.0: Backlight lvds set brightness 74367436 > [ 117.723197] Adding 4883756k swap on /dev/sda2. Priority:-1 extents:1 > across:4883756k SS > [ 117.911192] EXT3-fs (sda1): using internal journal -- mattia :wq! ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
gma500 suspend to ram fails (3.4)
On Mon, Jun 18, 2012 at 12:26:29PM +0100, Alan Cox wrote: > On Sun, 17 Jun 2012 19:03:43 +0900 > Mattia Dongili wrote: ... > > Is there anything else I can provide to help debug this? > > > > Thanks! > > You should be able to just the relevant commit from 3.5.rc > > (git show 7beff62 and apply it to 3.4) yeah actually the warning part was the easy one to solve ;) On Mon, Jun 18, 2012 at 10:04:00PM +0200, Patrik Jakobsson wrote: > On Sun, Jun 17, 2012 at 12:03 PM, Mattia Dongili wrote: > > > 3.5-rc2 is not quite usable, I get a pile of warnings for > > DRM_OBJECT_MAX_PROPERTY being too small and in the end I don't get > > neither a console nor X. > > Give 3.5-rc3 a try. There is a patch that at least silences the > DRM_OBJECT_MAX_PROPERTY on i915. > > 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:v8086d8108sv104Dsd905Fbc03sc00i00 361 ?D 0:00 /sbin/modprobe -b pci:v8086d811Bsv104Dsd905Fbc04sc03i00 422 ?D 0:00 /sbin/modprobe -b pci:v8086d8119sv104Dsd905Fbc06sc01i00 the aliases are respectively: pci:v8086d8108sv104Dsd905Fbc03sc00i00 gma500_gfx pci:v8086d811Bsv104Dsd905Fbc04sc03i00 snd_hda_intel snd_hda_intel pci:v8086d8119sv104Dsd905Fbc06sc01i00 lpc_sch Thanks! -- mattia :wq! -- next part -- [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.5.0-rc3 (mattia at ludwig) (gcc version 4.7.0 (Debian 4.7.1-1) ) #30 SMP PREEMPT Tue Jun 19 07:50:37 JST 2012 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] Disabled fast string operations [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x7f64cfff] usable [0.00] BIOS-e820: [mem 0x7f64d000-0x7f64dfff] reserved [0.00] BIOS-e820: [mem 0x7f64e000-0x7f655fff] ACPI NVS [0.00] BIOS-e820: [mem 0x7f656000-0x7f69efff] reserved [0.00] BIOS-e820: [mem 0x7f69f000-0x7f6a1fff] usable [0.00] BIOS-e820: [mem 0x7f6a2000-0x7f6defff] ACPI NVS [0.00] BIOS-e820: [mem 0x7f6df000-0x7f6eefff] ACPI data [0.00] BIOS-e820: [mem 0x7f6ef000-0x7f6e] usable [0.00] BIOS-e820: [mem 0x7f6f-0x7fff] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed003ff] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed13fff] reserved [0.00] BIOS-e820: [mem 0xfed4-0xfed4bfff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xfff0-0x] reserved [0.00] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! [0.00] DMI 2.4 present. [0.00] DMI: Sony Corporation VPCX11AKJ/VAIO, BIOS R0082U4 10/13/2009 [0.00] e820: update [mem 0x-0x] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x7f6f0 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-D uncachable [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 disabled [0.00] 1 base 0 mask 08000 write-back [0.00] 2 base 07F80 mask 0FF80 uncachable [0.00] 3 disabled [0.00] 4 base 07F6F mask 0 uncachable [0.00] 5 disabled [0.00] 6 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: update [mem 0x7f6f-0x7f6f] usable ==> reserved [0.00] initial memory mapped: [mem 0x-0x017f] [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 [0.00] init_memory_mapping: [mem 0x-0x377fdfff] [0.00] [mem 0x-0x003f] page 4k [0.00] [mem 0x0
gma500 suspend to ram fails (3.4)
On Sun, Jun 17, 2012 at 12:03 PM, Mattia Dongili wrote: > 3.5-rc2 is not quite usable, I get a pile of warnings for > DRM_OBJECT_MAX_PROPERTY being too small and in the end I don't get > neither a console nor X. Give 3.5-rc3 a try. There is a patch that at least silences the DRM_OBJECT_MAX_PROPERTY on i915. If possible, add drm.debug=7 to your boot line and send a dmesg of 3.5-rc3. Patrik
Re: gma500 suspend to ram fails (3.4)
On Sun, Jun 17, 2012 at 12:03 PM, Mattia Dongili wrote: > 3.5-rc2 is not quite usable, I get a pile of warnings for > DRM_OBJECT_MAX_PROPERTY being too small and in the end I don't get > neither a console nor X. Give 3.5-rc3 a try. There is a patch that at least silences the DRM_OBJECT_MAX_PROPERTY on i915. If possible, add drm.debug=7 to your boot line and send a dmesg of 3.5-rc3. Patrik ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
gma500 suspend to ram fails (3.4)
Hi, I just switched from an ancient installation of emgd on a vaio X11 to the mainstream gma500_gfx driver. One issue I have on 3.4 is that suspend to ram fails in psb_save_display_registers. I could only take a picture of the oops but it's quite incomplete: http://kamineko.org/oops/2012-06-17%2018.32.17.jpg 3.5-rc2 is not quite usable, I get a pile of warnings for DRM_OBJECT_MAX_PROPERTY being too small and in the end I don't get neither a console nor X. here's attached a 3.4 boot dmesg, I'll recompile 3.5 soon to get started with that too. Is there anything else I can provide to help debug this? Thanks! -- mattia :wq! [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.4.0+ (mattia@ludwig) (gcc version 4.7.0 (Debian 4.7.1-1) ) #28 SMP PREEMPT Sat Jun 16 17:25:13 JST 2012 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] Disabled fast string operations [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 7f64d000 (usable) [0.00] BIOS-e820: 7f64d000 - 7f64e000 (reserved) [0.00] BIOS-e820: 7f64e000 - 7f656000 (ACPI NVS) [0.00] BIOS-e820: 7f656000 - 7f69f000 (reserved) [0.00] BIOS-e820: 7f69f000 - 7f6a2000 (usable) [0.00] BIOS-e820: 7f6a2000 - 7f6df000 (ACPI NVS) [0.00] BIOS-e820: 7f6df000 - 7f6ef000 (ACPI data) [0.00] BIOS-e820: 7f6ef000 - 7f6f (usable) [0.00] BIOS-e820: 7f6f - 8000 (reserved) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fec0 - fec01000 (reserved) [0.00] BIOS-e820: fed0 - fed00400 (reserved) [0.00] BIOS-e820: fed1 - fed14000 (reserved) [0.00] BIOS-e820: fed4 - fed4c000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! [0.00] DMI 2.4 present. [0.00] DMI: Sony Corporation VPCX11AKJ/VAIO, BIOS R0082U4 10/13/2009 [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x7f6f0 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-D uncachable [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 disabled [0.00] 1 base 0 mask 08000 write-back [0.00] 2 base 07F80 mask 0FF80 uncachable [0.00] 3 disabled [0.00] 4 base 07F6F mask 0 uncachable [0.00] 5 disabled [0.00] 6 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820 update range: 7f6f - 7f70 (usable) ==> (reserved) [0.00] initial memory mapped : 0 - 0180 [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 [0.00] init_memory_mapping: -377fe000 [0.00] 00 - 40 page 4k [0.00] 40 - 003740 page 2M [0.00] 003740 - 00377fe000 page 4k [0.00] kernel direct mapping tables up to 377fe000 @ 17fb000-180 [0.00] ACPI: RSDP 000fe020 00024 (v02 Sony) [0.00] ACPI: XSDT 7f6ee120 00064 (v01 Sony VAIO 20091013 0113) [0.00] ACPI: FACP 7f6ed000 000F4 (v03 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20120320/tbfadt-629) [0.00] ACPI: DSDT 7f6e2000 0582B (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: FACS 7f6a6000 00040 [0.00] ACPI: HPET 7f6ec000 00038 (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: APIC 7f6eb000 00068 (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: MCFG 7f6ea000 0003C (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: SLIC 7f6e9000 00176 (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: ASF! 7f6e8000 000A5 (v32 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: BOOT 7f6e1000 00028 (v01 Sony
gma500 suspend to ram fails (3.4)
Hi, I just switched from an ancient installation of emgd on a vaio X11 to the mainstream gma500_gfx driver. One issue I have on 3.4 is that suspend to ram fails in psb_save_display_registers. I could only take a picture of the oops but it's quite incomplete: http://kamineko.org/oops/2012-06-17%2018.32.17.jpg 3.5-rc2 is not quite usable, I get a pile of warnings for DRM_OBJECT_MAX_PROPERTY being too small and in the end I don't get neither a console nor X. here's attached a 3.4 boot dmesg, I'll recompile 3.5 soon to get started with that too. Is there anything else I can provide to help debug this? Thanks! -- mattia :wq! -- next part -- [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.4.0+ (mattia at ludwig) (gcc version 4.7.0 (Debian 4.7.1-1) ) #28 SMP PREEMPT Sat Jun 16 17:25:13 JST 2012 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] Disabled fast string operations [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 7f64d000 (usable) [0.00] BIOS-e820: 7f64d000 - 7f64e000 (reserved) [0.00] BIOS-e820: 7f64e000 - 7f656000 (ACPI NVS) [0.00] BIOS-e820: 7f656000 - 7f69f000 (reserved) [0.00] BIOS-e820: 7f69f000 - 7f6a2000 (usable) [0.00] BIOS-e820: 7f6a2000 - 7f6df000 (ACPI NVS) [0.00] BIOS-e820: 7f6df000 - 7f6ef000 (ACPI data) [0.00] BIOS-e820: 7f6ef000 - 7f6f (usable) [0.00] BIOS-e820: 7f6f - 8000 (reserved) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fec0 - fec01000 (reserved) [0.00] BIOS-e820: fed0 - fed00400 (reserved) [0.00] BIOS-e820: fed1 - fed14000 (reserved) [0.00] BIOS-e820: fed4 - fed4c000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! [0.00] DMI 2.4 present. [0.00] DMI: Sony Corporation VPCX11AKJ/VAIO, BIOS R0082U4 10/13/2009 [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x7f6f0 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-D uncachable [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 disabled [0.00] 1 base 0 mask 08000 write-back [0.00] 2 base 07F80 mask 0FF80 uncachable [0.00] 3 disabled [0.00] 4 base 07F6F mask 0 uncachable [0.00] 5 disabled [0.00] 6 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820 update range: 7f6f - 7f70 (usable) ==> (reserved) [0.00] initial memory mapped : 0 - 0180 [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 [0.00] init_memory_mapping: -377fe000 [0.00] 00 - 40 page 4k [0.00] 40 - 003740 page 2M [0.00] 003740 - 00377fe000 page 4k [0.00] kernel direct mapping tables up to 377fe000 @ 17fb000-180 [0.00] ACPI: RSDP 000fe020 00024 (v02 Sony) [0.00] ACPI: XSDT 7f6ee120 00064 (v01 Sony VAIO 20091013 0113) [0.00] ACPI: FACP 7f6ed000 000F4 (v03 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20120320/tbfadt-629) [0.00] ACPI: DSDT 7f6e2000 0582B (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: FACS 7f6a6000 00040 [0.00] ACPI: HPET 7f6ec000 00038 (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: APIC 7f6eb000 00068 (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: MCFG 7f6ea000 0003C (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: SLIC 7f6e9000 00176 (v01 Sony VAIO 20091013 MSFT 0113) [0.00] ACPI: ASF! 7f6e8000 000A5 (v32 Sony VAIO 20091013 MSFT 0113) [0.00
