() at taskqueue_swi_run+0x10
ithread_loop() at ithread_loop+0x189
fork_exit() at fork_exit+0xbd
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xad5b0d30, rbp = 0 ---
Debugger(panic)
Stopped at Debugger+0x4c: xchgl %ebx,0x2caefe
db
--
Poul-Henning Kamp | UNIX since Zilog
, the user:sys time
ratio was around 1:1.)
I've seen UNIX systems have typical system/user splits from 1/9 to 9/1
it all depends on what you're doing.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
In message [EMAIL PROTECTED], Colin Percival
writes:
At 15:30 30/11/2003 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Colin
Percival
writes:
When running `make buildworld`, I see large amounts of sys time; eg, 27
minutes user 14 minutes sys for building 5.2, or 14
that the latch
functionality of the i8254 doesn't work properly. This is not
unheard off.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
notice a degradation in performance?
Setting it to 1 forces the timecounter to update every HZ.
You can say that 0 was an optimization which it seems may not be
safe on certain hardware combinations...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP
enough that I have never gotten around to
push it into the kernel.
http://phk.freebsd.dk/patch/GPIB.tgz
On the other hand, GPIB is not going to be a major market for us, but
merely a fringe convenience feature I suspect.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
In message [EMAIL PROTECTED], Gerrit =?iso-8859-1?Q?
K=FChn?= writes:
On Fri, Nov 28, 2003 at 05:03:22PM +0100, Poul-Henning Kamp wrote:
BTW: Are there more people around (except for you and me :-) who would like
to see decent gpib-support in FreeBSD?
Yes, me.
I might have guessed
/32524.html
100% |*| 22559 35.32 KB/s 00:00 ETA
22559 bytes retrieved in 00:00 (35.28 KB/s)
Wow! Learn something new every day around here.
For consistency, we should link ftp(1) to http(1) I guess...
--
Poul-Henning Kamp | UNIX since Zilog
will now ensue and people will argue
that there is a lot more to this dispute than what I've said above.
They're right of course, this is a very short summary :-)
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
softupdates dependencies are involved.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
project for the last ten
years. There, that should save a core member or two the trouble
of posting a disclaimer. Hope you appreciate it :-)
PPPS: If you post this to SlashDot, DaemonNews or other such fora,
you're lame beyond imagination.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
other libc calls may behave in
the same way).
Errno is undefined unless the relevant manual page states otherwise.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
In message [EMAIL PROTECTED], Andrew P. Lentvorski, Jr.
writes:
On Tue, 25 Nov 2003, Poul-Henning Kamp wrote:
I have for myself recently taken a break from all active FreeBSD
development because I find the environment about as pleasant as a
kindergarten right before lunch.
Does this mean
complicated to make it a tunable. Far easier to
go into the ACPI timecounter and just give it a negative quality,
that will disable it.
I'm not sure why Nate think this will change anything with respect
to interrupts, but I pressume he knows what he's talking about.
--
Poul-Henning Kamp | UNIX since
configurations (enabled by CPU_ELAN_PPS option).
The led(4) interface is of course not only useful with lamps, you
can use it with any sort of gadget connected to a GPIO pin.
I can not guarantee that these patches will make it into FreeBSD 5.2.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
In message [EMAIL PROTECTED], Ian Dowse writes:
I was planning to return a filesystem ID of {st_dev, 0} to non-root
users,
Please notice that st_dev is not constant across reboots.
Suggest you hash the real fsid and use the hash instead.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
In message [EMAIL PROTECTED], Josef Karthauser writes:
--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Nov 15, 2003 at 09:42:18AM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Josef
?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing
In message [EMAIL PROTECTED], Kris Kennaway writes:
# dumpon /dev/ccd0b
dumpon: ioctl(DIOCSKERNELDUMP): Invalid argument
Why doesn't this work?
Because it would require the entire GEOM I/O engine to participate
in dumping.
As far as I know you never could dump on CCD.
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], Josef Karthauser writes:
What's the best way to prepare for this? Should I leave some
unallocated space at the beginning of the disk so that any magic geom
bits can be inserted later?
Rather: leave a bit free at the end.
--
Poul-Henning Kamp | UNIX since
) at softclock+0x1fb
ithread_loop(c1180400,c5061d48,c06cbb54,311,558b0424) at ithread_loop+0x192
fork_exit(c050b090,c1180400,c5061d48) at fork_exit+0xb5
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xc5061d7c, ebp = 0 ---
--
Poul-Henning Kamp | UNIX since Zilog Zeus
as to whether it's a reality yet.
Does anyone know?
We're not there yet.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
then be the geom_mirror device and GEOM
should be able to offer that for root mounting.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
...10)/10 sec.
'A-J' gives on for (1...10)/10 sec.
'sAaAbBa': _-_--__-
m%s Morse
'.' dot
'-' dash
' ' letter space
'\n' word space
If somebody has time to hash out a led(4) man page for me I would
be very grateful.
--
Poul-Henning
In message [EMAIL PROTECTED], Bart Smit writes:
On Mon, 3 Nov 2003, Poul-Henning Kamp wrote:
I have introduced the CPU_SOEKRIS option to enable soekris hardware
specific options like the error LED.
great!!!
Support for the 4801's error led comes when Soren tell me how
to fiddle it.
Let
output, you should be able to grab it
in /var/log/messages.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
init /dev/ad0s2g -i -L /etc/gbde/ad0s1g
gbde: /dev/ad0s2g: No such file or directory
That's interesting!
Can you check with diskinfo that the partition has the right size ?
diskinfo -v /dev/ad0s2g
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP
In message [EMAIL PROTECTED], Erwin Lansing writes:
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Oct 25, 2003 at 02:07:34PM +0200, Poul-Henning Kamp wrote:
=20
Can you check with diskinfo
(NULL, mp, V_WAIT);
tl = nfsm_dissect(u_int32_t *, 3 * NFSX_UNSIGNED);
/*
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
way to hose
our overall system performance. I'm not going to set any
specific performance goal at this time, but I think we can
agree that more than one millisecond is way over the line.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
In message [EMAIL PROTECTED], Matthew Jacob writes:
Well, I don't agree with the design here, but it is what it is. I'll
make the change that you've added a requirement for.
This is nothing new, but it is new that we can and do enforce it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
the magic
labels on the disks, according to the script in the announce message:
geom_fox is no where close to finished yet, and your ideas mirror some
of the stuff on my TODO list.
Time, unfortunately, is in short supply for me.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
7147 7147 7147
7147
giving up on 3399 buffers
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED
to mount.
This problem hsould already be fixed, it was caused by a change in
the rijndael/AES code in the kernel.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what
I/O, and therefore likely lead to deadlock.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], Andrew Gallatin
writes:
Poul-Henning Kamp writes:
As soon as these uses of cloning code has been removed, I will move
the floppy and CD drivers under GEOM, paving the way for the
significant changes to the buf/VM system which some of you have
already
/devfs.conf is only
used by the /etc/rc.d/devfs startup script, to setup permissions
via chmod commands and such so no real relationship to the
devfs command.
Yes, probably a good idea.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
:-)
I personally end up less(1)'ing /etc/rc.d/* every time I want
to do something...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
In message [EMAIL PROTECTED], Bernd Walter writes:
On Mon, Oct 20, 2003 at 01:44:50PM +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Andreas Klemm writ
es:
[EMAIL PROTECTED] ~ ls -l /dev/ugen*
crw-r--r-- 1 root operator 114, 0 Oct 20 13:14 /dev/ugen0
crw-r--r-- 1 root
on harddisk.
There was a problem with an updated version of the kernels AES/Rijndael
routines, this was fixed some hours later than you CVSup'ed yesterday.
Pull in -current now, then it will work.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
I'm chasing a problem which indicates that I may have borked the
kernel with one of my last commits. I'm hunting it right now.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
from NIST ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
to `rijndael_cipherInit'
/usr/src/sys/geom/bde/g_bde.h:207: undefined reference to `rijndael_blockDecrypt'
I had same problem until I added device random to kernel config file.
Yes, the recent commits to the rijndael code must have messed up something
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
vm_pagezero(0,d88b1d48,c068719b,314,36208a1) at 0xc05fe98e = vm_pagezero+0xee
fork_exit(c05fe8a0,0,d88b1d48) at 0xc04e5a7f = fork_exit+0xcf
fork_trampoline() at 0xc0630ddc = fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd88b1d7c, ebp = 0 ---
db
--
Poul-Henning Kamp | UNIX since Zilog
.
Poul-Henning
[1] Not terribly because I seldomly use it myself, but the
inconsistency still bothers me.
[2] Your POLA may vary.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
-persistent media, a socket, a FIFO, a device, a process
and almost any oddball thing you can can come up with.
Persistence is a very optional property and it has nothing to do
with the object living in the filesystem naming space.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
) before you don't now, it will happen
automatically. If it doesn't happen, it wouldn't have worked to run
mknod(8) either.
Poul-Henning
PS: Eric, didn't you work at TFS at one time ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
bsdlabel -w /dev/ad3
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], ecsd writes:
MAKEDEV was the cheese since year zero. [...]
I suggest you stick with 4-stable until you have caught up with
the changes and the documentation.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
+1789,8 @@
xpt_release_ccb(ccb);
- free(rcap, M_TEMP);
+ if (rcap != NULL)
+ free(rcap, M_TEMP);
return (error);
}
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
In message [EMAIL PROTECTED], Poul-Henning Kamp writes:
In message [EMAIL PROTECTED], Dan Nelson writes:
Can you try this patch ?
Oops! ignore the scsi_da.c patch!
Index: scsi_da.c
===
RCS file: /home/ncvs/src/sys/cam/scsi
the key-handling a fair bit. I don't have an
ETA right now, but I hope to make it before 5.2
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
this means I have to wait about 60-90
seconds during boot time before the boot process continues:
Does the length of the delay depend on the precense of a CD in the
drive ?
I can see various hacks we could do to circumvent this delay, but
none of them are particularly attractive to me.
--
Poul-Henning
In message [EMAIL PROTECTED], Sascha Holzleiter wri
tes:
On Thu, 2003-10-02 at 08:55, Poul-Henning Kamp wrote:
Does the length of the delay depend on the precense of a CD in the
drive ?
Yes. If I have a cd in the drive while booting there is no delay.
The cd is read and status instantly
../../../dev/firewire/fwmem.c: In function `fwmem_strategy':
../../../dev/firewire/fwmem.c:316: warning: implicit declaration of function
`BUF_REFCNT'
*** Error code 1
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
of /crypto failed: Resource temporarily unavailable
Did you call gbde detach before the umount ? You need to unmount
first.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
In message [EMAIL PROTECTED], Thorsten Greiner writes:
* Poul-Henning Kamp [EMAIL PROTECTED] [2003-09-30 10:54]:
Did you call gbde detach before the umount ? You need to unmount
first.
After investigating further I think I have found the reason for the
problem. When I created the disklabel
, you could damage your hardware, or cause Wierd
Untraceable Problems.
...
not to mention escape of magic smoke, and in truly worst case:
permanent tax-exemption.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
qualify
due to nepotism, ia64 is not yet there. That leaves us only
sparc64 as candidate for that job.
Therefore I would like to keep the sparc64 port alive, even at a
pretty high cost in effort.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
dismantle and remove the interface and destroy the dev_t
| at last close of the device.
|
| Remove code from MOD_UNLOAD to dismantle things.
|
| Remove the list used to hang the tunnels from, it is no longer needed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
/uscanner.c
Failure to cache result of make_dev()
./dev/vinum
Failure to cache result of make_dev() ?
Thanks in advance!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since
In message [EMAIL PROTECTED], Greg 'groggy' Lehey
writes:
--yRA+Bmk8aPhU85Qt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
subsequent if_tap.c patch would
likely break the way people expect the vmnet device to work so I
have already canned that.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
from, it is no longer needed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
To: [EMAIL PROTECTED]
Subject: Geom and Gbde slides
From: Poul-Henning Kamp [EMAIL PROTECTED]
Date: Sun, 21 Sep 2003 21:19:52 +0200
Message-ID: [EMAIL PROTECTED]
As promised, but somewhat delayed, I have uploaded my slides from
BSDcon03 to my web-server:
http://phk.freebsd.dk/pubs
To: [EMAIL PROTECTED]
Subject: CF image building script (for soekris etc)
From: Poul-Henning Kamp [EMAIL PROTECTED]
Date: Sun, 21 Sep 2003 21:22:59 +0200
Message-ID: [EMAIL PROTECTED]
I promised various people to post my shellscript for building a CF
image for my soekris boxes:
http
In message [EMAIL PROTECTED], masta writes:
Thanks phk,
May I use this in wifibsd without any copywrite dramma?
Absolutely, go right ahead.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
88 (fsck_ufs), uid 0: exited on signal 8
I noticed the same thing when I did not try to boot into single-user mode.
Try to pull in the commit I just did to syscons, I looks like I messed
something up somewhere :-(
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
I seem to have messed up /dev/console. If you have any console
related problems with -current from today, please upgrade to
after this commit before sending me your error report!
Poul-Henning
phk 2003/09/26 12:35:50 PDT
FreeBSD src repository
Modified files:
sys/alpha/tlsb
In message [EMAIL PROTECTED], Ulrich Spoerlein writes:
--OwLcNYc0lM97+oe1
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, 23.09.2003 at 10:27:12 +0200, Poul-Henning Kamp wrote:
On sparc64 (or with geom_sunlabel in your
of CD images.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL
the same panic I named g_up double
panic. I post calling stack for it recently, but withous function
arguments (gdb can't find them), and it is the same in g_* section. GEOM
is phk@ area. Ask him to deal with.
Uhm, complete_rqe() is not GEOM, that's Vinum...
--
Poul-Henning Kamp | UNIX since
seeking to preposterous offsets, so they should
not be handled with panics.
They most certainly should! If the range checking in any filesystem
is not able to catch these cases I insist that GEOM do so with a panic.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
In message [EMAIL PROTECTED], Bernd Walter writes:
On Wed, Sep 17, 2003 at 09:07:24AM +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Bruce Evans writes:
This is either disk corruption or an ffs bug. ffs passes the garbage
block number 0xe5441ae9720 to bread. GEOM
.
That's the point: Our filesystems should be robust. If they're
not they should be fixed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/ZgHiWry0BWjoQKURAvPFAJ9vLJrNmZgRDT9Hhoked8il+5YGbACdENuh
U4x0Dyqvq01pYLya7q4Xo60=
=vAfZ
-END PGP SIGNATURE-
--OgqxwSJOaUobr8KG--
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD
(irq15: ahc0)
trap number = 12
panic: page fault
Uptime: 2d3h22m53s
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
In message [EMAIL PROTECTED], Josef Karthauser writes:
--7UIJfHqpdi+oBJdT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Sep 09, 2003 at 05:14:15PM +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Kevin
produced them if they will be willing to ship abroad, but I
doubt they are set up for that sort of thing.
The xfig source is here:
http://phk.frebsd.dk/misc/bsdcon03.fig
http://phk.frebsd.dk/misc/bsdcon03.pdf
Enjoy...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
In message [EMAIL PROTECTED], Brad Knowles writes:
I have interpreted your post to mean that it's okay for other
people to print up t-shirts, based on this image. However, if you
prefer that I take this down, just let me know.
Yes, absolutely.
--
Poul-Henning Kamp | UNIX since
In message [EMAIL PROTECTED], Brad Knowles writes:
At 2:11 AM +0200 2003/09/12, Poul-Henning Kamp wrote:
Yes, absolutely.
Okay, it should be down in a few minutes.
You misunderstood:
Yes, it is absolutely OK for you do print T-shirts, mugs, or anything
else you might want to use
it the subject of
a bikeshed discussion.
:-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
laptop this morning.)
If this is the case it is a bug in fdisk(8).
The only restriction GEOM introduces is that you cannot change an
_open_ device. Anything else is a bug.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
BSD disklabel.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
to be done with the
fdcontrol(8) utility instead.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
an
entry in paths.h.
Any objections against me committing the follwoing fixes to
-current ?
Yes, please don't.
We should not revert to putting BSD labels on everything.
I'll find the root cause and fix that instead, it's probably
fall-out from my ioctl change.
--
Poul-Henning Kamp | UNIX since
that at this point, we plan to talk
about it at BSDcon03 and try to settle on our strategy for the entire
area, and if we manage that we'll communicate it of course.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
, the same
effect could be had much cleaner by writing the signature of the dump
to a file in /var/ somewhere and not reading dumps already in that
file.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3
In message [EMAIL PROTECTED], Doug Barton writes:
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will require some gymnastics to accomodate
it.
Yeah
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
that is was hard to tell if the
problems I saw (lost packets) were due to this change or others.
This patch is different from the one you got earlier Sam, in particular
it only sets the interrupt holdoff (and much more conservatively)
and does not touch the DMA parameters at all.
--
Poul-Henning
of places in the giant/no-giant
shims for GEOM. I found one convenient trick was to sleep with a
timeout instead. It's not beautiful but it works.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
in use,
then the answer is probably no.
For that job you want to use the correct tools: fdisk(8) and
bsdlabel(8) (tacitly assuming i386 here).
If you are talking about a problem during initial install of FreeBSD
you need to provide more details about it.
--
Poul-Henning Kamp | UNIX since
down the devbuf thing by changing all users of M_DEVBUF until
something trips...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
kern.geom.debugflags=N and see if that offers
any clues.
N |= 1 topology events
N |= 2 bio processing (ie: many lines for each I/O)
N |= 4 access processing (open/close)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
In message [EMAIL PROTECTED], Doug Barton writes:
Poul-Henning,
Please don't forget to update src/share/examples/etc/make.conf
accordingly.
Hmm, so this stuff is documented both in make.conf(5) and an examples
file ? Sounds like one place too many to me.
--
Poul-Henning Kamp | UNIX
In message [EMAIL PROTECTED], Poul-Henning Kamp
writes:
phk 2003/08/30 09:44:27 PDT
FreeBSD src repository
Modified files:
sys/vm swap_pager.c
Log:
Add a close() method to a swapdev.
Add a GEOM based backend.
This is actually a quite significant step
...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing
301 - 400 of 1643 matches
Mail list logo
