o idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
216933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216933
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Be
Hi,
Emmanuel Fleury wrote:
>
> I did investigate a bit further the problem.
>
> When starting X on the laptop, the LCD display blank and stay in this
> state. The network access allowed me to see what was happening. The
> Xorg server is using 80-90% of the CPU power:
>
> PID USER PR NI
Hi,
I did investigate a bit further the problem.
When starting X on the laptop, the LCD display blank and stay in this
state. The network access allowed me to see what was happening. The
Xorg server is using 80-90% of the CPU power:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ CO
Hi all,
Joey Hess wrote:
>
> I haven't been seeing it with x.org 6.9 packages built with recent
> gcc's, but I assume this just means the code has stopped tickling the
> underlying bug in the crusoe code morpher.
My problems had disappeared for a while since Xorg was here. But, since
Xorg 6.9 I a
David Martínez Moreno wrote:
> What happened about the nasty Transmeta bug with X?
> Did you see any changes with new 6.9 packages and/or gcc-4.0?
I haven't been seeing it with x.org 6.9 packages built with recent
gcc's, but I assume this just means the code has stopped tickling the
underlying bu
Hello, Emmanuel, Joey. What happened about the nasty Transmeta bug with
X?
Did you see any changes with new 6.9 packages and/or gcc-4.0?
Best regards,
Ender.
--
Network engineer
Debian Developer
pgpQr0Y43k5WL.pgp
Description: PGP signature
On Wednesday 18 May 2005 14:12, Adam C Powell IV wrote:
> So here is the sample text:
I have included most of the proposed text, but shortened it somewhat as
the link to http://www.cs.auc.dk/~fleury/bug_cms/ IMO provides a very
good overview of details and exceptions. Beside this link, I've only
prietary CMS, making further
fixes unlikely.
For more details, see Debian bug #216933, freedesktop.org bugzilla id
455 (https://bugs.freedesktop.org/show_bug.cgi?id=455) and detailed
technical analysis and a list of known platforms with the bug at
http://www.cs.auc.dk/~fleury/bug_cms/ .
On Fri, 2005
Adam C Powell IV wrote:
I'd be happy to suggest wording for such a section, just let me know.
Please do this and send it to me and CC [EMAIL PROTECTED]
Cheers,
Rob
--
Rob Bradford <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EM
Greetings,
There's a major X stability problem with Transmeta Crusoe CPUs and
Radeon Mobility graphics hardware, discussed in Debian bug 216933, in
X.org bugzilla, and at http://www.cs.auc.dk/~fleury/bug_cms/ . This bug
causes X to crash seemingly randomly at a rate of approximately ever
An attachment named "Upgrade63.exe" was removed from this document as it
constituted a security hazard. If you require this document, please contact
the sender and arrange an alternate means of receiving it.
Microsoft
All Products |
Support |
Search |
Microsoft.com Guide
On Thu, Oct 14, 2004 at 02:29:31PM -0500, Branden Robinson wrote:
> Careless blacklister alert:
>
> <[EMAIL PROTECTED]>: host tardis.ath.cx[202.161.125.100] said: 554 Service
> unavailable; Client host [65.26.182.85] blocked using t1.dnsbl.net.au;
> 65.26.182.85 See
> http://www.dnsbl.
Careless blacklister alert:
<[EMAIL PROTECTED]>: host tardis.ath.cx[202.161.125.100] said: 554 Service
unavailable; Client host [65.26.182.85] blocked using t1.dnsbl.net.au;
65.26.182.85 See
http://www.dnsbl.sorbs.net/cgi-bin/lookup?NAME=65.26.182.85 (in reply to
RCPT TO command)
On Tue, Sep 21, 2004 at 06:51:18PM +1000, Chris Lange wrote:
> I've compiled XFree86 4.3.0 with the following compiler flags,
> -march=i386 -mcpu=i386 -O0 -fomit-frame-pointer -finline-functions,
> and my system has now been running without a hitch for 19 days (i was
> usually getting the "BadLengt
I've been running with current unstable versions of xserver-xfree86-dbg
for long enough to sometimes forget this bug. It's never shown up while
I'm running the -debug binary. This is a great workaround.
I suppose the next step would be to binary search through, building
individual files and eventu
Hi,
I have a laptop with a TM Crusoe TM5800 and ATi mobility M and have been
experiencing this same problem (albeit with Fedora Core 1 -- sorry for
posting here but i haven't found any other mention of it on the web and
thought the info might be handy to others)
I've compiled XFree86 4.3.0 with t
priority 261251 normal
merge 261251 216933
thanks
On Sat, 2004-07-24 at 17:17 +0200, Emmanuel Fleury wrote:
>
> I am hunting a very strange bug (probably hardware related). This bug
> has been reported by several people in bug #234556 as a bug of the
> xlibs package but I think I managed to push
e wondering
if it is your code morphing that is breaking X some how.
You can see the report at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216933
Joey Hess's comments in this bug and the similarity between all the
users having your chips have made me contact you.
The merged bug is at:
h
I'm not a debian user, but I've also got a fujitsu 2110 and have had
this issue with fedora C1, and gentoo 2004.0
gnome get totally hosed but kde seems to behave better. With kde the
mouse leaves artifacts just before a crash and like the rest of you if I
wait for some period of time it seems to
I've got a P2120:
[EMAIL PROTECTED]:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineTMx86
cpu family : 6
model : 4
model name : Transmeta(tm) Crusoe(tm) Processor TM5800
stepping: 3
cpu MHz : 925.007
cache size : 512 KB
fdiv_bug: n
I've been plagued with the BadLength error for sometimes now, and sure
enough I have a P2110. My machine has been quite stable for few years
before this BadLenght things, and I used to use the retinalburn DRI+Xv
patch to watch DVDs (sometimes without the DRI part), and I've never had
problems with
I've been using xserver-xfree86 4.2.1-10 for weeks, and it worked great
until today, when firebird died with a badlength error. Now dropping
back to 4.2.1-2, sigh.
--
see shy jo
signature.asc
Description: Digital signature
I have been experiencing this same error on my sony vaio u1.
It has been happening for at least 2 months.
I am running unstable, and currently have xlibs 4.2.1-15.
Like the others reporting this bug i also has a transmeta cpu.
I have a "ATI Technologies Inc Radeon Mobility M6 LY" video card.
Some
I downgraded the X server to 4.2.1-11, and did not see the problem for
nearly a week, but it has just reared its ugly head again, so that
didn't fix it. I will go back to -10 now..
--
see shy jo
signature.asc
Description: Digital signature
I also see the annoying BadLength/X_ChangeProperty on my p2120/ATI
Radeom M6/XFree86 4.3.0 (Fedora). I've experimented a little, and at one
point I had two displays running simultaneously, one showing the problem
and the other not. This was with two different executables, the standard
one and a
Michel Dänzer wrote:
> > xiTK WARNING(_x_error_handler:215): X error received: 'BadLength (poly
> > request too large or internal Xlib length error)'
>
> xine seems to be able to deal with the error; many (most?) X apps don't
> do any error handling, so AFAIK they get killed by the default libX11
On Wed, 2004-01-21 at 11:16, Christopher Hart wrote:
> So this evening I've hit the bug - 3 times. I'm not doing anything
> special, but I did stumble upon an interesting quark to the problem.
> Xine works after the "crash".
[...]
> xiTK WARNING(_x_error_handler:215): X error received: 'BadLengt
So this evening I've hit the bug - 3 times. I'm not doing anything
special, but I did stumble upon an interesting quark to the problem.
Xine works after the "crash". If I run xclock - I get the the standard:
--- begin paste ---
X Error of failed request: BadLength (poly request too large or
int
On Wed, 2004-01-21 at 01:10, Joey Hess wrote:
> Google has one relevant hit for "BadLength (poly request too large or
> internal Xlib length error) fujitsu":
> http://linuxquestions.org/questions/history/116108
>
> Another Fujitsu P2110, running slackware.
> X began "crashing" after he upgraded f
Google has one relevant hit for "BadLength (poly request too large or
internal Xlib length error) fujitsu":
http://linuxquestions.org/questions/history/116108
Another Fujitsu P2110, running slackware.
X began "crashing" after he upgraded from slackare 9 to 10.
He decided that an ATI patch from h
Tue, 20 Jan skrev Michel Dänzer ned dette:
MD> On Tue, 2004-01-20 at 19:51, Christopher Hart wrote:
>> > > I also started having this problem just this fall. The tranmetta
>> > > code-morphing bug is still plausible, but unless Joe's laptop is
>> > > significantly different from the p2120 a var
Tue, 20 Jan skrev Joey Hess ned dette:
JH> Åsmund Ødegård wrote:
>> just like to tell you that I experience this problem as well. Even when only
>> running a couple of rxvt's and emacs.
>>
>> I have never managed to recover without a reboot though, but thats probably
>> because of impatience...
On Tue, 2004-01-20 at 19:51, Christopher Hart wrote:
> > > I also started having this problem just this fall. The tranmetta
> > > code-morphing bug is still plausible, but unless Joe's laptop is
> > > significantly different from the p2120 a variety of the other components
> > > might be at fault
> > I also started having this problem just this fall. The tranmetta
> > code-morphing bug is still plausible, but unless Joe's laptop is
> > significantly different from the p2120 a variety of the other components
> > might be at fault.
>
> It seems unlikely to me that we all experienced a
Christopher Hart wrote:
> > >
> > > Hardware: laptop, Fujitsu lifebook p2120
> > > x: 4.3.0-0pre1v5, but I had the same problem with the xserver-xfree86 from
> > >sid
>
> The trend continues... I also have a lifebook p2120. However I'm
> running xserver-xfree86: 4.2.1-12.1.
I forget whe
> >
> > Hardware: laptop, Fujitsu lifebook p2120
> > x: 4.3.0-0pre1v5, but I had the same problem with the xserver-xfree86 from
> >sid
The trend continues... I also have a lifebook p2120. However I'm
running xserver-xfree86: 4.2.1-12.1.
> When did you start having the problem? I assume
Åsmund Ødegård wrote:
> just like to tell you that I experience this problem as well. Even when only
> running a couple of rxvt's and emacs.
>
> I have never managed to recover without a reboot though, but thats probably
> because of impatience...
>
> Hardware: laptop, Fujitsu lifebook p2120
> x
Mon, 19 Jan skrev Joey Hess:
> It's almost encouraging to hear that Christopher Hart has the same
> problem I do. I had begun to truely distrust my hardware. I wonder what
> hardware Christopher is using?
[snip]
just like to tell you that I experience this problem as well. Even when only
running
On Mon, 2004-01-19 at 20:26, Joey Hess wrote:
> Joey Hess wrote:
> > So: what if there is a bug in the optimizer, which generates incorrect
> > optimised code for either the X server, or X library, but only
> > sometimes. Some kind of math error might be involved. Once the badly
> > optimised code
Joey Hess wrote:
> So: what if there is a bug in the optimizer, which generates incorrect
> optimised code for either the X server, or X library, but only
> sometimes. Some kind of math error might be involved. Once the badly
> optimised code pops up, it would stay in the cache and this would
> exp
It's almost encouraging to hear that Christopher Hart has the same
problem I do. I had begun to truely distrust my hardware. I wonder what
hardware Christopher is using?
I still see the problem, on a perhaps slightly less frequent basis, but
still every other day or so. I have not managed to corre
Hi,
I've been experiencing this exact problem stochastically as well. Often
it seems that mozilla or mozilla-firebird seem to be the application
that breaks X for me. However it isn't always mozilla that is the
culprit so clearly there may be a link, but its not the problem
directly. As a hacki
On Thu, Nov 06, 2003 at 01:28:59AM +0100, Michel Dänzer wrote:
> On Thu, 2003-11-06 at 01:09, Joey Hess wrote:
> > (FWIW, I can reproduce the problem running X programs such as xterm,
> > from stable, on another computer with the DISPLAY set back to my laptop.)
>
> That would point to the server s
Michel Dänzer wrote:
> On Thu, 2003-11-06 at 01:09, Joey Hess wrote:
> >
> > Perhaps I should try a proprietary X server, a different X driver
> > (VESA)? Or install X in a stable chroot. If I can reproduce the problems
> > in any of those, it would be a hardware or kernel problem, right now my
>
On Thu, 2003-11-06 at 01:09, Joey Hess wrote:
>
> Perhaps I should try a proprietary X server, a different X driver
> (VESA)? Or install X in a stable chroot. If I can reproduce the problems
> in any of those, it would be a hardware or kernel problem, right now my
> money is still on the X server.
Siward wrote:
> here's my 2c , just a long shot ...
> did you consider that it could be a hardware problem,
>e.g. in the videocard ?
> i heard of thermal defects that can do things like this,
>e.g. a cracked solderjoint opening/closing a connection
>depending on temperature
> if yo
Hi Joey,
here's my 2c , just a long shot ...
did you consider that it could be a hardware problem,
e.g. in the videocard ?
i heard of thermal defects that can do things like this,
e.g. a cracked solderjoint opening/closing a connection
depending on temperature
if you take your hard
Processing commands for [EMAIL PROTECTED]:
> tag 216933 - moreinfo
Bug#216933: xlibs: many clients get BadLength error from X_ChangeProperty
request
Tags were: moreinfo
Tags removed: moreinfo
> tag 216933 + help
Bug#216933: xlibs: many clients get BadLength error from X_ChangeProperty
r
tag 216933 - moreinfo
tag 216933 + help
thanks
On Tue, Nov 04, 2003 at 03:35:39PM -0500, Joey Hess wrote:
> I'm not sure why this bug is tagged moreinfo; I have responded to all
> requests for information.
Sorry, it's only tagged that way because I forgot to untag it.
--
G. Branden Robinson
I'm not sure why this bug is tagged moreinfo; I have responded to all
requests for information.
Since I reported the bug, I have begun keeping a log of each occurance,
to try to work out what triggers it. I cannot see a pattern though. Here
is my current log:
26 Oct
fail: 5:10 pm
action: had jus
Damnit, that didn't take long.
[EMAIL PROTECTED]: LD_LIBRARY_PATH=/usr/X11R6/lib/debug/ gdb ./xlogo
GNU gdb 6.0-debian
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it unde
On Sun, Oct 26, 2003 at 06:20:28PM -0500, Joey Hess wrote:
> Breakpoint 9, 0x402bd9b6 in exit () from /lib/libc.so.6
> (gdb) bt
> #0 0x402bd9b6 in exit () from /lib/libc.so.6
> #1 0x40200beb in _XDefaultError (dpy=0x1, event=0x1) at XlibInt.c:2846
> #2 0x40200ce4 in _XError (dpy=0x8054328, rep=0
Branden Robinson wrote:
> On Sun, Oct 26, 2003 at 06:20:28PM -0500, Joey Hess wrote:
> > Breakpoint 9, 0x402bd9b6 in exit () from /lib/libc.so.6
> > (gdb) bt
> > #0 0x402bd9b6 in exit () from /lib/libc.so.6
> > #1 0x40200beb in _XDefaultError (dpy=0x1, event=0x1) at XlibInt.c:2846
> > #2 0x40200
(gdb) b exit
Breakpoint 9 at 0x402bd9b6
(gdb) c
Continuing.
X Error of failed request: BadLength (poly request too large or internal Xlib length
error)
Major opcode of failed request: 18 (X_ChangeProperty)
Serial number of failed request: 29
Current serial number in output stream: 30
Br
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Oct 25, 2003 at 02:01:40PM -0400, Joey Hess wrote:
> > Now I am seeing the X problem go away in the time it takes me to install
> > libxaw7-dbg and start up gdb on xlogo. This is twice now that it has
> > somehow recovered after exhibiting the problem, with me just waiting a
> > little whil
> Now I am seeing the X problem go away in the time it takes me to install
> libxaw7-dbg and start up gdb on xlogo. This is twice now that it has
> somehow recovered after exhibiting the problem, with me just waiting a
> little while in between.
>
> At approximatly 12:42, mozilla-firebird died wit
Now I am seeing the X problem go away in the time it takes me to install
libxaw7-dbg and start up gdb on xlogo. This is twice now that it has
somehow recovered after exhibiting the problem, with me just waiting a
little while in between.
At approximatly 12:42, mozilla-firebird died with the BadLen
Branden Robinson wrote:
> This problem description blows my mind. No matter how hosed the X
> server on :0 (or :1) is, the different instance at :2 should not be
> affected. Unless it's a bug in the source code. But then why don't you
> see this problem from the beginning?
A little birdie is te
Processing commands for [EMAIL PROTECTED]:
> retitle 216933 xlibs: many clients get BadLength error from X_ChangeProperty request
Bug#216933: X_ChangeProperty protocol error
Changed Bug title.
> tag 216933 + moreinfo
Bug#216933: xlibs: many clients get BadLength error from X_ChangePr
retitle 216933 xlibs: many clients get BadLength error from X_ChangeProperty request
tag 216933 + moreinfo
thanks
On Tue, Oct 21, 2003 at 03:46:19PM -0400, Joey Hess wrote:
> This is the problem I mentioned on irc. For the past week, plus or
> minus, X will once or twice a day hose itself. Then si
Package: xlibs
Version: 4.2.1-12.1
Severity: normal
This is the problem I mentioned on irc. For the past week, plus or
minus, X will once or twice a day hose itself. Then simple X programs
all fail to run with the same problem:
[EMAIL PROTECTED]:~>xterm
X Error of failed request: BadLength (poly
62 matches
Mail list logo
