From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15469] [Intel Graphics HD] Kernel panic on boot with certain BIOS options
Date: Sat, 8 May 2010 13:10:36 GMT [thread overview]
Message-ID: <201005081310.o48DAaql007901@demeter.kernel.org> (raw)
In-Reply-To: <bug-15469-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=15469
Artem S. Tashkinov <t.artem@mailcity.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |torvalds@linux-foundation.o
| |rg
--- Comment #7 from Artem S. Tashkinov <t.artem@mailcity.com> 2010-05-07 22:25:07 ---
I hate to be annoying but this time I have to be, because I don't like the idea
of not being able to use all the system memory Intel HD Graphics can
potentially claim and use.
Besides, the next stable kernel is closing in and it will be the second stable
Linux release I won't be able to use without crippling my hardware.
I ain't a Linux kernel expert but these messages seem bogus to me:
> [drm:i915_driver_load] *ERROR* Detected broken video BIOS with 262140/262144kB of video memory stolen.
> [drm:i915_driver_load] *ERROR* Disabling GEM. (try reducing stolen memory or updating the BIOS to fix).
My BIOS is certainly not broken and all future Intel on-die GPUs may use up to
1.7GB(1) of the system RAM.
References:
1. http://www.tomshardware.com/reviews/intel-clarkdale-core-i5-661,2514-4.html
Intel makes up to 1.7GB of system memory available to graphics, as with its
previous-generation integrated graphics core, but there’s really no reason to
dedicate that much RAM in light of the GPU’s performance characteristics.
--- Comment #8 from Daniel Vetter <daniel@ffwll.ch> 2010-05-08 13:10:24 ---
Well, these bios settings _are_ broken. They essentially steel 256MB of system
memory for the intel igd, which has two effects:
- Your usable system memory decreased by 256 (linux can't use this memory).
- You've reduced the memory available to the igd to zero (which then caused the
kernel oops later on).
So please change the bios settings to something sensible (32MB of so called
stolen space is enough) - linux will allocate anything it needs dynamically
anyway. This stolen space is only used to support certain special hw features
that absolutely require it.
I can't close this as "not a bug" due to not having sufficient bz permissions.
Can somebody else please take care of that?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
------------------------------------------------------------------------------
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-05-08 13:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15469-2300@https.bugzilla.kernel.org/>
2010-04-18 11:41 ` [Bug 15469] [Intel Graphics HD] Kernel panic on boot with certain BIOS options bugzilla-daemon
2010-04-21 9:59 ` bugzilla-daemon
2010-05-05 19:20 ` bugzilla-daemon
2010-05-05 19:47 ` bugzilla-daemon
2010-05-05 20:39 ` bugzilla-daemon
2010-05-08 13:10 ` bugzilla-daemon [this message]
2010-05-08 13:40 ` bugzilla-daemon
2010-05-08 21:03 ` bugzilla-daemon
2010-05-09 7:55 ` bugzilla-daemon
2010-05-09 8:49 ` bugzilla-daemon
2010-05-09 21:34 ` bugzilla-daemon
2010-05-10 10:06 ` bugzilla-daemon
2010-05-17 8:29 ` bugzilla-daemon
2010-05-17 14:54 ` bugzilla-daemon
2010-05-17 16:13 ` bugzilla-daemon
2010-05-17 17:27 ` bugzilla-daemon
2010-06-26 22:29 ` bugzilla-daemon
2010-07-05 20:43 ` bugzilla-daemon
2010-07-05 21:01 ` bugzilla-daemon
2010-07-07 21:43 ` bugzilla-daemon
2010-07-08 9:36 ` bugzilla-daemon
2010-07-08 15:59 ` bugzilla-daemon
2010-07-09 5:27 ` bugzilla-daemon
2010-07-09 7:24 ` bugzilla-daemon
2010-07-13 8:33 ` bugzilla-daemon
2010-07-13 15:52 ` bugzilla-daemon
2010-07-23 9:09 ` bugzilla-daemon
2010-07-23 19:36 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201005081310.o48DAaql007901@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.