On Mon, Dec 17, 2001 at 08:55:59PM +, David Hill wrote:
> Hello -
> Currently, if a user logs in using sftp, it does not log that user to the lastlog.
>In my opinion, I think it should log the connection.
>
> Is this how it is supposed to be?
Yes. You only see an entry in last(1) when the
Hi all
Glad to hear that it worked for you.
Just wondering..is your affected motherboard using AMI for BIOS?
Mine is AMI too.
I'll try to submit a PR. Hopefully the fix will be accepted.
kt
On Sun, Dec 16, 2001 at 10:25:52AM -0500, Brian K. White wrote:
>
> - Original Message -
> Fro
Hi all!
I've encountered really awful behavior of my SMC card using
tx driver in FreeBSD 4.3. On 100 Mbps network I get the throughput
just about 200 kBps :-( Colleagues of mine running some PC
based routers have very similar experiences with this driver
(in both 4.3 and 4.4 Rel's) The same card
Hi all!
I'm struggling my FireWire OHCI based card in my notebook.
I'm using driver from DVTS project (that's what I finally
want to have up and running). I'm running FreeBSD 4.4 Release.
dmesg of my machine is in the attachement (using boot -v).
I've already added proper id for my card in both
"make buildworld" doesn't work because src/usr.bin/xinstall/xinstall.c
has a __FBSDID(...) that's not wrapped around with an #ifdef __FBSDID.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I've stumbled on the ACPI_DEBUG issue in the module load as well.
The ACPI_DEBUG definition only propogates to the opt_acpi.h file
in the base kernel. The acpi module build doesn't seem to carry
forward the ACPI_DEBUG flag. As a workaround, I just wack the define
into the opt_acpi.h file in the
Hi!
I'd like to drop the support for the man(1)'s -m option,
which is almost undocumented and is of little interest.
Unless I hear any valid objections, I am going to nuke
it on Friday.
Index: Makefile
===
RCS file: /home/ncvs/src/g
In message <[EMAIL PROTECTED]>, Terry Lambert writes:
>> One nasty bug is that the code for un-exporting filesystems checks
>> to see if the filesystem is among a list of supported types, but
>> the code for exporting doesn't. This list of supported filesystems
>> does not include ext2fs or hpfs,
Soren!
I bet someone else already mentioned your commit broke Alpha kernels.
Index: fd.c
===
RCS file: /home/ncvs/src/sys/isa/fd.c,v
retrieving revision 1.223
diff -u -p -r1.223 fd.c
--- fd.c2001/12/16 05:37:22 1.223
+++
I've been informed that I should upgrade from -stable, not from
-release. I'll keep that in mind the next time I try.
Aside from that hitch, the upgrade to -current worked great:
http://web.nilpotent.org/tmp/dmesg-old.txt
http://web.nilpotent.org/tmp/dmesg-new.txt
Faried.
To Unsubscribe: se
On Tue, Dec 18, 2001 at 11:16:24PM +0459, Faried Nawaz wrote:
>
> I've been informed that I should upgrade from -stable, not from
> -release. I'll keep that in mind the next time I try.
>
> Aside from that hitch, the upgrade to -current worked great:
>
> http://web.nilpotent.org/tmp/dmesg-old.
On 18-Dec-01 Ruslan Ermilov wrote:
> Soren!
>
> I bet someone else already mentioned your commit broke Alpha kernels.
Søren didn't commit this, adn there has already been a discussion on this list
about it as it broke all non-i386 kernels.
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www
On Tue, Dec 18, 2001 at 10:35:39AM -0800, John Baldwin wrote:
>
> On 18-Dec-01 Ruslan Ermilov wrote:
> > Soren!
> >
> > I bet someone else already mentioned your commit broke Alpha kernels.
>
> S?ren didn't commit this, adn there has already been a discussion on this list
> about it as it broke
On Tue, Dec 18, 2001 at 08:09:18PM +0200, Ruslan Ermilov wrote:
s/Soren/Joerg/
And yes, he knows about it.
Wilko
> Soren!
>
> I bet someone else already mentioned your commit broke Alpha kernels.
>
> Index: fd.c
> ===
> RCS file
> Hi all
>
> Glad to hear that it worked for you.
>
> Just wondering..is your affected motherboard using AMI for BIOS?
> Mine is AMI too.
>
> I'll try to submit a PR. Hopefully the fix will be accepted.
A PR that hardwires IRQ 12 probably won't be accepted. Can you look
around the ACPI table
You can define ACPI_DEBUG in the environment before building the kernel,
or when manually building the module, or in /etc/make.conf.
> I've stumbled on the ACPI_DEBUG issue in the module load as well.
> The ACPI_DEBUG definition only propogates to the opt_acpi.h file
> in the base kernel. The
Hi,
On Tue, 18 Dec 2001, Petr Holub wrote:
> Hi all!
>
> I've encountered really awful behavior of my SMC card using
> tx driver in FreeBSD 4.3. On 100 Mbps network I get the throughput
> just about 200 kBps :-( Colleagues of mine running some PC
> based routers have very similar experiences wi
I can reproduce this at will using the following test. Note that the
machine does seem to recover from the error eventually.
(This is with -current patches at: http://apollo.backplane.com/FreeBSD/
However, I do not believe the patches are related to the SCSI bus
p
I might be doing something wrong here, this is my first try at
-CURRENT. Anyway, buildworld fails right at the start after yacc:
-8<-
cd /usr/src/usr.bin/xinstall; make obj; make depend; make all; make DESTDIR=/us
r/obj/usr/src/i386 install
/usr/obj/usr/src/i386/us
>I can reproduce this at will using the following test. Note that the
>machine does seem to recover from the error eventually.
According to the aic7xxx controller, the drive is not completing a
disconnected command. This is very similar to some problems with
some recent IBM firmware ver
Ruslan Ermilov <[EMAIL PROTECTED]> wrote:
> Oops sorry, that was Joerg.
It's fixed now, although i'm still not convinces that using __i386__
is the right thing. If our defines several
constants for _MACHINE_ARCH, they should all be distint for the
various machines. As it seems now, all of the
[Cc peter because he introduced this code]
Hi,
i was trying the following code in -current (basically copied from
vm_zeropage.c), to implement device polling in the idle loop, and
noticed that the process would take all of the CPU time. Being
suspicious that something was wrong with priorities, I
Near the end of fork1():
/*
* If RFSTOPPED not requested, make child runnable and add to
* run queue.
*/
microtime(&(p2->p_stats->p_start));
p2->p_acflag = AFORK;
if ((flags & RFSTOPPED) == 0) {
mtx_lock_spin(&sched_lock);
* Julian Elischer <[EMAIL PROTECTED]> [011218 18:20] wrote:
>
> now, what is to say that the process has not exitted by this stage, and
> been reeped by init (on SMP)
> particularly since between the two is:
>
> /*
> * Preserve synchronization semantics of vfork. If waiting for
On 19-Dec-01 Julian Elischer wrote:
> Near the end of fork1():
> /*
> * If RFSTOPPED not requested, make child runnable and add to
> * run queue.
> */
> microtime(&(p2->p_stats->p_start));
> p2->p_acflag = AFORK;
> if ((flags & RFSTOPPED) =
On 19-Dec-01 John Baldwin wrote:
>> It may be that due to some semantics of teh fork calls
>> you cannot have P_PPWAIT and a process queued to run on the other
>> processor while reparented to init(1) but I can't see it..
>> the result would be that the return value MIGHT be teh pid
>> of a total
On 19-Dec-01 Alfred Perlstein wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [011218 18:20] wrote:
>>
>> now, what is to say that the process has not exitted by this stage, and
>> been reeped by init (on SMP)
>> particularly since between the two is:
>>
>> /*
>> * Preserve sync
* John Baldwin <[EMAIL PROTECTED]> [011218 18:41] wrote:
>
> Actually, it's a bit worse than that. The parent process will sleep on itself
> waiting to be woken up, but when the child exits, it will wake up init
> (p->p_pptr) not the waiting process, so if you do a rfork(..., RFNOWAIT |
> RFPPWA
:
:>I can reproduce this at will using the following test. Note that the
:>machine does seem to recover from the error eventually.
:
:According to the aic7xxx controller, the drive is not completing a
:disconnected command. This is very similar to some problems with
:some recent IBM fir
Yes...you are absolutely correct. 8)
For my case, all that is needed is adding the correct pnp id and let the pnp
driver take care of the rest.
Thanks
kt
On Tue, Dec 18, 2001 at 11:35:33AM -0800, Mike Smith wrote:
> > Hi all
> >
> > Glad to hear that it worked for you.
> >
> > Just wondering.
Michel Oosterhof <[EMAIL PROTECTED]> writes:
> I might be doing something wrong here, this is my first try at
> -CURRENT. Anyway, buildworld fails right at the start after yacc:
It looks like Mark Murray broke xinstall.c in revision 1.45 by adding
__FBSDID() to a build tool. FreeBSD localisms sh
In message <[EMAIL PROTECTED]> "Faried Nawaz" writes:
: "make buildworld" doesn't work because src/usr.bin/xinstall/xinstall.c
: has a __FBSDID(...) that's not wrapped around with an #ifdef __FBSDID.
You are the second person to mention it to me. I've just applied a
fix. Anything else in the up
In message <9voh4s$q07$[EMAIL PROTECTED]> Michel Oosterhof writes:
: I might be doing something wrong here, this is my first try at
: -CURRENT. Anyway, buildworld fails right at the start after yacc:
You are the third person to notice this. I just committed a fix.
Warner
To Unsubscribe: send m
In message <[EMAIL PROTECTED]> Joerg Wunsch writes:
: Cc goes to [EMAIL PROTECTED]: what is the politically correct way to
: distinguish a PC-type architecture (in that case one that uses a
: PC-style RTC memory to store configuration information) from another
: architecture that uses IA32 CPUs (l
In message <[EMAIL PROTECTED]> Mike Barcroft writes:
: > Any suggestions?
:
: I would recommend removing the __FBSD() line locally until this has
: been resolved.
cvsup might be better :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of t
This is the problem:
vfscache781251 49097K 73745K 85234K 24112590 0 64,128,256,2=
56K
The VFS cache is running away. When it hits the 85MB kernel malloc
limit the machine will lockup.
The sbuf usage is also scary:
sbuf1074836 33589K 33590K 85234K 21
Warner Losh <[EMAIL PROTECTED]> writes:
You are the second person to mention it to me. I've just applied a
fix. Anything else in the upgrade path?
No -- there were no other problems.
Thanks,
Faried.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
37 matches
Mail list logo
