Bug 62629 - Screen blanking when copying files to USB/SD-Card ??
Summary: Screen blanking when copying files to USB/SD-Card ??
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-22 10:17 UTC by F. Delente
Modified: 2017-07-24 22:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description F. Delente 2013-03-22 10:17:45 UTC
I have noticed this bug of the driver when I copy a big gob of data to
an USB/SD-Card mounted driver, with vfat filesystem: the screen turns
off, and nothing can turn it on again. I can ssh into the machine,
where everything is still running ok, so it's really a display
problem.

I can turn off the screen with xset dpms force off, it turns back on
again correctly; I can use xscreensaver too.

This is on a Gentoo laptop, with this chipset:

# lspci
00:02.0 VGA compatible controller: Intel Corporation Mobile
GM965/GL960 Integrated Graphics Controller (primary) (rev 03)

I have this in Xorg.0.log:

[    62.133] (II) LoadModule: "intel"
[    62.192] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[    62.235] (II) Module intel: vendor="X.Org Foundation"
[    62.235]    compiled for 1.13.3, module version = 2.21.4
[    62.235]    Module class: X.Org Video Driver
[    62.235]    ABI class: X.Org Video Driver, version 13.1

[    62.241] (--) intel(0): Integrated Graphics Chipset: Intel(R) 965GM

I don't know if any other info in /var/log/Xorg.0.log is relevant.

In /var/log/messages, I found this dump:

Mar 18 07:07:27 slick kernel: [    8.293383] agpgart-intel
0000:00:00.0: Intel 965GM Chipset
Mar 18 07:07:27 slick kernel: [    8.293441] agpgart-intel
0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
Mar 18 07:07:27 slick kernel: [    8.293938] agpgart-intel
0000:00:00.0: detected 8192K stolen memory
Mar 18 07:07:27 slick kernel: [    8.294159] agpgart-intel
0000:00:00.0: AGP aperture is 256M @ 0xe0000000

and also

