On Wed, 9 Feb 2005 07:04:22 +0100
"Jurzitza, Dieter" <[EMAIL PROTECTED]> wrote:
> seing the communication between Jurij and Dave I took a glance into the
> 2.4.29 - tree and found the identical code segment as discussed below. This
> tells me that 2.4.X is supposed to suffer from the same issues
Dear listmembers,
seing the communication between Jurij and Dave I took a glance into the 2.4.29
- tree and found the identical code segment as discussed below. This tells me
that 2.4.X is supposed to suffer from the same issues as you tracked down for
2.6.X, isn't it? However, what I did not fi
On Tue, 2005-02-08 at 17:42 +0100, Georg Chini wrote:
> maybe this is an error in the driver for TGX. My SS5 has a TCX card and
> I had the same problem (screen blank but no X visible).
I've already got your fix applied, it doesn't look to be related. With a
similar patch, I can make the cg3 outp
Tom 'spot' Callaway wrote:
This is being BTFIXEDUP to pte_pfn.
Removing the if (srmmu_device_memory(pte_val(pte))) check stops the
oops, but it doesn't make X work. The screen goes blank, but the X
session never appears.
Hi,
maybe this is an error in the driver for TGX. My SS5 has a TCX card and
On Mon, 7 Feb 2005, David S. Miller wrote:
Yep, and notice that the "extra bit" is (1 << 32), or the first bit
in the upper 32-bits of the 64-bit kernel pointer. In short, we get
garbage from the upper 32-bits of the stack pointer, and need to
mask it out for 32-bit tasks. The fix is obvious, try
