I thought one of the SMP developers announced that it was now committed,
yet I haven't seen any commit messages for it ... I'm running the newest
patch, so am waiting for the commit messages before I actually do my next
upgrade ...
Did I mis-read a message from earlier today?
thanks ..
Marc
On Thu, Sep 07, 2000 at 03:11:27AM -0300, The Hermit Hacker wrote:
I thought one of the SMP developers announced that it was now committed,
yet I haven't seen any commit messages for it ... I'm running the newest
patch, so am waiting for the commit messages before I actually do my next
It seems Ryan Shannon wrote:
Any idea how long it will be before the HPT370 support comes to stable?
I'm fairly new to freebsd, so it might not be the wisest maneuver for me
to CVSup to current :)
It is in stable:
|date: 2000/08/22 08:41:28; author: sos; state: Exp; lines: +105 -67
|MFC:
|
Jason Evans writes:
jasone 2000/09/06 18:33:03 PDT
Modified files:
bin/ps print.c
[...]
Nice try, but you didn't fool me. That's the SMP patch, even if the
first change in the first modified file is a spelling fix in a comment
in userland code!
Nice to see it's
On Thu, 7 Sep 2000, Makoto MATSUSHITA wrote:
IIRC, the only file that uses USA_RESIDENT is src/secure/lib/Makefile,
and now it is gone away. Does this change imply that we are free from
defining USA_RESIDENT when building the FreeBSD world ?
I believe so - I'm going to go over the crypto
*ahem* oops... Thanks. :)
Is it still writing in ATA66 mode?
Thanks again,
Ryan
On Thu, 7 Sep 2000, Soren Schmidt wrote:
It seems Ryan Shannon wrote:
Any idea how long it will be before the HPT370 support comes to stable?
I'm fairly new to freebsd, so it might not be the wisest
It seems Ryan Shannon wrote:
*ahem* oops... Thanks. :)
Is it still writing in ATA66 mode?
Well, sortof, I havn't been able to make it go as fast as I want,
even when using HPTs method, thats why it done like it is.
However it does go faster than when using ATA66...
I'm investigating this
Can anyoine give me an idea when Perl 5.6 will be merged from current into
stable?
Real Soon Now(tm).
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
IIRC, the only file that uses USA_RESIDENT is src/secure/lib/Makefile,
and now it is gone away. Does this change imply that we are free from
defining USA_RESIDENT when building the FreeBSD world ?
Moreover, can we also throw USA_RESIDENT variable away from ports ?
I believe we can start
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea -
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
How can I do it?
Piotr Wozniak
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Did you check on the SANE home page whether your scanner is supported?
This is a USB driver and a trivial driver at that, with no vendor
specific code. So I won't be able to help.
Nick
I've quickly thrown together a driver for USB scanners. Unforunately, I
don't have a scanner available
At 6 Sep 2000 18:35:17 -0700,
Jason Evans [EMAIL PROTECTED] wrote:
If you run into issues that appear related to the SMP changes, and they
aren't listed as known issues, please bring them up on the -smp or -current
mailing list.
this breaks building GENERIC kernel.
cc -c -O -pipe -Wall
Original Message
On 9/7/00, 10:51:14 AM, Piotr Woniak [EMAIL PROTECTED]
wrote regarding XFree86:
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea
-
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
How can I do it?
Piotr
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea -
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
Tcl/Tk.
Build X, clean it out. Build Tcl/Tk 8.2. Build X again. You'll have XF86Setup.
BTW - there is no XF86Setup in XFree86-4
Original Message
On 9/7/00, 12:18:07 PM, Mark Murray [EMAIL PROTECTED] wrote regarding
Re: XFree86 :
Hi,
I have installed XFree86 and there is no XF86Setup. Have you any idea
-
why?
I want to increase depth of color and modifing /etc/XF86Config has no
result.
Tcl/Tk.
Build X,
In article [EMAIL PROTECTED] you wrote:
jasone 2000/09/06 18:33:03 PDT
Modified files:
.
1.7 +39 -5 src/sys/i386/include/globals.h
One of the changes is at line 107 :
#define currentldt GLOBAL_LVALUE(currentldt, int)
was changed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 7 Sep 2000, Sheldon Hearn wrote:
It's odd that you should send this STABLE-related report to the -current
mailing list. :-)
Yea, sorry, -current is where I am subscribed, as well as where I
KNOW people pay attention ;) I'll
Hi,
I got this error when trying to build a kernel with USER_LDT and -current
source. Its not a problem because I'm not using it at the moment, I just
thought I'll mention it.
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline
Hi folks,
Just a warning to anyone wanting to try out SMPng -- make sure that you
hdon't have ``linux_enable="YES"'' in /etc/rc.conf.
I got a kernel trap when /etc/rc tried to load the linux module. I
haven't had time to get a panic and backtrace to Marcel, but I thought
I'd send this warning
On Thu, 7 Sep 2000 00:23:22 -0700 (PDT), Kris Kennaway [EMAIL PROTECTED] said:
Moreover, can we also throw USA_RESIDENT variable away from ports ?
Perhaps..I'm not immediately sure.
This is almost certainly not the last patent issue we'll have to deal
with. Unfortunately, it is probably the
Hi,
Here is a patch which will allow init(8) (or rather, any process with
PID 1) to lower the securelevel to 0 when going into single-user
maintenence mode. This has no effect if securelevel is -1.
Feedback welcome -- there may be security implications I'm not aware
of. If this is well
On Thu, 7 Sep 2000, Sheldon Hearn wrote:
Just a warning to anyone wanting to try out SMPng -- make sure that you
hdon't have ``linux_enable="YES"'' in /etc/rc.conf.
I got a kernel trap when /etc/rc tried to load the linux module. I
haven't had time to get a panic and backtrace to Marcel,
On Wed, 6 Sep 2000, Jason Evans wrote:
A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches
have now been committed.
Is it safe to follow src-sys from PRE_SMPNG and everything else as
-current?
--
_ __ ___ ___ ___ ___
On Thu, Sep 07, 2000 at 03:31:06PM -0400, Wesley Morgan wrote:
On Wed, 6 Sep 2000, Jason Evans wrote:
A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches
have now been committed.
Is it safe to follow src-sys from PRE_SMPNG and everything else as
-current?
top and
On Thu, Sep 07, 2000 at 06:33:20PM +0200, Paul Herman wrote:
Here is a patch which will allow init(8) (or rather, any process with
PID 1) to lower the securelevel to 0 when going into single-user
maintenence mode. This has no effect if securelevel is -1.
Feedback welcome -- there may be
In message [EMAIL PROTECTED] The Hermit Hacker
writes:
: sio1: 32 more interrupt-level buffer overflows (total 32)
From the man page:
sio%d: interrupt-level buffer overflow. Problem in the bottom half of
the driver.
This likely means that the bottom half of sio isn't running fast
Jason Evans wrote:
On Thu, Sep 07, 2000 at 03:31:06PM -0400, Wesley Morgan wrote:
On Wed, 6 Sep 2000, Jason Evans wrote:
A static tag, named PRE_SMPNG, was created at 18:00 PDT. The SMP patches
have now been committed.
Is it safe to follow src-sys from PRE_SMPNG and everything
On Thu, 7 Sep 2000, Zach N. Heilig wrote:
On Thu, Sep 07, 2000 at 06:33:20PM +0200, Paul Herman wrote:
Here is a patch which will allow init(8) (or rather, any process with
PID 1) to lower the securelevel to 0 when going into single-user
maintenence mode. This has no effect if
On Thu, 7 Sep 2000, Zach N. Heilig wrote:
On Thu, Sep 07, 2000 at 06:33:20PM +0200, Paul Herman wrote:
Here is a patch which will allow init(8) (or rather, any process with
PID 1) to lower the securelevel to 0 when going into single-user
maintenence mode. This has no effect if
FYI, this is very likely not caused by the heavy weight
interrupt threads, but rather because the interrupt threads can't
be run because the giant lock is held by a process running in the
kernel. Once we get drivers to have their own locking and pulled out
from under the giant lock this
Mark Murray wrote:
BTW - there is no XF86Setup in XFree86-4 yet.
No, but there is xf86cfg, which is even better ;^)
It correctly autodetected both my Monitor and Video card, meaning that I
was able to get maximum performance out of both (proper Modelines).
Though 1962x1440 is pushing it on
On Thursday, 7 September 2000 at 3:11:27 -0300, The Hermit Hacker wrote:
I thought one of the SMP developers announced that it was now committed,
yet I haven't seen any commit messages for it ... I'm running the newest
patch, so am waiting for the commit messages before I actually do my
On Fri, 8 Sep 2000, Greg Lehey wrote:
On Thursday, 7 September 2000 at 3:11:27 -0300, The Hermit Hacker wrote:
I thought one of the SMP developers announced that it was now committed,
yet I haven't seen any commit messages for it ... I'm running the newest
patch, so am waiting for the
On Thursday, 7 September 2000 at 20:06:20 +0900, Motomichi Matsuzaki wrote:
At 6 Sep 2000 18:35:17 -0700,
Jason Evans [EMAIL PROTECTED] wrote:
If you run into issues that appear related to the SMP changes, and they
aren't listed as known issues, please bring them up on the -smp or -current
Just upgraded to -CURRENT as of about noon (EST) today. At reboot
I got a lot of these:
microuptime() went backwards (1.7682417 - 1.997434)
I recall reading in -current earlier this week that someone was
looking for victims getting this. What further information can I provide?
-Steve
To
On Thursday, 7 September 2000 at 17:00:15 -0600, Chuck Paterson wrote:
FYI, this is very likely not caused by the heavy weight
interrupt threads, but rather because the interrupt threads can't
be run because the giant lock is held by a process running in the
kernel. Once we get drivers
Steve Ames wrote:
Just upgraded to -CURRENT as of about noon (EST) today. At reboot
I got a lot of these:
microuptime() went backwards (1.7682417 - 1.997434)
I recall reading in -current earlier this week that someone was
looking for victims getting this. What further information can I
On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote:
Steve Ames wrote:
Just upgraded to -CURRENT as of about noon (EST) today. At reboot
I got a lot of these:
microuptime() went backwards (1.7682417 - 1.997434)
I recall reading in -current earlier this week that someone
Greg Lehey wrote:
On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote:
Steve Ames wrote:
Just upgraded to -CURRENT as of about noon (EST) today. At reboot
I got a lot of these:
microuptime() went backwards (1.7682417 - 1.997434)
I recall reading in -current earlier
On Thu, 7 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] The Hermit Hacker
writes:
: sio1: 32 more interrupt-level buffer overflows (total 32)
From the man page:
sio%d: interrupt-level buffer overflow. Problem in the bottom half of
the driver.
This likely means
On Thursday, 7 September 2000 at 17:48:06 -0700, John Baldwin wrote:
Greg Lehey wrote:
On Thursday, 7 September 2000 at 17:28:02 -0700, John Baldwin wrote:
Steve Ames wrote:
Just upgraded to -CURRENT as of about noon (EST) today. At reboot
I got a lot of these:
microuptime() went
looks like the boot loader is killing -current. I have a patch, but
it just cuts all the offending references.
Comments?
Warner
cc -nostdlib -static -Ttext 0x0 -o loader.sym
/usr/obj/home/imp/FreeBSD/src/sys/boot/i386/loader/../btx/lib/crt0.o main.o conf.o
bcache.o boot.o commands.o
The point I'm making is that we've had these problems before SMPng,
and that you can't automatically assume that it's SMPng just because
you get the messages. On the other hand, the 7 digits seem to be a
pretty reliable signature.
I'm getting this error while starting XFree86 4.0.1 on my
Also, this is interrupt level overflows. We can run the fast
interrupts fast enough to harvest characters from the hardware.
What's not happening is that sio's bottom half isn't being run fast
enough so the interrupt level buffers overflow.
Warner
To Unsubscribe: send mail to [EMAIL
In message [EMAIL PROTECTED] Mike Smith writes:
:
: looks like the boot loader is killing -current. I have a patch, but
: it just cuts all the offending references.
:
: Comments?
:
: rebuild/reinstall libstand. Sorry; should have HEADS-UPped that one.
I can't reinstall libstand. I'm
On Thursday, 7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote:
The point I'm making is that we've had these problems before SMPng,
and that you can't automatically assume that it's SMPng just because
you get the messages. On the other hand, the 7 digits seem to be a
pretty
On Thu, 7 Sep 2000, Warner Losh wrote:
Also, this is interrupt level overflows. We can run the fast
interrupts fast enough to harvest characters from the hardware.
What's not happening is that sio's bottom half isn't being run fast
enough so the interrupt level buffers overflow.
Okay, I'm
On Thu, 7 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] The Hermit Hacker
writes:
: Okay, I'm a little confused here ... from what I'm reading/following, this
: isn't a new problem ... or is it? If not, why has it suddenly manifested
: itself with the new SMP code?
It seems
How do I upgrade it 'with the new kernel', as the UPDATING file
suggests? I've looked at the man pages for loader, and it doesn't suggest
anything ... help?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL
Bruce Evans wrote:
On Thu, 7 Sep 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] The Hermit
Hacker writes:
: sio1: 32 more interrupt-level buffer overflows (total 32)
From the man page:
sio%d: interrupt-level buffer overflow. Problem in the bottom half of
the
In message [EMAIL PROTECTED] John Baldwin writes:
: My guess then is that we aren't scheduling the
: soft interrupt to harvest the data in the top half from the bottom half.
That's what I think as well.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
On Friday, 8 September 2000 at 0:18:07 -0400, Kenneth Wayne Culver wrote:
On Fri, 8 Sep 2000, Greg Lehey wrote:
On Thursday, 7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote:
The point I'm making is that we've had these problems before SMPng,
and that you can't automatically
On Thursday, 7 September 2000 at 22:43:11 -0700, Mike Smith wrote:
Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -
10412, -694583121)y
this is bad.. right ? :-)
Well, at any rate it looks very funny. If this is a laptop, try
building a kernel without apm and
Hi,
[ Bcc'ed to -current ]
Perhaps it was a mistake :) but I took up someone else's cause and
started a thread on -current which now probably belongs on -hackers.
So:
What are the dangers of having init lower the securelevel to 0 when
the system goes into single user? Looking at the
54 matches
Mail list logo
