← Back to team overview

kernel-packages team mailing list archive

[Bug 1443976] [NEW] splash+KMS+radeon causes screen to freeze

 

Public bug reported:

I have Radeon HD 7970 video card and I'm using open source radeon driver.
If I try to boot with kernel parameters "quiet splash", system boots normally at first, splash screen is shown, but when it's time to start X server, screen instead shows garbage (http://s014.radikal.ru/i327/1504/3a/281b75b0ef2d.jpg), turns off and on several times, then shows quickly changing pattern (http://s020.radikal.ru/i704/1504/88/b9d2169bca29.jpg). The system don't respond to Ctrl-Alt-F?, but I still can connect using ssh. "reboot" doesn't work. kern.log has following error messages:

Apr 14 15:01:52 gurren kernel: [   35.081980] [drm:si_dpm_set_power_state] *ERROR* si_restrict_performance_levels_before_switch failed
Apr 14 15:01:59 gurren kernel: [   42.601562] radeon 0000:01:00.0: Saved 193 dwords of commands on ring 0.
Apr 14 15:01:59 gurren kernel: [   42.601606] radeon 0000:01:00.0: GPU softreset: 0x0000016C
Apr 14 15:01:59 gurren kernel: [   42.601608] radeon 0000:01:00.0:   GRBM_STATUS               = 0xA0003028
Apr 14 15:01:59 gurren kernel: [   42.601609] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000006
Apr 14 15:01:59 gurren kernel: [   42.601610] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000006
Apr 14 15:01:59 gurren kernel: [   42.601611] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200206C0
Apr 14 15:01:59 gurren kernel: [   42.601645] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
Apr 14 15:01:59 gurren kernel: [   42.601646] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Apr 14 15:01:59 gurren kernel: [   42.601647] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Apr 14 15:01:59 gurren kernel: [   42.601648] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000802
Apr 14 15:01:59 gurren kernel: [   42.601649] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x800000E3
Apr 14 15:01:59 gurren kernel: [   42.601650] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83506
Apr 14 15:01:59 gurren kernel: [   42.601651] radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   = 0x44E83566
Apr 14 15:01:59 gurren kernel: [   42.601652] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Apr 14 15:01:59 gurren kernel: [   42.601653] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Apr 14 15:02:00 gurren kernel: [   43.280219] radeon 0000:01:00.0: Wait for MC idle timedout !
Apr 14 15:02:00 gurren kernel: [   43.280222] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
Apr 14 15:02:00 gurren kernel: [   43.280273] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100540
Apr 14 15:02:00 gurren kernel: [   43.281420] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003028
Apr 14 15:02:00 gurren kernel: [   43.281421] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000006
Apr 14 15:02:00 gurren kernel: [   43.281422] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000006
Apr 14 15:02:00 gurren kernel: [   43.281423] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200006C0
Apr 14 15:02:00 gurren kernel: [   43.281457] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
Apr 14 15:02:00 gurren kernel: [   43.281458] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Apr 14 15:02:00 gurren kernel: [   43.281459] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Apr 14 15:02:00 gurren kernel: [   43.281460] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
Apr 14 15:02:00 gurren kernel: [   43.281461] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
Apr 14 15:02:00 gurren kernel: [   43.281462] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
Apr 14 15:02:00 gurren kernel: [   43.281463] radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
Apr 14 15:02:00 gurren kernel: [   43.281543] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
Apr 14 15:02:05 gurren kernel: [   48.292813] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Apr 14 15:02:05 gurren kernel: [   48.292816] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C973 (len 254, WS 0, PS 4) @ 0xC99D
Apr 14 15:02:05 gurren kernel: [   48.292817] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C009 (len 106, WS 0, PS 8) @ 0xC05E
Apr 14 15:02:05 gurren kernel: [   48.296773] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
Apr 14 15:02:05 gurren kernel: [   48.296775] [drm] PCIE gen 3 link speeds already enabled
Apr 14 15:02:05 gurren kernel: [   48.558122] radeon 0000:01:00.0: Wait for MC idle timedout !
Apr 14 15:02:05 gurren kernel: [   48.688713] radeon 0000:01:00.0: Wait for MC idle timedout !
Apr 14 15:02:05 gurren kernel: [   48.690354] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
Apr 14 15:02:05 gurren kernel: [   48.690440] radeon 0000:01:00.0: WB enabled
Apr 14 15:02:05 gurren kernel: [   48.690442] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff88020f636c00
Apr 14 15:02:05 gurren kernel: [   48.690443] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff88020f636c04
Apr 14 15:02:05 gurren kernel: [   48.690444] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff88020f636c08
Apr 14 15:02:05 gurren kernel: [   48.690445] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff88020f636c0c
Apr 14 15:02:05 gurren kernel: [   48.690446] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff88020f636c10
Apr 14 15:02:05 gurren kernel: [   48.690813] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90005ab5a18
Apr 14 15:02:05 gurren kernel: [   48.968423] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
Apr 14 15:02:05 gurren kernel: [   48.968425] [drm:si_resume] *ERROR* si startup failed on resume

