A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
It seems that really there is no one place that one can put code that will
be called ONCE and ONLY ONCE as a thread progresses to
Hi!
Recently I have done some kind of pathologically brain-dead experiment. :)
I have checked out pre-KSE FreeBSD HEAD branch to one of my Intel
servers and allowed to re-build entire -SNAP-type release for my newly
acquired DEC Alpha machine.
Host environment: i386 (Pentium III
I am in the same situation(Jul 8 -current)
From: walt [EMAIL PROTECTED]
Subject: openoffice won't compile on -CURRENT [July 7]
Date: Sun, 07 Jul 2002 16:39:37 -0700
Is openoffice supposed to be okay on -CURRENT these days?
Been two months or so since I tried compiling openoffice on
On Mon, Jul 08, 2002 at 07:28:50PM -0400, Anthony Jenkins wrote:
I finally shelled out Radio Shack's ridiculous amount for a null modem cable
and can do remote debugging now, but I can't remember the URL for that recent
series of articles on getting started with CURRENT debugging...anyone?
On (2002/07/08 13:52), Peter Wemm wrote:
I have found some of them. And what is really scary is that I have
verified that some of what Terry has been FUD'ing(*) about for our TLB
(mis)management is actually correct. :-(
Ha! Justice!
troll
All those who slapped me around on IRC for
Warning
Unable to process data:
multipart/mixed;boundary==_NextPart_000_00Q6_58U79W9Y.ZC11
I found the problem two weeks ago, but I can not find a better way to
avoid userret() to be called twice. so I keep silence. :(
David Xu
Gartner: Apache is vulnerable, we recommend switching back to IIS to protect yourselves
- Original Message -
From: Julian Elischer [EMAIL PROTECTED]
/usr/include/sys/stat.h:127: sizeof applied to an incomplete type
/usr/include/sys/stat.h:128: sizeof applied to an incomplete type
sys/stat.h is broken hat the moment if _POSIX_SOURCE is defined. This
breaks many ports (like gcc295, omniORB, ...).
To Unsubscribe: send mail to [EMAIL
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
On 09-Jul-2002 Julian Elischer wrote:
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
ast() is really a special form of a trap that is triggered by doing
a last-minute type check
On 09-Jul-2002 David Xu wrote:
I found the problem two weeks ago, but I can not find a better way to
avoid userret() to be called twice. so I keep silence. :(
It is only called twice if an AST is posted. It is _not_ always called
twice.
--
John Baldwin [EMAIL PROTECTED]
On 09-Jul-2002 Don Lewis wrote:
I recently started seeing the warning message:
/usr/src/sys/vm/uma_core.c:1332: could sleep with kernel linker locked
from /usr/src/sys/kern/kern_linker.c:1797
at boot time on my -current box. It appears to be related to the
changes in rev 1.90 of
On 09-Jul-2002 John Baldwin wrote:
On 09-Jul-2002 Julian Elischer wrote:
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
ast() is really a special form of a trap that is
On 06-Jul-2002 Julian Elischer wrote:
Well with various hints from here and there I have fixed
the ^Z/fg problem (at least it seems fixed to me and others that
have tested) This basically leaves only one outstanding
problem that I know of which is a problem that Warner has with a
Hello:
Do FreeBSD-5.0 developers plan to implement divert sockets for IPv6
and ip6fw ?
It would be difficult to do it ?
Thanks.
JFRH.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, Jul 02, 2002 at 14:01:35 +0200, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
I just upgrade to recent -current sshd and found that
PasswordAuthentication not works anymore (always fails, with right
password too). I not yet dig deeper at this moment, just
On Monday 2002-July-08 19:47, Don Lewis wrote:
On 8 Jul, Anthony Jenkins wrote:
I've been looking at the pcm code and I can see where it locks, then
allocates memory with the M_WAITOK flag thing. I'm wondering if there's
a standard procedure for fixing these... would I just nail down the
On Tue, Jul 09, 2002 at 16:49:44 +0400, Andrey A. Chernov wrote:
It not helps. Moreover, I found that I am able to do 'ssh localhost' but
unable to do ssh from any other machine, with exact the same password.
DEBUG3 output clearly indicates that this error is related to PAM somehow:
Andrey A. Chernov [EMAIL PROTECTED] writes:
It not helps. Moreover, I found that I am able to do 'ssh localhost' but
unable to do ssh from any other machine, with exact the same password.
Try commenting out the pam_opieaccess line in /etc/pam.d/sshd.
DES
--
Dag-Erling Smorgrav - [EMAIL
On 7 Jul, Kenneth D. Merry wrote:
This happens when ENABLE_VFS_IOOPT is configured by ZERO_COPY_SOCKETS is
not configured.
The attached patch should fix both issues.
Let me know whether this fixes it for you.
Yes, compiles fine here.
Bye,
Alexander.
--
Speak softly and
On Tue, Jul 09, 2002 at 15:16:01 +0200, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
It not helps. Moreover, I found that I am able to do 'ssh localhost' but
unable to do ssh from any other machine, with exact the same password.
Try commenting out the
Andrey A. Chernov [EMAIL PROTECTED] writes:
Normally OPIE not accepts plain Unix password remotely, and it is right,
because of cleartext. But it is wrong for sshd, because no cleartext
sended for PasswordAuth. It seems that opieaccess in pam.d/sshd should not
fails by default or maybe even
On Mon, Jul 08, 2002 at 07:26:26PM -0700, Terry Lambert wrote:
Bernd Walter wrote:
The system g++ 3.1 complains that stdlib.h typedefs wchar_t:
/usr/include/stdlib.h:57: redeclaration of C++ built-in type `wchar_t'
I posted a patch for this already, based on Garrett Wollman's
point about
- Original Message -
From: John Baldwin [EMAIL PROTECTED]
To: John Baldwin [EMAIL PROTECTED]
Cc: FreeBSD current users [EMAIL PROTECTED]; FreeBSD current users
[EMAIL PROTECTED]; Julian Elischer [EMAIL PROTECTED]
Sent: Tuesday, July 09, 2002 8:40 PM
Subject: RE: userret() , ast() and
On Tue, Jul 09, 2002 at 04:08:52PM +0200, Bernd Walter wrote:
On Mon, Jul 08, 2002 at 07:26:26PM -0700, Terry Lambert wrote:
Bernd Walter wrote:
The system g++ 3.1 complains that stdlib.h typedefs wchar_t:
/usr/include/stdlib.h:57: redeclaration of C++ built-in type `wchar_t'
I
Hi,
Ok, I have fixed the bugs and finished it. I tested the functionality and
it seems to work with both IPv4 and IPv6 (and both mixed).
104tcp 0.0.0.0.0.111 portmapper superuser
103tcp 0.0.0.0.0.111 portmapper superuser
10
I was studying the following DEBUG_VFS_LOCKS panic and noticed something
bothersome about the ordering of the code in coredump(). It looked to
me like it made more sense to verify that the file was something that
was valid to dump to before doing the vn_start_write() stuff.
Rearranging the code
OK. How the * do I get a *!@#$@$#% crash dump on current? I
did a dumpon to enable the dumping, which appeared to work. I then
did a savecore after the system came back up (but before any swapping
happened) and that seemed to work. I then tried to use gdb to read
the core dump and got the
I have an idea in regards to the page-zero issue. Presumably we want
to avoid doing an IPI to every cpu to clear the TLB, so what we do
instead is create a lazy TLB clearing mechanism based on the thread.
The scheduler detects the request when it switches the thread in and
In the last episode (Jul 09), M. Warner Losh said:
OK. How the * do I get a *!@#$@$#% crash dump on current? I
did a dumpon to enable the dumping, which appeared to work. I then
did a savecore after the system came back up (but before any swapping
happened) and that seemed to work. I
On Tue, Jul 09, 2002 at 15:59:04 +0200, Dag-Erling Smorgrav wrote:
What if the client is untrusted? Do you find it reasonable to allow
users to type their password on an untrusted client? Many of our
users use OPIE for precisely this scenario - reading their mail on an
untrusted machine in
On Tue, Jul 09, 2002 at 15:59:04 +0200, Dag-Erling Smorgrav wrote:
What if the client is untrusted? Do you find it reasonable to allow
users to type their password on an untrusted client? Many of our
users use OPIE for precisely this scenario - reading their mail on an
untrusted machine in
Normally OPIE not accepts plain Unix password remotely, and it is right,
because of cleartext. But it is wrong for sshd, because no cleartext
sended for PasswordAuth. It seems that opieaccess in pam.d/sshd should not
fails by default or maybe even not present there.
des What if the client is
On 09-Jul-2002 M. Warner Losh wrote:
OK. How the * do I get a *!@#$@$#% crash dump on current? I
did a dumpon to enable the dumping, which appeared to work. I then
did a savecore after the system came back up (but before any swapping
happened) and that seemed to work. I then tried to
The patch corrected the Panic and ACPI loads.
Will it be submitted?
I'll import the latest version of Intel ACPICA shortly. The bug was
fixed already.
One outstanding problem.
When enabling APIC _AND_ having run X11, i get a hang after the line:
Waiting (max 60 seconds) for system
:
: critical_enter();
:*CMAP2 = PG_V | PG_RW | phys | PG_A | PG_M;
:invltlb_1pg((vm_offset_t)CADDR2);
: curthread-td_lazytlb = PCPU_GET(cpumask);
: critical_exit();
:
On Tue, Jul 09, 2002 at 09:46:40 -0700, Gregory Neil Shapiro wrote:
one of the authentication techniques early on). Also, pam_opieaccess is
broken at the moment anyway as /usr/src/contrib/opie/libopie/accessfile.c
is not compiled with PATH_ACCESS_FILE defined. The maintainer of OPIE
ache == Andrey A Chernov [EMAIL PROTECTED] writes:
ache On Tue, Jul 09, 2002 at 09:46:40 -0700, Gregory Neil Shapiro wrote:
one of the authentication techniques early on). Also, pam_opieaccess is
broken at the moment anyway as /usr/src/contrib/opie/libopie/accessfile.c
is not compiled
:
:OK. How the * do I get a *!@#$@$#% crash dump on current? I
:did a dumpon to enable the dumping, which appeared to work. I then
:did a savecore after the system came back up (but before any swapping
:happened) and that seemed to work. I then tried to use gdb to read
:the core dump and
On Tue, 9 Jul 2002, John Baldwin wrote:
If anyone knows of something that was broken by the KSE commit,
(i.e. it worked just before and not after) and is STILL
broken please let me know because I think I can pretty much declare that
chapter finished, and I'd like to get on with
On Tue, 9 Jul 2002, Robert Watson wrote:
On Tue, 9 Jul 2002, John Baldwin wrote:
If anyone knows of something that was broken by the KSE commit,
(i.e. it worked just before and not after) and is STILL
broken please let me know because I think I can pretty much declare that
I'm trying to cleanup the Alpha MD flags and discovered that in KSE-2,
the struct mdthread td_md is in the copy section of struct thread even
though struct mdproc p_md is not (and wasn't before KSE-2 either). Just
curious if this was accidental or intentional? I think mdthread should
not be
On Tue, 9 Jul 2002, John Baldwin wrote:
On 09-Jul-2002 John Baldwin wrote:
On 09-Jul-2002 Julian Elischer wrote:
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
ast() is
Andrey A. Chernov [EMAIL PROTECTED] writes:
I understand that. What I say - it must be not in default setup because
break normal password auth for ssh.
Only for users who have set up an OPIE password, but explicitly choose
not to use OPIE.
I.e. I not set
Andrey A. Chernov [EMAIL PROTECTED] writes:
BTW, OPIE auth broken too that way. In any ssh client I use I see _no_
OPIE prompt like: [...]
You're jinxed. You probably offended an evil spirit in a previous
life and it has come back to haunt you.
Seriously, can you please turn down the
On Wed, 10 Jul 2002, Bruce Evans wrote:
Hopefully there won't be any unconditional code. Unconditional code
in userret() pessimizes all syscalls. Unconditional code added by KSEIII
pessimized basic syscall overhead by 10% according to lmbench2.
Mostly it's conditional..
if
Gosh I did that SOOO long ago (almost a year I guess)
that I really cannot remember..
I think I looked at the fields and decided that since there
weren't any at that time It could probably be in that reagion..
you are right I think..
feel free to shift it.
Matt has since been there.. I can't
Hi
I cant get my NETGEAR MA401 network pccard to work in CURRENT.
I have a Compaq Evo N160 laptop.
Today I saw that the man-page for pcic(4) was updated (v.1.5) and stated
This does not work at all at the moment.
Does this mean that there is no way I can get my pccard to work in CURRENT,
either
Bernd Walter wrote:
On Mon, Jul 08, 2002 at 07:26:26PM -0700, Terry Lambert wrote:
I posted a patch for this already, based on Garrett Wollman's
point about where theings are defined (actually, it requires a
non-definition one up from the one Garrett noted as the problem).
I did a
On Tue, Jul 09, 2002 at 23:42:32 +0200, Dag-Erling Smorgrav wrote:
Seriously, can you please turn down the hysteria a couple of notches
and give me a proper bug report?
On Tue, Jul 09, 2002 at 23:42:32 +0200, Dag-Erling Smorgrav wrote:
Seriously, can you please turn down the hysteria a
Thus spake Gregory Neil Shapiro [EMAIL PROTECTED]:
Interestingly enough, pam_opieaccess doesn't help at all in this
situation. The remote user is still prompted for their plain text
password, it just isn't accepted. However, the damage is already done -- a
compromised ssh client would have
On Wed, Jul 10, 2002 at 03:26:02 +0400, Andrey A. Chernov wrote:
1) It is client-related, so even if you'll fix sshd to print OTP prompt,
This is the question: who print password prompt? By very quick and
incomplete look I see that it is client himself, not server, so it seems
there is no way
On Wed, 10 Jul 2002, Bruce Evans wrote:
On Tue, 9 Jul 2002, Julian Elischer wrote:
On Wed, 10 Jul 2002, Bruce Evans wrote:
Hopefully there won't be any unconditional code. Unconditional code
in userret() pessimizes all syscalls. Unconditional code added by KSEIII
pessimized
On Thu, Jul 04, 2002 at 09:20:38AM -0500, Richard Seaman, Jr. wrote:
On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote:
Something has messed up natd. If I don't have the
punch_fw option in the /etc/natd.conf file it eventuially
core dumps with a bus error. I think
On Wed, 10 Jul 2002, Bruce Evans wrote:
Can these flags be changed asynchronously? If so, then everything needs
to be handled by ast() anyway. userret() should only check for work that
needs doing in the usual case, and hopefully there is none (except for
things like ktrace).
That's an
Dear all,
I'm looking to compile a list of known problems with USB under -current.
If you've got any issues can you please mail me privately.
Thanks,
Joe
p.s. mail me anyway even if you think that I know about it already - ta.
msg40767/pgp0.pgp
Description: PGP signature
John Baldwin writes:
code would be modified to fit this new behaviour, besides this, everywhere
callout_stop() is used need to hold sched_lock and do a mi_switch() and
modify td_flags is also unacceptable, this SMP race should be resolved in
kern_timeout.c.
How would you resolve it
In message: 046701c2279c$2878c4e0$0e81a8c0@gilgamesh
Mauritz Sundell [EMAIL PROTECTED] writes:
: I cant get my NETGEAR MA401 network pccard to work in CURRENT.
Bummer. It works for other people.
: I have a Compaq Evo N160 laptop.
What kind of pccard/cardbus bridge do you have?
:
In message: [EMAIL PROTECTED]
Paul Herman [EMAIL PROTECTED] writes:
: I've got a Linksys WMP11 wireless PCI card. It is recognized under
: -STABLE, but not -CURRENT.
:
: wi_alloc() seems to fail at bus_alloc_resource() while requesting
: I/O memory. I'm not familiar with this part
59 matches
Mail list logo
