manage jailed IPC.
The disadvantage is restricting the ranges of various counters -
though I believe they are overly generous by default.
This doesn't really address the problem of SysV IPC and jails becoming
more intimately entwined.
--
Peter Jeremy
__
sV IPC' :(
There's the old standby: You have the source code.
You should be able to get things to work by expanding prison_check()
into cr_cansignal() and changing the error return from ESRCH to EPERM.
Having not tried this, I can't comment on possible adver
tter is much harder, there is apparently a RELENG_4 patch in
kern/48471 but it's not clear how much work would be necessary to
being it up to scratch.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
d their pets. Significant features in this release:
Thank you for this. I was beginning to think the 2.2 branch had been
abandoned - the mailing lists seem full of references to 5.5 and 6.1
these days. Can you please advise what CVSup tag I should use to
upgrade to 2.2.9.
--
1280x1024": 135.0 MHz, 80.0 kHz, 75.0 Hz
It also finds a keyboard and mouse - everything looks normal.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t;I've attached a Xorg log with the bitdepth set to 15 and using the radeon
>driver. It's the only way I can get X to start with the driver. Note 15bits
>isn't supported no DRI is disabled.
What happens if you explicitly disable DRI? (Comment out 'Load "
On Sat, 2006-Mar-25 21:39:27 +1100, Peter Jeremy wrote:
>What happens if you simulate read-ahead yourself? Have your main
>program fork and the child access pages slightly ahead of the parent
>but do nothing else.
I suspect something like this may be the best approach for your applica
On Tue, 2006-Mar-28 06:00:23 +1000, Alastair G. Hogge wrote:
>On Tuesday 28 March 2006 04:08, Peter Jeremy wrote:
>> On Mon, 2006-Mar-27 17:58:32 +1000, Alastair G. Hogge wrote:
>> >Having some problem with Xorg-6.9.0 and the radeon or ati driver on mad64
>> >system. X
el config
>and I've also added the appropriate lines to xorg.conf
How did you build xorg.conf?
>dmesg and pciconf are attached
They have been text filled, making them unintelligible.
Can you please post dmesg and /var/log/Xorg.0.log without text-filling the
e.
However, systat is reporting 23-25MB/sec (whereas dd peaks at ~30MB/sec) so the
time to gzip the datafile isn't that much different to the time to just read it.
My guess is that the read-ahead algorithms are working but aren't doing enough
re-ahead to cope with "read a bit
.
I tried generating an 11GB test file and got results consistent with my
previous tests: grep using read or mmap, as well as mmap'ing the entire
file give similar times with the disk mostly saturated.
I suggest you try converting mzip.c to us
. It would be nicer if both read and
mmap managed this gain, irrespective of how the data had been previously
accessed.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ered
via signals (which may not be as easy to handle).
>Peter Jeremy wrote:
>> On an amd64 system running about 6-week old -stable, both ['grep' and 'grep
>> --mmap' -mi] behave pretty much identically.
>
>Peter, I read grep's source -- it is not using m
allocating ~60MB/s
>(or whatever your disk can do), so the pageout thread ought to be able
>to keep up.
This is a laptop so the disk can only manage a bit over 25 MB/sec.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http:/
7.54 real 6.37 user 9.39 sys
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
getting a
valid FH) and then write to it (even though it couldn't have opened the
file for writing).
--
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 reference, what boot manager should I choose next
>time I install FreeBSD? Lilo? Grub? If so, where is the option for
>installing it?
I've never seen any reason to move away from MBR. If you want to use
LILO or Grub, you will need to install and configure it yourself -
google shou
ackets.
How much RAM is there now? Why did you add the additional RAM (since
you suggest the machine isn't heavily loaded)? What happens if you
remove the RAM?
It's possible that the additional RAM means that you are running out
of KVA under high network load.
--
Peter Jeremy
sm
ns are also rare, missing a change
could have far more subtle effects than installworld failing.
--
Peter Jeremy
pgpoyOKBJKOE4.pgp
Description: PGP signature
satisfactory solution AFAIK. Look for 'SIGDANGER' in the archives.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
md64, the 'LM' flag will be set in 'AMD Features='. Looking at the
code in identcpu.c, I suspect it may be the same for emt64.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
gging into the inode structures I though it would be a good
>idea to check my understanding to this point. Am I on the right path?
Yes you are.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sat, 2006-Mar-04 00:25:01 +0200, Dmitry Pryanishnikov wrote:
>On Sat, 4 Mar 2006, Peter Jeremy wrote:
>>swap space for a process and failed. The kernel tries to recover by
>>killing the largest process (which should also be syslog'd). I'm
>
> In my case, not a
he kernel tries to recover by
killing the largest process (which should also be syslog'd). I'm
surprised that you got this on the "rm" as the buildworld should
create bigger processes. If the "rm" was killed, you will need to
re-issue it to actually delete the files
D, I'd make sure I bought an
>appropriately-sized spare disk at the same time as the rest of the set.
Solaris requires that all disks in a RAID set have the same firmware
version (though this isn't documented very well). Tru64 requires that
both system disks have the
>I think the filesystem must be unmounted to enable softupdates.
One approach would be to stick a script into /etc/rc.d that executes
early (before root is made R/W) to run "tunefs -n enable ..." and then
delete the script after rebooting.
--
Peter Jeremy
___
igured out why the system freezes in the middle of a core dump.
Are you dumping to an ATA or SCSI disk? If the latter, it's possible that
the panic has upset the CAM subsystem (though this isn't supposed to happen).
--
Peter Jeremy
___
freebs
appear to recover from errors on the hardware side. In my case,
that USB port wedges and cannot be used until the system is reset
(though other ports are OK).
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rnings?
Are you able to successfully use floating point (and get correct answers)?
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
his might help
identify where the problem is.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
are built as part of the kernel build process. Can you please
explain how you are attempting to compile the kernel.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
ggest running (eg) memtest86 on it for a
few hours and see if that picks anything up.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
l seeing it on any other drivers.
> I'll try to check with -current as soon as
>I can install it on this machine.
Same thing happens on -current/amd64 using a
bge0:
>I am using FreeBSD 6.0-STABLE #15: Tue Jan 31 21:25:42 CET 2006
You might like to mention wha
ernel but you have to build the cross build tools and use them to build
the kernel.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, 2006-Feb-01 11:44:08 +, Pete French wrote:
>I have a piece of coode which does some networking, in which I see read
>and write calls failing with 'Interrupted system call' from time to time.
You will get EINTR if the interrupt occurs before any data is read
or wri
ake it dump a core
>file. so, what should I do the next time it happens to make it dump
>core?
"kill -QUIT ..." is the generic answer. sigaction(2) provides the
definitive list of which signals default to dumping core.
--
Peter Jeremy
_
lib/pluginwrapper/flash6.so (0x280f5000)
That last line is definitely wrong. Check /etc/libmap.conf (maybe
rename it temporarily).
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To un
offloading? If so, then
I think you've bumped into the same (mis-)feature.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
roblem with PC
hardware is that vendors regularly "update" the electronics without
changing the model designations. This doesn't affect Windoze users
because they provide updated drivers to match.
--
Peter Jeremy
___
freebsd-stable@
fff8053a340,
lo_name = 0x803f6841 "if_addr_mtx",
lo_type = 0x803f6841 "if_addr_mtx", lo_flags = 196608,
lo_list = {tqe_next = 0x0, tqe_prev = 0x0}, lo_witness = 0x0},
mtx_lock = 4, mtx_recurse = 0}}
(kgdb)
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t doesn't clash with (eg) tip.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e
>left side of the screen and then will only move vertically.
I don't think that should happen, though I doubt that combination is
officially supported.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ly and then shut down cleanly. Presumably the
xorg.conf.new is the result of "Xorg -configure".
How about supplying the command line you used to start X, the output
written to the console and anything else you did between starting X
and getting the console prom
y isolating the
problem.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e the information you promised.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
for the rest of us, how about using same terminology
as the rest of the Project. It makes it much simpler if we all agree
on the meanings of the words we use.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
m code is not looping when passed 1610612736 (1.5G) - which explains
the rapid exit and incorrect result.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
systems
without customisation. There are too many variables and some kernel
functionality can't be readily converted to modules (eg IPv6 support).
In any case, the way to minimise the kernel footprint is to statically
load all the required functionality and not have any modules.
--
first line of code.
In which case you need to move this thread to freebsd-arch where these
sort of issues are discussed. You need to clearly define your goals
and suggest a design to meet them. If your idea has merit, you'll be
able to convince at least one committer
some good debugging facilities built in - check
malloc(3) for details.
>I'm running flow-capture on AMD64 on Fedora Core 3 with no problems.
>The only issue I run into is lack of disk space! Sometimes 50GB is not
>enough!
Unfortunately, Jonathan didn't say what the process s
e patched...
Have you looked at tools like Bcfg2 ( http://www.mcs.anl.gov/cobalt/bcfg2/ )?
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
of doing so.
>3. FreeBSD Update can't handle updates of jails and other situations that
>package systems deal with just fine.
I don't run jails so I'm not familiar with the problems here. Maybe you'd
like to explain the problems you run into.
--
Peter Jeremy
_
perl, games and UUCP come to mind) but packaging the
entire system is a major undertaking. In any case, I don't see how
packaging the system would help you. Taking Solaris as an example of
an OS which is broken up into lots of packages, patches don't replace
whole packages, they repla
On Mon, 2005-Dec-19 01:37:44 -0800, Jon Dama wrote:
>I haven't see any evidence that suggests using NFS with UDP is actually
>useful. IMO, its a false economy.
On modern hardware anyway. Keep in mind that NFS was written to run
on a 25MHz (or so) 68020.
--
P
>things.
How about big/fragmented UDP packets? NFS typically sends 8K packets
which are split into 6 UDP packets.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscrib
On Sat, 2005-Dec-17 18:19:25 -0700, Scott Long wrote:
>Peter Jeremy wrote:
>>I think FreeBSD Update shows the way forward but IMHO there needs to
>>be an "official" binary update tool accessible from www.freebsd.org.
>
>FreeBSD Update was written by, and is continu
uestions and answer seemingly silly
questions) are going to have to cope with people who've made a typo
somewhere in the sequence and can't explain exactly what they did -
without putting them off FreeBSD.
I think FreeBSD Update shows the way forwa
s not attached - eg in single user after boot). If you
suspect retries are a problem, monitor the I/O rate with iostat or
systat and see if it suddenly drops.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
x27;ll see that
hz now defaults to 1000.
>-acd0: CDRW at ata1-master PIO4
>+acd0: CDRW at ata1-master UDMA33
>
>That's *very* nice!
Again, that's just a change in defaults. Problems were found with DMA to
ATAPI devices so the decision was made to default to PIO4 in 5.x. You can
se
ource code to explain it. Since
you don't mention actual times, is the difference statistically
significant? (see src/tools/tools/ministat)
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
after the last process detaches (see IPC_RMID in shmctm(2)).
> You can check that by looking at
>the output of ``ipcs -p'': If the process IDs listed under
>the CPID and LPID columns don't exist, chances are that the
>memory segment
a 586. And these routines have been disabled since
mid-2001. See my mail in the "Odd performance problems..." thread
for more details.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
optimisations. If there is better code then generic_*() for Athlon
or P4 CPUs, we should implement it. If there isn't, we can get a
(slight) performance improvement by removing the indirection through
*_vector - I suspect that CPUs can't predict/pipeline an indirect
branch as
es a few config files for kgdb]
# gdb kernel.debug /var/crash/vmcore.1
(kgdb) kldsyms
(kgdb) where
Hopefully this will decode #7 and you can provide a few more frames.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.fre
]@
>--
The most likely problem is that your vmcore file doesn't match your kernel.
Are you running kgdb with the same kernel as was running when the system
crashed? (If you don't have that kernel handy, you might as well delete
vmcore.0).
--
Peter Je
and whether we would be able to reproduce it at all.
Depending on your application and the interfaces to it, it might be
feasible to either tee live traffic into both systems and just junk
the responses from your test bed, or "record" live traffic and
replay it into your test bed.
-
g/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebg-gdb.html
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lst I realise that you can't have production machines freezing on
schedule, your assistance in providing more information about your
problem will help make 6.x more stable.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
a "no release without quality documentation assurance" policy.
...
>development is so good. It deserves better and more professional attention to
>the role of end user documentation.
Are you volunteering?
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
those of us who run FreeBSD in VMWare are a
>minority of a minority,
I run FreeBSD in VMware at work. After installing vmware-tools and
telling VMware to use the host clock I haven't seen any clock problems
(definitely in 5.x and I don't recall seeing any i
the problems reported here have been related to VMware
clients. And as someone stated "VMware plays fast and loose with
clocks".
>I'm sure I'm not the only end-user who would appreciate it if the core team
This is nothing to do with the core team.
--
Peter Jeremy
___
es that the hardware (LAPIC) clock (cpu0) needs
to be faster than hz. The original commit ran LAPIC at hz*3 but this
was later changed to hz*2 to reduce overheads.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.or
is correctly allocated.
In order to simulate two clocks, FreeBSD runs the hardware clock at a
high rate and uses two different divisors for the soft clocks (/2 for
tick, /3 for profhz and /15 for stathz). Larger divisors are better
for utilisation statistics but increase clock interrupt overheads.
--
If that file does not exist, it means that the CMOS
clock keeps UTC time. adjkerntz sets machdep.wall_cmos_clock.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
this affecting all users or just one?
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
't recall if
it bit me in 4.x). In my case, the trigger is OpenOffice.org - one
of the offending processes is almost always OOo/program/pagein.
Unfortunately, I haven't been able to get to the bottom of this (and
my son isn't happy that OOo keeps d
RNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tions DDB
options BREAK_TO_DEBUGGER
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e kgdb
to rummage around once you reboot - see
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html
If in doubt, post the output from the above commands here and someone
will hopefully provide further input.
--
Peter Jeremy
__
nable you to build a debug kernel.
>First I used 128 MB swapfile on root partition;
>then tried again with a 128 MB swapfile on /var.
>However, exactly the same deadlock occurs:
Have you pre-allocated the swapfile or is it being allocated as necessary?
If the latter, try "dd if=/dev/zero
ery opaque but some googling turned up a site
with a tutorial (unfortunately, I didn't keep a record).
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
in
/usr/include/sys rather than the ones in /usr/src/sys/sys.
Where is this error occurring during the buildworld? (What are the
latest lines beginning '>>>' and '===>')
What non-standard bits do you have in your command line, /etc/make.conf
or MAKEOBJDIRPREFIX?
ot; so that the output only includes
active directives).
Someone mentioned CISCO IOS directives - the biggest problem with the
CISCO approach is that the configuration is defined as a set of
differences from a default configuration but (AFAIK) the default
configuration isn't
the correct behaviour. You have
specified that you only want to be able to use 7-bit ASCII which
doesn't include accents.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
hats when it rebooted.
That sounds very much like hardware. I'd check the hardware before
anything else - faulty fans, loose cards/cables, give memtest86 a run.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
ound then it's probably hardware. Do you have problems compiling
anything else (buildworld in particular).
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> handle =
>(void *)dlopen("/usr/lib/libm.so", RTLD_LAZY)
It doesn't make sense for an attempt to dlopen libm to complain about
an X library.
You might like to try asking the port maintainer (see the Makefile).
--
Peter Jeremy
___
ebsite is incompatible with lynx is a bit
of an exaggeration.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
it's still usable with a text
browser. On the downside, I notice it now uses cookies.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
r early in the 6.x-STABLE cycle to provide adequate notice.
There's no reason why the handbook can't mention both (or, preferably,
all three) bridging devices - it just needs to mention that if_bridge
doesn't exist in 5.x
--
Peter Jeremy
___
TAPI CDROM
>drive (master on ata0).
You shouldn't have two masters on ata0. I hope that's a typo.
How far through the boot process do you get? I gather the loader runs
successfully and loads the kernel but the kernel can't find ad0. Does
it find the co
twice for
>each file.
Lots of kernel printf messages won't be helping performance.
[1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ctm.html
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.
On Thu, 2005-Sep-22 07:13:29 -0400, Peter D. Quilty wrote:
>On Wed, 2005-09-21 at 18:01 +1000, Peter Jeremy wrote:
>> Have you tried anything other that FreeBSD 5.4 on your Tecra?
>
>No, I haven't. It is my primary laptop and I would prefer not to have
>to load another OS
t;pccard1: <16-bit PCCard bus> on cbb1
...
>an0: at port 0xc000-0xc03f irq
>11 function 0 config 5 on pccard0
>an0: got RSSI <-> dBM map
>an0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>an0: Ethernet address: 00:07:0e:b9:2e:d5
--
Peter Jeremy
__
ice will
cause it to re-assert the interrupt request. I've also seen it when
a device configured for polling (and hence without an installed
interrupt handler) decides to raise an interrupt and gets upset at
the interrupt not being handled.
--
Peter Jeremy
___
as ffs_dirpref
The disassembly is about 280 lines and someone will need to map 0xc063c94d
to the source line within ffs_dirpref() to locate which divide is failing.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
o the loader prompt
and entering "boot -s" or entering "4" (from memory) into the boot menu?
When you boot single user, what are console messages between "Mounting
root..." and the "can't exec getty" message?
--
Peter Jeremy
__
synchronizes with the
profiling/statistics clock then the statistics become unreliable (and
a process can cheat the scheduler by appearing to use no CPU time).
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mai
t, you are more familiar with it. And, once 6.x does become
more stable, moving from 5.x to 6.x will be far easier than moving
from 4.x to 6.x.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
enough RAM.
17 processes sounds a bit high. You can probably find some that aren't
necessary - in particular, you probably only want one or two gettys.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
401 - 500 of 639 matches
Mail list logo