[Intel-gfx] Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Sep 25, 2013 at 05:48:06PM +0200, Daniel Vetter wrote: > On Wed, Sep 25, 2013 at 06:34:38PM +0300, Michael S. Tsirkin wrote: > > On Wed, Sep 25, 2013 at 09:56:52AM +0200, Daniel Vetter wrote: > > > On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: > > > > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin > > > redhat.com> wrote: > > > > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > > > > >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > > > > >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] > > > > >> > > > > > >> > Hi, > > > > >> > > > > > >> > saw your posting in [1]... can you try the patches below? > > > > >> > Not sure if they apply. > > > > >> > Did you try v3.11-rc6(+)... or drm-intel-nightly? > > > > >> > > > > > >> > Regards, > > > > >> > - Sedat - > > > > >> > > > > > >> > [1] > > > > >> > http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html > > > > >> > > > > >> Same thing observed with v3.11-rc7. > > > > > > > > > > I still see this with 3.11. > > > > > Following this message, my VGA monitor goes blank and > > > > > shows an error suggesting a wrong resolution or frequency are set. > > > > > Anyone? > > > > > > > > Daniel, Jesse? > > > > > > > > still ongoing I think. > > > > > > Yeah, I've dismissed it since the original issue in this thread is > > > resolved. But it's something else. > > > > > > Note to bug reporters: Please don't me-too, but start a new thread/report > > > - almost every gfx bug is different, even if it superficially looks the > > > same. > > > > > > Michael, can you please boot with drm.debug=0xe, reproduce the problem and > > > then attach the complete dmesg? Please make sure dmesg contains everything > > > since boot-up, if not please increase the dmesg buffer size with > > > log_buf_len=4M. > > > > Complete dmesg attached. > > > > > Also please test the latest drm-intel-fixes release to check that we > > > haven't just forgotten to send the patch to stable (there's at least one > > > flags mismatch fix already in-flight to 3.11 stable kernels). > > > > > > Thanks, Daniel > > > > Is it included in latest -rc2? It's easier for me to test that. > > -rc2 should be good enough for testing - the additional patches in > -fixes won't affect your issue. > -Daniel Either it's gone in -rc2 or it's masked with drm.debug=0xe. I will keep running with drm.debug=0xe some more, if it does not trigger anymore, I'll go back to -rc2 without drm.debug=0xe. > > > > > -- > > > Daniel Vetter > > > Software Engineer, Intel Corporation > > > +41 (0) 79 365 57 48 - http://blog.ffwll.ch > > > [0.00] Initializing cgroup subsys cpuset > > [0.00] Initializing cgroup subsys cpu > > [0.00] Initializing cgroup subsys cpuacct > > [0.00] Linux version 3.11.0-mst (mst at robin.redhat.com) (gcc > > version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #258 SMP Sun Sep 22 02:49:15 IDT > > 2013 > > [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-mst > > root=UUID=75d505b0-6e76-4f40-9cbc-0d6e700effd1 ro rd.md=0 rd.lvm=0 rd.dm=0 > > SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet drm.debug=0xe > > [0.00] Disabled fast string operations > > [0.00] e820: BIOS-provided physical RAM map: > > [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable > > [0.00] BIOS-e820: [mem 0x0009d800-0x0009] > > reserved > > [0.00] BIOS-e820: [mem 0x000e-0x000f] > > reserved > > [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable > > [0.00] BIOS-e820: [mem 0x2000-0x201f] > > reserved > > [0.00] BIOS-e820: [mem 0x2020-0x3fff] usable > > [0.00] BIOS-e820: [mem 0x4000-0x401f] > > reserved > > [0.00] BIOS-e820: [mem 0x4020-0xda99efff] usable > > [0.00] BIOS-e820: [mem 0xda99f000-0xdae9efff] > > reserved > > [0.00] BIOS-e820: [mem 0xdae9f000-0xdaf9efff] ACPI > > NVS > > [0.00] BIOS-e820: [mem 0xdaf9f000-0xdaffefff] ACPI > > data > > [0.00] BIOS-e820: [mem 0xdafff000-0xdaff] usable > > [0.00] BIOS-e820: [mem 0xdb00-0xdf9f] > > reserved > > [0.00] BIOS-e820: [mem 0xf800-0xfbff] > > reserved > > [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] > > reserved > > [0.00] BIOS-e820: [mem 0xfed08000-0xfed08fff] > > reserved > > [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] > > reserved > > [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] > > reserved > > [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] > > reserved > > [0.00] BIOS-e820: [mem
[Intel-gfx] Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
On Wed, Sep 25, 2013 at 06:34:38PM +0300, Michael S. Tsirkin wrote: > On Wed, Sep 25, 2013 at 09:56:52AM +0200, Daniel Vetter wrote: > > On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote: > > > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin > > > wrote: > > > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote: > > > >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote: > > > >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ] > > > >> > > > > >> > Hi, > > > >> > > > > >> > saw your posting in [1]... can you try the patches below? > > > >> > Not sure if they apply. > > > >> > Did you try v3.11-rc6(+)... or drm-intel-nightly? > > > >> > > > > >> > Regards, > > > >> > - Sedat - > > > >> > > > > >> > [1] > > > >> > http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html > > > >> > > > >> Same thing observed with v3.11-rc7. > > > > > > > > I still see this with 3.11. > > > > Following this message, my VGA monitor goes blank and > > > > shows an error suggesting a wrong resolution or frequency are set. > > > > Anyone? > > > > > > Daniel, Jesse? > > > > > > still ongoing I think. > > > > Yeah, I've dismissed it since the original issue in this thread is > > resolved. But it's something else. > > > > Note to bug reporters: Please don't me-too, but start a new thread/report > > - almost every gfx bug is different, even if it superficially looks the > > same. > > > > Michael, can you please boot with drm.debug=0xe, reproduce the problem and > > then attach the complete dmesg? Please make sure dmesg contains everything > > since boot-up, if not please increase the dmesg buffer size with > > log_buf_len=4M. > > Complete dmesg attached. > > > Also please test the latest drm-intel-fixes release to check that we > > haven't just forgotten to send the patch to stable (there's at least one > > flags mismatch fix already in-flight to 3.11 stable kernels). > > > > Thanks, Daniel > > Is it included in latest -rc2? It's easier for me to test that. -rc2 should be good enough for testing - the additional patches in -fixes won't affect your issue. -Daniel > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > +41 (0) 79 365 57 48 - http://blog.ffwll.ch > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00] Initializing cgroup subsys cpuacct > [0.00] Linux version 3.11.0-mst (mst at robin.redhat.com) (gcc > version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #258 SMP Sun Sep 22 02:49:15 IDT 2013 > [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-mst > root=UUID=75d505b0-6e76-4f40-9cbc-0d6e700effd1 ro rd.md=0 rd.lvm=0 rd.dm=0 > SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet drm.debug=0xe > [0.00] Disabled fast string operations > [0.00] e820: BIOS-provided physical RAM map: > [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable > [0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved > [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved > [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable > [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved > [0.00] BIOS-e820: [mem 0x2020-0x3fff] usable > [0.00] BIOS-e820: [mem 0x4000-0x401f] reserved > [0.00] BIOS-e820: [mem 0x4020-0xda99efff] usable > [0.00] BIOS-e820: [mem 0xda99f000-0xdae9efff] reserved > [0.00] BIOS-e820: [mem 0xdae9f000-0xdaf9efff] ACPI NVS > [0.00] BIOS-e820: [mem 0xdaf9f000-0xdaffefff] ACPI > data > [0.00] BIOS-e820: [mem 0xdafff000-0xdaff] usable > [0.00] BIOS-e820: [mem 0xdb00-0xdf9f] reserved > [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved > [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved > [0.00] BIOS-e820: [mem 0xfed08000-0xfed08fff] reserved > [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved > [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved > [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved > [0.00] BIOS-e820: [mem 0xffd2-0x] reserved > [0.00] BIOS-e820: [mem 0x0001-0x00021e5f] usable > [0.00] BIOS-e820: [mem 0x00021e60-0x00021e7f] reserved > [0.00] NX (Execute Disable) protection: active > [0.00] SMBIOS 2.6 present. > [0.00] DMI: LENOVO 4243BQ9/4243BQ9, BIOS 8AET57WW (1.37 ) 04/05/2012 > [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved > [0.00] e820: remove [mem 0x000a-0x000f] usable
