>
> Thanks Bruce. It sounds like we'll have to live with this problem for now?
>
For the lack of better ideas, I am just reposting the patch I sent to
Bruce about one year ago. I have been happily using it on all my systems
since then.
Index: su.c
gt; wrote:
>
> On 10-May-2002 Alexander Kabaev wrote:
> > Serial console and remote GDB were working just fine for me ever
> > since that entry has been added to the task SMPng unresolved issues
> > list.
>
> At 115200?
>
> --
>
> John Baldwin &l
Serial console and remote GDB were working just fine for me ever since
that entry has been added to the task SMPng unresolved issues list.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Calling freeenv with the pointerm different from one received from
getenv seldom is a good idea :) Indeed, CURRENT panics with the
following stack trace (patch below fixes that):
_mtx_lock_sleep(c08300e4,0,c03644b1,649,c08300e4) at
_mtx_lock_sleep+0x122
_mtx_lock_flags(c08300e4,0,c03644b1,649,c03
>You could add one, it would be trivial to add a TAILQ_ENTRY to the
>vnode strcture as well as add/remove the nodes from
>the list in the vnode allocation and deallocation code.
I was thinking about mp->mnt_nvnodelist, unless there are compelling
reasons not to trust it.
>Feel ambitious? :)
Feel
Apologies if you will get this message twice. My ISP seems to be
blocked in hub.freebsd.org so I had to use temporary hotmail account.
I found the reason for crashes I was experiencing ever since UMA has
been committed into -CURRENT. Apparently UMA has nothing to do with the
breakage. Th
> 2) Bug is in os delivered gcc but not in port gcc.
>a) port has more or less patches / os gcc has been modified
> --> Didn't someone told they are the same?
GCC from ports uses DWARF2 exception unwinding while GCC in src tree
uses sjlj exceptions. The exception handling code generated
> Do you have a patch for this ?
I do not fully understand the parts of GCC involved, so I need some
time to verify my initial diagnosis and to create a patch. In other
words - not yet :)
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd
This is a case of exception context register getting clobbered in
shared library function call. GCC does not reload it when needed and
this ultimately leads to semi-random word in program memory decremented
by the __cp_pop_exception function. The bug is only triggered under very
specific circums
This is a case of exception context register getting clobbered in
shared library function call. GCC does not reload it when needed and
this ultimately leads to semi-random word in program memory decremented
by the __cp_pop_exception function. The bug is only triggered under very
specific circums
The stack trace below shows exactly the symptoms of the binutils
DT_TEXTREL bug, which has been fixed by the latest vendor import.
Rebuilding world IS NOT ENOUGH to solve the problem. You will need to
rebuild all the incorrect libraries which have been built with broken
binutils before. Libpng is
I had no problem with kernel from February 14, but failed ums probes are
happening very consistently with kernel from Feb 18. Kernels from dates
earlier than Feb 14 failed to attach USB mouse most of the time but
sometimes misteriously managed to work. No configuration was changing
between success
>
> Sorry, no hint by my side, but I can report exactly the same problem
> on an Athlon-C System equipped with a VIA-KT133A chipset.
> (actually it has the same USB controller, so it was expectable)
>
> Riggs
I am seeing the same symptoms while using Microsoft USB mouse with
KT133A-based comp
> no, should I?
Only if you have older libraries with the same names as as ones
installed in /usr/lib/compat. As Ruslan pointed out, existing Makefiles
in lib/compat should take care of that automatically. The change was
added in last September.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
> and I've "made world" a lot of times like that.
> and if I do it by hand as sugested, it doesn;t make any difference
> either.
Just a guess - have you removed existing old libraries from /usr/lib?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of t
My previos mail
a) is missing a Subject
b) contains typo in the patch,
(td ? td->td_proc : NULLi)^ Unwanted 'i' is here
:(
Apologies to everyone again. I was in a bit of a hurry
when sending previos messages.
___
Apologies to everyone who will get this e-mail twice. My previuos
attempt usig different email account has been bounced back by
hub.freebsd.org.
I reported this bug to Julian and he promised to fix it soon. Unfortunately,
that didn't happen yet. In a meantime, I am using
the patch attached.
Of
ECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
E-Mail: Alexander Kabaev <[EMAIL PROTECTED]>
Date: 19-Jul-2001
Time: 07:37:04
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>
> Ciao,
> Sheldon.
Sorry for butting in. Adding new non-portable functionality to solve the problem
which could be adequitely taken care of using existing and well known
techniquies is not appropriate, I completely agree with you on that.
----------
E-Mail: Alexander
L PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
E-Mail: Alexander Kabaev <[EMAIL PROTECTED]>
Date: 21-Apr-2001
Time: 10:49:59
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
201 - 220 of 220 matches
Mail list logo
