Attachment 126020 Details for Bug 97363 – drm-debug-linux-4.6

drm-debug-linux-4.6

drm-debug-linux-4.6 (text/plain), 3.45 KB, created by Robin Müller on 2016-08-24 21:07:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Robin Müller

Created: 2016-08-24 21:07:36 UTC

Size: 3.45 KB

patch

obsolete

>[drm:drm_pci_init] 
>[drm:drm_get_pci_dev] 
>[drm:drm_minor_register] 
>[drm:drm_minor_register] new minor registered 64
>[drm:drm_minor_register] 
>[drm:drm_minor_register] new minor registered 128
>[drm:drm_minor_register] 
>[drm:drm_minor_register] new minor registered 0
>[drm:i915_dump_device_info] i915 device info: gen=7, pciid=0x0166 rev=0x09 flags=is_mobile,need_gfx_hws,is_ivybridge,has_fbc,has_hotplug,has_llc,
>[drm:intel_detect_pch] Found PantherPoint PCH
>[drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K
>[drm:i915_gem_gtt_init] GMADR size = 256M
>[drm:i915_gem_gtt_init] GTT stolen size = 64M
>[drm:i915_gem_gtt_init] ppgtt mode: 1
>fb: switching to inteldrmfb from VESA VGA
>[drm:intel_opregion_setup] graphic opregion physical addr: 0xdaf75018
>[drm:intel_opregion_setup] Public ACPI methods supported
>[drm:intel_opregion_setup] SWSCI supported
>[drm:swsci_setup] SWSCI GBDA callbacks 00000cf3, SBCB callbacks 00000241
>[drm:intel_opregion_setup] ASLE supported
>[drm:intel_opregion_setup] ASLE extension supported
>[drm:intel_opregion_setup] Found valid VBT in ACPI OpRegion (Mailbox #4)
>[drm:intel_device_info_runtime_init] slice total: 0
>[drm:intel_device_info_runtime_init] subslice total: 0
>[drm:intel_device_info_runtime_init] subslice per slice: 0
>[drm:intel_device_info_runtime_init] EU total: 0
>[drm:intel_device_info_runtime_init] EU per subslice: 0
>[drm:intel_device_info_runtime_init] has slice power gating: n
>[drm:intel_device_info_runtime_init] has subslice power gating: n
>[drm:intel_device_info_runtime_init] has EU power gating: n
>[drm:init_vbt_defaults] Set default to SSC at 120000 kHz
>[drm:intel_bios_init] VBT signature "$VBT SNB/IVB-MOBILE ", BDB version 165
>[drm:parse_general_features] BDB_GENERAL_FEATURES int_tv_support 0 int_crt_support 1 lvds_use_ssc 1 lvds_ssc_freq 120000 display_clock_mode 0 fdi_rx_polarity_inverted 0
>[drm:parse_general_definitions] crt_ddc_bus_pin: 2
>[drm:parse_lfp_panel_data] DRRS supported mode is seamless
>[drm:parse_lfp_panel_data] Found panel mode in BIOS VBT tables:
>[drm:drm_mode_debug_printmodeline] Modeline 0:"1600x900" 0 100400 1600 1648 1680 1792 900 902 907 932 0x8 0xa
>[drm:parse_lfp_panel_data] VBT initial LVDS value 30033c
>[drm:parse_lfp_backlight] VBT backlight PWM modulation frequency 210 Hz, active high, min brightness 0, level 255
>[drm:parse_sdvo_panel_data] Found SDVO panel mode in BIOS VBT tables:
>[drm:drm_mode_debug_printmodeline] Modeline 0:"1600x1200" 0 162000 1600 1664 1856 2160 1200 1201 1204 1250 0x8 0xa
>[drm:parse_sdvo_device_mapping] No SDVO device info is found in VBT
>[drm:parse_driver_features] DRRS State Enabled:1
>[drm:intel_dsm_pci_probe] no _DSM method for intel device
>[drm:intel_power_well_enable] enabling always-on
>[drm:drm_irq_install] irq=24
>[drm:intel_print_wm_latency] Primary WM0 latency 12 (1.2 usec)
>[drm:intel_print_wm_latency] Primary WM1 latency 4 (2.0 usec)
>[drm:intel_print_wm_latency] Primary WM2 latency 16 (8.0 usec)
>[drm:intel_print_wm_latency] Primary WM3 latency 32 (16.0 usec)
>[drm:intel_print_wm_latency] Sprite WM0 latency 12 (1.2 usec)
>[drm:intel_print_wm_latency] Sprite WM1 latency 4 (2.0 usec)
>[drm:intel_print_wm_latency] Sprite WM2 latency 16 (8.0 usec)
>[drm:intel_print_wm_latency] Sprite WM3 latency 32 (16.0 usec)
>[drm:intel_print_wm_latency] Cursor WM0 latency 12 (1.2 usec)
>[drm:intel_print_wm_latency] Cursor WM1 latency 4 (2.0 usec)
>[drm:intel_print_wm_latency] Cursor WM2 latency 16 (8.0 usec)
>[drm:intel_print_wm_latency] Cursor WM3 latency 64 (32.0 usec)

Actions: View

Attachments on bug 97363: 125813 | 125814 | 126020 | 126021 | 126253

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.