In message <[EMAIL PROTECTED]>, Giorgos Keramidas writes:
>mdconfig -l stopped working in -current after revision 1.76 of md.c.
>
>I just reverted src/sys/dev/md/md.c to revision 1.76 and removed
>M_WAITOK to let me build a kernel with that version of md.c. Now
>mdconfig correctly lists the open m
On Thu, Jan 23, 2003 at 01:42:58PM +0300, Maxim Konovalov wrote:
> Any objections to a diff below?
We should be moving away from magic numbers to #defined constants, not
the otherway around.
> Index: newfs/newfs.c
> ===
> RCS file:
Sorry, this is probably a stupid question, but:
[riggs] ~ > ll /dev/ds*
crw-rw-rw- 1 root wheel 30, 3 27 Jan 14:46 /dev/dsp0.0
crw-rw-rw- 1 root wheel 30, 0x00010003 27 Jan 10:59 /dev/dsp0.1
crw-rw-rw- 1 root wheel 30, 5 27 Jan 10:59 /dev/dspW0.0
crw-rw-rw- 1 root wheel 30, 0x0
In message <[EMAIL PROTECTED]>, "Thomas E. Zander" write
s:
>Sorry, this is probably a stupid question, but:
>
>[riggs] ~ > ll /dev/ds*
>crw-rw-rw- 1 root wheel 30, 3 27 Jan 14:46 /dev/dsp0.0
>crw-rw-rw- 1 root wheel 30, 0x00010003 27 Jan 10:59 /dev/dsp0.1
>crw-rw-rw- 1 root wheel 30,
At Tue, 21 Jan 2003 23:29:16 + (UTC),
Masafumi NAKANE wrote:
> Well, not so quick. I took another -CURRENT box and the problem was
> not reproduceable on this box. I can't quite figure out what the
> differences between these two boxes are, though.
I think I found the solution.
On HEAD and
On Sun, Jan 26, 2003 at 12:03:47AM -0500, Jeff Roberson wrote:
> I'm about to commit code that will make one of :
>
> options SCHED_4BSD
>
> or
>
> options SCHED_ULE
>
As far as I see, SCHED_ULE scheduler doesn't take advantage of having more
than 1 processor.
During make -j 6 buildworld, and o
On Thu, 23 Jan 2003, Dan Nelson wrote:
> In the last episode (Jan 23), Vincent Poy said:
> > Greetings everyone,
> >
> > With the latest -CURRENTs ever since atleast September 12, 2002
> > that I have tested on several different machines ranging from
> > PII/PIII/PIV Desktop and Notebooks, whene
On 26 Jan 2003, Eric Jones wrote:
> On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
>
> Sorry if this is the second copy, I'm not sure if it went out the first
> time or not
>
> > On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
> > >
> > > /boot/kernel/acpi.ko text=0x2fab4 data=-0x1a8
Hi,
On Mon, 27. Jan 2003, at 9:49 +0100, [EMAIL PROTECTED] wrote
according to [Re: Am I blind? (devfs issue)]:
> >Could somebody explain to me why the device isn't listed in the first
> >ls -l call?
>
> Hehe: welcome to clonable devices :-)
>
> Notice that the major/minor is 3/27 which maps to
On Sun, 26 Jan 2003, Steve Kargl wrote:
> On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
> > On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
> > > >
> > >
> > > Disable acpi. acpi is broken.
> >
> > I had the same problem until today. If ACPI was enabled, I would get a
> > panic on b
On Sun, 26 Jan 2003, Terry Lambert wrote:
> walt wrote:
> > Steve Kargl wrote:
> > > On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
> > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > >
> > > I don't know. I've always used MAXMEM. Guess it's
> > > time t
On 26 Jan 2003, Eric Jones wrote:
> On Sun, 2003-01-26 at 20:55, Terry Lambert wrote:
> > walt wrote:
> > > Steve Kargl wrote:
> > > > On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
> > > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > > >
> > > > I don't
On Sun, Jan 26, 2003 at 03:15:28PM -0800, David O'Brien wrote:
> On Sat, Jan 25, 2003 at 06:50:08PM +0200, Ruslan Ermilov wrote:
> > On Fri, Jan 24, 2003 at 05:54:46PM -0800, Kris Kennaway wrote:
> > > On Fri, Jan 24, 2003 at 02:45:44PM -0800, Kris Kennaway wrote:
> > > > I'm getting this when tryi
Hi,
> So, problem may be in mountd. I tested with reverting the commit at
> 2003/01/15, and it works fine.
There seem to be definitly a problem around. Can you exactly tell
me how you can reproduce it ?
I tried it too and amd still works. I use on both servers a recent
CURRENT and one has amd
Hi,
> I don't know the problem is in amd or mountd. I fear other programs
> are broken with this commit...
Mounting nfs volumes manually works, as other services work fine.
I also tested other rpc-service and they seem to be fine. So we
have to find out why mountd replies twice.
With the commi
At Mon, 27 Jan 2003 11:21:54 +0100 (CET),
Martin Blapp wrote:
> There seem to be definitly a problem around. Can you exactly tell
> me how you can reproduce it ?
Hmm, sorry for my little description.
> I tried it too and amd still works. I use on both servers a recent
> CURRENT and one has amd ru
Hi,
> In my environment, server is 5.0-RELEASE and client is HEAD as of Jan
> 20th. Both have nfsd, rpc.lockd, rpc.statd and nfs client.
Just tried to reproduce it again.
I'm not able to reproduce it :-(
Can you try to cvsup on both boxes and then manually rebuild
libc, mountd, rpcbind, nfsd.
At Mon, 27 Jan 2003 11:58:34 +0100 (CET),
Martin Blapp wrote:
> Can you try to cvsup on both boxes and then manually rebuild
> libc, mountd, rpcbind, nfsd.
Hmm, 5.0-RELEASE box is difficult to upgrade to HEAD.
I'll try to update my box to the latest of HEAD tomorrow.
--
Jun Kuriyama <[EMAIL PR
On Sun, Jan 26, 2003 at 04:08:31PM +0800, Greg Lehey wrote:
> On Sunday, 26 January 2003 at 14:24:02 +1030, Daniel O'Connor wrote:
> > On Sun, 2003-01-26 at 08:08, David Schultz wrote:
> >> Good. I was referring to IDE in this case, because I assume
> >> that's what Greg's laptop uses. The ATA dr
Thus spake Maxim Konovalov <[EMAIL PROTECTED]>:
> newfs(8) incorrectly claims that FS_OPTTIME is unavailable when
> minfree is less than MINFREE. MINFREE is defined in ufs/ffs/fs.h:
>
> #define MINFREE 8
>
> But relevant code in ufs/ffs/ffs_alloc.c uses hardcoded value:
>
> 288 if (fs->
Hello!
because my old (-stable) harddisk was broken (bad sectors)
i've done the switch to -current earlier as i wanted.
now if i want to copy everything what possible from my old disk.
but when i cd into a directory or read a file which is not readable
my pc is doing this:
first i get these me
Thus spake Greg Lehey <[EMAIL PROTECTED]>:
> I've been thinking about what happened, and I have a possibility: the
> session before shutdown included a lot of writing to that file system,
> and I did a shutdown -p. It's possible that the shutdown powered off
> the system before the disk had flush
Seems like it's typo in src/UPDATING about acpi disabling.
Can somebody fix it?
--- UPDATING.orig Mon Jan 27 14:14:12 2003
+++ UPDATINGMon Jan 27 14:07:50 2003
@@ -290,7 +290,7 @@
20010927:
Some weird problems result from using ACPI on some machines.
To disable ACPI you
===> if_tap
rm -f opt_devfs.h opt_inet.h vnode_if.h /usr/src/sys/modules/if_tap/export_syms
if_tap.ko if_tap.kld if_tap.o @ machine symb.tmp tmp.o opt_inet.h vnode_if.h
rm -f .depend GPATH GRTAGS GSYMS GTAGS
===> if_tun
rm -f /usr/src/sys/modules/if_tun/export_syms if_tun.ko if_tun.kld if_tun.o @
The correct files/patch-an for the port mysql 3.23.55:
--- Makefile.in.origThu Dec 5 10:37:22 2002
+++ Makefile.in Sat Dec 14 16:24:26 2002
@@ -195,10 +195,11 @@
EXTRA_DIST = INSTALL-SOURCE README \
COPYING COPYING.LIB MIRRORS
-SUBDIRS = . include @docs_dirs@ @readli
Hi,
> s->c MOUNT V1 EXPORT Reply (duplicate)
I suspect timeouts or packet loss cause this together with
the new nonblock code change.
I just tried V2 (mountd -2) and amd with -2 option. The
bug does not appear.
If possible I'd like to reproduce packet loss with dummynet,
has anyone the necessa
[EMAIL PROTECTED] wrote:
>
> In message <[EMAIL PROTECTED]>, "Peter Edwards" writes:
>
> >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process
> >has its P_CONTROLT flag set, then it's session has a valid vnode for it's
> >controlling terminal. This doesn't hold if the
In message <[EMAIL PROTECTED]>, "Peter Edwards" writes:
>> >The problem is in kern/tty_tty.c:ctty_clone. It's assuming that if the process
>> >has its P_CONTROLT flag set, then it's session has a valid vnode for it's
>> >controlling terminal. This doesn't hold if the terminal was revoked.
>Yes, t
Dear Hackers,
During the testing process for the new in-kernel RFCOMM Bluetooth
code my not so -current panic()ed with the trace below. This panic
happend while ~2MB FTP transfer (PPP over new RFCOMM over
Bluetooth).
A little detail - new RFCOMM code opens L2CAP sockets from inside
kernel (very m
I'm getting the following error when I try and start X. I just built 5.0
and had x working untill I portupgraded gnome2. I have rebuilt wrapper,
and freetype2. I have also re-run xf86config. No one can start x, not
root, nor a regular user. Is this a font path problem? if so what should I
try?
Tha
I am getting LORs on my ThinkPad 600e running current of 1/24. I don't
know if these have been previously reported, so I thought I'd send
them in.
lock order reversal
1st 0xc20193f8 process lock (process lock) @ /scratch/src/sys/kern/kern_descrip.c:2104
2nd 0xc1ff7934 filedesc structure (filedes
On Jan 27, Scott Sipe wrote:
>
> This defaulted to 1 ony my Current--is there a reason for this? I like
> being able to press the power putton and have it shutdown properly, or have
> shutdown -p power down.
Hello Scott,
When it's 0, it's prevents some rogue machines from
mysteri
Hi all,
I've just installed my first 5.0-rel system and did some
"torture-testing". When resetting the machine to test the backgrounded
fsck I experienced the following problem:
All filesystems came back quickly and bg fsck worked fine, except for
one. I had created a large (>50GB) /export filesys
Kris Kennaway <[EMAIL PROTECTED]> writes:
> I've just updated bento to 5.0, and sshd is now giving the following
> error every few seconds:
>
> bento sshd[55737]: in _openpam_check_error_code():
> pam_sm_setcred(): unexpected return value 24
>
> Peter says he's seen this elsewhere on the cluster.
Hi,
I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now
everything seems OK, but my sound card. In the handbook they say I must
use the MAKEDEV script (as in Linux) but I can't find it on my disk.
I tried to download it with the sysinstall tool but again there seems to
be no pac
On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote:
> Hi,
>
> I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now
> everything seems OK, but my sound card. In the handbook they say I must
> use the MAKEDEV script (as in Linux) but I can't find it on my disk.
> I tried to
On Mon, Jan 27, 2003 at 09:14:36PM +0100, FredBriand wrote:
> everything seems OK, but my sound card. In the handbook they say I must
> use the MAKEDEV script (as in Linux) but I can't find it on my disk.
freebsd 5.0 is using devfs(5). so device inodes are created
automatically.
for your soundca
On 25-Jan-2003 Nate Lawson wrote:
> On Sat, 25 Jan 2003, Morten Rodal wrote:
>> The system is running 5.0-RELEASE with a pretty standard kernel (just
>> removed all the drivers I don't use and added SMP support). I think
>> the load of the system might have been high at the moment as I had
>> jus
On 25-Jan-2003 Morten Rodal wrote:
> Is this a known panic? I tried to search the mailinglist archives to
> see if somebody had posted something similar, but I couldn't find
> anything.
>
> The system is running 5.0-RELEASE with a pretty standard kernel (just
> removed all the drivers I don't us
On 27-Jan-2003 FredBriand wrote:
> Hi,
>
> I'm new to FreeBSD and I'm busy installing it on a notebook. Up to now
> everything seems OK, but my sound card. In the handbook they say I must
> use the MAKEDEV script (as in Linux) but I can't find it on my disk.
> I tried to download it with the sysi
On 27-Jan-2003 Julian Elischer wrote:
>
>
> On Sun, 26 Jan 2003, David O'Brien wrote:
>
>> On Sun, Jan 26, 2003 at 04:05:31PM -0800, Julian Elischer wrote:
>> >
>> > or simply check out the newer sources.
>>
>> Looking at the commit you made, it doesn't seem to address the other
>> issues of
On Sat, 25 Jan 2003, Bryan Liesner wrote:
> Thanks, Nate. When you suggested that I remove the apm stuff fron the
> kernel, you meant ALL of the apm stuff, didn't you :) . I took a
> second look and found I still had viapm and its requirements still in
> the config file. The system boots fine no
On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote:
> Do you still have the kernel.debug from this kernel lying around?
> Can you pop gdb up on it and do 'l *0xc01bdb48' please? That is
> the instruction pointer from the fault and will give the line that
> the actual panic occurred at.
>
please add ext2fs to the modules list in src/sys/modules/Makefile.
my /usr/src tree resides on an ext2fs partition and the fact that
ext2fs.ko isn't built causes me trouble when making installworld
just after rebooting the new kernel.
Thanks & Regards
Adi
--- /arc/freebsd/src/sys/modules/Makefil
I get this when I try to access for the first time a file on an ext2fs
filesystem.
VOP_STRATEGY on VCHR
: 0xc1c23000: tag devfs, type VCHR, usecount 2, writecount 0, refcount 3,
backtrace(c02fe7bd,c1c23000,0,c87eb938,c0166ed8) at backtrace+0x8
spec_strategy(c87eb960,c87eb97c,c1c416
hi,
got no useful response from -mobile so re-posting to -current:
i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
driver for my 3com 3ccfe575ct writes the following message to the
console "xl0: watchdog timeout".
after skimming through newsgroups i found out that it has
somethi
"Kevin Oberman" <[EMAIL PROTECTED]> writes:
> I am getting LORs on my ThinkPad 600e running current of 1/24. I don't
> know if these have been previously reported, so I thought I'd send
> them in.
>
> lock order reversal
> 1st 0xc20193f8 process lock (process lock) @
>/scratch/src/sys/kern/kern
Charlie ROOT <[EMAIL PROTECTED]> writes:
> root, nor a regular user. Is this a font path problem?
No, it is not.
> /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol
> "__thr_jtable"
This is a problem. Version numbers are OK, though.
--
Alexander Pohoyda
<[EMAIL PROTECTED]>
T
I have viapm, smb, and acpi enabled on my system, and console is
not gone. It works just fine. I can [ctrl-alt]-F[1-8] as normal
and xdm works just fine. I can get a dmesg and kernel config if
people want it.
On Mon, Jan 27, 2003 at 12:36:18PM -0800, Nate Lawson wrote:
: On Sat, 25 Jan 2003, Br
On Mon, Jan 27, 2003 at 11:14:41PM +0200, Enache Adrian wrote:
> please add ext2fs to the modules list in src/sys/modules/Makefile.
>
> my /usr/src tree resides on an ext2fs partition and the fact that
> ext2fs.ko isn't built causes me trouble when making installworld
> just after rebooting the ne
On Mon, Jan 27, 2003 at 03:18:51PM +0300, Odhiambo Washington wrote:
> rm -f /usr/src/sys/modules/ip_mroute_mod/export_syms ip_mroute.ko ip_mroute.kld
>ip_mroute.o @ machine symb.tmp tmp.o opt_mac.h opt_mrouting.h opt_random_ip_id.h
> Illegal instruction (core dumped)
> *** Error code 132
Can yo
On 27-Jan-2003 Morten Rodal wrote:
> On Mon, Jan 27, 2003 at 03:27:00PM -0500, John Baldwin wrote:
>> Do you still have the kernel.debug from this kernel lying around?
>> Can you pop gdb up on it and do 'l *0xc01bdb48' please? That is
>> the instruction pointer from the fault and will give the li
On Mon, Jan 27, 2003 at 10:18:48PM +0100, Toni Schmidbauer wrote:
> hi,
>
> got no useful response from -mobile so re-posting to -current:
>
> i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
> driver for my 3com 3ccfe575ct writes the following message to the
> console "xl0: watch
> Sender: [EMAIL PROTECTED]
> From: Alexander Pohoyda <[EMAIL PROTECTED]>
> Date: 27 Jan 2003 22:13:40 +0100
>
> "Kevin Oberman" <[EMAIL PROTECTED]> writes:
>
> > I am getting LORs on my ThinkPad 600e running current of 1/24. I don't
> > know if these have been previously reported, so I thought I
FreeBSD used to have an irritating boot delay in 4.4. It was gone in
~4.6, never reappeared in -STABLE, but is there in -CURRENT.
(I've seen it also mentioned in some vmware documentation).
Applying this patch fixes it:
--- /arc/freebsd/src/sys/dev/ata/ata-all.c Sun Jan 19 23:54:13 2003
+++
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Thus spake Enache Adrian <[EMAIL PROTECTED]>:
> FreeBSD used to have an irritating boot delay in 4.4. It was gone in
> ~4.6, never reappeared in -STABLE, but is there in -CURRENT.
> (I've seen it also mentioned in some vmware documentation).
>
> Applying this patch fixes it:
>
> --- /arc/freebsd/
> The sound on the 600E is weird. It connect to both PCI and ISA for
> different functions. As a result, I have to edit /sys/conf/files to
> delete the csa pcm entry and add csa to the csapcm line.
>
> dev/sound/pci/csa.c optional csa pci
> #dev/sound/pci/csa.c optional pcm pci
> dev/sound/pci
On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> Portions of the ext2fs source are covered by the GPL. You
> need to rebuild the kernel with "option EXT2FS". The
> FreeBSD cannot create a ext2fs.ko and comply with the GPL.
This is weird.
Builting it as part of kernel is ok, but sep
On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL. You
> > need to rebuild the kernel with "option EXT2FS". The
> > FreeBSD cannot create a ext2fs.ko and comply wit
On Tue, 28 Jan 2003, Enache Adrian wrote:
> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL. You
> > need to rebuild the kernel with "option EXT2FS". The
> > FreeBSD cannot create a ext2fs.ko and comply with the GPL.
>
> Thi
> Date: Mon, 27 Jan 2003 23:32:57 +0100 (CET)
> From: Alexander Pohoyda <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
>
> > The sound on the 600E is weird. It connect to both PCI and ISA for
> > different functions. As a result, I have to edit /sys/conf/files to
> > delete the csa pcm entry a
Thanks for your suggestions! I will try it out.
> The sound on the 600 is different from the 600E and, while I know the
> magic was different on V4, I don't have any experience with it. Most
> likely you need adjustments to hints file.
Funny is that if I add some:
hint.pcm.0.at="isa"
...
to /bo
On Mon, 27 Jan 2003, Nate Lawson wrote:
> On Sat, 25 Jan 2003, Bryan Liesner wrote:
> > Thanks, Nate. When you suggested that I remove the apm stuff fron the
> > kernel, you meant ALL of the apm stuff, didn't you :) . I took a
> > second look and found I still had viapm and its requirements stil
Hi all,
We can end this tread. The bug has been found and fixed
in HEAD.
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
hi, there!
Is it possible to build a part of (for example) 5.x tree on 4.x machine?
Suppose I have run make buildworld once, have bootstrap toolchain
in /usr/obj and want to rebuild only libc.
/fjoe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
David Schultz wrote:
> I still can't figure out why the problem would trash your entire
> home directory, though. Even if the disk reordered writes and
> failed to write some sectors, directory entries that were not
> being actively modified shouldn't have become corrupted, as far as
>
This prevents fsck from failing at boot if there are nullfs or unionfs
filesystems in fstab(5), as reported by [EMAIL PROTECTED] Anyone mind
if I commit this? (Or have suggestions for filesystems to add to the
list?)
%%%
Index: fsck.c
=
I'm talking about TP600E and 4.7-STABLE (as of yesterday) here.
Just recompiled:
apog@oak:~$ grep csa /sys/conf/files
dev/sound/pci/csa.c optional csa pci
#dev/sound/pci/csa.coptional pcm pci
dev/sound/pci/csapcm.c optional csa pcm pci
apog@oak:~$ grep pcm0 /sys/i386/conf/OAK
device
hi, there!
On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
> On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > Portions of the ext2fs source are covered by the GPL. You
> > need to rebuild the kernel with "option EXT2FS". The
> > FreeBSD cannot create a ext2fs.ko a
* De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> hi, there!
>
> On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
>
> > On Mon, Jan 27, 2003 at 01:36:35PM -0800, Steve Kargl wrote:
> > > Portions of
* De: Juli Mallett <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Diff to make fsck(8) ignore certain filesystems. ]
> This prevents fsck from failing at boot if there are nullfs or unionfs
> filesystems in fstab(5), as reported by [EMAIL PROTECTED] Anyone mind
> if I commit this? (
I recently was installing the world when it ran out of space. I ^C'ed too
many times and ended up with trying to start up on an incomplete world,
really incomplete. I don't have /bin/sh, for example. Can someone point me
toward an i386 Live Filesystem ISO so I can try to fix my mess?
Thanks a lo
Vincent Poy wrote:
> > > >>Is there any reason, on newer motherboards, to need the MAXMEM option?
> > > >
> > > > I don't know. I've always used MAXMEM. Guess it's
> > > > time to remove it from my kernel config file.
> > >
> > > FWIW, I've been using FBSD -stable and -current for about 3 years
>
On Mon, Jan 27, 2003 at 03:50:40PM -0800, Evan Dower wrote:
> I recently was installing the world when it ran out of space. I ^C'ed too
> many times and ended up with trying to start up on an incomplete world,
> really incomplete. I don't have /bin/sh, for example. Can someone point me
> toward
Vincent Poy wrote:
> > > MAXMEM is useful for testing configurations with less memory,
> > > without having to open up your box and yank SIMMs, or to have
> > > a bunch of different sized pairs of SIMMs lying around.
> >
> > For uses such as testing I can understand, but I don't see a use under
> >
Oh, I didn't realize. Fantastic. Thanks a lot. :-)
From: Kris Kennaway <[EMAIL PROTECTED]>
To: Evan Dower <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: 5.0 i386 Live Filesystem
Date: Mon, 27 Jan 2003 15:57:18 -0800
MIME-Version: 1.0
Received: from mc7-f40.law1.hotmail.com ([65.54.253.47]
It looks like firewall in 5.0-RELEASE doesn't respect uid option.
I migrated from 4.7 where the following lines worked fine:
allow tcp from me to any uid 500 setup
allow udp from me to any uid 500 keep-state
I couldn't get these lines working on 5.0 (packets don't match these rules).
it's a littl
On Mon, 27 Jan 2003, Toni Schmidbauer wrote:
> got no useful response from -mobile so re-posting to -current:
>
> i am having problems with 5.0-REL on an ibm thinkpad 600x.the xl
> driver for my 3com 3ccfe575ct writes the following message to the
> console "xl0: watchdog timeout".
The 575 may requ
* De: "Matthew N. Dodd" <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: xl thinkpad 600x watchdog timeout ]
> On Mon, 27 Jan 2003, Toni Schmidbauer wrote:
> > got no useful response from -mobile so re-posting to -current:
> >
> > i am having problems with 5.0-REL on an ibm thinkpad
On Mon, 27 Jan 2003, Alexander Pohoyda wrote:
> I'd wish to have sound working.. On my second notebook (TP600E) I have
> a PCI sound card -- 0x1013 0x6001. Don't you?
You'll need to configure the sound resources in DOS using the 'ps2.exe'
utility. (Or you can wait a few days until I get my confi
On Tue, 28 Jan 2003, Alexander Pohoyda wrote:
> I'm talking about TP600E and 4.7-STABLE (as of yesterday) here.
>
> Just recompiled:
>
> apog@oak:~$ grep csa /sys/conf/files
> dev/sound/pci/csa.c optional csa pci
> #dev/sound/pci/csa.coptional pcm pci
> dev/sound/pci/csapcm.c optional csa
Installs from network just fine, no problems besides not finding the ports
package. Then, when reboots, system goes into panic almost immediately after
booting.
Because it is not feasible to make screenshots using some program in this
case, I made them in the literal sense with my digital camer
I'm getting some odd behavior with tunefs (5.0-CURRENT cvsupped and built
Sunday, Jan 26). If a filesystem, rather than an actual device, is specified,
it spits out a weird error message regarding my linproc mount:
# tunefs -p /tmp
tunefs: linproc: could not find special device
My /etc/fstab:
#
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 26 Jan 2003 13:42:32 -0500
Mikhail Teterin <[EMAIL PROTECTED]> wrote:
> Can anyone, please, try the following URL, for example:
>
> pnm://rm.content.loudeye.com/~ttt-600111/0619060_0103_00_0002.ra
>
> It causes RealPlayer8.cs2 to get SIGABRT on two of my -current systems. I must
>
* De: Conrad Sabatier <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: tunefs using libufs. ]
> I'm getting some odd behavior with tunefs (5.0-CURRENT cvsupped and built
> Sunday, Jan 26). If a filesystem, rather than an actual device, is specified,
> it spits out a weird error mes
> > If it's long enough to pause the console noticibly, the next
> > thing to try is breaking to the debugger -- which might require
> > an NMI card -- to see what code it's stuck in during the pause.
>
> It's noticeable - if you type under heavy load in console, you
> experience similar to ssh la
Hi,
I am seeingthis from a kernel cvsup'd a few days ago:
login: lock order reversal
1st 0xc060ad20 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151
2nd 0xc339097c radix node head (radix node head) @ /usr/src/sys/net/route.c:549
Thanks.
--
Craig Rodrigues
http://home.attbi.
There's a load balancing configuration known as direct server return
(DSR), in which packets pass from the client through the load balancer to
the server, but then the replies from the server go directly to the client
(bypassing the load balancer). The way this works is that the load
balancer sen
You need to set
net.inet.ip.check_interface=0
John David Duncan ([EMAIL PROTECTED]) wrote:
>
> There's a load balancing configuration known as direct server return
> (DSR), in which packets pass from the client through the load balancer to
> the server, but then the replies from the server go dir
John David Duncan wrote:
> There's a load balancing configuration known as direct server return
> (DSR), in which packets pass from the client through the load balancer to
> the server, but then the replies from the server go directly to the client
> (bypassing the load balancer). The way this wor
Hi,
I've built and installed a complete system with the patch
below. Amoung other things, this allows the individual mount_$vfstype
executables to not have to differentiate how they were
invoked. They can then have their XXX sections removed along
with a small amount of code (and this will help
Hi
I agree here with Terry. It is immense help to be able to set
MAXMEM to something less to study the behaviour of the system under
memory pressure for one.
It is also helpful to keep the size of the crash dumps small
Aniruddha
On Mon, 27 Jan 2003, Terry Lambert wrote:
> Vinc
Thus spake Juli Mallett <[EMAIL PROTECTED]>:
> * De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
> [ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> > hi, there!
> >
> > On Tue, Jan 28, 2003 at 12:40:12AM +0200, Enache Adrian wrote:
> >
> > > On Mon, Jan 27, 2003 a
* De: David Schultz <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
[ Subjecte: Re: add ext2fs to the module list in modules/Makefile ]
> Thus spake Juli Mallett <[EMAIL PROTECTED]>:
> > * De: Max Khon <[EMAIL PROTECTED]> [ Data: 2003-01-27 ]
> > [ Subjecte: Re: add ext2fs to the module list i
Hello,
I've seen this very same message on one of my -current testboxes. While
we're on the topic of LORs, I've also come across the following:
Jan 27 00:44:57 largo kernel: lock order reversal
Jan 27 00:44:57 largo kernel: 1st 0xc6708314 inp (inp)
@../../../netinet/tcp_input.c:641
Jan 27 00:44:
Hi,
I'm doing some performance analysis on FreeBSD. I would like to
be able to make an SMP kernel use only one CPU. Of course I
realize running GENERIC would only use 1 CPU but the concern is
that the overhead assoicated with SMP will skew the statistics.
So my question is what would be the 'bes
I'm trying to upgrade from 4.7-RELEASE-P1 to 5.0-RELEASE but I consistently
get the same error when trying to compile a kernel (GENERIC or otherwise):
linking kernel
textdata bss dec hex filename
3043330 343744 277828 3664902 37ec06 kernel
cd /usr/src/sys/modules ;
MAKEOBJDI
On Sat, Jan 25, 2003 at 12:12:34AM -0800, Kris Kennaway wrote:
> One of the alpha package clients panicked with this. It was under
> very high load at the time (25 simultaneous package builds):
>
> fatal kernel trap:
>
> trap entry = 0x2 (memory management fault)
> faulting va= 0
1 - 100 of 102 matches
Mail list logo
