Jesse Barnes wrote:
> An alternative to fixing grub would be to add aliases like you mention,
> and/or change the parser to accept "_" as an alias for " ". Then we
> could leave the sysfs values and string table alone.
Is it already case insensitive?
//Peter
On Thu, 2010-12-09 at 08:21 +0100, Thomas Hellstrom wrote:
> On 12/09/2010 03:26 AM, skeggsb at gmail.com wrote:
> > From: Ben Skeggs
> >
> > Drivers using their own implementation of io_mem_reserve/io_mem_free are
> > likely to store the tracking information for the map in mem.mm_node, so
> > it c
At Thu, 9 Dec 2010 09:18:14 -0800,
Jesse Barnes wrote:
>
> On Wed, 8 Dec 2010 15:30:26 -0800
> Greg KH wrote:
> > What kernel version did these options first show up in? Does any
> > other tools rely on the spaces?
>
> And it's ugly; can't we fix grub instead?
I think renaming connectors is g
2010/12/9 Michel D?nzer :
> On Fre, 2010-12-03 at 16:38 -0500, jglisse at redhat.com wrote:
>> From: Jerome Glisse
>>
>> Forbid allocating buffer bigger than visible VRAM or GTT, also
>> properly set lpfn field.
>>
>> v2 - use max macro
>> ? ?- silence warning
>> v3 - don't explicitly set range li
https://bugzilla.kernel.org/show_bug.cgi?id=24462
--- Comment #9 from Luca Tettamanti 2010-12-09
20:12:05 ---
(In reply to comment #8)
> This patch disables use of the ss fixed ref divide and should fix it.
Yes, taking out that code worked. I'm of course available for further testing
if yo
https://bugs.freedesktop.org/show_bug.cgi?id=30901
--- Comment #4 from Marek Olšák 2010-12-09 19:09:01 PST ---
I've been running Mesa with --enable-gallium-llvm all the time and I don't have
this issue.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are r
https://bugs.freedesktop.org/show_bug.cgi?id=30901
--- Comment #4 from Marek Ol??k 2010-12-09 19:09:01 PST
---
I've been running Mesa with --enable-gallium-llvm all the time and I don't have
this issue.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are
* Chris Wilson (chris at chris-wilson.co.uk) wrote:
> On Wed, 8 Dec 2010 16:10:21 +, David Flynn wrote:
> > This fixes broken EDID reading when using an active DisplayPort to
> > duallink DVI converter. If the AUX CH replier chooses to defer the
> > transaction, a short read occurs and errone
https://bugs.freedesktop.org/show_bug.cgi?id=32272
--- Comment #3 from Marek Olšák 2010-12-09 16:52:56 PST ---
It doesn't work with neither r300g nor llvmpipe nor swrast. I am almost sure it
used to work. Could you please bisect it?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.c
https://bugs.freedesktop.org/show_bug.cgi?id=32272
--- Comment #3 from Marek Ol??k 2010-12-09 16:52:56 PST
---
It doesn't work with neither r300g nor llvmpipe nor swrast. I am almost sure it
used to work. Could you please bisect it?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.
IS_ERR() already implies unlikely(), so it can be omitted here.
Signed-off-by: Tobias Klauser
---
drivers/gpu/drm/ttm/ttm_tt.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index af789dc..fb83a90 100644
---
https://bugs.freedesktop.org/show_bug.cgi?id=32272
--- Comment #2 from Álmos 2010-12-09 15:42:52 PST ---
Created an attachment (id=40971)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40971)
tire smoke in vdrift 2010 release with r300g on an rv350
--
Configure bugmail: https://bugs.freed
https://bugs.freedesktop.org/show_bug.cgi?id=32272
--- Comment #2 from ?lmos 2010-12-09 15:42:52 PST ---
Created an attachment (id=40971)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40971)
tire smoke in vdrift 2010 release with r300g on an rv350
--
Configure bugmail: https://bugs.freed
https://bugs.freedesktop.org/show_bug.cgi?id=32271
--- Comment #2 from Marek Olšák 2010-12-09 14:45:57 PST ---
I wonder if lowering DDX/DDY to SFL makes any difference compared to using a
shader that outputs (0,0,0,1).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
-
https://bugs.freedesktop.org/show_bug.cgi?id=32271
--- Comment #2 from Marek Ol??k 2010-12-09 14:45:57 PST
---
I wonder if lowering DDX/DDY to SFL makes any difference compared to using a
shader that outputs (0,0,0,1).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
https://bugs.freedesktop.org/show_bug.cgi?id=32272
--- Comment #1 from Marek Olšák 2010-12-09 14:33:30 PST ---
Could you please attach a screenshot?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assign
https://bugs.freedesktop.org/show_bug.cgi?id=32272
--- Comment #1 from Marek Ol??k 2010-12-09 14:33:30 PST
---
Could you please attach a screenshot?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assig
Jesse Barnes wrote:
> An alternative to fixing grub would be to add aliases like you mention,
> and/or change the parser to accept "_" as an alias for " ". Then we
> could leave the sysfs values and string table alone.
Is it already case insensitive?
//Peter
https://bugs.freedesktop.org/show_bug.cgi?id=32277
--- Comment #2 from Alban Browaeys 2010-12-09 14:14:53 PST
---
Created an attachment (id=40967)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40967)
valgrind output from such an etracer run which shows the overflow
the overflow happens i
https://bugs.freedesktop.org/show_bug.cgi?id=32277
--- Comment #2 from Alban Browaeys 2010-12-09 14:14:53
PST ---
Created an attachment (id=40967)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40967)
valgrind output from such an etracer run which shows the overflow
the overflow happens i
https://bugs.freedesktop.org/show_bug.cgi?id=32277
--- Comment #1 from Alban Browaeys 2010-12-09 14:11:16 PST
---
Created an attachment (id=40965)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40965)
backtrace of the calloc failure in radeon drm due to this previous corruption
--
Config
https://bugs.freedesktop.org/show_bug.cgi?id=32277
--- Comment #1 from Alban Browaeys 2010-12-09 14:11:16
PST ---
Created an attachment (id=40965)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40965)
backtrace of the calloc failure in radeon drm due to this previous corruption
--
Config
https://bugs.freedesktop.org/show_bug.cgi?id=32277
Summary: overflow in calculate_miptree_layout_r300
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: major
Priority: medium
https://bugs.freedesktop.org/show_bug.cgi?id=32277
Summary: overflow in calculate_miptree_layout_r300
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: major
Priority: medium
https://bugs.freedesktop.org/show_bug.cgi?id=32246
--- Comment #3 from Ian Romanick 2010-12-09 13:42:17 PST
---
This looks a lot like bug #32096. Different driver, but the end of the
backtrace (from _mesa_generate_mipmap to the segfault) is the same.
--
Configure bugmail: https://bugs.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=32246
--- Comment #3 from Ian Romanick 2010-12-09 13:42:17
PST ---
This looks a lot like bug #32096. Different driver, but the end of the
backtrace (from _mesa_generate_mipmap to the segfault) is the same.
--
Configure bugmail: https://bugs.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=32273
Ian Romanick changed:
What|Removed |Added
Status|NEW |ASSIGNED
Keywords|
https://bugs.freedesktop.org/show_bug.cgi?id=32273
Ian Romanick changed:
What|Removed |Added
Status|NEW |ASSIGNED
Keywords|
On Thu, 2010-12-09 at 12:03 -0800, Joe Perches wrote:
> Tobias Klauser sent a patch to remove
> an unnecessary unlikely from drivers/misc/c2port/core.c,
> https://lkml.org/lkml/2010/12/9/199
It seems that Tobias did send all the appropriate patches,
not as a series, but as individual patches to k
Tobias Klauser sent a patch to remove
an unnecessary unlikely from drivers/misc/c2port/core.c,
https://lkml.org/lkml/2010/12/9/199
Here are the other instances treewide.
I think it'd be good if people would, when noticing defects in a
specific subsystem, look for and correct the same defect tree
On Thu, 2010-12-09 at 12:03 -0800, Joe Perches wrote:
> Tobias Klauser sent a patch to remove
> an unnecessary unlikely from drivers/misc/c2port/core.c,
> https://lkml.org/lkml/2010/12/9/199
It seems that Tobias did send all the appropriate patches,
not as a series, but as individual patches to k
https://bugs.freedesktop.org/show_bug.cgi?id=32246
--- Comment #2 from Christopher James Halse Rogers
2010-12-09 12:25:50 PST ---
This is not fixed in mesa up to commit 05e534e6, which includes fd543e1f. The
backtrace remains the same.
--
Configure bugmail: https://bugs.freedesktop.org/userpr
https://bugs.freedesktop.org/show_bug.cgi?id=32246
--- Comment #2 from Christopher James Halse Rogers
2010-12-09 12:25:50 PST ---
This is not fixed in mesa up to commit 05e534e6, which includes fd543e1f. The
backtrace remains the same.
--
Configure bugmail: https://bugs.freedesktop.org/userpr
https://bugzilla.kernel.org/show_bug.cgi?id=24462
--- Comment #9 from Luca Tettamanti 2010-12-09 20:12:05
---
(In reply to comment #8)
> This patch disables use of the ss fixed ref divide and should fix it.
Yes, taking out that code worked. I'm of course available for further testing
if yo
IS_ERR already uses unlikely, remove unlikely from the call sites.
Signed-off-by: Joe Perches
---
drivers/gpu/drm/ttm/ttm_tt.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index af789dc..fb83a90 100644
---
IS_ERR already uses unlikely, remove unlikely from the call sites.
Signed-off-by: Joe Perches
---
drivers/gpu/drm/ttm/ttm_tt.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index af789dc..fb83a90 100644
---
Tobias Klauser sent a patch to remove
an unnecessary unlikely from drivers/misc/c2port/core.c,
https://lkml.org/lkml/2010/12/9/199
Here are the other instances treewide.
I think it'd be good if people would, when noticing defects in a
specific subsystem, look for and correct the same defect tree
On Don, 2010-12-09 at 20:19 +1000, Dave Airlie wrote:
> 2010/12/9 Michel D?nzer :
> > On Fre, 2010-12-03 at 16:38 -0500, jglisse at redhat.com wrote:
> >> From: Jerome Glisse
> >>
> >> Forbid allocating buffer bigger than visible VRAM or GTT, also
> >> properly set lpfn field.
> >>
> >> v2 - use
https://bugs.freedesktop.org/show_bug.cgi?id=32271
Ian Romanick changed:
What|Removed |Added
Platform|Other |All
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=32271
Ian Romanick changed:
What|Removed |Added
Platform|Other |All
CC|
* Chris Wilson (ch...@chris-wilson.co.uk) wrote:
> On Wed, 8 Dec 2010 16:10:21 +, David Flynn wrote:
> > This fixes broken EDID reading when using an active DisplayPort to
> > duallink DVI converter. If the AUX CH replier chooses to defer the
> > transaction, a short read occurs and erroneous
On Fre, 2010-12-03 at 16:38 -0500, jglisse at redhat.com wrote:
> From: Jerome Glisse
>
> Forbid allocating buffer bigger than visible VRAM or GTT, also
> properly set lpfn field.
>
> v2 - use max macro
>- silence warning
> v3 - don't explicitly set range limit
>- use min macro
>
> Cc:
At Thu, 9 Dec 2010 09:18:14 -0800,
Jesse Barnes wrote:
>
> On Wed, 8 Dec 2010 15:30:26 -0800
> Greg KH wrote:
> > What kernel version did these options first show up in? Does any
> > other tools rely on the spaces?
>
> And it's ugly; can't we fix grub instead?
I think renaming connectors is g
https://bugs.freedesktop.org/show_bug.cgi?id=31670
Alain Perrot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=31670
Alain Perrot changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=32273
Summary: assertion fails when starting vdrift 2010 release with
shaders enabled
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Sev
https://bugs.freedesktop.org/show_bug.cgi?id=32273
Summary: assertion fails when starting vdrift 2010 release with
shaders enabled
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Sev
https://bugs.freedesktop.org/show_bug.cgi?id=32272
Summary: tire smoke is solid white in vdrift 2010 release
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
https://bugs.freedesktop.org/show_bug.cgi?id=32272
Summary: tire smoke is solid white in vdrift 2010 release
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
On Wed, 2010-12-08 at 18:14 -0500, Alex Deucher wrote:
> Grub doesn't parse spaces in parameters correctly, so
> this makes it impossible to force video= parameters
> for kms on the grub kernel command line.
I'm sorta tempted to just go the extra step towards DIN, HDMIA, HDMIB,
DP and eDP, typing
https://bugs.freedesktop.org/show_bug.cgi?id=32271
Summary: DDX opcode is not implemented in radeon shader
compiler
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=32271
Summary: DDX opcode is not implemented in radeon shader
compiler
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
On Thu, 09 Dec 2010 20:33:18 +0300
Sergej Pupykin wrote:
> At Thu, 9 Dec 2010 09:18:14 -0800,
> Jesse Barnes wrote:
> >
> > On Wed, 8 Dec 2010 15:30:26 -0800
> > Greg KH wrote:
> > > What kernel version did these options first show up in? Does any
> > > other tools rely on the spaces?
> >
>
On Thu, 09 Dec 2010 20:33:18 +0300
Sergej Pupykin wrote:
> At Thu, 9 Dec 2010 09:18:14 -0800,
> Jesse Barnes wrote:
> >
> > On Wed, 8 Dec 2010 15:30:26 -0800
> > Greg KH wrote:
> > > What kernel version did these options first show up in? Does any
> > > other tools rely on the spaces?
> >
>
On Thu, Dec 9, 2010 at 9:30 AM, Greg KH wrote:
> On Wed, Dec 08, 2010 at 06:14:03PM -0500, Alex Deucher wrote:
>> Grub doesn't parse spaces in parameters correctly, so
>> this makes it impossible to force video= parameters
>> for kms on the grub kernel command line.
>>
>> Reported-by: Sergej Pupyk
On Wed, 8 Dec 2010 15:30:26 -0800
Greg KH wrote:
> On Wed, Dec 08, 2010 at 06:14:03PM -0500, Alex Deucher wrote:
> > Grub doesn't parse spaces in parameters correctly, so
> > this makes it impossible to force video= parameters
> > for kms on the grub kernel command line.
> >
> > Reported-by: Ser
From: Jerome Glisse
Forbid allocating buffer bigger than visible VRAM or GTT, also
properly set lpfn field.
v2 - use max macro
- silence warning
v3 - don't explicitly set range limit
- use min macro
v4 - use max btw GTT & VRAM size
Cc: stable
Signed-off-by: Jerome Glisse
---
drivers/g
On Wed, 8 Dec 2010 15:30:26 -0800
Greg KH wrote:
> On Wed, Dec 08, 2010 at 06:14:03PM -0500, Alex Deucher wrote:
> > Grub doesn't parse spaces in parameters correctly, so
> > this makes it impossible to force video= parameters
> > for kms on the grub kernel command line.
> >
> > Reported-by: Ser
IS_ERR() already implies unlikely(), so it can be omitted here.
Signed-off-by: Tobias Klauser
---
drivers/gpu/drm/ttm/ttm_tt.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
index af789dc..fb83a90 100644
---
The "e" pointer is either NULL or freed when we call
drm_vblank_put(dev, e->pipe) on the error path. Just pass the "pipe"
variable directly instead.
I changed another caller to use "pipe" as well for consistency.
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu
Hi Linus,
didn't see much point in queueing these up for a longer period of time,
they are all fairly small and make sense.
The use after free is from the vblank leak fixing, so since nobody noticed
we probably don't hit the error path so often, the AGP fix is
reported/tested in k.org, and th
2010/12/9 Dave Airlie :
> 2010/12/9 Michel D?nzer :
>> On Fre, 2010-12-03 at 16:38 -0500, jglisse at redhat.com wrote:
>>> From: Jerome Glisse
>>>
>>> Forbid allocating buffer bigger than visible VRAM or GTT, also
>>> properly set lpfn field.
>>>
>>> v2 - use max macro
>>> ? ?- silence warning
>>>
From: Jerome Glisse
Forbid allocating buffer bigger than visible VRAM or GTT, also
properly set lpfn field.
v2 - use max macro
- silence warning
v3 - don't explicitly set range limit
- use min macro
v4 - use max btw GTT & VRAM size
Cc: stable
Signed-off-by: Jerome Glisse
---
drivers/g
2010/12/9 Dave Airlie :
> 2010/12/9 Michel Dänzer :
>> On Fre, 2010-12-03 at 16:38 -0500, jgli...@redhat.com wrote:
>>> From: Jerome Glisse
>>>
>>> Forbid allocating buffer bigger than visible VRAM or GTT, also
>>> properly set lpfn field.
>>>
>>> v2 - use max macro
>>> - silence warning
>>> v3
On Thu, 2010-12-09 at 08:21 +0100, Thomas Hellstrom wrote:
> On 12/09/2010 03:26 AM, skeg...@gmail.com wrote:
> > From: Ben Skeggs
> >
> > Drivers using their own implementation of io_mem_reserve/io_mem_free are
> > likely to store the tracking information for the map in mem.mm_node, so
> > it can'
On Don, 2010-12-09 at 20:19 +1000, Dave Airlie wrote:
> 2010/12/9 Michel Dänzer :
> > On Fre, 2010-12-03 at 16:38 -0500, jgli...@redhat.com wrote:
> >> From: Jerome Glisse
> >>
> >> Forbid allocating buffer bigger than visible VRAM or GTT, also
> >> properly set lpfn field.
> >>
> >> v2 - use max
2010/12/9 Michel Dänzer :
> On Fre, 2010-12-03 at 16:38 -0500, jgli...@redhat.com wrote:
>> From: Jerome Glisse
>>
>> Forbid allocating buffer bigger than visible VRAM or GTT, also
>> properly set lpfn field.
>>
>> v2 - use max macro
>> - silence warning
>> v3 - don't explicitly set range limit
On Fre, 2010-12-03 at 16:38 -0500, jgli...@redhat.com wrote:
> From: Jerome Glisse
>
> Forbid allocating buffer bigger than visible VRAM or GTT, also
> properly set lpfn field.
>
> v2 - use max macro
>- silence warning
> v3 - don't explicitly set range limit
>- use min macro
>
> Cc: st
Hi Linus,
didn't see much point in queueing these up for a longer period of time,
they are all fairly small and make sense.
The use after free is from the vblank leak fixing, so since nobody noticed
we probably don't hit the error path so often, the AGP fix is
reported/tested in k.org, and th
69 matches
Mail list logo
