| Summary: | Inconsistent Boot Time Error Reported: "Boot Time Error Reported: "drm:i915_gem_init-stolen"" | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Clive <sad_bunny> |
| Component: | DRM/Intel | Assignee: | Alejandro Vilicic <alejandro.vilicich> |
| Status: | CLOSED DUPLICATE | QA Contact: | Seba <sebastian.sanchez33> |
| Severity: | critical | ||
| Priority: | highest | CC: | alejandro.vilicich, jano.vilicic, sebastian.sanchez33, sebavts |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | www.simpleaccess.cl | ||
| Whiteboard: | |||
| i915 platform: | SKL | i915 features: | GEM/Other |
Nope, that error message is just warning you that the BIOS has inconsistently marked up the memory it reserved for the igfx. It is more or less harmless, we disable a small bit of functionality (which does impair powersaving). It does not relate to the system state. Chris, Thank you *very much* for the prompt response. Unfortunately, I am not sure what [if anything] I can do about this. Do you have any suggestions please? Is this a case of look for a new BIOS? No idea where to go next, sorry... Thank you Clive On the other hand, I think we're pretty sure we can't do anything about this. As Chris says, the warning about stolen memory conflict is unrelated to the other symptoms you're seeing. I'm not even quite sure what appears to be the main problem for you. But apparently it's not graphics. Additionally you seem to be running a distro version of i915, called i915_bpo. We don't support that upstream. Finally, here DRM means Direct Rendering Manager. fjjklsdfsjkfvlña<nvklñn *** Bug 98750 has been marked as a duplicate of this bug. *** |
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.
I've just encountered a remarkably interesting error when attempting to boot my computer to run Mint Linux 18.0 (Sarah) 64-Bit. I think I might have a rough idea of the problem [more detail below] but first here is a little information about the platform on which I see this... Hardware: Asus z170i Motherboard / Intel Core i7 6700T CPU / 16Gb RAM / 1Tb Samsung 850 Pro SSD OS Configuration: Windows 10 Pro, 64-Bit / Mint 18.0, 64-Bit - dual-booting using the Mint grub bootloader Hard Drive Configuraiton [Partitions]:- 1. System Reserved [500Mb] 2. C: NTFS Windows primary partition [512Gb] 3. / [16Gb] 4. {swap{ [16Gb] 5. /usr [16Gb] 6. /home [16Gb] 7. /var [16Gb] 8. /tmp [8Gb] 9. /media/local {D:} [357Gb] Observation:- Perform a routine power-on boot into Mint. Either wait for grub to time-out, or select and then press enter for "default" Mint initiation... Screen initially shows the Mint Logo and the row of dots which change between green and white in colour, then the screen clears and I observe [in what I take to be console font] the following text:- [ 1.377121] [drm:i915_gem_init-stolen [i915_bpo]] *ERROR* conflict detected with stolen region: [0xc6000000 - oxc8000000] Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into default mode. Give root password for maintenance (or press Ctrl-D to continue): If I then type in "systemctl reboot" I go back to the Mint Logo, but this time there is a new message displayed centre-screen, immediately beneath the logo, which reads, "Unattended-upgrade in progress during shutdown, sleeping for 5s" But... I have not asked this computer to perform any unattended updates. Pretty much every time I boot Mint, I check "update Manager" and perform necessary updates... I am 99.99999% confident that there were no "background" updates being performed by this system. Having gained access via the root password, if I explore the system I can see a few running processes and that, for example, etc/fstab has not yet been parsed... The Windows 10 partition appears [so far] to be unaffected by this Suspicion:- I wonder if this might actually relate to the Video Driver? [Hence my posting it here...] Specifically, I see the reference which says, "[drm:i915_gem_init-stolen [i915_bpo]]" and I wonder if this in some way relates to the Digital Rights Management functionality built into the HDMI interface? Could there be something between the interaction with the HDMI driver within the Intel Graphics Driver for Linux that is tripping up here? The issue seems to manifest during a "cold boot", i.e. from power up. However, once observed, I am able to circumvent the issue by:- 1. Power recycle reboot 2. Select Windows 10 from the grub menu 3. Let Windows 10 Load 4. Request a reboot 5. Upon reaching the grub menu for a second time, let default [Mint 18.0] load Current high level config as follows:- $ uname -a Linux skylake 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Further System Details:- $ inxi -v6 System: Host: skylake Kernel: 4.4.0-21-generic x86_64 (64 bit gcc: 5.3.1) Desktop: Cinnamon 3.0.7 (Gtk 3.18.9-1ubuntu3.1) dm: mdm Distro: Linux Mint 18 Sarah Machine: Mobo: ASUSTeK model: Z170I PRO GAMING v: Rev X.0x Bios: American Megatrends v: 2002 date: 09/19/2016 CPU: Quad core Intel Core i7-6700T (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 22466 clock speeds: min/max: 800/3600 MHz 1: 799 MHz 2: 1182 MHz 3: 799 MHz 4: 2849 MHz 5: 1580 MHz 6: 2034 MHz 7: 1100 MHz 8: 880 MHz Memory: No dmidecode memory data: try newer kernel. Graphics: Card: Intel Sky Lake Integrated Graphics bus-ID: 00:02.0 chip-ID: 8086:1912 Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1200@59.95hz, 1920x1200@59.95hz GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:a170 Sound: Advanced Linux Sound Architecture v: k4.4.0-21-generic Network: Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 chip-ID: 8086:15b8 IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: f8:32:e4:9a:87:f5 Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter driver: ath10k_pci bus-ID: 04:00.0 chip-ID: 168c:003e IF: wlp4s0 state: down mac: 30:52:cb:21:aa:bf Any suggestions gratefully received... Happy to provide more system information if needed to help with triage... Thank you, C