--- Original message ---
From: Julien Cristau
Pretty sure what you should be looking for is in the kernel, not the X
driver.
I thought this announcement covered the kernel side of things too, which it
then obviously does not. OK, there is hope then. ;-)
--
Bojan
_
On Sun, 2011-10-30 at 16:57 +, Chris Wilson wrote:
> Bugs fixed in this snapshot (compared to 2.16.0)
No hibernation memory corruption fix. Sniff, sniff... :-(
--
Bojan
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freede
--- Original message ---
From: Nicolas Kalkhof
No Idea if all of these params are effective but this works for me on my
lenovo t420 with a i7 2620M.
Out of curiosity, unrelated to this problem and because you have similar
hardware to mine - do repeated hibernate/thaw cycles cause th
On Wed, 2011-10-12 at 14:09 +1100, Bojan Smojver wrote:
> Bug #41705.
Just to follow up on this a bit, I cloned Linus' tree as of today (i.e.
currently staged stuff for 3.2) then pulled Keith's tree
(git://people.freedesktop.org/~keithp/linux drm-intel-next) over the top
and com
On Fri, 2011-10-14 at 12:39 +1100, Bojan Smojver wrote:
> So, I'm going to test this next.
That patch didn't help. Again, the box hung.
--
Bojan
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mai
On Fri, 2011-10-14 at 12:02 +1100, Bojan Smojver wrote:
> Just one more note here.
Forgot - Rafael mentioned that the patch below may help with 64-bit
boxes. So, I'm going to test this next.
-
arch/x86/mm/init.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-
On Fri, 2011-10-14 at 12:14 +1100, Bojan Smojver wrote:
> I still have to test this
With intel_ips removed but with KMS kept, the machine hung on thaw
number three or four, so pretty soon.
I think the best bet is to look into general KMS code. Of course, take
all I say with lots and lots of s
On Tue, 2011-10-11 at 13:31 +0200, Daniel Vetter wrote:
> Another thing to check: Do you have the intel_ips module loaded? If
> so, does the corruption still occur if you never ever load it?
I still have to test this, but with nomodeset, this module is loaded as
well, resulting in no trouble.
Or
On Tue, 2011-09-27 at 16:12 +1000, Bojan Smojver wrote:
> Does anyone have any idea what's causing this? Or better, how to fix
> it? I can confirm that as of kernel 3.1.0-rc7 this is still a problem.
Just one more note here. I tested hibernation/thaw cycles on one of my
old mach
On Wed, 2011-10-12 at 14:09 +1100, Bojan Smojver wrote:
> Bug #41705.
Going off list for a while (way too much info I don't need/cannot grok).
If anything new develops, please let me know through the bug. Thanks.
--
Bojan
___
Intel-gfx mail
On Tue, 2011-10-11 at 13:22 +0200, Daniel Vetter wrote:
> Can you open a bug at fdo with the usual details (dont forget lspci
> -nn) and all the things we've already gathered/tried.
Bug #41705.
--
Bojan
___
Intel-gfx mailing list
Intel-gfx@lists.freed
On Tue, 2011-10-11 at 13:31 +0200, Daniel Vetter wrote:
> Do you have the intel_ips module loaded?
I do.
> If so, does the corruption still occur if you never ever load it?
Will have to test.
--
Bojan
___
Intel-gfx mailing list
Intel-gfx@lists.free
--- Original message ---
From: Daniel Vetter
Another thing to check: Do you have the intel_ips module loaded? If so,
does the corruption still occur if you never ever load it?
Will check in the morning.
--
Bojan
___
Intel-gfx mailing lis
--- Original message ---
From: Daniel Vetter
Ok, this is bug thread is getting a bit unwindy. And I am running low on
ideas. Can you open a bug at fdo with the usual details (dont forget
lspci
-nn) and all the things we've already gathered/tried.
Shall do.
--
Bojan
__
On Tue, 2011-10-11 at 20:42 +1100, Bojan Smojver wrote:
> Shall do.
Sent the files to your e-mail address. Ended in a crash.
--
Bojan
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Tue, 2011-10-11 at 12:39 +0200, Daniel Vetter wrote:
> Probably drop it. This checks for a rather different kind of bug.
OK.
--
Bojan
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--- Original message ---
From: Daniel Vetter
memmap=2M#512M memmap=2M#1024M
added to your boot cmdline?
One question: should I keep the patch thar replaces freeze/thaw with
suspend/resume when testing or not?
--
Bojan
___
Intel-gfx ma
--- Original message ---
From: Daniel Vetter
Ok, we have a new idea. Can you boot your kernel with
memmap=2M#512M memmap=2M#1024M
added to your boot cmdline? Also please attach the full dmesg after
boot (only the boot messages matter) both with and without these
options.
Shall do.
On Mon, 2011-10-10 at 21:37 +1100, Bojan Smojver wrote:
> Let me repeat my tests using nomodeset.
I just repeated 67 hibernate/thaw cycles with nomodeset, which took
almost an hour. I'm writing this e-mail from that thawed session. No
trouble whatsoever.
So, two conclusions:
- the pr
On Mon, 2011-10-10 at 21:12 +1100, Bojan Smojver wrote:
> When I attempted to shut the machine down, it hung and I could see
> more
> kernel traces on the console.
Tried again, but this time I used chvt 2; sleep 1; chvt 1 in the
sequence (this seems to agitate the bug faster). In
On Mon, 2011-10-10 at 21:05 +1100, Bojan Smojver wrote:
> Which may or may not be corruption. Will have to test more.
When I attempted to shut the machine down, it hung and I could see more
kernel traces on the console.
--
Bojan
___
Intel-gfx mail
On Mon, 2011-10-10 at 19:18 +1100, Bojan Smojver wrote:
> I will try and let you know. From what I've seen at some other bugs,
> it helped some people, but not others.
After about 20 cycles, got:
---
[ 173.834896] BUG: unable to handle
On Mon, 2011-10-10 at 09:53 +0200, Daniel Vetter wrote:
> Can you try the patch attached to fdo #40241, i.e.
> https://bugs.freedesktop.org/attachment.cgi?id=50648
>
> I think I have an idea what's going wrong here.
I will try and let you know. From what I've seen at some other bugs, it
helped s
On Mon, 2011-10-10 at 18:15 +1100, Bojan Smojver wrote:
> Will try some more tests, just to confirm whether memory corruption
> thing is still present.
Yes, still present. I did this on my Fedora 15 system with 3.1.0-rc9+
(git pull as of half an hour ago):
echo -n reboot > /sys/power
On Tue, 2011-09-27 at 16:12 +1000, Bojan Smojver wrote:
> I can confirm that as of kernel 3.1.0-rc7 this is still a problem.
Just tried some hibernation loops with 3.1.0-rc9+ and got a hang caused
by one of the GPU threads being busy (claimed that GPU was busy). When I
tried the same w
On Tue, 2011-10-04 at 13:46 +1100, Bojan Smojver wrote:
> So, yeah, for all intents and purposes, I can only reproduce it on
> this system.
If it matters, before I switched to ThinkPad T510, I had a Dell Inspiron
6400, also with Intel graphics. I was then hitting:
https://bugzilla.redh
On Mon, 2011-10-03 at 23:32 -0300, Eugeni Dodonov wrote:
> I was investigating the issue for a couple of weeks, but I was unable
> to reproduce it on any of my machines. Does it only happens only on
> this thinkpad, or you can reproduce it consistently on other machines
> as well?
My other machine
On Tue, 2011-09-27 at 16:12 +1000, Bojan Smojver wrote:
> This problem is covered by various bugs, one of them being:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=37142
>
> At some point there was a "solution" to essentially the same bug (I
> believe http://bugzill
On Tue, 2011-09-27 at 16:12 +1000, Bojan Smojver wrote:
> Does anyone have any idea what's causing this? Or better, how to fix
> it? I can confirm that as of kernel 3.1.0-rc7 this is still a problem.
Anyone?
--
Bojan
___
Intel-gfx mailing
This problem is covered by various bugs, one of them being:
https://bugzilla.kernel.org/show_bug.cgi?id=37142
At some point there was a "solution" to essentially the same bug (I
believe http://bugzilla.kernel.org/show_bug.cgi?id=13811), but the
problem quickly resurfaced.
There are also similar
30 matches
Mail list logo
