)
Is this with integrated or discrete graphics? Have you tried to bisect
yet?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
)
Can you try bisecting this one?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
the outputs and attach some modes, but they sound
like the wrong ones for your config. Maybe we broke EDID fetching for
your config?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord
Date : 2011-05-31 02:53 (13 days old)
Possibly more DPMS confusion; Chris what's the latest on that?
rocko, did you ever bisect this to a particular commit (sounds like
between .38 and .39)?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send
[cc'ing Chris]
On Wed, 15 Jun 2011 11:48:49 -0700
Jesse Barnes jbar...@virtuousgeek.org wrote:
On Sun, 12 Jun 2011 23:12:10 +0200 (CEST)
Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.38
: Dennis Jansen dennis.jan...@web.de
Date : 2011-06-01 04:41 (12 days old)
Did you ever bisect this issue?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
-28 20:29 (6 days old)
Message-ID: 20110128202905.gb3...@schottelius.org
References: http://marc.info/?l=linux-kernelm=129624657425949w=2
Does this also occur with the drm-intel-next branch? Do you have a
picture of the corruption?
Thanks,
--
Jesse Barnes, Intel Open Source Technology
On Thu, 3 Feb 2011 19:44:12 +0100
Nico Schottelius nico-kernel-20110...@schottelius.org wrote:
Jesse Barnes [Thu, Feb 03, 2011 at 10:11:11AM -0800]:
On Thu, 3 Feb 2011 00:31:29 +0100 (CET)
Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part
: 2010-09-15 14:35 (6 days old)
Message-ID: 4c90d998.6050...@infernix.net
References: http://marc.info/?l=linux-kernelm=128456187928496w=2
Just sent a patch to Matthew and the x86 driver list for this bug.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from
On Sun, 25 Jul 2010 10:54:13 +0800
Kan-Ru Chen ka...@kanru.info wrote:
Hi,
On Sat, 24 Jul 2010 11:19:50 +0200, Enrico Bandiello en...@postal.uv.es
wrote:
On 07/23/2010 07:25 PM, Jesse Barnes wrote:
On Fri, 23 Jul 2010 13:47:31 +0200 (CEST)
Rafael J. Wysockir...@sisk.pl wrote
days old)
Message-ID: 4c26317a.5070...@postal.uv.es
References: http://marc.info/?l=linux-kernelm=127757403404259w=2
Just updated the bug for this one. Enrico, you say this behavior is
recent. Can you bisect between 2.6.34 and when the problem started?
--
Jesse Barnes, Intel Open Source
?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
switch problems for me.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
this is?
Also, what chipset do you have? Maybe I can reproduce it here with
your kernel config.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Fri, 23 Jul 2010 19:50:56 +0200
Tino Keitel tino.kei...@tikei.de wrote:
On Fri, Jul 23, 2010 at 10:33:36 -0700, Jesse Barnes wrote:
[...]
I think this may actually be an X server bug. 2.6.34 introduced some
Hi,
that seems to be not a kernel issue indeed, as at some point I never
with the new code, which could cause clients to hang after VT switch,
waiting to be woken up.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info
. I dunno.
Yeah, this is weird. Norbert, do you still see this? Have you tried
to bisect it?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info
openspace.w...@gmail.com
Date : 2010-06-07 0:23 (32 days old)
Message-ID: aanlktincwmzpnyw3s4uz4k2gon52rpgbibrfzyd01...@mail.gmail.com
References: http://marc.info/?l=linux-kernelm=127587022219378w=2
I thought this one was closed with the revert of the slot symlink?
--
Jesse
On Sun, 04 Jul 2010 20:08:13 +0200
Alexey Fisher bug-tr...@fisher-privat.net wrote:
Hallo all,
i have suspend problem after this patch:
commit 70565d00db6ef5735819db973fa8da95bd34a6ab
Author: Jesse Barnes jbar...@jbarnes-acer.localdomain
Date: Thu Jul 1 04:45:43 2010 -0700
drm
the symlink patch that was causing the trouble. The root
cause is elsewhere though; it seems some firmwares report duplicate PCI
slot numbers...
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body
On Fri, 18 Jun 2010 16:40:44 -0400
Brian Bloniarz b...@athenacr.com wrote:
On 06/18/2010 04:26 PM, David Miller wrote:
From: Jesse Barnes jbar...@virtuousgeek.org
Date: Fri, 18 Jun 2010 13:10:49 -0700
I reverted the symlink patch that was causing the trouble. The root
cause
13:28 (118 days old)
First-Bad-Commit:
http://git.kernel.org/git/linus/27dfaf4f5825a119305db1bc63bef30ed400e376
Handled-By: Zhao Yakui yakui.z...@intel.com
Looks like Yakui just pushed the fix for this one, so hopefully we'll
be able to close it soon.
--
Jesse Barnes, Intel Open Source
On Mon, 8 Feb 2010 12:24:10 -0500
Chris Mason chris.ma...@oracle.com wrote:
On Fri, Feb 05, 2010 at 11:17:47AM -0800, Jesse Barnes wrote:
On Fri, 5 Feb 2010 14:09:16 -0500
Chris Mason chris.ma...@oracle.com wrote:
On Fri, Feb 05, 2010 at 11:01:00AM -0800, Jesse Barnes wrote:
On Mon
On Mon, 8 Feb 2010 01:28:20 +0100 (CET)
Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.31 and 2.6.32.
The following bug entry is on the current list of known regressions
introduced between
On Mon, 8 Feb 2010 15:00:44 -0500
Chris Mason chris.ma...@oracle.com wrote:
On Mon, Feb 08, 2010 at 09:35:51AM -0800, Jesse Barnes wrote:
Ok, updating to rc7 and updating my xf86 driver to 2.10 seems to
have fixed up my suspend/resume problems. So, I should be able
to trigger
toralf.foers...@gmx.de Date : 2010-01-21
08:56 (11 days old) First-Bad-Commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c1c7af60892070e4b82ad63bbfb95ae745056de0
Just updated the bug, looks like another LID status related bug.
--
Jesse Barnes, Intel
On Wed, 27 Jan 2010 22:02:26 -0600
j...@jgarrett.org (Jeff Garrett) wrote:
On Wed, Jan 27, 2010 at 07:24:09PM -0800, Jesse Barnes wrote:
On Wed, 27 Jan 2010 17:50:17 -0800 (PST)
Linus Torvalds torva...@linux-foundation.org wrote:
On Tue, 26 Jan 2010, Yinghai Lu wrote:
[PATCH] x86
of
action (but I'm still pretty sure it's not disable ACPI).
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
already fix
it.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
(18 days old)
Chris, any ideas about this one? I remember seeing a few like this
that have been bisected to 2D driver changes recently...
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message
://marc.info/?l=linux-kernelm=126315457519505w=4
If this isn't fixed yet, I hope David's patch fixes it. See [Bug
#14897] i915: Commit 0e442c60 causes flickering.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body
missing something?
No that's the plan. intel_bus.c was a good effort, but it's just too
different from what Windows does, and it'll always be behind. We'll
disable it for 2.6.33 and try again to move to _CRS in 2.6.34 (but
fixing the problem with large numbers of _CRS resources this time).
--
Jesse
On Wed, 27 Jan 2010 12:59:05 -0800
Jesse Barnes jbar...@virtuousgeek.org wrote:
On Wed, 27 Jan 2010 12:50:12 -0800 (PST)
Linus Torvalds torva...@linux-foundation.org wrote:
On Wed, 27 Jan 2010, Bjorn Helgaas wrote:
Without intel_bus.c, we essentially assume config 1 all
this.
Ok, we'll just kill it entirely then. I'll send a patch tomorrow
unless Yinghai beats me to it.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info
the docs with
the necessary info likely won't be public most of the time.
For 2.6.33 I'd like a minimal fix though, can you disable it for all
but the multi-IOH case perhaps?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel
, so switching that on for 2.6.33 isn't an option.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 12 Jan 2010 18:43:09 +0100
Thomas Meyer tho...@m3y3r.de wrote:
Am Montag, den 11.01.2010, 11:19 -0800 schrieb Jesse Barnes:
On Mon, 11 Jan 2010 20:03:57 +0100
Thomas Meyer tho...@m3y3r.de wrote:
Am 11.01.2010 um 17:55 schrieb Jesse Barnes
jbar...@virtuousgeek.org
:
http://marc.info/?l=linux-kernelm=126037889600769w=4
Still present in 2.6.33-rc3.
Thanks for the update.
David I guess you weren't on the bug cc list so you didn't see Yakui's
question. I just attached a patch to it as well. Please check it out.
Thanks,
--
Jesse Barnes, Intel
to have a workable system.
Does this patch prevent the flicker?
--
Jesse Barnes, Intel Open Source Technology Center
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 9187a17..0ab1bef 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu
On Mon, 11 Jan 2010 20:03:57 +0100
Thomas Meyer tho...@m3y3r.de wrote:
Am 11.01.2010 um 17:55 schrieb Jesse Barnes
jbar...@virtuousgeek.org:
On Mon, 11 Jan 2010 17:53:04 +0100
Thomas Meyer tho...@m3y3r.de wrote:
Am Sonntag, den 10.01.2010, 23:56 +0100 schrieb Rafael J. Wysocki
VTs causes this problem too? Based on your initial
description it sounds like a panic (keyboard LEDs were flashing). If
it happens at VT switch time you should be able to capture the panic
output with netconsole like Linus mentioned.
--
Jesse Barnes, Intel Open Source Technology Center
be racing to queue new work
after the idle call since we suspend GEM at that point, so we must be
failing to manage our active lists properly somehow?
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body
On Tue, 8 Sep 2009 12:26:45 -0700 (PDT)
Linus Torvalds torva...@linux-foundation.org wrote:
On Tue, 8 Sep 2009, Jesse Barnes wrote:
Theoretically i915_gem_idle should prevent any user interrupts from
coming in.
That is _entirely_ immaterial.
The thing is, interrupts can
On Tue, 8 Sep 2009 15:06:21 -0700 (PDT)
Linus Torvalds torva...@linux-foundation.org wrote:
On Tue, 8 Sep 2009, Jesse Barnes wrote:
Yeah, saw that. I don't think that's the root cause though. If we
see a user interrupt after gem_idle is called we may have serious
issues in our
shared ones
just fine as no-ops) at the point where we no longer need them, then
let the DRM core code take care of finally unregistering it.
Ugly, but I'd like to know if it works for you. Any chance you could
give it a try Reinette?
--
Jesse Barnes, Intel Open Source Technology Center
diff
On Tue, 8 Sep 2009 16:36:06 -0700 (PDT)
Linus Torvalds torva...@linux-foundation.org wrote:
On Tue, 8 Sep 2009, Jesse Barnes wrote:
This regression is almost two months old, and apparently the
Intel graphics people DID ABSOLUTELY NOTHING about it during
those two months, because
what I'd expect... ah no I see we don't call the
routine that requires interrupts in that path like I thought.
So Linus's patch is fine with me.
Acked-by: Jesse Barnes jbar...@virtuousgeek.org
Sorry Linus, you were right; I was making this more complicated than it
had to be.
--
Jesse Barnes
)
This no longer occurs right? Maybe it was fixed by
commit cb66c692d1ae257f32dc7f6085cf9cb9f2f6bab8
Author: Ma Ling ling...@intel.com
Date: Sun May 31 16:58:32 2009 +0800
If we can identify the fix we can submit it to the 2.6.30.x stable
series.
--
Jesse Barnes, Intel Open Source
=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7662c8bd6545c12ac7b2b39e4554c3ba34789c50
References:
http://marc.info/?l=linux-kernelm=124820945815030w=4
Handled-By: Jesse Barnes jbar...@virtuousgeek.org
Patch :
http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git
=124851427612720w=4
I probably wasn't clear enough in my last mail about this one. The
errors have always been present, we just report them now. I think this
particular one is harmless, but we should still try to fix it (now that
we have more data about it).
--
Jesse Barnes, Intel Open Source
=14d200c5e5bd19219d930bbb9a5a22758c8f5bec
References :
http://marc.info/?l=linux-kernelm=123523074304955w=4
http://lkml.org/lkml/2009/4/27/317 Handled-By : Jesse Barnes
jbar...@virtuousgeek.org Patch:
http://patchwork.kernel.org/patch/20197/
Still here on 2.6.31-rc1 but...
...this seems to be tied
)
References:
http://marc.info/?l=linux-kernelm=124022460014812w=4
I'm curious about this one... we pushed some display setup related
fixes recently so things should be working well in all configs now
afaik.
Alex can you post your X log?
--
Jesse Barnes, Intel Open Source Technology Center
reproducing it.
--
Jesse Barnes, Intel Open Source Technology Center
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index 69aa0ab..c41cba4 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -341,7 +341,7 @@ int drm_control(struct drm_device *dev, void *data
) References :
http://marc.info/?l=linux-kernelm=124034980819102w=4
Can you elaborate the issues you're seeing with UXA+KMS? EXA had some
breakage in several configs, though it shouldn't have caused gem_idle
warnings (those are real bugs I think).
Cc'ing Eric since this is more his area.
--
Jesse
a bug at
freedesktop.org for this? That way we won't lose it, and we'll have
all the info in one place.
Eric, do you know of any changes recently that might affect the
gem_idle warning Niel sees here? Seems like in any UMS config the GEM
lists should be clear at VT switch time...
--
Jesse
the irq is ok
signal, but we call it at a time when the corresponding pipe is off, so the
kernel ignores the call.
Can you file a bug for this at bugs.freedesktop.org? Is it easy for you to
rebuild test xf86-video-intel driver patches?
Thanks,
--
Jesse Barnes, Intel Open Source Technology
of incorrect mtrr setup and
opregion not working as a result.
I sent one out; it just made the ioremap in i915_initialize into an ioremap_wc
for consistency.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body
On Friday, February 6, 2009 7:05 pm Benjamin Herrenschmidt wrote:
On Fri, 2009-02-06 at 14:45 -0800, Jesse Barnes wrote:
+if (Base = 1024*1024) {
+/* Try legacy_mem (may not be available or implemented) */
+if ((fd = linuxOpenLegacy(dev, legacy_mem)) 0
On Friday, February 6, 2009 2:17 pm Hugh Dickins wrote:
On Fri, 6 Feb 2009, Jesse Barnes wrote:
Hugh, did you get a chance to try my X patch (w/o Ben's patch applied)?
If it also works, we should apply it to X too, if only to make porting to
future platforms a little easier.
I have tried
(): mmap() failure\n);
+ xf86Msg(X_WARNING, xf86MapDomainMem(): mmap() failure: %s\n,
+ strerror(errno));
+ return NULL;
}
return addr;
}
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers
- haven't checked if the patch made it to Linus' tree,
assuming yes.
It's on its way. Just applied it to my for-linus branch.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord
is
loaded, we might have to figure out what to do with the dummy video device
(device 2:1).
So in the long term I think we either need to find a more specific root
cause, or implement a PCI quirk for this quirky machine.
Yeah.
--
Jesse Barnes, Intel Open Source Technology Center
-12 18:42 (11 days old)
References : http://marc.info/?l=linux-kernelm=122651551216820w=4
Handled-By : Jesse Barnes [EMAIL PROTECTED]
I can reproduce this problem on Toshiba Portege R500, with the same
symptoms (please see the bug entry for details).
Well, we have at lease three DRM-related
On Wednesday, September 24, 2008 5:33 pm Jiri Kosina wrote:
On Wed, 24 Sep 2008, Jesse Barnes wrote:
That said, adding a check to the x86 code would be a good thing to do;
I'll hack up a patch tomorrow unless someone beats me to it.
The problem here is that what we desperately need first
On Thursday, September 25, 2008 10:24 am Jiri Kosina wrote:
On Thu, 25 Sep 2008, Frans Pop wrote:
Extra datapoint. As far as I've seen this problem has not yet been
reported by any people running Debian. This could point to X.Org as
Debian currently has 7.3 while I think the reports so far
drivers or the kernel. In fact, in many cases X should be
accessing the RAM copy of the ROM at 0xc rather than via the ROM BAR.
That said, adding a check to the x86 code would be a good thing to do; I'll
hack up a patch tomorrow unless someone beats me to it.
--
Jesse Barnes, Intel Open
be in Linus' tree now.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
[EMAIL PROTECTED]
Patch : http://bugzilla.kernel.org/attachment.cgi?id=17043action=view
Fix pushed to Linus.
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to [EMAIL PROTECTED]
More
69 matches
Mail list logo
