Re: Problems with pf + ftp-proxy on gateway

--- Renato Botelho [EMAIL PROTECTED] wrote: I'm trying to use pf + ftp-proxy n a 6.1-PRERELEASE machine. I have this line on inetd.conf: ftp-proxy stream tcp nowait root/usr/libexec/ftp-proxy ftp-proxy -n And this lines on pf.conf: rdr on $int_if proto tcp from any

Re: Script-friendly (parseble) ps(1) output?

everything beyond it... ie; poshta:$ps axuww| while read USER PID CPU MEM VSZ RSS TT STAT STARTED TIME; do echo $PID $CPU $USER $TIME;done |head -3 PID %CPU USER TIME COMMAND 11 77.9 root 138080:11.91 [idle] 13607 5.0 qscand 0:09.12 spamd child (perl5.8.8) etc.etc... ]Peter

stable/8/UPDATING - no mention of 8.0 release

=markup It just confused me for awhile after I did a 'svn up' and did not see the release notes... [for the 7.X series, both stable/ and release/ mention the release in UPDATING] ]Peter[ ___ freebsd-stable@freebsd.org mailing list http

panic: spin lock held too long 8.0-STABLE r207638

a Windows VM running on there, and it starts using some swap, anywhere from 20MB to 150MB it eventually panics [usually within an hour or so]. Any ideas ? hardware issues? Anyone successfull in running several VMs on FreeBSD - VirtualBox ? [overloading it?] ]Peter

Re: Some questions about jails on FreeBSD9.0-RC1

, but with setfib 1 /usr/sbin/setfib 1 /usr/local/etc/rc.d.fib/obspamd $1 I had moved the 'obspamd' startup script to rc.d.fib just so a 'setfib 1' wrapper is called. ]Peter[ FIBs are awesome when you don't have many public IPs and when host is _only_ a jail host running no services

Re: why is pkg_add on 9.0 stable still using packages from packages-9-current?

, 999000, /packages-9-current }, They haven't updated main.c for -stable yet and -stable is at 900500 per sys/sys/param.h [or URL]. I'm just setting PACKAGESITE=ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/ manually. ]Peter

ZFS l2arc broken in 10.3

details to follow ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[fixed] ZFS l2arc broken in 10.3

