Dave Jones wrote:
On Mon, Feb 05, 2007 at 01:56:22PM +0100, Thomas Hellström wrote:
> Dave Jones wrote:
> > On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
> > > On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
> > > > Eric,
> > > > Sorry for the
On Mon, Feb 05, 2007 at 01:56:22PM +0100, Thomas Hellström wrote:
> Dave Jones wrote:
> > On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
> > > On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
> > > > Eric,
> > > > Sorry for the breakage. Can you try the
Dave Jones wrote:
On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
> On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
> > Eric,
> > Sorry for the breakage. Can you try the attached patch and see if it
> > fixes the problem.
> >
> > /Thomas
>
> Thomas,
Dave Jones wrote:
On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
Eric,
Sorry for the breakage. Can you try the attached patch and see if it
fixes the problem.
/Thomas
Thomas,
Thanks!
On Mon, Feb 05, 2007 at 01:56:22PM +0100, Thomas Hellström wrote:
Dave Jones wrote:
On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
Eric,
Sorry for the breakage. Can you try the attached patch
Dave Jones wrote:
On Mon, Feb 05, 2007 at 01:56:22PM +0100, Thomas Hellström wrote:
Dave Jones wrote:
On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
Eric,
Sorry for the breakage. Can you try
On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
> On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
> > Eric,
> > Sorry for the breakage. Can you try the attached patch and see if it
> > fixes the problem.
> >
> > /Thomas
>
> Thomas,
>
> Thanks! That
On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
> Eric,
> Sorry for the breakage. Can you try the attached patch and see if it
> fixes the problem.
>
> /Thomas
Thomas,
Thanks! That seems to fix it:
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt :01:00.0[A] ->
Eric Buddington wrote:
On Sun, Feb 04, 2007 at 10:20:29AM +1100, Dave Airlie wrote:
What AGP chipset do you have? it looks like it might be caused by the
AGP changes for TTM..
lspci:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev
03)
00:01.0 PCI
Eric Buddington wrote:
On Sun, Feb 04, 2007 at 10:20:29AM +1100, Dave Airlie wrote:
What AGP chipset do you have? it looks like it might be caused by the
AGP changes for TTM..
lspci:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev
03)
00:01.0 PCI
On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
Eric,
Sorry for the breakage. Can you try the attached patch and see if it
fixes the problem.
/Thomas
Thomas,
Thanks! That seems to fix it:
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt :01:00.0[A] - GSI 16
On Sun, Feb 04, 2007 at 02:26:59PM -0500, Eric Buddington wrote:
On Sun, Feb 04, 2007 at 11:00:05AM +0100, Thomas Hellstr?m wrote:
Eric,
Sorry for the breakage. Can you try the attached patch and see if it
fixes the problem.
/Thomas
Thomas,
Thanks! That seems to fix
On Sun, Feb 04, 2007 at 10:20:29AM +1100, Dave Airlie wrote:
> What AGP chipset do you have? it looks like it might be caused by the
> AGP changes for TTM..
lspci:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev
03)
00:01.0 PCI bridge: Silicon Integrated Systems
agpgart: Found an AGP 3.5 compliant device at :00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
agpgart: Putting AGP V2 device at :01:00.0 into 1x mode
BUG: unable to handle kernel NULL pointer dereference at
On Sat, Feb 03, 2007 at 04:22:17PM -0500, Lee Revell wrote:
> On 2/3/07, Eric Buddington <[EMAIL PROTECTED]> wrote:
> >EIP:0060:[<>]Tainted: G M VLI
> >EFLAGS: 00013246 (2.6.20-rc6-mm3 #1)
>
> The "M" taint flag indicates that a machine check exception has
> occured. Check
On 2/3/07, Eric Buddington <[EMAIL PROTECTED]> wrote:
EIP:0060:[<>]Tainted: G M VLI
EFLAGS: 00013246 (2.6.20-rc6-mm3 #1)
The "M" taint flag indicates that a machine check exception has
occured. Check your logs for the MCE and make sure the hardware is
OK.
Lee
-
To
While repeatedly recompiling and restarting xorg-server-1.1.1, I
managed to generate the following BUG. Kernel is 2.6.20-rc6-mm3, video card is
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF
(prog-if 00 [VGA])
-Eric
--
BUG: unable
While repeatedly recompiling and restarting xorg-server-1.1.1, I
managed to generate the following BUG. Kernel is 2.6.20-rc6-mm3, video card is
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF
(prog-if 00 [VGA])
-Eric
--
BUG: unable
On 2/3/07, Eric Buddington [EMAIL PROTECTED] wrote:
EIP:0060:[]Tainted: G M VLI
EFLAGS: 00013246 (2.6.20-rc6-mm3 #1)
The M taint flag indicates that a machine check exception has
occured. Check your logs for the MCE and make sure the hardware is
OK.
Lee
-
To unsubscribe
On Sat, Feb 03, 2007 at 04:22:17PM -0500, Lee Revell wrote:
On 2/3/07, Eric Buddington [EMAIL PROTECTED] wrote:
EIP:0060:[]Tainted: G M VLI
EFLAGS: 00013246 (2.6.20-rc6-mm3 #1)
The M taint flag indicates that a machine check exception has
occured. Check your logs for
agpgart: Found an AGP 3.5 compliant device at :00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
agpgart: Putting AGP V2 device at :01:00.0 into 1x mode
BUG: unable to handle kernel NULL pointer dereference at
On Sun, Feb 04, 2007 at 10:20:29AM +1100, Dave Airlie wrote:
What AGP chipset do you have? it looks like it might be caused by the
AGP changes for TTM..
lspci:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev
03)
00:01.0 PCI bridge: Silicon Integrated Systems
22 matches
Mail list logo