Mar 19 11:20:51 slick kernel: [  752.186046] WARNING: at
drivers/gpu/drm/i915/intel_display.c:1225 assert_pipe+0x70/0x75
[i915]()
Mar 19 11:20:51 slick kernel: [  752.186049] Hardware name:
EasyNote_BG46-P-042FR
Mar 19 11:20:51 slick kernel: [  752.186051] pipe A assertion failure
(expected on, current off)
Mar 19 11:20:51 slick kernel: [  752.186052] Modules linked in: hidp
rfcomm ipv6 bnep af_packet vboxnetadp(O) vboxnetflt(O) vboxdrv(O)
usb_storage btusb bluetooth i915 snd_hda_codec_realtek arc4 snd_hda_
intel r8169 snd_hda_codec fbcon bitblit iwl3945 softcursor font
i2c_algo_bit snd_hwdep iwlegacy uhci_hcd intel_agp snd_pcm tileblit
snd_page_alloc mac80211 drm_kms_helper snd_timer ehci_hcd snd drm
intel
_gtt usbcore cfg80211 soundcore i2c_core agpgart asus_laptop
usb_common input_polldev sparse_keymap led_class acpi_cpufreq rfkill
psmouse thermal mperf coretemp video processor thermal_sys rtc_cmos
backl
ight microcode battery ac hwmon evdev unix
Mar 19 11:20:51 slick kernel: [  752.186112] Pid: 2649, comm: X
Tainted: G        W  O 3.7.1-tuxonice #1
Mar 19 11:20:51 slick kernel: [  752.186114] Call Trace:
Mar 19 11:20:51 slick kernel: [  752.186120]  [<ffffffff810357ef>]
warn_slowpath_common+0x7e/0x96
Mar 19 11:20:51 slick kernel: [  752.186124]  [<ffffffff8103589b>]
warn_slowpath_fmt+0x41/0x43
Mar 19 11:20:51 slick kernel: [  752.186137]  [<ffffffffa01e3b98>]
assert_pipe+0x70/0x75 [i915]
Mar 19 11:20:51 slick kernel: [  752.186148]  [<ffffffffa01e48aa>]
intel_enable_plane+0x2f/0x70 [i915]
Mar 19 11:20:51 slick kernel: [  752.186160]  [<ffffffffa01e4a2e>]
i9xx_crtc_enable+0x143/0x1a0 [i915]
Mar 19 11:20:51 slick kernel: [  752.186172]  [<ffffffffa01e82ac>]
intel_crtc_update_dpms+0x54/0x6d [i915]
Mar 19 11:20:51 slick kernel: [  752.186184]  [<ffffffffa01e8342>]
intel_encoder_dpms+0x1e/0x20 [i915]
Mar 19 11:20:51 slick kernel: [  752.186196]  [<ffffffffa01e94a0>]
intel_connector_dpms+0x34/0x5a [i915]
Mar 19 11:20:51 slick kernel: [  752.186205]  [<ffffffffa030e034>]
drm_mode_obj_set_property_ioctl+0x181/0x215 [drm]
Mar 19 11:20:51 slick kernel: [  752.186214]  [<ffffffffa030e0f3>]
drm_mode_connector_property_set_ioctl+0x2b/0x2d [drm]
Mar 19 11:20:51 slick kernel: [  752.186221]  [<ffffffffa0300676>]
drm_ioctl+0x2c9/0x38b [drm]
Mar 19 11:20:51 slick kernel: [  752.186225]  [<ffffffff81315549>] ?
_raw_spin_unlock_irq+0x26/0x31
Mar 19 11:20:51 slick kernel: [  752.186233]  [<ffffffffa030e0c8>] ?
drm_mode_obj_set_property_ioctl+0x215/0x215 [drm]
Mar 19 11:20:51 slick kernel: [  752.186237]  [<ffffffff810125cc>] ?
__restore_xstate_sig+0x2dc/0x2e0
Mar 19 11:20:51 slick kernel: [  752.186241]  [<ffffffff810112d8>] ?
__switch_to_xtra+0x145/0x16e
Mar 19 11:20:51 slick kernel: [  752.186245]  [<ffffffff81059641>] ?
set_next_entity+0x3b/0x60
Mar 19 11:20:51 slick kernel: [  752.186249]  [<ffffffff810e1d2c>]
do_vfs_ioctl+0x40d/0x44e
Mar 19 11:20:51 slick kernel: [  752.186252]  [<ffffffff81080993>] ?
do_raw_spin_unlock+0x9/0xd
Mar 19 11:20:51 slick kernel: [  752.186256]  [<ffffffff81040be2>] ?
recalc_sigpending+0x46/0x4a
Mar 19 11:20:51 slick kernel: [  752.186259]  [<ffffffff8104124d>] ?
__set_task_blocked+0x60/0x67
Mar 19 11:20:51 slick kernel: [  752.186262]  [<ffffffff810e1dc6>]
sys_ioctl+0x59/0x7f
Mar 19 11:20:51 slick kernel: [  752.186266]  [<ffffffff8104305c>] ?
sigprocmask+0x5e/0x62
Mar 19 11:20:51 slick kernel: [  752.186270]  [<ffffffff813161ed>]
system_call_fastpath+0x1a/0x1f
Mar 19 11:20:51 slick kernel: [  752.186272] ---[ end trace
d4f758f48e7a9ae1 ]---
Mar 19 11:20:52 slick kernel: [  753.240037] [drm:intel_enable_lvds]
*ERROR* timed out waiting for panel to power on
Comment 1 Daniel Vetter 2013-03-24 13:17:30 UTC
Chris' suspected that this is another variant of the reloc-tree fail, reporter confirmed that 3.8.4 works.

For reference the mailing list thread: http://lists.freedesktop.org/archives/intel-gfx/2013-March/025907.html


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.