sendbug seems not to work anymore, I end up on websites with marketing- babble and finally get asked to provide some login and passwd. :( But the former mail looks like having come back to me, so it seems I'm still allowed to post here... ***

Re: ZFS l2arc broken in 10.3

Details: After upgrading 2 machines from 9.3 to 10.3-STABLE, on one of them the l2arc stays empty (capacity alloc = 0), although it is online and gets accessed. It did work well on 9.3. I did the following tests: * Create a zpool on a stick, with two volumes: one filesystem and one cache.

Re: Nightly disk-related panic since upgrade to 10.3

Andrea Venturoli wrote: Hello. Last week I upgraded a 9.3/amd64 box to 10.3: since then, it crashed and rebooted at least once every night. Hi, I have quite similar issue, crash dumps every night, but then my stacktrace is different (crashing mostly in cam/scsi/scsi.c), and my env is also

Re: zfs, a directory that used to hold lot of files and listing pause

Eugene M. Zheganin wrote: Hi. I have FreeBSD 10.2-STABLE r289293 (but I have observed this situation on different releases) and a zfs. I also have one directory that used to have a lot of (tens of thousands) files. I surely takes a lot of time to get a listing of it. But now I have 2 files and

10-STABLE zfs: strange memory stats

I observe a strange reading of the ZFS memory stats: Mem: 298M Active, 207M Inact, 446M Wired, 10M Cache, 91M Buf, 29M Free ARC: 339M Total, 8758K MFU, 43M MRU, 52K Anon, 35M Header, 40M Other Swap: 2441M Total, 402M Used, 2040M Free, 16% Inuse Usually I perceived the "Total" value being

Re: Dying jail

Eugene Grosbein wrote: Hi! Recently I've upgraded one of my server running 9.3-STABLE with jail containing 4.11-STABLE system. The host was source-upgraded upto 10.3-STABLE first and next to 11.0-STABLE and jail configuration migrated to /etc/jail.conf. The jail kept intact. "service jail

Re: ZFS l2arc broken in 10.3

Pete French wrote: Ok, thats a bit worry if true - but I can confirm that l2arc works fine under 10.3 on amd64, so what you say about cross-compling might be true. Am taking an inetrest in this as I have just dpeloyed a lot of machines which are going to be relying on l2arc working to get

Rel.10.3 zfs GEOM removal and memory leak

Question: how to get ZFS l2arc working on FBSD 10.3 (RELENG or STABLE)? Problem using 10.3 RELENG: When ZFS is called the first time after boot, it will delete all device nodes of the drive carrying l2arc. ZFS itself will access it's slices by a "diskid/" string, but all other access is

11.1-RELEASE: huge amount of l2_cksum_bad

After upgrading 11.0-RELEASE-p10 to 11.1-RELEASE I suddenly see a huge amount of kstat.zfs.misc.arcstats.l2_cksum_bad (nearly 2% of kstat.zfs.misc.arcstats.l2_hits). I have set > vfs.zfs.compressed_arc_enabled="0" in loader.conf. When removing this, the errors are gone. It seems that option

11.1-RELEASE: new line containing garbage added to "top"

After upgrading to 11.1-RELEASE, a new line appears in the output of "top" which contains rubbish: > last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46 03:23:51 > 1030 processes:9 running, 1004 sleeping, 17 waiting > CPU 0: 16.0% user, 0.0% nice, 78.7% system, 4.9%

Re: 11.1-RELEASE: new line containing garbage added to "top"

Glen Barber wrote: On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote: After upgrading to 11.1-RELEASE, a new line appears in the output of "top" which contains rubbish: last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46 03:23:51 1030 processes:9 running, 100

11.1-RELEASE: panic! acl_from_aces: a_type is 0x4000

This is mostly for the search engines, so others running into it may find it easier to solve. While updating some ports via "portupgrade", I got this panic: Panic String: acl_from_aces: a_type is 0x4000 The phenomen was reproducible; it appeared while creating a backup package from the

errors from port make (analyzed: bug in pkg)

For a long time already, I get these strange messages whenever building a port: pkg: Bad argument on pkg_set 2143284626 Today I looked into it, and found it is easily reproducible: # pkg audit whatever pkg: Bad argument on pkg_set 2143284618 0 problem(s) in the installed packages found. #

Re: a strange and terrible saga of the cursed iSCSI ZFS SAN

Eugene M. Zheganin wrote: Hi, On 05.08.2017 22:08, Eugene M. Zheganin wrote: pool: userdata state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise

Re: 11.1-RELEASE: new line containing garbage added to "top"

Glen Barber wrote: On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote: After upgrading to 11.1-RELEASE, a new line appears in the output of "top" which contains rubbish: last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46 03:23:51 1030 processes:9 running, 100

Re: 11.1-RELEASE: new line containing garbage added to "top"

Glen Barber wrote: On Fri, Jul 28, 2017 at 07:04:51PM +0200, Peter wrote: Glen Barber wrote: On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote: After upgrading to 11.1-RELEASE, a new line appears in the output of "top" which contains rubbish: last pid: 10789; load avera

11.1-RELEASE: magic hosed, file recognition fails

Just found that my scripts that would detect image types by means of the "file" command do not work anymore in RELEASE-11. :( Whats happening in R11.1 is this: $ scanimage > /tmp/SCAN $ file /tmp/SCAN /tmp/SCAN: data While on R10 in looked this way, which appears slightly more useful: $

11.1-BETA1: lsof build failure

FYI, please check if reproducible and/or issue: Installed this from SVN & local build: 11.1-BETA1 FreeBSD 11.1-BETA1 #0 r319858:319867M ... amd64 Then tried to update lsof-4.90.f,8 and got this error: cc -pipe -DNEEDS_BOOL_TYPEDEF -DHASTASKS -DHAS_PAUSE_SBT -DHASEFFNLINK=i_effnlink

Re: 11.1-BETA1: lsof build failure

Larry Rosenman wrote: Current lsof is 4.90M. Ack, that does. Larry Sysutils/lsof maintainer On 6/14/17, 8:13 AM, "Peter" <owner-freebsd-sta...@freebsd.org on behalf of p...@citylink.dinoex.sub.org> wrote: FYI, please check if reproducible and/or issue: Install

Security patch SA-18:03 removed from 11.2 - why?

Release/update 11.1-p8 introduced so-called "mitigation for speculative execution vulnerabilities". In RElease 11.2 these "mitigation" have been removed. What is the reason for the removal, and specifically why is Security advisory 18:03 still mentioned in the release notes? Behaviour with

Re: kern.sched.quantum: Creepy, sadistic scheduler

Eugene Grosbein wrote: I see no reasons to use SHED_ULE for such single core systems and use SCHED_BSD. Nitpicking: it is not a single core system, it's a dual that for now is equipped with only one chip, the other is in the shelf. But seriously, I am currently working myself through the

Re: more data: SCHED_ULE+PREEMPTION is the problem

Hi Stefan, I'm glad to see You're thinking along similar paths as I did. But let me fist answer Your question straight away, and sort out the remainder afterwards. > I'd be interested in your results with preempt_thresh set to a value > of e.g.190. There is no difference. Any value above 7

Appendices - more data: SCHED_ULE+PREEMPTION is the problem

I forgot to attach the commands used to create the logs - they are ugly anyway: [1] dtrace -q -n '::sched_choose:return { @[((struct thread *)arg1)->td_proc->p_pid, stringof(((struct thread *)arg1)->td_proc->p_comm), timestamp] = count(); } tick-1s { exit(0); }' | sort -nk 3 | awk '$1 > 27

Found the issue! - SCHED_ULE+PREEMPTION is the problem

Results: 1. The tdq_ridx pointer The perceived slow advance (of the tdq_ridx pointer into the circular array) is correct behaviour. McKusick writes: The pointer is advanced once per system tick, although it may not advance on a tick until the currently selected queue is empty. Since each

Re: kern.sched.quantum: Creepy, sadistic scheduler

Hi Alban! Alban Hertroys wrote: Occasionally I noticed that the system would not quickly process the tasks i need done, but instead prefer other, longrunning tasks. I figured it must be related to the scheduler, and decided it hates me. If it hated you, it would behave much worse. Thats

Re: kern.sched.quantum: Creepy, sadistic scheduler

George Mitchell wrote: On 04/04/18 06:39, Alban Hertroys wrote: [...] That said, SCHED_ULE (the default scheduler for quite a while now) was designed with multi-CPU configurations in mind and there are claims that SCHED_4BSD works better for single-CPU configurations. You may give that a try,

Re: Try setting kern.sched.preempt_thresh != 0

Stefan Esser wrote: I'm guessing that the problem is caused by kern.sched.preempt_thresh=0, which prevents preemption of low priority processes by interactive or I/O bound processes. For a quick test try: # sysctl kern.sched.preempt_thresh=1 Hi Stefan, thank You, thats an interesting knob!

more data: SCHED_ULE+PREEMPTION is the problem (was: kern.sched.quantum: Creepy, sadistic scheduler

Hi all, in the meantime I did some tests and found the following: A. The Problem: --- On a single CPU, there are -exactly- two processes runnable: One is doing mostly compute without I/O - this can be a compressing job or similar; in the tests I used simply an endless-loop. Lets

Re: kern.sched.quantum: Creepy, sadistic scheduler

Julian Elischer wrote: for a single CPU you really should compile a kernel with SMP turned off and 4BSD scheduler. ULE is just trying too hard to do stuff you don't need. Julian, if we agree on this, I am fine. (This implies that SCHED_4BSD will *not* be retired for an indefinite time!) I

Re: kern.sched.quantum: Creepy, sadistic scheduler

Andriy Gapon wrote: On 04/04/2018 03:52, Peter wrote: Lets run an I/O-active task, e.g, postgres VACUUM that would continuousely read from big files (while doing compute as well [1]): Not everyone has a postgres server and a suitable database. Could you please devise a test scenario

Re: kern.sched.quantum: Creepy, sadistic scheduler

Andriy Gapon wrote: Not everyone has a postgres server and a suitable database. Could you please devise a test scenario that demonstrates the problem and that anyone could run? Alright, simple things first: I can reproduce the effect without postgres, with regular commands. I run this on my

Re: kern.sched.quantum: Creepy, sadistic scheduler

Hi all of You, thank You very much for Your commenting and reports! From what I see, we have (at least) two rather different demands here: while George looks at the over-all speed of compute throughput, others are concerned about interactive response. My own issue is again a little bit

Re: kern.sched.quantum: Creepy, sadistic scheduler

EBFE via freebsd-stable wrote: On Tue, 17 Apr 2018 09:05:48 -0700 Freddie Cash wrote: # Tune for desktop usage kern.sched.preempt_thresh=224 ​Works quite nicely on a 4-core AMD Phenom-II X4 960T Processor (3010.09-MHz K8-class CPU) running KDE4 using an Nvidia 210 GPU.

kern.sched.quantum: Creepy, sadistic scheduler

Occasionally I noticed that the system would not quickly process the tasks i need done, but instead prefer other, longrunning tasks. I figured it must be related to the scheduler, and decided it hates me. A closer look shows the behaviour as follows (single CPU): Lets run an I/O-active task,

kernel crash from adjacent partitions (gpart, zfs)

Hi, when creating partitions directly adjacent without a safety free space between them, the kernel may crash. Does anybody know how big that free space needs to be? How I found out (and how to reproduce the crash):

Rel. 11.3: Kernel doesn't compile anymore :(

Trying to compile my custom kernel in Rel. 11.3 results in this: [code]--- kernel.full --- linking kernel.full atomic.o: In function `atomic_add_64': /usr/obj/usr/src/sys/E1R11V1/./machine/atomic.h:629: multiple definition of `atomic_add_64'

Re: Rel. 11.3: Kernel doesn't compile anymore (SVN-334762, please fix!)

> Trying to compile my custom kernel in Rel. 11.3 results in this: > > -- kernel.full --- > linking kernel.full > atomic.o: In function `atomic_add_64': > /usr/obj/usr/src/sys/E1R11V1/./machine/atomic.h:629: multiple definition of > `atomic_add_64' >

Re: Rel. 11.3: Kernel doesn't compile anymore (SVN-334762, please fix!)

Hi Hans Petter, glad to read You! :) On Thu, Jul 25, 2019 at 09:39:26AM +0200, Hans Petter Selasky wrote: ! On 2019-07-25 01:00, Peter wrote: ! >> The offending feature is either ! >> options ZFS ! >> or ! >> device dtrace ! >> (Adding any of these to the

Re: wrong value from DTRACE (uint32 for int64)

On Mon, 02 Dec 2019 21:58:36 +0100, Mark Johnston wrote: The DTRACE_PROBE* macros cast their parameters to uintptr_t, which will be 32 bits wide on i386. You might be able to work around the problem by casting arg0 to uint32_t in the script. Thanks for the info - good that it has a logical

Re: Disabling speculative execution mitigations

On Fri, 06 Dec 2019 06:21:04 +0100, O'Connor, Daniel wrote: vm.pmap.pti="0"# Disable page table isolation hw.ibrs_disable="1"# Disable Indirect Branch Restricted Speculation hw.mds_disable="0" # Disable Microarchitectural Data Sampling flush hw.vmm.vmx="1" # Don't

wrong value from DTRACE (uint32 for int64)

Hi @all, I felt the need to look into my ZFS ARC, but DTRACE provided misleading (i.e., wrong) output (on i386, 11.3-RELEASE): # dtrace -Sn 'arc-available_memory { printf("%x %x", arg0, arg1); }' DIFO 0x286450a0 returns D type (integer) (size 8) OFF OPCODE INSTRUCTION 00: 29010601

jedec_dimm fails to boot

I met an Issue: When I kldload jedec_dimm durig runtime, it works just as expected, and the DIMM data appears in sysctl. But when I do * load the jedec_dimm at the loader prompt, or * add it to loader.conf, or * compile it into a custom kernel, it does not boot anymore. My custom kernel

panic: too many modules

Front up: I do not like loadable modules. They are nice to try something out, but when you start to depend on some dozen loaded modules, debugging becomes a living hell: say you hunt some spurious misbehaviour and compare logfiles with those from four weeks ago, you will not know exactly which

Re: jedec_dimm fails to boot

On Wed, Mar 04, 2020 at 11:41:22PM +0300, Yuri Pankov wrote: ! On 04.03.2020 19:09, Peter wrote: ! > When I kldload jedec_dimm durig runtime, it works just as expected, ! > and the DIMM data appears in sysctl. ! > ! > But when I do ! > * load the jedec_dimm at the loader prompt,

Re: ZFS and power management

On Wed, 18 Dec 2019 17:22:16 +0100, Karl Denninger wrote: I'm curious if anyone has come up with a way to do this... I have a system here that has two pools -- one comprised of SSD disks that are the "most commonly used" things including user home directories and mailboxes, and another that

session mgmt: does POSIX indeed prohibit NOOP execution?

pgrp = getpid(); if(setpgid(0, pgrp) < 0) err(1, "setpgid"); This appears to me a program trying to deemonize itself (in the old style when there was only job control but no session management). In the case this program is already properly daemonized, e.g. by starting it from

Re: session mgmt: does POSIX indeed prohibit NOOP execution?

On Mon, 06 Jan 2020 01:10:57 +0100, Christoph Moench-Tegeder wrote: When a program is invoked via /usr/sbin/daemon, it should already be session leader AND group leader, and then the above code WOULD be a NOOP, unless POSIX would require the setpgid() to fail and thereby the program to abort

Fwd: Re: session mgmt: does POSIX indeed prohibit NOOP execution?

> Not much room to argue? Why that? This is not about laws you have to follow blindly whether you understand them or not, this is all about an Outcome - a working machine that should properly function. "Not much to argue about what behaviour is required by the standard". The standard could

12.2 cpuset behaves unexpected

After upgrading 11.4 -> 12.2, cpuset now behaves rather different: # cpuset -C -p NNN 11.4: a new set is created with all cpu enabled, and the process is moved into that set, with the thread mask unchanged. 12.2: nothing is done, but an error raises if threadmask == setmask. # cpuset -l

12.2 Firefox immediate crash "exiting due to channel error"

Hi all, I was forced to upgrade 11.4 -> 12.2, as QT5 reqires openssl 1.1.1. I did a full rebuild from source as of this: 12.2-RC2 FreeBSD 12.2-RC2 #11 r366648M#N1055:1078 (local patches applied - some published via sendbug 10 or 12 years ago) I did a full rebuild of ALL ports from source,

Re: How to free used Swap-Space?

On Tue, Sep 22, 2020 at 12:33:19PM -0400, Mark Johnston wrote: ! On Tue, Sep 22, 2020 at 06:08:01PM +0200, Peter wrote: ! > my machine should use about 3-4, maybe 5 GB swapspace. Today I found ! > it suddenly uses 8 GB (which is worryingly near the configured 10G). ! > ! > I

Re: How to free used Swap-Space? (from errno=8)

I think I can reproduce the problem now. See below. On Tue, Sep 22, 2020 at 02:09:01PM -0400, Mark Johnston wrote: ! On Tue, Sep 22, 2020 at 07:31:07PM +0200, Peter wrote: ! > There is something, and I don't know who owns that: ! > $ vmstat -m | grep shmfd ! > shmfd

Re: How to free used Swap-Space? (from errno=8)

On Wed, Sep 23, 2020 at 12:03:32AM +0300, Konstantin Belousov wrote: ! On Tue, Sep 22, 2020 at 09:11:49PM +0200, Peter wrote: ! > So what happens then is this: ! > ! > $ file scc.e ! > scc.e: ELF 32-bit LSB executable, Intel 80386, version 1 ! > (FreeBSD), dynamically linked, inter

How to free used Swap-Space?

Hi all, my machine should use about 3-4, maybe 5 GB swapspace. Today I found it suddenly uses 8 GB (which is worryingly near the configured 10G). I stopped all the big suckers - nothing found. I stopped all the jails - no success. I brought it down to singleuser: it tried to swapoff, but

Help! 12.2 mem ctrl knob missing, might need 3 times more memory

Hiya, after upgrading 11.4 -> 12.2, I get this error: > sysctl: unknown oid 'vm.pageout_wakeup_thresh' at line 105 How do I adjust the paging now? The ARC is much too small: Mem: 1929M Active, 109M Inact, 178M Laundry, 1538M Wired, 37M Buf, 88M Free ARC: 729M Total, 428M MFU, 154M MRU, 196K

Panic: 12.2 fails to use VIMAGE jails

After clean upgrade (from source) from 11.4 to 12.2-p1 my jails do no longer work correctly. Old-fashioned jails seem to work, but most are VIMAGE+NETGRAPH style, and do not work properly. All did work flawlessly for nearly a year with Rel.11. If I start 2-3 jails, and then stop them again,

Analyzing kernel panic from VIMAGE/Netgraph takedown

Stopping a VIMAGE+Netgraph jail in 12.2 in the same way as it did work with Rel. 11.4, crashes the kernel after 2 or 3 start/stop iterations. Specifically. this does not work: exec.poststop = "/usr/sbin/ngctl shutdown ${ifname1l}:"; Also this new option from Rel.12 does not work either, it

Re: Panic: 12.2 fails to use VIMAGE jails

Hi Kristof, it's great to read You! On Mon, Dec 07, 2020 at 09:11:32PM +0100, Kristof Provost wrote: ! That smells a lot like the epair/vnet issues in bugs 238870, 234985, 244703, ! 250870. epair? No. It is purely Netgraph here. ! I pushed a fix for that in CURRENT in r368237. It’s

Re: Panic: 12.2 fails to use VIMAGE jails

On Tue, Dec 08, 2020 at 04:50:00PM +0100, Kristof Provost wrote: ! Yeah, the bug is not exclusive to epair but that’s where it’s most easily ! seen. Ack. ! Try http://people.freebsd.org/~kp/0001-if-Fix-panic-when-destroying-vnet-and-epair-simultan.patch Great, thanks a lot. Now I have bad

Re: Panic: 12.2 fails to use VIMAGE jails

Here is the next funny crashdump - I obtained this one twice and also the sysctl_rtsock() again. I can reproduce this by just starting and stopping a most simple jail that does only exec.start = "/bin/sleep 4 &"; (And as usual, when I let it time out, nothing bad happens.) Fatal trap 9:

Re: Panic: 12.2 fails to use VIMAGE jails

On Tue, Dec 08, 2020 at 08:02:47PM +0100, Kristof Provost wrote: ! > Sorry for the bad news. ! > ! You appear to be triggering two or three different bugs there. That is possible. Then there are two or three different bugs in the production code. In any case, my current workaround, i.e.

Re: Panic: 12.2 fails to use VIMAGE jails

On Tue, Dec 08, 2020 at 07:51:07PM -0600, Kyle Evans wrote: ! You seem to have misinterpreted this; he doesn't want to narrow it ! down to one bug, he wants simple steps that he can follow to reproduce Maybe I did misinterpret, but then I don't really understand it. I would suppose, when

Re: Panic: 12.2 fails to use VIMAGE jails

On Wed, Dec 09, 2020 at 02:00:37PM +1100, Dewayne Geraghty wrote: ! On a jail with config: ! exec.start = "/bin/sh -x /etc/rc"; ! exec.stop = "/bin/sh /etc/rc.shutdown"; ! exec.clean; ! ! test_prod { jid=7; persist; ip4.addr = ! "10.0.7.96,10.0.5.96,127.0.5.96"; devfs_ruleset = "6"; !

Re: 4.11 snapshots?

better. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD Security Survey

boxes against the risks of the update system being subverted. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Odd RS232 problem

On Tue, 2006-May-23 19:23:20 +0930, Daniel O'Connor wrote: I would hope that 9600 baud wouldn't be *too* fast for a 2GHz CPU :( That depends on what else is sharing the IRQ. PLIP can give you 10's of msec of latency. PIO disks can also destroy latency as can NE2000-style NICs. -- Peter Jeremy

Re: 6.1-stable crash

tested in -current is supposed to be commited. There are also fairly regular postings pointing out that _all_ software has bugs. Some of these bugs will cause crashes. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org

Re: (bsd)tar is broken on 6.1

could support it - though tar(5) states dates before the epoch are not handled consistently. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL

Re: How can I know which files a proccess is accessing?

message but lsof needs to very closely match your running kernel: You should have the kernel sources installed when you build lsof. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable

Re: Error while 'make buildworld' in terminal.o

and then running make clean. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: unmounting a filesystem safely that doesn't exist anymore

of the superblock and is cleared when a filesystem is mounted. It will be set only if the filesystem is cleanly unmounted. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe

'make release' questions...

the amount of time it takes to roll out a new release) ;) Second, is there a way to build/tell sysinstall that if NO_OPENSSH is set, that it doesn't ask you whether you want to enable SSH logins? Thanks again in advance for any advice you can provide. Best Wishes - Peter -- [ http://www.plosh.net

Re: Powerd: Adaptive mode causing a hard hang

and have only had a single hang in the past four months. -- Peter Jeremy pgpHl4a1DWqvN.pgp Description: PGP signature

make rerelease broken at camcontrol...

. Any ideas? The make rerelease command used is: make -i rerelease NODOC=YES NO_FLOPPIES=YES CHROOTDIR=/hog/release \ BUILDNAME=6.1-RELEASE-p2 CVSROOT=/hog/FreeBSD-CVS RELEASETAG=RELENG_6_1 (no optimizations, etc.) Thanks - Peter signature.asc Description: OpenPGP digital signature

Re: 'make release' questions...

@ to get their input. That's all from memory, may contain rough edges, hope it helps anyway. Thanks... The base release is done, it's just the pesky frills that take forever to resolve... :) Best Wishes - Peter signature.asc Description: OpenPGP digital signature

Re: Effects of changing tar's -b option.

should look at increasing net.inet.tcp.sendspace and maybe net.inet.tcp.recvspace, or using an intervening program on hostA that does its own re-buffering. -- Peter Jeremy pgpG7EqbGqXO2.pgp Description: PGP signature

Re: RELENG_6_1 unstable also ...

a marginal DRAM cell. -- Peter Jeremy pgpQweltzDuE4.pgp Description: PGP signature

Re: What denotes a 'blocked' process?

these counters onto ps output. State 'D' and 'W' should catch most of them. You might find it useful looking through the MWCHAN column for anything looking suspicious. -- Peter Jeremy pgpMYVQSfkNHN.pgp Description: PGP signature

Re: FreeBSD 6.x CVSUP today crashes with zero load ...

between the northbridge and the CPU (including the cache). Some caches (eg Alpha) have parity to help here. Mainframes typically have ECC or parity on _all_ datapaths (including through the ALU) to catch those errors. -- Peter Jeremy pgpDBoWJivs0T.pgp Description: PGP signature

Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)

--- Fabian Keil [EMAIL PROTECTED] wrote: There was a request for Tor related problem reports a while ago, I couldn't find the message again, but I believe it was posted here. Is anyone on this list running a Tor node on FreeBSD 6.1-RELEASE or later with similar or higher load? I am hitting

Re: em device hangs on ifconfig alias ...

) is currently unsuitable for them. -- Peter Jeremy pgpCzMs0W9tP4.pgp Description: PGP signature