If I ether add "nomodeset" or remove "splash" from kernel command line
system boots normally.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-34-generic 3.16.0-34.47
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  ranma      5617 F.... pulseaudio
 /dev/snd/controlC1:  ranma      5617 F.... pulseaudio
CurrentDesktop: KDE
Date: Tue Apr 14 16:43:04 2015
IwConfig:
 eth0      no wireless extensions.
 
 lo        no wireless extensions.
MachineType: ASUS All Series
ProcFB:
 0 radeondrmfb
 1 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-34-generic root=UUID=cb5dacd2-d63f-4cf5-a9fa-0ec0f85ec4b4 ro rootflags=subvol=@ drm.debug=0x06
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-34-generic N/A
 linux-backports-modules-3.16.0-34-generic  N/A
 linux-firmware                             1.138.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-10-29 (166 days ago)
dmi.bios.date: 04/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0329
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-C
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0329:bd04/23/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-C:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1443976

Title:
  splash+KMS+radeon causes screen to freeze

Status in linux package in Ubuntu:
  New

Bug description:
  I have Radeon HD 7970 video card and I'm using open source radeon driver.
  If I try to boot with kernel parameters "quiet splash", system boots normally at first, splash screen is shown, but when it's time to start X server, screen instead shows garbage (http://s014.radikal.ru/i327/1504/3a/281b75b0ef2d.jpg), turns off and on several times, then shows quickly changing pattern (http://s020.radikal.ru/i704/1504/88/b9d2169bca29.jpg). The system don't respond to Ctrl-Alt-F?, but I still can connect using ssh. "reboot" doesn't work. kern.log has following error messages:

  Apr 14 15:01:52 gurren kernel: [   35.081980] [drm:si_dpm_set_power_state] *ERROR* si_restrict_performance_levels_before_switch failed
  Apr 14 15:01:59 gurren kernel: [   42.601562] radeon 0000:01:00.0: Saved 193 dwords of commands on ring 0.
  Apr 14 15:01:59 gurren kernel: [   42.601606] radeon 0000:01:00.0: GPU softreset: 0x0000016C
  Apr 14 15:01:59 gurren kernel: [   42.601608] radeon 0000:01:00.0:   GRBM_STATUS               = 0xA0003028
  Apr 14 15:01:59 gurren kernel: [   42.601609] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000006
  Apr 14 15:01:59 gurren kernel: [   42.601610] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000006
  Apr 14 15:01:59 gurren kernel: [   42.601611] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200206C0
  Apr 14 15:01:59 gurren kernel: [   42.601645] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
  Apr 14 15:01:59 gurren kernel: [   42.601646] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
  Apr 14 15:01:59 gurren kernel: [   42.601647] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
  Apr 14 15:01:59 gurren kernel: [   42.601648] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000802
  Apr 14 15:01:59 gurren kernel: [   42.601649] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x800000E3
  Apr 14 15:01:59 gurren kernel: [   42.601650] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83506
  Apr 14 15:01:59 gurren kernel: [   42.601651] radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   = 0x44E83566
  Apr 14 15:01:59 gurren kernel: [   42.601652] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
  Apr 14 15:01:59 gurren kernel: [   42.601653] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
  Apr 14 15:02:00 gurren kernel: [   43.280219] radeon 0000:01:00.0: Wait for MC idle timedout !
  Apr 14 15:02:00 gurren kernel: [   43.280222] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF
  Apr 14 15:02:00 gurren kernel: [   43.280273] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100540
  Apr 14 15:02:00 gurren kernel: [   43.281420] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003028
  Apr 14 15:02:00 gurren kernel: [   43.281421] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000006
  Apr 14 15:02:00 gurren kernel: [   43.281422] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000006
  Apr 14 15:02:00 gurren kernel: [   43.281423] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200006C0
  Apr 14 15:02:00 gurren kernel: [   43.281457] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
  Apr 14 15:02:00 gurren kernel: [   43.281458] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
  Apr 14 15:02:00 gurren kernel: [   43.281459] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
  Apr 14 15:02:00 gurren kernel: [   43.281460] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
  Apr 14 15:02:00 gurren kernel: [   43.281461] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
  Apr 14 15:02:00 gurren kernel: [   43.281462] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
  Apr 14 15:02:00 gurren kernel: [   43.281463] radeon 0000:01:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
  Apr 14 15:02:00 gurren kernel: [   43.281543] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
  Apr 14 15:02:05 gurren kernel: [   48.292813] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
  Apr 14 15:02:05 gurren kernel: [   48.292816] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C973 (len 254, WS 0, PS 4) @ 0xC99D
  Apr 14 15:02:05 gurren kernel: [   48.292817] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C009 (len 106, WS 0, PS 8) @ 0xC05E
  Apr 14 15:02:05 gurren kernel: [   48.296773] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  Apr 14 15:02:05 gurren kernel: [   48.296775] [drm] PCIE gen 3 link speeds already enabled
  Apr 14 15:02:05 gurren kernel: [   48.558122] radeon 0000:01:00.0: Wait for MC idle timedout !
  Apr 14 15:02:05 gurren kernel: [   48.688713] radeon 0000:01:00.0: Wait for MC idle timedout !
  Apr 14 15:02:05 gurren kernel: [   48.690354] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
  Apr 14 15:02:05 gurren kernel: [   48.690440] radeon 0000:01:00.0: WB enabled
  Apr 14 15:02:05 gurren kernel: [   48.690442] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff88020f636c00
  Apr 14 15:02:05 gurren kernel: [   48.690443] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff88020f636c04
  Apr 14 15:02:05 gurren kernel: [   48.690444] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff88020f636c08
  Apr 14 15:02:05 gurren kernel: [   48.690445] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff88020f636c0c
  Apr 14 15:02:05 gurren kernel: [   48.690446] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff88020f636c10
  Apr 14 15:02:05 gurren kernel: [   48.690813] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90005ab5a18
  Apr 14 15:02:05 gurren kernel: [   48.968423] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
  Apr 14 15:02:05 gurren kernel: [   48.968425] [drm:si_resume] *ERROR* si startup failed on resume

  If I ether add "nomodeset" or remove "splash" from kernel command line
  system boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-34-generic 3.16.0-34.47
  ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ranma      5617 F.... pulseaudio
   /dev/snd/controlC1:  ranma      5617 F.... pulseaudio
  CurrentDesktop: KDE
  Date: Tue Apr 14 16:43:04 2015
  IwConfig:
   eth0      no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: ASUS All Series
  ProcFB:
   0 radeondrmfb
   1 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-34-generic root=UUID=cb5dacd2-d63f-4cf5-a9fa-0ec0f85ec4b4 ro rootflags=subvol=@ drm.debug=0x06
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-34-generic N/A
   linux-backports-modules-3.16.0-34-generic  N/A
   linux-firmware                             1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-29 (166 days ago)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0329
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0329:bd04/23/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-C:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443976/+subscriptions


Follow ups

References