6.1-RELEASE won't boot on Compaq 1580

models with 4.11 so I wasn't expecting any problems. Before I start re-writing boot0.S, does anyone have any suggestions on how to debug this or what I've missed? -- Peter Jeremy pgpPxRvWikbIW.pgp Description: PGP signature

Re: 6.1-RELEASE won't boot on Compaq 1580

On Sat, 2006-Jul-01 08:02:56 +1000, Peter Jeremy wrote: I've just acquired a couple of old Compaq Armada laptops. I can successfully install 6.1-RELEASE but the system won't boot from the HDD: The MBR menu displays but pressing F1 (the FreeBSD partition) just beeps. Pressing F3 (the Compaq

Re: FreeBSD 6.0-6.1 binary upgrade script

of your key and FreeBSD SO key (0xCA6CDFB2) that are counter-signed by each other? -- Peter Jeremy pgpi5U6qviUzV.pgp Description: PGP signature

Re: MySQL and default memory limits (mysqld: Out of memory)

to it. This isn't quite enough if you have 4GB RAM. -- Peter Jeremy pgpPna19fy7xV.pgp Description: PGP signature

Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)

and see if I crash or not. -Peter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: How to setup polling on 'bge' interface

. (My testing also suggests that I don't really need to do any tweaking because the limiting factor is the gigabit interfaces rather than the V20z). -- Peter Jeremy pgpMPGKdXFs4w.pgp Description: PGP signature

Re: Xen dom0 support?

On Sat, 2006-Jul-22 06:56:44 -0500, Nikolas Britton wrote: Does FreeBSD support Xen 3 dom0 yet??? It looks like work is in progress. See http://www.fsmware.com/ What's the current status of domU support? See http://wiki.xensource.com/xenwiki/OSCompatibility -- Peter Jeremy

Re: Memory management

? Do you have any tools to monitor memory usage of processes ? ps(1) -- Peter Jeremy pgpYlM6L9c5ab.pgp Description: PGP signature

Re: filesystem full error with inumber

On Wed, 2006-Jul-26 13:07:19 -0400, Sven Willenberger wrote: One of my machines that I recently upgraded to 6.1 (6.1-RELEASE-p3) is also exhibiting df reporting wrong data usage numbers. What did you upgrade from? Is this UFS1 or UFS2? Does a full fsck fix the problem? -- Peter Jeremy

Sound device reported but no devices created

: ESS 18xx DSP on sbc0 I suspect the problem is that sbc0 is not triggering attachment of pcm0 but I'm uncertain why. Does anyone have any suggestions? -- Peter Jeremy pgpjNBhOfnkYL.pgp Description: PGP signature

Re: Sound device reported but no devices created

On Sun, 2006-Jul-30 12:10:54 +0800, Ariff Abdullah wrote: On Sun, 30 Jul 2006 13:43:52 +1000 Peter Jeremy [EMAIL PROTECTED] wrote: I've been trying to get sound working on a Compaq Armada 1580 with a recent 6-STABLE. With devices 'sound' and 'snd_sbc' built into the kernel and no hints, I get

Re: Sound device reported but no devices created

On Sun, 2006-Jul-30 17:52:27 +1000, Ian Smith wrote: Peter, I don't know if this is likely helpful or not, but my Compaq is a 1500c with an ESS ES1869, reporting (on 5.4-RELEASE): sbc0: ESS ES1869 (Compaq OEM) at port 0x330-0x331,0x388-0x38b,0x220-0x22f irq 5 drq 5,1 on isa0 pcm0: ESS 18xx DSP

  1   2   3   4   5   6   7   8   9   10   >