Re: developer laptop choices
On Mon, Jun 16, 2008 at 08:52:44AM -0500, Ed Ahlsen-Girard wrote: I'm curious as to the 'modal' laptop that the developers use - that would probably be a good steer for what to buy. usually people seem to prefer laptops that have keyboards. some really advanced models may even have a screen but that is really optional. also notice that battery is sort of important as otherwise it's not really a laptop right? there seems to be a greate debate as towards pros and cons of clitors (vs pads mice and etc) but perhaps that is solely a sexuality induced measure. all other bells and whistles such as usb or embedded audio speakers with dolby 3d sound and stuff surely only eat extra battery and yeah -- GET CHICKS! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: uvm_mapent_alloc: out of static map entries on 4.3 i386
On Fri, May 16, 2008 at 08:21:25AM -0700, Darrian Hale wrote:
Can you please point me to where the diffs you refer to reside?
I'd definitely like to try them out.
most of these are filed in sendbug (some for months) already...
here is a cumulative diff also w/ a bonus himem high-quality
software (in caase you managed to squeeze more than 4g of memory
in your box ;).
cu
--
paranoic mickey (my employers have changed but, the name has remained)
Index: arch/i386/conf/GENERIC
===
RCS file: /cvs/src/sys/arch/i386/conf/GENERIC,v
retrieving revision 1.603
diff -u -r1.603 GENERIC
--- arch/i386/conf/GENERIC 25 Feb 2008 23:16:47 - 1.603
+++ arch/i386/conf/GENERIC 7 May 2008 12:55:43 -
@@ -37,6 +37,8 @@
config bsd swap generic
mainbus0 at root
+himem0 at root # himem.sys
+scsibus* at himem?
cpu0 at mainbus?
bios0 at mainbus0
Index: arch/i386/conf/files.i386
===
RCS file: /cvs/src/sys/arch/i386/conf/files.i386,v
retrieving revision 1.172
diff -u -r1.172 files.i386
--- arch/i386/conf/files.i386 4 Mar 2008 21:14:29 - 1.172
+++ arch/i386/conf/files.i386 7 May 2008 12:55:43 -
@@ -440,6 +440,10 @@
attach esm at mainbus
file arch/i386/i386/esm.cesm needs-flag
+device himem: scsi
+attach himem at root
+filearch/i386/i386/himem.c himem needs-flag
+
#
# VESA
#
Index: arch/i386/i386/autoconf.c
===
RCS file: /cvs/src/sys/arch/i386/i386/autoconf.c,v
retrieving revision 1.78
diff -u -r1.78 autoconf.c
--- arch/i386/i386/autoconf.c 27 Dec 2007 18:04:27 - 1.78
+++ arch/i386/i386/autoconf.c 7 May 2008 12:55:43 -
@@ -71,6 +71,7 @@
#include dev/cons.h
#include ioapic.h
+#include himem.h
#if NIOAPIC 0
#include machine/i82093var.h
@@ -117,6 +118,10 @@
if (config_rootfound(mainbus, NULL) == NULL)
panic(cpu_configure: mainbus not configured);
+
+#if NHIMEM 0
+ config_rootfound(himem, NULL);
+#endif
#if NIOAPIC 0
if (nioapics 0)
Index: arch/i386/i386/himem.c
===
RCS file: arch/i386/i386/himem.c
diff -N arch/i386/i386/himem.c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ arch/i386/i386/himem.c 9 May 2008 09:23:37 -
@@ -0,0 +1,476 @@
+/* $OpenBSD$ */
+
+/*
+ * Copyright (c) 2008 Michael Shalayeff
+ * All rights reserved.
+ *
+ * Permission to use, copy, modify, and distribute this software for any
+ * purpose with or without fee is hereby granted, provided that the above
+ * copyright notice and this permission notice appear in all copies.
+ *
+ * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+ * WHATSOEVER RESULTING FROM LOSS OF MIND, USE, DATA OR PROFITS, WHETHER IN
+ * AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+ * OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ */
+
+#include sys/param.h
+#include sys/systm.h
+#include sys/proc.h
+#include sys/kthread.h
+#include sys/queue.h
+#include sys/mutex.h
+#include sys/buf.h
+#include sys/disk.h
+#include sys/disklabel.h
+
+#include scsi/scsi_all.h
+#include scsi/scsi_disk.h
+#include scsi/scsiconf.h
+#include scsi/sdvar.h
+
+#include uvm/uvm.h
+
+/* arbitrary numbers */
+#defineHIMEM_MAXCMDS 256 /* each one is a page */
+
+/* derived from page table structure */
+#defineHIMEM_OFFSET((sizeof(struct hibuf) + 7) / 8)
+#defineHIMEM_MAXSEGS (512 - HIMEM_OFFSET - 2)
+#defineHIMEM_MAXPHYS (HIMEM_MAXSEGS * PAGE_SIZE)
+
+#defineHIMEM_PDE (8)
+#defineHIMEM_VA(HIMEM_PDE 21)
+#defineHIMEM_LOW (HIMEM_VA + (PAGE_SIZE * HIMEM_OFFSET))
+#defineHIMEM_HIGH (HIMEM_VA + (PAGE_SIZE * 512))
+#definePDE_MASK((512 * (PAGE_SIZE / DEV_BSIZE)) - 1)
+
+void himem_zefix(u_int64_t *, void *, void *, u_int); /* locore.s */
+
+struct hibuf {
+ TAILQ_ENTRY(hibuf) hb_list;
+ paddr_t hb_pa;
+ struct scsi_xfer *hb_xs;
+ void *hb_src, *hb_dst;
+ u_int hb_bno, hb_len;
+ int hb_flags;
+#defineHIMEM_WAKE 0x0001
+};
+
+struct himem_softc {
+ struct device sc_dev;
+ struct scsi_link sc_link;
+
+ int sc_flags;
+#defineHIMEM_RDONLY0x0001
+#defineHIMEM_DISKLABEL 0x0002
+ int sc_size;/* blocks */
+
+ struct proc *sc_kthread;
+ u_int64_t *sc_pdir;
+ paddr_t sc_paddr;
+ struct mutex sc_inmtx;
+ struct mutex sc_freemtx;
+ TAILQ_HEAD
Re: uvm_mapent_alloc: out of static map entries on 4.3 i386
On Thu, May 15, 2008 at 10:07:14PM -0400, Ted Unangst wrote: On 5/15/08, Kevin [EMAIL PROTECTED] wrote: All, I'm getting quite a lot of these errors in /var/log/messages and can't seem to find an appropriate fix in the archives: May 14 21:05:54 svr02 /bsd: uvm_mapent_alloc: out of static map entries May 14 21:57:47 svr02 /bsd: uvm_mapent_alloc: out of static map entries May 14 23:00:05 svr02 /bsd: uvm_mapent_alloc: out of static map entries May 15 07:27:53 svr02 /bsd: uvm_mapent_alloc: out of static map entries May 15 07:39:59 svr02 /bsd: uvm_mapent_alloc: out of static map entries N.B. This machine serves mirror content for various F/OSS projects in addition to standard www content, so it quite often has 350 users concurrently connected downloading mirrored content (in addition to visitors who're actually visiting the site). Are you using squid as well? You may try doing something like restarting apache. The problem seems related to certain long running processes with fragmented address spaces. Basically, in order to manage address spaces, the kernel keeps track of a bunch of maps. Entries in these maps are stored in... map entries. In certain situations, the kernel can't wait to allocate a map entry, so it grabs one from a static list. Previously, when they ran out, the kernel paniced. Now it just says uh oh. The kernel will merrily go on making more static entries as needed. the problem is not in the user land. the problem is in i386 pmap which abuses kmem_map that is there for malloc(9)s use and allocates pv_entries from it. this leads to enormous kmem_map fragmentation and unaccounted allocations that does not show up in the vmstat and as well leads to livelocks (sleeping on kmem_map) and out of space in kmem_map panics as well. there is a number of measures to remediate the situation proper - convert pv_entries allocations to pool (i have a diff if you wanna) - backend malloc w/ pool (filed in sendbug) - a number of uvm fixes (such as amap ops) that reduce fragmentation. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: How to copy/pipe console buffert to file?
On Thu, May 08, 2008 at 03:06:49PM -0500, Joachim Schipper wrote: On Thu, May 08, 2008 at 12:37:47PM +0200, rancor wrote: Hi Is there any way of copy/pipe the information on the console to a file? I need the same information that I can see of I hold down Ctrl+Shift and using PageUp/Down when I'm on the console. I'm not using serial, that would be simple but I'm stuck right on the machine. While Mickey's solution is rather cool, misc/screen would allow you to copy text off the screen (Ctrl-A [, select. Ctrl-A ]). It also has a lot of other useful commands. i'd think it's impossible to find a person today who does not know what screen is... the question was how to capture existing (as in already happened) console output as far as i understand it. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: How to copy/pipe console buffert to file?
On Thu, May 08, 2008 at 12:37:47PM +0200, rancor wrote: Hi Is there any way of copy/pipe the information on the console to a file? I need the same information that I can see of I hold down Ctrl+Shift and using PageUp/Down when I'm on the console. I'm not using serial, that would be simple but I'm stuck right on the machine. dd if=/dev/mem of=/tmp/a bs=32k skip=23 count=1 cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: How to copy/pipe console buffert to file?
On Thu, May 08, 2008 at 10:59:46AM +, mickey wrote:
On Thu, May 08, 2008 at 12:37:47PM +0200, rancor wrote:
Hi
Is there any way of copy/pipe the information on the console to a file? I
need the same information that I can see of I hold down Ctrl+Shift and using
PageUp/Down when I'm on the console. I'm not using serial, that would be
simple but I'm stuck right on the machine.
dd if=/dev/mem of=/tmp/a bs=32k skip=23 count=1
if you ain't require original color pipe thru
hexdump -e '%_c\n' | awk 'NR % 2 {s=s $0} END {print s}'|more
cu
--
paranoic mickey (my employers have changed but, the name has remained)
Re: Editing C with...
[EMAIL PROTECTED] wrote: Yes, I know, it's completely a dumb question; but I'm curious about it. I'm just learning C applied in networking area and I wonder what editor is preferred by OpenBSD developers. At present moment I use vim. it's not the size of your editor -- it's what you do w/ it that matters. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Kernel trap with custom ramdisk
On Tue, Apr 29, 2008 at 02:28:11AM +0400, B A wrote: Hello! I'm trying to build custom kernel+ramdisk for my router. But I'm getting: panic: pmap_enter: missing kernel PTP! Stopped at 0x0d47ba08: leave Any ideas what I did wrong? I build 5 meg ramdisk, I can't even boot larger ramdisk's, system just immediately rebooting. peraps you need larger NKPTP like 8 for example cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Chatting with developers? Is it soo 1996?
On Wed, Apr 16, 2008 at 08:16:11AM -0500, Jacob Yocom-Piatt wrote: Artur Grabowski wrote: Andris [EMAIL PROTECTED] writes: On Tue, Apr 15, 2008 at 2:20 PM, Theo de Raadt [EMAIL PROTECTED] wrote: I found an old email on the mailing lists, dating back to 1996, when Theo announced users could connect and chat with the developers on their ICB server. Many developers did not like it, so please leave them alone. I can understand your point, but isn't there a way of connecting to just read? I mean, we only read, you talk. That would be very interesting. Is there a way to connect to your phone to just listen? Not talk, just listen. That would be very interesting. apparently that's what the government thinks here in the US too (read CALEA, et al). this is the most obvious indication that something is a good idea. i think you've just invoked the godwin's law... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Cd boot issue, boot.conf
On Mon, Mar 31, 2008 at 06:21:30PM +0400, B A wrote: Hello! Do you know why bootloader ignores option set device cd0a on etc/boot.conf while booting from cd? It's always asking me about root device. because root on cd is not supported. there are diffs that were sent about 2-3y ago but they were not welcome for some reason... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: kernel naming proposal
On Wed, Feb 27, 2008 at 01:15:56PM +0100, Piotrek Kapczuk wrote: 2008/2/25, Don Jackson [EMAIL PROTECTED]: The issue is that when building and installing new kernels (eg, when a new security patch is released), it is not totally obvious to the (automated) build script what the file /bsd really is, is it the uniprocessor kernel, or a link to the multiprocessor kernel? If the latter, than blindly copying the new uniprocessor kenel to /bsd is probably not what you want to do. let's rename ls(1) -- it's so 80s man! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: RNG and intel 815 support
On Wed, Feb 06, 2008 at 08:57:14PM -0500, scott wrote: I have an Intel D815EEA2 motherboard; its spec is supposed to include the RNG hardware; however, the dmesg output is void of any indication that obsd discovered or uses it. not all chipset versions have the rng. perhaps yours does not. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Real men don't attack straw men
On Thu, Dec 13, 2007 at 11:58:51AM -0700, Tom Rosso wrote: On Dec 13, 2007 10:30 AM, Mayuresh Kathe [EMAIL PROTECTED] wrote: Good people of MISC land, could we please drop this thread, its lasted way longer than really needed. I'm enjoying watching RMS struggle and fail to make any headway with his argument. isn't it like hitler in '44 ? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD in the webcomic XKCD
On Mon, Nov 26, 2007 at 01:55:16PM +0200, Paul Irofti wrote: On Mon, Nov 26, 2007 at 10:57:28AM +, Edd Barrett wrote: On 26/11/2007, Richard Wilson [EMAIL PROTECTED] wrote: http://www.xkcd.com/349/ Observe the ALT text on the comic. Haven't seen a PR on that one... What do they mean by this? poor dude pbly cannot do adding proper in his disklabel... MATH WORKS BITCHES! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Kernel problem...
On Sat, Nov 24, 2007 at 12:13:41PM -0300, Limaunion wrote: Hi misc! I upgraded my old i486 box to a _new_ pentium 166, but after less than 24 hours running it I got a kernel crash. I'm sending dmesg plus some screenshots from ps + trace + show registers. this looks like a signal jump to a trampoline but is hard to tell w/o poking in pcb (ps /a; x uarea*). do you get it often? Thanks in advance for any comment. Jorge. PS: I've been running memtest86+ during the las 109 hours (229 passes) without a single error detected. screenshot 1: http://img57.imageshack.us/img57/6695/robsd1qx8.jpg screenshot 2: http://img104.imageshack.us/img104/3669/robsd2xa7.jpg screenshot 3: http://img217.imageshack.us/img217/3852/robsd3pw3.jpg screenshot 4: http://img216.imageshack.us/img216/1834/robsd4nx5.jpg OpenBSD 4.2 (GENERIC) #375: Tue Aug 28 10:38:44 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 167 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX cpu0: F00F bug workaround installed real mem = 66678784 (63MB) avail mem = 55799808 (53MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/15/95, BIOS32 rev. 0 @ 0xfdb80 apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled) apm0: APM power management enable: power management disabled (1) apm0: APM engage (device 1): power management disabled (1) apm0: AC on, battery charge unknown apm0: flags b0102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI BIOS has 5 Interrupt Routing table entries pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371AB PIIX4 ISA rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82439TX System rev 0x01 piixpcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x01 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: WDC AC310200R wd0: 16-sector PIO, LBA, 9787MB, 20044080 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: irq 12 piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x01: SMBus disabled xl0 at pci0 dev 8 function 0 3Com 3c905B 100Base-TX rev 0x30: irq 9, address 00:01:02:87:fc:88 exphy0 at xl0 phy 24: 3Com internal media interface xl1 at pci0 dev 9 function 0 3Com 3c905B 100Base-TX rev 0x30: irq 10, address 00:01:02:6e:c5:08 exphy1 at xl1 phy 24: 3Com internal media interface vga1 at pci0 dev 10 function 0 S3 Trio32/64 rev 0x54 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) isa0 at piixpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 usb0 at uhci0: USB revision 1.0 uhub0 at usb0: Intel UHCI root hub, rev 1.00/1.00, addr 1 biomask f965 netmask ff65 ttymask ffe7 pctr: 586-class performance counters and user-level cycle counter enabled dkcsum: wd0 matches BIOS drive 0x80 root on wd0a swap on wd0b dump on wd0b WARNING: / was not properly unmounted -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD in the webcomic XKCD
On Mon, Nov 26, 2007 at 05:14:50PM +0100, Artur Grabowski wrote: frantisek holop [EMAIL PROTECTED] writes: but can't call yerself a unix guru if havent fu*ed up dual boot at least once :] never fucked up a dual boot. Only tried it two times and both times it worked. Dual boot is for sissies who can't get a second machine. doh! i have more than one and i dual-boot most of 'em (: cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Is anybody working on Wine?
On Wed, Nov 21, 2007 at 12:13:53PM +0300, Dmitrij Czarkoff wrote: Is anybody working on WINE for OpenBSD? The avaliable package support to small amount of software for now... most pplz seem to work on beer rather... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: avail mem is only 66% of real mem
On Mon, Nov 05, 2007 at 04:43:48PM -0800, Ted Unangst wrote: On 11/5/07, Wade, Daniel [EMAIL PROTECTED] wrote: Any guess as to why I'm losing about 33% of my RAM? When you are only working with 32MB to start with every little bit counts. the kernel and the buffer cache have to go somewhere. not buffer cache nomore (: cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD kernel janitors
On Wed, Oct 31, 2007 at 03:01:03PM +, [EMAIL PROTECTED] wrote: On 31.10-08:20, Theo de Raadt wrote: [ ... ] They don't need a list. They could already have started coding. Yet we see how few people actually do start coding. Instead, they choose to write in english... on the counter-side we appear to have people who can code but are unable to communicate productively otherwise. as opposed to a majority of people who talk and not code anything? here is a solution for you -- read http://openbsd.org/query-pr.html and start fixing those. pretty simple solution if you get no bugs of your own. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD kernel janitors
On Wed, Oct 31, 2007 at 01:41:14PM -0200, Marcus Andree wrote: snip as opposed to a majority of people who talk and not code anything? here is a solution for you -- read http://openbsd.org/query-pr.html and start fixing those. pretty simple solution if you get no bugs of your own. cu -- Good point. I was wondering what to do next, once/if I can finish fixing a wi driver issue... Let me raise one question... There are quite a few books written about how certain things work on a kernel level, but they're for other operating systems. start writing a book then... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD kernel janitors
On Wed, Oct 31, 2007 at 03:50:14PM +, n0g0013 wrote: On 31.10-15:25, mickey wrote: [ ... ] on the counter-side we appear to have people who can code but are unable to communicate productively otherwise. as opposed to a majority of people who talk and not code anything? here is a solution for you -- read http://openbsd.org/query-pr.html and start fixing those. pretty simple solution if you get no bugs of your own. anyone, who thinks that learning and development need nothing more than web web access to PR database is mistaken. development is a complex process, one that requires a great number of things not least which is an idea of where to start. yes development of yourself is a complex process to which only yourself can do any help (or harm). nobody here is your mother and will not do anything about what you want to get. get it yourself! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Non-x86
On Fri, Oct 26, 2007 at 01:39:56PM +0200, Martin Schr?der wrote: 2007/10/26, Lars Noodin [EMAIL PROTECTED]: I'm not sure there is a context in which Wikipedia is ever relevant: it It's only as relevant as YOU help make it. Shut up and improve it. why don't you shuddup? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: MAXDSIZ 1GB memory limit for process
On Mon, Oct 22, 2007 at 07:17:02PM +0200, Markus Hennecke wrote: Richard Storm schrieb: On 10/22/07, Ted Unangst [EMAIL PROTECTED] wrote: On 10/21/07, Richard Storm [EMAIL PROTECTED] wrote: Is it possible to bypass this limit somehow? depends, but if it's easy to bypass a limit, it's not much of a limit. Is there possible workarounds for my program to allocate more memory than 1GB? http://monkey.org/openbsd/archive/misc/0412/msg01039.html So mmap seems to be the way. it's outdated. mmap is counted into dsiz limit now. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: iSCSI
On Thu, Oct 18, 2007 at 04:13:35PM +0200, Artur Litwinowicz wrote: Hi :), quick question: how can I connect OpenBSD box to iSCSI storage ? by means of an iSCSI cable? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Get developers some big machines to support more RAM
On Mon, Oct 08, 2007 at 11:23:12AM +0200, Tonnerre LOMBARD wrote: Salut, On Mon, Oct 08, 2007 at 09:14:05AM +, mickey wrote: myself in need to build some big, phat machines (8GByte, or even 16GByte RAM) for a customer that run OpenBSD *and* having seen (again) a discussion on 'how much RAM is supported' [0] I decided to PAE support has already been hacked up. apparently it was backed out for some obscure stability problems on certain amd machines. and this is (as i see it) fault exactly of these people who wants this support since when it was asked for the diff received ZERO testing for large memory use from the list. i will repost it again (w/ weak hope) that somebody bothers to actually test or look at it... PAE is slow and has hairy paws. I am glad that we have real amd64 machines now so we don't need it anymore. you do not need it perhaps. otherwise there has been lots of talkers for it on i386. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Get developers some big machines to support more RAM
On Mon, Oct 08, 2007 at 09:43:25AM +, mickey wrote: On Mon, Oct 08, 2007 at 11:23:12AM +0200, Tonnerre LOMBARD wrote: Salut, On Mon, Oct 08, 2007 at 09:14:05AM +, mickey wrote: myself in need to build some big, phat machines (8GByte, or even 16GByte RAM) for a customer that run OpenBSD *and* having seen (again) a discussion on 'how much RAM is supported' [0] I decided to PAE support has already been hacked up. apparently it was backed out for some obscure stability problems on certain amd machines. and this is (as i see it) fault exactly of these people who wants this support since when it was asked for the diff received ZERO testing for large memory use from the list. i will repost it again (w/ weak hope) that somebody bothers to actually test or look at it... PAE is slow and has hairy paws. I am glad that we have real amd64 machines now so we don't need it anymore. besides that what do you think amd64 runs? (: it uses the same pae as i386. and it is not any faster. learn what are you talking about... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Get developers some big machines to support more RAM
On Mon, Oct 08, 2007 at 11:53:50AM +0200, Tonnerre LOMBARD wrote: Salut, On Mon, Oct 08, 2007 at 09:44:48AM +, mickey wrote: PAE is slow and has hairy paws. I am glad that we have real amd64 machines now so we don't need it anymore. besides that what do you think amd64 runs? (: it uses the same pae as i386. and it is not any faster. learn what are you talking about... No, it uses 48-bit addresses and some flag bits, but it can use a 64-bit selector rather than two 32-bit ones, improving the performance significantly. format and amount of data is the same. it does not matter how many bits are used or not. it's about how much larger page tables are and how much longer it takes for the tlb reload. or what you think loading 36bit physaddr is slower than loading 48bits? segments have nothing to do w/ page tables and tlb performance. they will be as much slowdown on pae or non-pae page tables. get a clue. you are talking about non-related improvements and might as well compare this to sparc64 tlb performance... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Get developers some big machines to support more RAM
On Mon, Oct 08, 2007 at 12:13:55PM +0200, Tonnerre LOMBARD wrote: Salut, On Mon, Oct 08, 2007 at 10:02:22AM +, mickey wrote: or what you think loading 36bit physaddr is slower than loading 48bits? I think that loading 48-bits in one step is faster than loading 36-bit in two. It is also a matter of experience that amd64 memory access is way faster than i386 with PAE. why do you think that tlb loader cannot load 64bits in one step in i386 mode either? i386 is dying out finally, that's what I meant to say. amd64 has been elected as the architecture of the future by most if not all hardware producers. We got rid of one of the worst pieces of hardware ever, at least partially. This is why I suggested that it might be less of an issue to most people. For a good reason: nowadays, you just get an amd64 and don't have the problem. lots of amd64 machines have much of their own stability problems. it is as well a different architecture that requires recompiling software that may or may not be 64bit clean. of course running your favourite irc client would not matter... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Define hosts lookup for pf.conf
On Wed, Sep 19, 2007 at 06:51:19AM -0600, Diana Eichert wrote: On Wed, 19 Sep 2007, Craig Skinner wrote: SNIP Now you are crying like a girl. Your problems are not this list's problems. Craig I find that statement incredibly offensive. I think a more appropriate statement is: Now you are crying like a closeted cross-dressing British man wait that is no better! how about: unshaved bloody communist! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Perl segfault on 3.7
On Thu, Sep 13, 2007 at 08:10:35PM -0300, Alejandro Lozanoff wrote: Thanks for your explanation and quick response, however with -Uusemymalloc it segfaults almost when it starts. At least it showed that the problem comes from that way, probably the mymalloc is worse than the OpenBSD one. :P memory use-wise it is not. perhaps you have hit a geniune perl bug then. We found what appears to be a workaround on awstats. Changing $tokenquery=$1||''; to $tokenquery='?'; after we traced what was awstats running when segfaulting. It's on awstats.pl line 6574 - awstats 6.7 (build 1.892) (c) 2000-2007 Laurent Destailleur - It runs perfect and we didnt find any problem, but we don't have a clue as to why that is... We are still looking for a real solution Thanks again, Alejandro. mickey wrote: On Thu, Sep 13, 2007 at 05:25:32PM -0300, Alejandro Lozanoff wrote: Hello list, re We recently updated a 3.7 machine running awstat(perl) to parse all our websites logs with the biggest being around 1GB. When parsing the big log it randomly segfaults on 4.1, 3.9 and 3.8, we tried new clean release installs and it still segfaults. On 3.7 it works flawlessly, on 3.8 which has the same perl version as 3.7 (5.8.6) it still segfaults. The problem is completely random but it tends to happen after its been running for a while as it doesnt happen on small logs (or the probability for it to happen on those files is too low ) As the trace below (from the perl.core) shows, it's an out of bounds problem, then we remember about a change on 3.8: malloc(3) has been rewritten to use the mmap(2) system call, introducing unpredictable allocation addresses and guard pages, which helps in detecting heap based buffer overflows and prevents various types of attacks. yes. this increases memory fragmentation immensly resulting in (practically) less virtual space available for data. as an increased penalty (200-300%) for cpu consuption on processes w/ lots (20M and more) malloc(3)ed memory... as well increased demand for the physical memory that on the overcommiting nature of it you perhaps observe. a way around it is only to use perl malloc (sbrk-based) cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Perl segfault on 3.7
On Thu, Sep 13, 2007 at 05:25:32PM -0300, Alejandro Lozanoff wrote: Hello list, re We recently updated a 3.7 machine running awstat(perl) to parse all our websites logs with the biggest being around 1GB. When parsing the big log it randomly segfaults on 4.1, 3.9 and 3.8, we tried new clean release installs and it still segfaults. On 3.7 it works flawlessly, on 3.8 which has the same perl version as 3.7 (5.8.6) it still segfaults. The problem is completely random but it tends to happen after its been running for a while as it doesnt happen on small logs (or the probability for it to happen on those files is too low ) As the trace below (from the perl.core) shows, it's an out of bounds problem, then we remember about a change on 3.8: malloc(3) has been rewritten to use the mmap(2) system call, introducing unpredictable allocation addresses and guard pages, which helps in detecting heap based buffer overflows and prevents various types of attacks. yes. this increases memory fragmentation immensly resulting in (practically) less virtual space available for data. as an increased penalty (200-300%) for cpu consuption on processes w/ lots (20M and more) malloc(3)ed memory... as well increased demand for the physical memory that on the overcommiting nature of it you perhaps observe. a way around it is only to use perl malloc (sbrk-based) cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Sun Netra Disk Arrays
On Wed, Sep 12, 2007 at 12:09:50PM +0100, Edd Barrett wrote: Hi there, I'm just looking at some disk arrays on ebay, the netra range from sun are reasonably priced. For example the Netra st D130. Has anyone tried using this kind of thing with OpenBSD? The official way to configure these kits is via the SSM software for solaris. Is there a way to do this with bioctl or some other tool in OpenBSD, or will I be limited to straight forward non-raid disk access? it;s just a plain scsi box. all three drives show up as plain devices on the host scsi bus. thus in conjunction w/ netra t1 one gets 5-drives (or 8 w/ two of those d130 thingies) on one scsi bus. quite good for a software raid thingie... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: 3ware 9650SE support
On Fri, Jul 27, 2007 at 11:32:36AM -0700, [EMAIL PROTECTED] wrote: Are there plans to support 3ware's 9650SE SATA RAID controller? If so, will it be far off? 9000 controllers require a totally new driver w/ a huge firmware image also that has to be loaded pretty early. meaning it has to be in the kernel which most likely excludes this driver from any ramdisk image thus makes it kinda useless... another example of brilliant hardware engineering. so use something else. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: limited number of carp devices?
On Fri, Jun 22, 2007 at 11:27:56AM +0200, Peter Niehues wrote: Hi misc, I'm building an high availability internet gateway using openbsd 4.0. On the internet side I need more than 100 ip addresses. The idea was to build this ip's via CARP devices, but now it seems that there is some kind of limitation on the number of working devices. I can build up to 255 CARP devices and ifconfig is telling me, that all devices are UP and MASTER. But only the first 50 devices are working and answering to arp requests. All other addresses are not accessible and not answering. To build the devices I use the following script. you can assign more than one address to each carp device. #!/usr/local/bin/bash i=1 max=70 ip=10 vhid=10 device=10 while [ $i -le $max ] ; do ifconfig carp$device create ifconfig carp$device vhid $vhid pass test \ carpdev bge0 10.0.0.$ip netmask 255.255.255.0 echo $i carp$device 10.0.0.$ip vhid $vhid i=`expr $i + 1` device=`expr $device + 1` ip=`expr $ip + 1` vhid=`expr $vhid + 1` done btw, pf is still disabled. Is there a limitation on the maximal number of carp devices? Thanks Peter -- Pt! Schon vom neuen GMX MultiMessenger gehvrt? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger -- paranoic mickey (my employers have changed but, the name has remained)
Re: Kernel MINIROOTSIZE 8192 = No Boot
On Wed, Jun 06, 2007 at 01:39:47PM -0400, Brian A. Seklecki wrote: The 1st stage loader just resets the prom before the kernel load. Can anyone else confirm this? You don't even need to elfrdsetroot(8) to test. Just compile bsd.rd with MINIROOTSIZE=16384. I've been using 32768 on my 4.0 systems for the bsd-appliance project. I've tested it on an AMD Athalon, an AMD Geode, and a VMWare machine. you need to raise NKPTP also to say 8... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Kernel MINIROOTSIZE 8192 = No Boot
On Thu, Jun 07, 2007 at 11:52:24AM -0400, Brian A. Seklecki wrote: Just recompiled with: #define NKPTP_MIN 8 #define NKPTP_MAX 191 Same result. Thank you though. We'll revisit it in the future when the money is available? i said NKPTP. if 8 is not enough -- try 16 cu On Thu, 7 Jun 2007, mickey wrote: On Wed, Jun 06, 2007 at 01:39:47PM -0400, Brian A. Seklecki wrote: The 1st stage loader just resets the prom before the kernel load. Can anyone else confirm this? You don't even need to elfrdsetroot(8) to test. Just compile bsd.rd with MINIROOTSIZE=16384. I've been using 32768 on my 4.0 systems for the bsd-appliance project. I've tested it on an AMD Athalon, an AMD Geode, and a VMWare machine. you need to raise NKPTP also to say 8... cu -- paranoic mickey (my employers have changed but, the name has remained) l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~James Maynard Keenan -- paranoic mickey (my employers have changed but, the name has remained)
Re: Linux Compat Query
On Mon, May 28, 2007 at 09:59:19PM +0100, Edd Barrett wrote: Hi, Maybe your path is not set correctly (for this specific problem). Today has been one dumb mistake after another. I apologize. I'll do it properly shall I: # sysctl -a | grep linux kern.emul.linux=1 # ls -al a.out -rwxr-xr-x 1 edd edd 1176578 May 28 13:18 a.out # file a.out a.out: ELF 32-bit LSB executable, Intel 80386, version 1, for GNU/Linux 2.6.9, statically linked, not stripped # uname -a OpenBSD puff.langash.lan 4.1 GENERIC#1435 i386 # ktrace ./a.out ktrace: exec of './a.out' failed: Operation not permitted # kdump -f ktrace.out 8108 ktrace RET ktrace 0 8108 ktrace CALL execve(0xcfbdc9d3,0xcfbdc89c,0xcfbdc8a4) 8108 ktrace NAMI ./a.out 8108 ktrace RET execve -1 errno 1 Operation not permitted you sure the file system where a.out is allows execution? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Linux Compat Query
On Mon, May 28, 2007 at 10:32:29PM +0100, Edd Barrett wrote: Hi Mickey, On 28/05/07, mickey [EMAIL PROTECTED] wrote: you sure the file system where a.out is allows execution? $ cat /etc/fstab /dev/wd0a / ffs rw 1 1 /dev/wd0d /home ffs rw 1 1 /dev/wd1a /mnt/media ffs rw 1 2 normally you'd do a mount -v to sure see how they are mounted. but maybe that's not really a problem (looking at fstab). cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: 4GB limits per system, or processor
On Thu, May 24, 2007 at 05:38:18AM -0400, Daniel Ouellet wrote: I guess as well that the 4GB limit is per system, not per processor right? I assume wrong when I added memory in that box looks like. assuming this is i386 -- it's 3.75G physical memory per system. also depending on your bios it may map the memory differently such as that you only get 2G out of your 4G installed. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: 4GB limits per system, or processor
On Thu, May 24, 2007 at 06:05:40AM -0400, Daniel Ouellet wrote: mickey wrote: On Thu, May 24, 2007 at 05:38:18AM -0400, Daniel Ouellet wrote: I guess as well that the 4GB limit is per system, not per processor right? I assume wrong when I added memory in that box looks like. assuming this is i386 -- it's 3.75G physical memory per system. also depending on your bios it may map the memory differently such as that you only get 2G out of your 4G installed. It's AMD64 with two dual core processor. DMESG was sent just before this email as well. http://marc.info/?l=openbsd-miscm=11750904364w=2 So, better to remove them then or is current would be any different? currently memory above 4G is not supported there either. and yes same note about bios mapping it funky applies for amd64 machines too. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Softupdates question
On Wed, May 09, 2007 at 12:03:40PM -0400, Peter Fraser wrote: I did read the papers. There is a difference between the file system being screwed and data lost. Softupdates hopefully stops the files system from being in a bad state, but it is amazing how much user data can be lost on a power failure while using softupdates. you can loose much more data w/o softdeps _and_ get your filesystem horribly broken. cu -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mickey Sent: Wednesday, May 09, 2007 11:49 AM To: Peter Fraser Cc: misc@openbsd.org Subject: Re: Softupdates question On Wed, May 09, 2007 at 10:45:15AM -0400, Peter Fraser wrote: I had always assumed the use of softupdates was safe as long as you could have reasonable assurances that the machine would not be shutdown without warning. (i.e. no loss of power or reset being hit). So if you had a UPS, good hardware, and no vandals it's good to use. actually if you bother to read the papers whole idea behind softdeps is to ensure better recoverability from crashes/power/etc. cu -- paranoic mickey (my employers have changed but, the name has remained) -- paranoic mickey (my employers have changed but, the name has remained)
Re: Softupdates question
On Wed, May 09, 2007 at 06:46:19AM -0400, Nick Holland wrote: mickey wrote: On Tue, May 08, 2007 at 07:06:06AM -0400, Nick Holland wrote: George C wrote: ... Is it always best to mount /, /tmp, /usr, /var, /home with softdep? Under what curcumstances would it not be appropriate? If your app makes assumptions about write ordering, softdeps can negate the care the app author took. For example, some mail programs don't ack the receipt of a message until it has been safely written to disk, the idea being that if the power goes out or the machine crashes, if the message has been acknowledged, IT HAS BEEN RECEIVED and will be there when the machine comes back up. Softdeps promises that what is on your disk is coherent, but coherent usually means the last few files written to disk may be just removed when the system comes back up. Not desired in this case. this is not true. fsync() works as specified. Apparently, not all apps use fsync, or don't use it properly. oh so now you are saying that softdeps are broken because applications are not calling fsync() ? At least qmail advises against the use of softdeps: http://cr.yp.to/qmail/faq/reliability.html#filesystems I also found a reference to another mail program which had people making similar advisories, but not sure if they are still applicable. you whole above statement is wrong and is not based on facts. now you are trying to back it up w/ somebody elses opinion that is also not based on facts. now it is also in the archives and peoples will refer to it as some sort of truth. the damage has been done. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Softupdates question
On Tue, May 08, 2007 at 07:06:06AM -0400, Nick Holland wrote: George C wrote: I've just stumbled across the SoftUpdates section in the FAQ, and was rather surprised that I had never seen/heard of this feature before. Before I mount any partition using softdep, I thought I'd google, browse the archives, etc. for any information about when/where they should be used. Although I've found a plethora of information about soft updates, much of it is either contradictory or incomplete I thought I'd ask here for clarification. Is it always best to mount /, /tmp, /usr, /var, /home with softdep? Under what curcumstances would it not be appropriate? If your app makes assumptions about write ordering, softdeps can negate the care the app author took. For example, some mail programs don't ack the receipt of a message until it has been safely written to disk, the idea being that if the power goes out or the machine crashes, if the message has been acknowledged, IT HAS BEEN RECEIVED and will be there when the machine comes back up. Softdeps promises that what is on your disk is coherent, but coherent usually means the last few files written to disk may be just removed when the system comes back up. Not desired in this case. this is not true. fsync() works as specified. Softdeps don't do anything for you if you are mostly reading from disk, or if the partition is mounted read-only. It's about writing. of course they do. there are still atime updates for example that will be handled if not mount read-only. Softdeps is much more complex than conventional disk access. While I have not personally seen a softdep-related bug in some time, and that one was quickly fixed, you HAVE to assume it is more likely to have bugs than the non-softdep systems. this is also not exactly true -- there are softdep bugs fixed at the rate of ten per year if not more. most of them are bugs that been there forever. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Back again with funny network interfaces
On Fri, Apr 20, 2007 at 06:16:32AM -0700, Manuel Ravasio wrote: I have a doubt... PCMCIA ethernet interface cannot negotiate more than 10Mbps, ignoring my trials to force 100full... PCMCIA wireless interface doesn't run at more than 11Mbps, ignoring my trials to force 54Mbps... Maybe it's something with old PCMCIA cardbus? pcmcia cardbus is an oxymoron. pcmcia is a 16bit isa-like bus w/ 3.3v and 5v power. cardbus is a pci-like 32bit bus w/ 3.3v power only. pccard is a form factor for this devices also. so what exactly do you have? (: cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Back again with funny network interfaces
On Fri, Apr 20, 2007 at 08:10:10AM -0700, Manuel Ravasio wrote: pcmcia cardbus is an oxymoron. Whoops... Something like childproof and CiscoWorks? :-) pcmcia is a 16bit isa-like bus w/ 3.3v and 5v power. cardbus is a pci-like 32bit bus w/ 3.3v power only. pccard is a form factor for this devices also. Hmmm... I have something that looks like a couple of pcmcia cards, which fit into two pcmcia slots... I don't have a tester at home, so I can't check voltages. The laptop is quite old, (8 years old at the very least), the wireless card is a Netgear WPN511, described only as pccard, the ethernet card... I can't really say, there's nothing interesting written on it. cardbus cards always have a golden plate at the connector side. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: adjusting mbuf
On Mon, Mar 19, 2007 at 06:41:06AM -0700, Darren Spruell wrote: On 3/19/07, Gustavo Rios [EMAIL PROTECTED] wrote: Dear list members, how could i adjust my mbuf size? Need i to compile a news kernel ? kern.maxclusters allows setting new limits for mbufs. this will set a new limit for mbuf clusters. mbufs 'emselves have no limit except for the kernel virtual space. this should go w/ a usual tuning advice -- be accurate about what you are describing. This would supposedly go out with the same tuning warnings as usual; you may find you need a very good reason to adjust that, if it should be adjusted at all. Does 'netstat -m' show that you're hitting limits? This advice may apply to your situation as well: http://archives.neohapsis.com/archives/openbsd/2004-07/1783.html DS -- paranoic mickey (my employers have changed but, the name has remained)
Re: Free Linux Driver Development!
On Wed, Feb 14, 2007 at 01:45:06PM +0100, Paul de Weerd wrote: On Wed, Feb 14, 2007 at 12:18:16PM +, Jeff Rollin wrote: | On 14/02/07, Han Boetes [EMAIL PROTECTED] wrote: | | Artur Grabowski wrote: | Stephan A. Rickauer [EMAIL PROTECTED] writes: |I did read your FAQ but I can't see how it rebuts what has |just been said. You seem to be happy with signing NDAs. If the |result is a readable and understandable GPL'ed driver, |companies will be even less motivated to release programming |documentation. This will lead to a GPL-lock-in since you |simply replace the vendor not willing to share specifications |with an NDA'ed GPL developer not willing to share those, but |GPL code only. | | Which is exactly what the GPL people want since that's the whole | point of the license. Otherwise they wouldn't be using the | GPL. Duh. | | Nah, RMS doesn't want this. A lot of `GPL people' don't want this | at all. | | This deal is meant to divide. | | | And this discussion isn't? There are already plenty of divisions within the | FOSS world - between the F and OS of FOSS, between Linux and BSD, between | the various BSDs. It's not as if TdR started OpenBSD to continue | contributing to NetBSD, is it? | | And yet when a driver is released under the BSD licence, which conflicts | with the GPL, when do we hear the bitching about it on the BSD side? Wait, | what's that? Oh, we don't? When vendors open up their docs, all profit. When one signs an NDA, in the end, no one profits. Besides, what is keeping Linux from including BSD licensed drivers ? I was under the impression that they have done this in the past. How does a BSD licensed driver conflict with the GPL ? I've heard that the two-clause BSD license should be compatbile with the GPL... oh come fucking on! do not start this bsd vs gpl crap again! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: dmesg and fdisk do not match about usb external disk
On Thu, Feb 08, 2007 at 10:13:29AM +0100, frantisek holop wrote: hmm, on Tue, Jan 30, 2007 at 07:40:52PM -0500, Nick Holland said that It means translation is stupid, but we keep doing it. :) it is not really the translation that got me worried (although wouldn't it be more consistent to use the n x 255 x 63 version everywhere?) but the different number of sectors.. thanks for the great explanation. who gives a flying fuck? bios is using it's own geometry and we are using ours. how about you ask those spammers to send dick measurements in meters? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: dmesg and fdisk do not match about usb external disk
On Thu, Feb 08, 2007 at 03:02:32PM +0100, frantisek holop wrote: hmm, on Thu, Feb 08, 2007 at 02:06:45PM +0100, mickey said that On Thu, Feb 08, 2007 at 10:13:29AM +0100, frantisek holop wrote: hmm, on Tue, Jan 30, 2007 at 07:40:52PM -0500, Nick Holland said that It means translation is stupid, but we keep doing it. :) it is not really the translation that got me worried (although wouldn't it be more consistent to use the n x 255 x 63 version everywhere?) but the different number of sectors.. thanks for the great explanation. who gives a flying fuck? bios is using it's own geometry and we are using ours. how about you ask those spammers to send dick measurements in meters? perhaps this could go into the faq? what? dick measurement techniques? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: dmesg and fdisk do not match about usb external disk
On Thu, Feb 08, 2007 at 03:22:21PM +0100, chefren wrote: On 2/8/07 3:09 PM, mickey wrote: On Thu, Feb 08, 2007 at 03:02:32PM +0100, frantisek holop wrote: hmm, on Thu, Feb 08, 2007 at 02:06:45PM +0100, mickey said that On Thu, Feb 08, 2007 at 10:13:29AM +0100, frantisek holop wrote: hmm, on Tue, Jan 30, 2007 at 07:40:52PM -0500, Nick Holland said that It means translation is stupid, but we keep doing it. :) it is not really the translation that got me worried (although wouldn't it be more consistent to use the n x 255 x 63 version everywhere?) but the different number of sectors.. thanks for the great explanation. who gives a flying fuck? bios is using it's own geometry and we are using ours. how about you ask those spammers to send dick measurements in meters? perhaps this could go into the faq? what? dick measurement techniques? OpenBSD is about pro active security, those techniques should be integrated into the kernel. this is a part of my plan right after i finally commit my optimised xml parser for kernel. it has also asm implemetation for vax (requires CIS-XML microcode though). cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: dmesg and fdisk do not match about usb external disk
On Thu, Feb 08, 2007 at 10:01:07AM -0500, [EMAIL PROTECTED] wrote: On Thu, 8 Feb 2007 15:09:10 +0100, mickey [EMAIL PROTECTED] said: On Thu, Feb 08, 2007 at 03:02:32PM +0100, frantisek holop wrote: hmm, on Thu, Feb 08, 2007 at 02:06:45PM +0100, mickey said that On Thu, Feb 08, 2007 at 10:13:29AM +0100, frantisek holop wrote: hmm, on Tue, Jan 30, 2007 at 07:40:52PM -0500, Nick Holland said that It means translation is stupid, but we keep doing it. :) it is not really the translation that got me worried (although wouldn't it be more consistent to use the n x 255 x 63 version everywhere?) but the different number of sectors.. thanks for the great explanation. who gives a flying fuck? bios is using it's own geometry and we are using ours. how about you ask those spammers to send dick measurements in meters? perhaps this could go into the faq? what? dick measurement techniques? And not long ago I wrote to the list that this list *is* nice and people don't get attacked unless they become obnoxious. Please thank you for proving me absolutely wrong. Jeez, you know more about how the bios and the OS report disk geometries and his enquiries annoy you? Please get over it. Sorry to everyone for also wasting more of this lists bandwidth. you cannot read can you? it does not matter what geometries are as long as you do not change any yourself. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: dmesg and fdisk do not match about usb external disk
On Thu, Feb 08, 2007 at 04:27:21PM +0100, chefren wrote: On 2/8/07 4:13 PM, mickey wrote: On Thu, Feb 08, 2007 at 03:22:21PM +0100, chefren wrote: On 2/8/07 3:09 PM, mickey wrote: On Thu, Feb 08, 2007 at 03:02:32PM +0100, frantisek holop wrote: hmm, on Thu, Feb 08, 2007 at 02:06:45PM +0100, mickey said that On Thu, Feb 08, 2007 at 10:13:29AM +0100, frantisek holop wrote: hmm, on Tue, Jan 30, 2007 at 07:40:52PM -0500, Nick Holland said that It means translation is stupid, but we keep doing it. :) it is not really the translation that got me worried (although wouldn't it be more consistent to use the n x 255 x 63 version everywhere?) but the different number of sectors.. thanks for the great explanation. who gives a flying fuck? bios is using it's own geometry and we are using ours. how about you ask those spammers to send dick measurements in meters? perhaps this could go into the faq? what? dick measurement techniques? OpenBSD is about pro active security, those techniques should be integrated into the kernel. this is a part of my plan right after i finally commit my optimised xml parser for kernel. it has also asm implemetation for vax (requires CIS-XML microcode though). OK, even better! Just to be sure, I know this is a little paranoid but the users really need it top notch: You won't forget full ASN.1 support won't you? of course! it's a part of the original specification for this project we are doing for a very important customer that i cannot name openly here. it is going to change the world, man, as everything that comes from germany! you'll see. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Slow write performance on Compaq Smart Array 64xx (ciss0)
On Sun, Jan 28, 2007 at 05:32:41PM +0100, Henning Brauer wrote: * Vijay Sankar [EMAIL PROTECTED] [2007-01-28 16:07]: bioctl -h ciss0 gives me bioctl: Can't locate ciss0 device via /dev/bio ciss doesn't support bio yet. rtfm bio(4) support is only possible for one volume right now. so if you'd have only sd0 there it'd work. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: uvm_fault
On Tue, Jan 23, 2007 at 03:40:11PM -0500, test wrote: I have a similar problem. I would suspect it's my hdd or possible RAM, because this only happens when I am trying to recompile the kernel, or install something from the ports tree. It panics with this error. this problem is there from about 3.6 at least. in a nutshell pmap leaks pv_entry structs and those contain pointers that become invalid and dereferenced. in your case it's the page directory pointer that's get busted. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Merchandise idea: OpenBSD mug
On Fri, Jan 12, 2007 at 05:19:47PM +, Tom Beard wrote: Otto Moerbeek wrote: Wow, nobody ever thought of that before You could at leats have searcghed the archives to see if your idea is new. That was over three years ago, surely there's nothing wrong with bringing an old idea back up for reconsideration? reconsideration by who? you really mean _you_ are going to make it happen? or perhaps you even know how and where and what it costs to make it? Personally I think that a mug would be a good idea. I can hardly wear a 'cute' t-shirt to work, but I can fill my OpenBSD mug with coffee and put it on my desk. do it yourself then cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: panic in pmap_page_remove
On Sat, Dec 02, 2006 at 04:36:35PM -0800, Marco S Hyman wrote: I've got a reproducable crash on my Mac mini (intel). Sources are as of 30 Nov. No, I'm not running a generic kernel because a generic kernel doesn't run on the mini. And the keyboard doesn't work in ddb so getting more info is difficult at best. Here are photos of two different crashes. The first was while doing a make build, the second while building some ports. The crash and stack traces are pretty close in each case: panic panic trap --- trap (number 6) --- pmap_page_remove uvm_vnp_terminate uvn_attach uvm_unmap_detach uvmspace_free uvm_exit reaper http://www.snafu.org/crash/p-20061202-0035-2230.jpg http://www.snafu.org/crash/p-20061202-1454-2232.jpg Ideas? I'm trying to get a crash dump, but this last time the box hung at syncing disks... known bug. hard to fix (; every time i add debugging for it it stops panicing... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: autoconf error message suggestion
On Mon, Dec 04, 2006 at 04:15:41PM +0100, Karel Kulhavy wrote: [EMAIL PROTECTED]:~$ autoconf Provide an AUTOCONF_VERSION environment variable, please I suggest this error message to be extended with a pointer to information how to set this environment variable. As I wrote, I didn't find any manpage about this topic (even if the manpage list suggested it should be installed), but maybe there is some URL explaining this topic. why don't yo talk to the autoconf developers? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Which tools the OpenBSD developers are using?
On Wed, Nov 29, 2006 at 07:20:22PM +0100, Johan P. Lindstr?m wrote: So far, only NetBSD runs on the AK* architecture. most of the struggling nations run on AK-* architecture (AK-47 mostly). On 11/29/06, Ioan Nemes [EMAIL PROTECTED] wrote: That's the problem, you should use an AK45! Much-much cheaper than the AR-15 (I've been offred one for $US15.00 in Sudan), and is widely available. Ioan Diana Eichert [EMAIL PROTECTED] 11/29 9:58 am I use a soldering iron, dremel tool, sheet metal/plastic nibbler and solder wick. diana PS Then I load my AR-15 to see if I can shoot any holes in my code. -- // Johan -- paranoic mickey (my employers have changed but, the name has remained)
Re: panic: cpu1: TLB IPI rendezvous failed
On Thu, Nov 16, 2006 at 03:09:08PM +0100, Federico Giannici wrote: As it is a production server, I'd like to avoid -current. Do you think I can apply that single patch to -stable? yes Aaron Campbell wrote: On Thu, 16 Nov 2006, Federico Giannici wrote: panic: cpu1: TLB IPI rendezvous failed (mask 0x1) Stopped at Debugger+0x4: leave Try updating to the very latest snapshot. This commit from yesterday is supposed to help avoid these panics: Date: Wed, 15 Nov 2006 07:40:50 -0700 (MST) From: Michael Shalayeff [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: CVS: cvs.openbsd.org: src CVSROOT:/cvs Module name:src Changes by: [EMAIL PROTECTED] 2006/11/15 07:40:50 Modified files: sys/arch/i386/i386: apicvec.s Log message: do not go processing normal interrupts after ipi. this is to avoid spins at high spl especialy on cpu0. other local interrupts (timer and softint) still do also pending interrupts processing. niklas@ ok -aar -- ___ __ |- [EMAIL PROTECTED] |ederico Giannici http://www.neomedia.it ___ -- paranoic mickey (my employers have changed but, the name has remained)
Re: anyone know where I can get a PLEXTOR 250GB NAS in the United States?
On Wed, Nov 08, 2006 at 03:57:30PM -0700, Diana Eichert wrote: On Fri, 6 Oct 2006, Diana Eichert wrote: On Sat, 7 Oct 2006, mickey wrote: SNIP woman you are fast (: there is supposedly a piece sold in .eu (see landisk.html) but then nobody knows for sure... it's a japanese sex toy. cu -- and once again I'm fast on the draw, I see a landisk directory showing up in the snapshots directory. ftp://iawnet.sandia.gov/pub/OpenBSD/snapshots/landisk/ I have a Plextor, just waiting for my 'sample' connector to show up so I can wire my rs232 line driver chip/cable to it in a pseudo 'production' manner. i didn't do it! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: bsdstats.org WOW
On Thu, Oct 19, 2006 at 08:52:14AM -0400, MikeM wrote: On 10/18/2006 at 7:37 PM Sam Fourman Jr. wrote: |Check out OpenBSD :) | |http://www.bsdstats.org/ = OK, I see a table full of numbers, but no explanation of what is being measured or how. Yes, OpenBSD is on the top, but on the top of what? it's all written there how it works and how one can participate. so why ain't you jerk off on random numbers somewhere else please? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: question about swapped processes
On Thu, Oct 12, 2006 at 11:37:14AM +0200, frantisek holop wrote: i know ps is only showing what was, or might have been, not what it is.. but how come in one moment 40-50 (out of the total 110-120 processes) are swapped out and in the next instant none of them? status swapped out does not mean they are physically and completely written out of memory. the swapped out status only means that in case of physmem shortage they will have their u-area paged out. if process transition thru running then it will have it's u-area paged in or otherwise marked as not swapped out... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: question about swapped processes
On Thu, Oct 12, 2006 at 12:14:51PM +0200, frantisek holop wrote: hmm, on Thu, Oct 12, 2006 at 11:51:12AM +0200, mickey said that On Thu, Oct 12, 2006 at 11:37:14AM +0200, frantisek holop wrote: i know ps is only showing what was, or might have been, not what it is.. but how come in one moment 40-50 (out of the total 110-120 processes) are swapped out and in the next instant none of them? status swapped out does not mean they are physically and completely written out of memory. the swapped out status only means that in but if that is the case, is top(1) wrong in showing RES 4k for these processes? doesn't this mean that they are not in memory anymore? 4k is memory isn't it? (: cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Broadcom HT-1000 chipset
On Mon, Oct 09, 2006 at 09:02:19AM +0200, Stephan A. Rickauer wrote: Building a new OpenBSD server I am planning to buy a Tyan S3950 mainboard. Has anybody experience with that chipset? http://tyan.com/products/html/tomcath1000s.html unfortunately lots of boards have prblems w/ interrupts. also there are no docs on that chipset so it's really hard to fix (: cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: anyone know where I can get an IO-DATA USL-5P in the United States?
On Fri, Oct 06, 2006 at 04:10:44PM -0600, Diana Eichert wrote: The subject line sez it all. I've been looking for a small embedded system to run OpenBSD on and very recent commits makes this look interesting. woman you are fast (: there is supposedly a piece sold in .eu (see landisk.html) but then nobody knows for sure... it's a japanese sex toy. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Brooktree BT878 support?
On Thu, Sep 21, 2006 at 03:48:11PM -0500, Kevin wrote: What is the current status of the Brooktree (bktr) driver and userland applications? I've found the ProVideo PV-143 quad-port BT878 capture cards for about fifty dollars, and would like to use the card with 'fxtv' (from ports) or perhaps danovitschwebcam, all four ports active. I've also found the PixelView PlayTVpro tuner card, at about the same price. This tuner isn't on the list of compatible cards in the driver, and I know tuner cards can be more problematic. Is anybody using the ProVideo or PixelView cards under OpenBSD? Is there any active development? as long as they are compatible design it's usually a question of small magic numbers table being filled up and then they just work. the multi-port cards might be of more challangle depending on how they are design. in case it's just a bridge and four devices behind it supposedly it's the same amount of work -- fill out small table. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Low priority or real coders
On Thu, Sep 14, 2006 at 04:02:53PM +0200, Gilles Chehade wrote: Marco Peereboom wrote: Bash should be bashed. Its horrible garbage and should be banned from the face of this earth. We all know that real men use ksh. what you really meant was `real men use csh/tcsh' right ? :-) what said is that bash a load of incompatible boolshit. bash is not progress. bash is ten steps back before middle ages. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: fsck hangs
On Wed, Sep 13, 2006 at 10:06:43AM -0300, Pedro Martelletto wrote: On Wed, Sep 13, 2006 at 02:19:36PM +0200, Han Boetes wrote: umass0: BBB bulk-in stall clear failed, IOERROR umass0: BBB bulk-in stall clear failed, IOERROR umass0: BBB bulk-in stall clear failed, IOERROR These look highly suspicious, but just for the sake of it, can you please provide the output of 'ps aklwx'? i've discovered some umass problems w/ some mp3 player recently. i think it's smth in the driver or scsi layer cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Kernel swelling
On Sat, Sep 09, 2006 at 05:02:51PM -0400, Woodchuck wrote: Tag OPENBSD_3_9, GENERIC.MP kernel (i386) seems to have grown by 1.1 MB in size between 5 Aug and 9 Sep. -rwxr-xr-x 1 root wheel - 7621080 Sep 9 10:11 bsd*- MP kernel -rw-r--r-- 1 root wheel - 7565469 Sep 9 10:11 bsd.sg - single proc -rwxr-xr-x 1 root wheel - 5507544 Aug 5 14:41 obsd* - Previous MP Can anyone offer any clues why? we've been fucking w/ it (as usual). cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: 3.9-stable (weird) panic pccom
function 4 vendor VIA, unknown product 0x4314 rev 0x00 pchb5 at pci0 dev 0 function 7 vendor VIA, unknown product 0x7314 rev 0x00 ppb0 at pci0 dev 1 function 0 VIA VT8377 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor VIA, unknown product 0x3344 rev 0x01: aperture at 0xf400, size 0x1000 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) VIA VT6306 FireWire rev 0x80 at pci0 dev 13 function 0 not configured vge0 at pci0 dev 14 function 0 VIA VT612x rev 0x11: irq 10, address 00:40:63:e6:8f:13 ciphy0 at vge0 phy 1: Cicada CS8201 10/100/1000TX PHY, rev. 2 pciide0 at pci0 dev 15 function 0 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST38420A wd0: 16-sector PIO, LBA, 8223MB, 16841664 sectors wd1 at pciide0 channel 0 drive 1: ST38421A wd1: 16-sector PIO, LBA, 8056MB, 16498944 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: , ATAPI CDROM.48X, 180J SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x81: irq 5 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x81: irq 5 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 16 function 2 VIA VT83C572 USB rev 0x81: irq 11 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 16 function 4 VIA VT6202 USB rev 0x86: irq 10 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: VIA EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered viapm0 at pci0 dev 17 function 0 VIA VT8237 ISA rev 0x00 iic0 at viapm0 xl0 at pci0 dev 20 function 0 3Com 3c905C 100Base-TX rev 0x74: irq 11, address 00:04:76:a1:cc:d1 bmtphy0 at xl0 phy 24: Broadcom 3C905C internal PHY, rev. 6 isa0 at mainbus0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lm0 at isa0 port 0x290/8: W83697HF npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo biomask ffe5 netmask ffe5 ttymask ffe7 pctr: user-level cycle counter enabled axe0 at uhub3 port 3 configuration 1 interface 0 axe0: Cisco-Linksys USB200M v2, rev 2.00/0.01, addr 2, AX88772, address 00:10:60:06:10:22 ukphy0 at axe0 phy 16: Generic IEEE 802.3u media interface, rev. 1: OUI 0x000ec6, model 0x0001 dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 WARNING: / was not properly unmounted pppoe0: phase establish pppoe0: phase authenticate pppoe0: phase network Regards, ahb -- paranoic mickey (my employers have changed but, the name has remained)
Re: NXE bit on amd64 hardware and i386 kernel
On Tue, Sep 05, 2006 at 07:39:21PM +0200, Piotrek Kapczuk wrote: Hello When I boot 64 bit kernel on amd64 hardware I got NXE bit recognized. When I boot 32 bit kernel on amd64 it doesn't appear. I wonder if it's normal. If it's simply not supported/not done yet are there any plans to support this ? i386 cannot support nxe right now. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: watching tv (via bktr driver) with fxtv on current = no sound + strange kernel message
On Mon, Aug 28, 2006 at 06:59:07PM +, Didier Wiroth wrote: Hello, I've purchased a leadtek winfast tv 2000 xp tv tuner card. The card is supported via the bktr driver. I'm getting a clean image of my tv channels (the input format is pal and the tuner mode is cable) but I don't get any sound. I noticed the following message in dmesg (actuall yI don't know it is related to the sound problem): bktr0: ioctl: 701: columns too large or not even. The pci card has an audio out card which is connected to the aux audio in of the motherboard. Here is the related mixerctl output: inputs.aux=255,255 (it's the maximum) inputs.aux.mute=off I do get a perfect sound with other applications, so my soundcard works. it can be that your aux input is wired as smth else such as line-in. so try other sets in mixerctl. and also unmute in fxtv too. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: radioctl error on i386 Aug 1 snapshot; Inappropriate ioctl for device
On Fri, Aug 04, 2006 at 07:25:55AM -0600, Diana Eichert wrote: On Fri, 4 Aug 2006, mickey wrote: On Thu, Aug 03, 2006 at 12:49:17PM -0600, Diana Eichert wrote: I'm getting the following error when I try to access my bktr(4) card. $ sudo radioctl -f /dev/bktr0 -a radioctl: RIOCGINFO: Inappropriate ioctl for device I was trying to set the tuner to cable/NTSC/channel#. radio(4) is only attached if you have a second fm tuner Okay, so have I misinterpreted using radioctl(1) to set the channel and broadcast type? From RTFM radioctl operates on radio device. if it is not attached then it will not work. besides the fact that to _view_ tv you need some ext program anyway. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: radioctl error on i386 Aug 1 snapshot; Inappropriate ioctl for device
On Fri, Aug 04, 2006 at 10:46:10AM -0600, Diana Eichert wrote: NetNeanderthal, mickey, et al On Thu, 3 Aug 2006, NetNeanderthal wrote: On 8/3/06, Diana Eichert [EMAIL PROTECTED] wrote: snip bktr0 at pci1 dev 14 function 0 Brooktree BT878 rev 0x02: irq 10 bktr0: Askey/Dynalink Magic TView, Temic NTSC tuner. Brooktree BT878 Audio rev 0x02 at pci1 dev 14 function 1 not configured The RIOCGINFO ioctl(2) is reserved for /dev/radioN(4) devices.. I didn't see it in your dmesg, but I seem to recall my ancient 848 enumerating radio0 at bktr0 for NTSC tuning purposes, barring memory problems (of the brain sort). I believe there are also some kernel config options to force manual enumeration of the device rather than relying on built-in autodetection code. I never had to worry about them, but you might give that a go if you're in the kernel-config neighbourhood. On Fri, 4 Aug 2006, mickey wrote: SNIP radioctl operates on radio device. if it is not attached then it will not work. besides the fact that to _view_ tv you need some ext program anyway. OK, so it takes a bit for me to be clued in and it's quite possible I'm still not there. Here's what I think I know. I have a bktr(4) card with an onboard NTSC tuner. I can't control the bktr(4) setup channel and broadcast type because there is no radio(4) device attached, probably? because the auto-detect of the tuner failed? My plan is to pull the card, and verify what tuner is on it. Then build a new kernel based on GENERIC adding option BKTR_OVERRIDE_TUNER and possibly option BKTR_OVERRIDE_CARD to see if I can get a radio(4) device attached. My purpose in going through all this is to capture video on my OpenBSD system and stream it on my local network to a PrismIQ media player. to capture video you need more than just channel setting. you need to install a port like fxtv or smth... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD's own compiler
On Mon, Jul 31, 2006 at 06:32:45PM -0300, Andr??s wrote: We should convince both the Free Software Foundation and the Open Source Initiative that Lucent Public License Version 1.02 is not a free software license. Mainly based in Theo's arguments*. This paragraph says it all: And come on it says certain responsibilities. Good god. Are you people dumb to accept such a term in a legal document? It is like your house mortgage can be considered invalid in certain situations and then we own your house. A BSD future for that compiler is not guaranteed, but I think a free software future is. I don't think Lucent would step back. Maybe they will use a copyleft license, but I think that would be much better than now. the plan9 compiler had been released under free license. now try to compile it under unix. then try to make it generate correct code under unix. after that compile fucking openbsd with it. the last (but not least) make an openbsd release with it. you (and your kids) will go greyhair before you get halfway thru it. so can you people fucking shuddup and do smth useful now plz? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD's own compiler
On Mon, Jul 31, 2006 at 02:12:47PM +0100, Steve Fairhead wrote: Rico Secada [EMAIL PROTECTED] said: I read about how Ada is been used in all areas where safety is of great issue, and about how it's being used in rockets, Boing Airplanes and so on because of it's high level of safety. What I understood from it is, that the demand and control upon compilers, rather than on the sourcecode, eliminates the possibility of a lot of errors in the sourcecode, the compiler will not compile the program, and since Ada is being used in a lot places, where lives dependt upon the software, it has to be very safe. I was wondering, would it be a stupid and bad idea, for the OpenBSD team to develope, an OpenBSD C compiler based upon the OpenBSD security knowledge and internal standards regarding the language? yeah we will just drop everything we do now, quit all our jobs, send our families and other sos shopping at the mall in zimbabwe, not make a release for two years and produce the best compiler ever by then of course everybody will stop using openbsd for obvious reasons so we can finally all go drinking beer... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: OpenBSD's own compiler
On Mon, Jul 31, 2006 at 10:35:29AM -0500, R. Tyler Ballance wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was wondering, would it be a stupid and bad idea, for the OpenBSD team to develope, an OpenBSD C compiler based upon the OpenBSD security knowledge and internal standards regarding the language? yeah we will just drop everything we do now, quit all our jobs, send our families and other sos shopping at the mall in zimbabwe, not make a release for two years and produce the best compiler ever by then of course everybody will stop using openbsd for obvious reasons so we can finally all go drinking beer... Jeeez, talk about an overreaction to the suggestion. The GNU Compiler Collection has been something most people put up with as opposed to enjoy using. It's not that far fetched of an idea, remember a spin- off project that the OpenBSD guys are responsible that's become the most heavily used SSH code on the planet... Since nobody else has mentioned TeNDRA project, I might as well: http://www.tendra.org/ If you're interested in a BSD compiler collection, start by helping them out, it's been dormant (somewhat) but I'm certain it'd just take a few talented individuals with spare time to really get it going again. just god damn try it. come back when you can compile and run a hello world... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: About soft updates
On Thu, Jul 06, 2006 at 12:35:51PM +0200, Pablo Mar?n Ram?n wrote: I've been trying to find out whether to enable soft updates or not, and I have not really seen any reason not to, other than that it is not enabled by default. Pros: * Improved performance there are known scenarios where it does degrades performance. * Faster recovery latency after a crash this is just not true at all. * Can handle a security problem that can occur (AFAIK) in bare FFS (see http://archives.neohapsis.com/archives/openbsd/2006-06/1045.html) Cons: * Less tested than bare FFS * More complex than bare FFS * Disk space is not immediately released (problematic during ugrades) I think the disabled by default solution is fine: if a user knows what he's doing (i.e. knows the pros and cons) he can enable them manually, disabling them on upgrades or other circumstances if required. By default, a well tested and less complex FS, with the default BSD semantics (for example, synchronous directory metadata updates, expected by programs like some MTAs) is provided. The solution adopted by other systems, such as FreeBSD, is to enable them on all non-root partitions. PS: A note in the FAQ saying that all the previous concerns are meaningless if an IDE HD write cache is enabled would be nice. -- paranoic mickey (my employers have changed but, the name has remained)
Re: About soft updates
On Thu, Jul 06, 2006 at 05:08:56PM +0200, Pablo Mar?n Ram?n wrote: * Improved performance there are known scenarios where it does degrades performance. I meant in the general case. me too Do you refer to systems with low memory (or at least the need to have the kernel not to occupy more memory than a minimum), for example? If not, some example would be really appreciated to get a deeper understanding of the technology. you can start by reading some on the subject... your lame generalised statements on smth you do not understand are not helping anybody... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: 3.9 freeze
On Mon, Jul 03, 2006 at 09:45:22AM -0300, diego wrote: no, I can only ping the server or change tty (ctrl alt fn), but I can't type anything. you should sysctl ddb.console=1 for that to work... - Original Message - From: Pedro Martelletto [EMAIL PROTECTED] To: diego [EMAIL PROTECTED] Cc: misc@openbsd.org Sent: Monday, July 03, 2006 9:34 AM Subject: Re: 3.9 freeze Can you break into ddb? -p. -- paranoic mickey (my employers have changed but, the name has remained)
Re: Trouble with Cisco Aironet 350 (PCM352)
On Wed, Jun 21, 2006 at 11:32:50PM +0200, Laurens Vets wrote:
Matt Van Mater wrote:
I ran into a very similar (maybe same) problem here:
http://marc.theaimsgroup.com/?l=openbsd-miscm=113236417207016w=2
I have not found a solution to my problem yet unfortunately. One
thing I noticed is that my an0 card worked just find in 3.7 and 3.8
broke it, you might want to verify if that is the case with you as
well.
Another thing I noticed is that the an0 card gets a dhcp address and
works properly during the initial install via cd or the ram disk off
of a floppy, but stops working upon first reboot.
I have noticed the exact same problem as the link above. Card worked
with OpenBSD 3.7. I did an upgrade from 3.7 - 3.8 - 3.9 following the
OpenBSD upgrade guides.
After the upgrade to 3.8, I also saw the error an0: failed to enable
MAC, but wifi access still worked. After the upgrade to 3.9, I got the
following in my dmesg at startup:
an0 at pcmcia1 function 0 Cisco Systems, 350 Series Wireless LAN Adapter
an0: record buffer is too small, rid=ff00, size=198, len=258
an0: read caps failed
an0: failed to attach controller
this is a piece of our changes that was lost when a driver was converted
to use net80211. i think this diff should fix it. please try.
i have not tested it beyound compile.
10x
cu
--
paranoic mickey (my employers have changed but, the name has remained)
Index: an.c
===
RCS file: /cvs/src/sys/dev/ic/an.c,v
retrieving revision 1.51
diff -u -r1.51 an.c
--- an.c22 May 2006 20:35:12 - 1.51
+++ an.c22 Jun 2006 09:37:00 -
@@ -146,7 +146,7 @@
intan_cmd(struct an_softc *, int, int);
intan_seek_bap(struct an_softc *, int, int);
-intan_read_bap(struct an_softc *, int, int, void *, int);
+intan_read_bap(struct an_softc *, int, int, void *, int, int);
intan_write_bap(struct an_softc *, int, int, void *, int);
intan_mwrite_bap(struct an_softc *, int, int, struct mbuf *, int);
intan_read_rid(struct an_softc *, int, void *, int *);
@@ -367,7 +367,7 @@
fid = CSR_READ_2(sc, AN_RX_FID);
/* First read in the frame header */
- if (an_read_bap(sc, fid, 0, frmhdr, sizeof(frmhdr)) != 0) {
+ if (an_read_bap(sc, fid, 0, frmhdr, sizeof(frmhdr), sizeof(frmhdr)) !=
0) {
CSR_WRITE_2(sc, AN_EVENT_ACK, AN_EV_RX);
ifp-if_ierrors++;
DPRINTF((an_rxeof: read fid %x failed\n, fid));
@@ -437,12 +437,13 @@
*/
gap = m-m_data + sizeof(struct ieee80211_frame) -
sizeof(uint16_t);
- an_read_bap(sc, fid, -1, gap, gaplen + sizeof(u_int16_t));
+ an_read_bap(sc, fid, -1, gap, gaplen + sizeof(u_int16_t),
+ gaplen + sizeof(u_int16_t));
} else
gaplen = 0;
an_read_bap(sc, fid, -1,
- m-m_data + sizeof(struct ieee80211_frame) + gaplen, len);
+ m-m_data + sizeof(struct ieee80211_frame) + gaplen, len, len);
an_swap16((u_int16_t *)(m-m_data + sizeof(struct ieee80211_frame) +
gaplen), (len+1)/2);
m-m_pkthdr.len = m-m_len = sizeof(struct ieee80211_frame) + gaplen +
len;
@@ -695,11 +696,11 @@
}
int
-an_read_bap(struct an_softc *sc, int id, int off, void *buf, int buflen)
+an_read_bap(struct an_softc *sc, int id, int off, void *buf, int len, int blen)
{
- int error, cnt;
+ int error, cnt, cnt2;
- if (buflen == 0)
+ if (len == 0 || blen == 0)
return 0;
if (off == -1)
off = sc-sc_bap_off;
@@ -708,8 +709,10 @@
return EIO;
}
- cnt = (buflen + 1) / 2;
+ cnt = (blen + 1) / 2;
CSR_READ_MULTI_STREAM_2(sc, AN_DATA0, (u_int16_t *)buf, cnt);
+ for (cnt2 = (len + 1) / 2; cnt cnt2; cnt++)
+ (void) CSR_READ_2(sc, AN_DATA0);
sc-sc_bap_off += cnt * 2;
return 0;
@@ -841,19 +844,12 @@
return error;
/* length in byte, including length itself */
- error = an_read_bap(sc, rid, 0, len, sizeof(len));
+ error = an_read_bap(sc, rid, 0, len, sizeof(len), sizeof(len));
if (error)
return error;
len -= 2;
- if (*buflenp len) {
- printf(%s: record buffer is too small,
- rid=%x, size=%d, len=%d\n,
- sc-sc_dev.dv_xname, rid, *buflenp, len);
- return ENOSPC;
- }
- *buflenp = len;
- return an_read_bap(sc, rid, sizeof(len), buf, len);
+ return an_read_bap(sc, rid, sizeof(len), buf, len, *buflenp);
}
int
Re: 3.9 release 1st boot: kernel: stopped at scan_smbios
On Sat, Jun 17, 2006 at 01:41:27AM +, Travers Buda wrote: Looks like a crappy bios (pardon the redundancy,) try boot boot -c UKC disable pcibios UKC quit this obviously has nothing to do w/ pcibios. disable ipmi would be a better solution. i think this was fixed in -current that you should try as well plz. cu On Sat, 17 Jun 2006 00:45:29 +0100 Craig Skinner [EMAIL PROTECTED] wrote: Hi List, I've just installed 3.9 RELEASE on an i386 and got a kernel page fault. Booted the box from the floppy39.fs, sliced the disk, installed some sets rebooted, as per normal. I don't use this box very often and the last release I had on it was 3.6, which worked fine. Where do I go from here? 3.8? I piped the boot output from tip into a file: =07connected=0D =FC OpenBSD/i386 BOOT 2.10 =0Dbooting hd0a:/bsd: \=08|=08/=08-=08\=084966344|=08/=08-=08\=08|=08/ =08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08- =08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/ =08-= =08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08- =08\=08|=08= /=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\= =08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08= -=08\=08|=08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|= =08/=08-=08\=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08= \=08|=08/=08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/= =08-=08 \=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08= |=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/=08-=08\=08|=08/ =08-= =08\=08+867848 [52+255872|=08/=08-=08\=08|=08/=08-=08\=08|=08/ =08-=08\=08|= =08/=08-=08+237161\=08|=08/=08-=08\=08|=08/=08-=08\=08| =08/=08-=08\=08|=08/= =08]=3D0x608d64 entry point at 0x100120 [ using 493460 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.o= rg OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class, 128KB L2 cache) 635 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE= 36,MMX,FXSR,SSE real mem =3D 199729152 (195048K) avail mem =3D 175271936 (171164K) using 2463 buffers containing 10088448 bytes (9852K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 01/15/99, BIOS32 rev. 0 @ 0xfdb70 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI BIOS has 9 Interrupt Routing table entries pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801AA LPC rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 uvm_fault(0xd05c2f60, 0xdeeb8000, 0, 1) - e kernel: page fault trap, code=3D0 Stopped at scan_smbios+0xb9: cmpb$0,0(%ebx) ddb=20 -- paranoic mickey (my employers have changed but, the name has remained)
Re: 3.9 release 1st boot: kernel: stopped at scan_smbios
On Mon, Jun 19, 2006 at 10:29:06AM +0100, Craig Skinner wrote: On Mon, Jun 19, 2006 at 10:43:10AM +0200, mickey wrote: On Sat, Jun 17, 2006 at 01:41:27AM +, Travers Buda wrote: Looks like a crappy bios (pardon the redundancy,) try boot boot -c UKC disable pcibios UKC quit this obviously has nothing to do w/ pcibios. disable ipmi would be a better solution. i think this was fixed in -current that you should try as well plz. Thanks for the idea, but no difference. I have other boxes that this is not a problem for, so I'll use them until the next release. oh right. me bad. ipmi is one of those drivers that is broken and does probe all the time that cannot be disabled... you can compile a kernel w/ removed ipmi i suppose. (or patch it w/ gdb and put xorl %eax, %eax; ret in ipmi_probe ;) cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Kernel Hangs; Supermicro 5015M-MR (Intel E7230)
enabled dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 -- paranoic mickey (my employers have changed but, the name has remained)
Re: savecore segfaults in June 7 i386 -current snapshot (#870)
1 configuration 1 interface 0 uhidev0: vendor 0x062a product 0x, rev 1.10/0.00, addr 2, iclass 3/1 ums0 at uhidev0: 3 buttons and Z dir. wsmouse0 at ums0 mux 0 dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 -- paranoic mickey (my employers have changed but, the name has remained)
Re: ??????????: other languages support?
On Wed, May 31, 2006 at 04:16:12PM -0700, Spruell, Darren-Perot wrote: huh? bedroom? is this a joke? KOMHATA. Not that I'd really consider this multi-language support... :) actually that'd be CnA^bH9! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: ioapic0 degraded performance
9) pcscp0: AM53C974, 40MHz, SCSI ID 7 scsibus0 at pcscp0: 8 targets cd0 at scsibus0 targ 5 lun 0: HP, CD-Writer+ 9200, 1.0e SCSI4 5/cdrom removable isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask 0 netmask 0 ttymask 0 ioapic0: pin 19 shares different IPL interrupts (40..90), degraded performance pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support uhub0: device problem, disabling port 1 dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 wd2: no disk label dkcsum: wd2 matches BIOS drive 0x82 dkcsum: wd3 matches BIOS drive 0x83 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 -- paranoic mickey (my employers have changed but, the name has remained)
Re: Static functions in C code
On Fri, May 26, 2006 at 10:14:04AM -0300, Diego Giagio wrote: On 5/25/06, Marco Peereboom [EMAIL PROTECTED] wrote: Because it'll clash. Clashing is good. I'm pretty sure you would be more successfull on a humor TV show as a clown than wasting people time and bandwith with stupid statements like that. And I don't mind if you are a OpenBSD developer, contributor, US president or a dirty bitch. nobody cares if you use static or not. if you do not understand answers given you can as well make your own decisions yourself godamnit! cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Soundcard AD1981B @ auich0 debugging
ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x03: irq 9 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x03pci_intr_map: no mapping for pin C : couldn't map interrupt ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x03pci_intr_map: no mapping for pin D : couldn't map interrupt ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x83 pci1 at ppb0 bus 1 cbb0 at pci1 dev 5 function 0 Ricoh 5C475 CardBus rev 0xb8: irq 3 Ricoh 5C551 Firewire rev 0x00 at pci1 dev 5 function 1 not configured fxp0 at pci1 dev 8 function 0 Intel PRO/100 VE rev 0x83, i82562: irq 9, address 08:00:46:b7:96:70 inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0 ath0 at pci1 dev 11 function 0 Atheros AR5212 rev 0x01: irq 9 ath0: AR5213 5.6 phy 4.1 rf5111 1.7 rf2111 2.3, MKK1A, address 00:02:8a:be:1b:07 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 2 device 0 cacheline 0x0, lattimer 0x40 pcmcia0 at cardslot0 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x03 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: HTC426060G9AT00 wd0: 16-sector PIO, LBA48, 57231MB, 117210240 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, UJDA755 DVD/CDRW, 1.00 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x03pci_intr_map: no mapping for pin B : polling iic0 at ichiic0 auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x03: irq 9, ICH4 AC97 ac97: codec id 0x41445374 (Analog Devices AD1981B) ac97: codec features headphone, 20 bit DAC, No 3D Stereo ac97: ext id 601vra,amap,rev0 read(2) = 8000 read(18) = 8808 read(1c) = 8000 read(1a) = 0 audio0 at auich0 Intel 82801DB Modem rev 0x03 at pci0 dev 31 function 6 not configured isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: using exception 16 biomask effd netmask effd ttymask pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support ugen0 at uhub1 port 1 ugen0: Sony product 0x0107, rev 1.10/0.00, addr 2 dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 -- paranoic mickey (my employers have changed but, the name has remained)
Re: HP DL140 G2 Openbsd
On Mon, May 22, 2006 at 05:22:21PM +0200, Per-Olov Sjoholm wrote: On Monday 22 May 2006 13:51, Unnikrishnan, Puthanveetil wrote: Hi , I plan to install Openbsd3.9 on HP DL140 G2 machine. Is this machine Compatible with OpenBSD 3.9 ? Regards Unni We have four HP DL140 G2 machines running on 3.7 at a customer site (dns and mail relays) without any problems at all. The interrupt router was the only problem (not recognized). Be we run on it anyway. But 3.9 would probably be much better. We will also upgrade these servers to 3.9 within a month... According to the people that knows more about it than me, the Warning, unable to fix up PCI interrupt routing message is harmless. It tells you that your motherboard manufacturer sucks for shipping with a broken BIOS. The only possibility is to update your bios but that is by no means a guarantee that it'll work. it most likely is not related to bios. if interrupt router is not supported that is no driver for it currently then you get that msg. the only way to fix that is to write a driver assuming one can find docs for it. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: security bug in x86 hardware (thanks to X WIndows)
On Tue, May 16, 2006 at 11:27:00AM +0200, Joachim Schipper wrote: On Tue, May 16, 2006 at 03:26:39PM +1000, Steffen Kluge wrote: On Sat, 2006-05-13 at 16:18 +0200, Ed White wrote: It seems XFree people disagree... [...] ...and some Linux developers too... Alan Cox: What it essentially says is if you can hack the machine enough to get the ability to issue raw i/o accesses you can get any other power you want. Thats always been true. Using SMM to do this seems awfully hard work. He said that in reply to you saying: The big problem is that the attack is possible thanks to the way X Windows is designed He didn't comment on whether X is flawed or not, but rather that from a Linux perspective this whole issue is a storm in a tea cup. In (distribution default) Linux it is always possible for root to get ring 0 access. Simply because root can load kernel modules. That's what root kits do. Fumbling registers through a hacked X server is a novel but rather complicated way, in comparison. Hence, securing a Linux server has always meant (besides removing X and tons of other crud) to build a kernel that doesn't support loadable modules. And adding something to ensure that /dev/*mem cannot be written by root. There exist pre-written rootkits which load directly via /dev/mem, IIRC. Of course, simply disabling loadable modules does do some good... and this is related to openbsd how? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Intel 82801FB HD Audio
On Tue, May 16, 2006 at 11:44:02AM +, bdz wrote: I built the current kernel that sees the device but can not configure it. Any idea? did forget line: audio* at azalia? dmesg shortened output: azalia0 at pci0 dev 27 function 0 Intel 82801FB HD Audio rev 0x04: irq 5 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Realtek ALC880 (rev. 5.0) azalia0: codec: High Definition Audio rev. 0.9 azalia0: playback: encodings=1PCM azalia0: playback: PCM formats=e056024bit,20bit,16bit,192kHz,96kHz,48kHz,44.1kHz azalia0: playback: max channels=8 azalia0: recording: encodings=1PCM azalia0: recording: PCM formats=6016020bit,16bit,96kHz,48kHz,44.1kHz azalia0: recording: max channels=2 create encodings... format(0): encoding 6 vbits 16 prec 16 chans 2 cmask 0x3 format(0) rates: 44100 48000 96000 192000 format(1): encoding 6 vbits 20 prec 32 chans 2 cmask 0x3 format(1) rates: 44100 48000 96000 192000 format(2): encoding 6 vbits 24 prec 32 chans 2 cmask 0x3 format(2) rates: 44100 48000 96000 192000 format(3): encoding 6 vbits 16 prec 16 chans 4 cmask 0x33 format(3) rates: 44100 48000 96000 192000 format(4): encoding 6 vbits 20 prec 32 chans 4 cmask 0x33 format(4) rates: 44100 48000 96000 192000 format(5): encoding 6 vbits 24 prec 32 chans 4 cmask 0x33 format(5) rates: 44100 48000 96000 192000 format(6): encoding 6 vbits 16 prec 16 chans 6 cmask 0x3f format(6) rates: 44100 48000 96000 192000 format(7): encoding 6 vbits 20 prec 32 chans 6 cmask 0x3f format(7) rates: 44100 48000 96000 192000 format(8): encoding 6 vbits 24 prec 32 chans 6 cmask 0x3f format(8) rates: 44100 48000 96000 192000 format(9): encoding 6 vbits 16 prec 16 chans 8 cmask 0x63f format(9) rates: 44100 48000 96000 192000 format(10): encoding 6 vbits 20 prec 32 chans 8 cmask 0x63f format(10) rates: 44100 48000 96000 192000 format(11): encoding 6 vbits 24 prec 32 chans 8 cmask 0x63f format(11) rates: 44100 48000 96000 192000 format(12): encoding 6 vbits 16 prec 16 chans 2 cmask 0x3 format(12) rates: 44100 48000 96000 format(13): encoding 6 vbits 20 prec 32 chans 2 cmask 0x3 format(13) rates: 44100 48000 96000 azalia0: codec: 0x14f1/0x2bfa (rev. 0.0) azalia0: codec: High Definition Audio rev. 0.9 azalia0: codec[1]: No audio functions audio at azalia0 not configured Adam -- paranoic mickey (my employers have changed but, the name has remained)
Re: azalia panic (appendum)
On Mon, May 15, 2006 at 01:35:21PM +0200, Didier Wiroth wrote: Hello, For those who might be interested. Here is the azalia panic output: seems like codec list is being misprobed or smth... i think if you can compile it w/ #define AZALIA_DEBUG uncommented in azalia.h you should get it figured out better. boot boot bsd.azalia booting hd0a:bsd.azalia: 5039360+868208 [52+259584+241088]=0x61c9d8 entry point at 0x200120* [ using 501096 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.9-current (GENERIC_AZALIA_NTFS) #1: Mon May 15 12:16:55 CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC_AZALIA_NTFS cpu0: Genuine Intel(R) CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2 cpu0: Enhanced SpeedStep 1000 MHz (1244 mV): unknown EST cpu, no changes possible real mem = 2137419776 (2087324K) avail mem = 1942114304 (1896596K) using 4256 buffers containing 106975232 bytes (104468K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(25) BIOS, date 03/13/06, BIOS32 rev. 0 @ 0xfd690, SMB IOS rev. 2.4 @ 0xe0010 (67 entries) bios0: LENOVO 17025PG pcibios0 at bios0: rev 2.1 @ 0xfd620/0x9e0 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdea0/272 (15 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #6 is the last bus bios0: ROM list: 0xc/0xe400! 0xce800/0x1000 0xcf800/0x1000 0xdc000/0x4000! 0 xe/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM MCH rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03: aperture at 0xee10 , size 0x1000 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: irq 11 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Analog Devices AD1981HD (rev. 2.0) azalia0: codec: High Definition Audio rev. 1.0 uvm_fault(0xd06f37e0, 0x0, 0, 1) - e kernel: page fault trap, code=0 Stopped at 0:uvm_fault(0xd06f37e0, 0x0, 0, 1) - e kernel: page fault trap, code=0 Stopped at db_read_bytes+0x14: movb0(%edx),%al ddb ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND *0 -1 0 0 7 0x80204 swapper ddb trace db_read_bytes(0,1,d0822ae4,2,0) at db_read_bytes+0x14 db_get_value(0,1,0,d06249c3,0) at db_get_value+0x19 db_disasm(0,0,d0326dd0,0,0) at db_disasm+0x1d db_print_loc_and_inst(0,d0822b9c,d0822bc4,d0822ba4,0) at db_print_loc_and_inst+0x2d db_trap(6,0,d0822bc4,d0326e65,0) at db_trap+0x75 kdb_trap(6,0,d0822c2c,0) at kdb_trap+0xab trap() at trap+0xa9 --- trap (number 6) --- (null)(d2aa504c,2e9b,d0822cd8,d056d195) at 0 azalia_attach_intr(d2aa5000,d06eb2c0,4,3adc7c,1) at azalia_attach_intr+0xb1 azalia_pci_attach(d2a8ff00,d2aa5000,d0822d80,0,8000d800) at azalia_pci_attach+0x16c config_attach(d2a8ff00,d06b0d98,d0822d80,d0472178) at config_attach+0xef pci_probe_device(d2a8ff00,8000d800,0,0,0) at pci_probe_device+0x135 pci_enumerate_bus(d2a8ff00,0,0,0,0) at pci_enumerate_bus+0xef config_attach(d2a8efc0,d06b0aec,d0822e80,d0471f08) at config_attach+0xef mainbus_attach(0,d2a8efc0,0,0,d0822ef0) at mainbus_attach+0x1ce config_attach(0,d06b0ac8,0,0,d06f38c0) at config_attach+0xef config_rootfound(d0647a1c,0,d0822f38,d04441b1) at config_rootfound+0x27 cpu_configure(0,1,3,0,0) at cpu_configure+0x24 main(0,0,0,0,0) at main+0x352 -- paranoic mickey (my employers have changed but, the name has remained)
Re: Dual Core
On Tue, Apr 18, 2006 at 09:19:55AM -0600, Matt Jibson wrote: Some of us have had problems with dual core: http://marc.theaimsgroup.com/?l=openbsd-miscm=113860396723795w=2 and where does it have any relation to the dual-core nature of the problem? it's mpbios problem. On 4/17/06, Gustavo Rios [EMAIL PROTECTED] wrote: Does it make any difference to have dual core processor or not with openbsd ? one or two cores does not really apear any different to software. on amd64 (numa) there could be consirderations wrt os design. still. we are not doing any of that (yet) anyway. cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: ping shows negative times
time=-8.-560 ms 64 bytes from 172.20.10.1: icmp_seq=136 ttl=64 time=-4.-348 ms 64 bytes from 172.20.10.1: icmp_seq=137 ttl=64 time=-4.-662 ms 64 bytes from 172.20.10.1: icmp_seq=138 ttl=64 time=10.020 ms 64 bytes from 172.20.10.1: icmp_seq=139 ttl=64 time=-5.-442 ms 64 bytes from 172.20.10.1: icmp_seq=140 ttl=64 time=-5.-130 ms 64 bytes from 172.20.10.1: icmp_seq=141 ttl=64 time=-6.-843 ms Other machines on that same 100MBit/s Ethernet respond within more or less consistent times of some 0.3-0.5 ms. Any suggestions are most welcome! Best, --Toni++ -- paranoic mickey (my employers have changed but, the name has remained)
Re: some crashes with VIA VT-310DP (npxdna_xmm(d06e7660) at npxdna_xmm+0x71)
On Thu, Mar 30, 2006 at 12:54:16AM -0500, jared r r spiegel wrote:
On Mon, Mar 27, 2006 at 03:11:49PM -0500, jared r r spiegel wrote:
i forgot 'show panic' and 'show registers' these three times.
this looks totally from outa space!
can you please 'x /i' around the softclock+0x22c ?
id dna indeed comes from there then there have to
be some sort of fpu/xmm/blah instruction there.
10x
cu
ddb{0} show panic
the kernel did not panic
ddb{0} show registers
ds 0x10
es 0x10
fs 0x58
gs 0x10
edi 0xd06e7660cpu_info_primary
esi 0x20
ebp 0xe7d2be68
ebx0
edx 0x2
ecx0
eax0
eip 0xd0491475npxdna_xmm+0x71
cs 0x8
eflags 0x10246
esp 0xe7d2be40
ss0xe7d20010
npxdna_xmm+0x71:movl0x12c(%ebx),%eax
ddb{0} trace
npxdna_xmm(d06e7660) at npxdna_xmm+0x71
Xdna(d0657b2c,e7d2bef8,d02537f7,2000,0) at Xdna+0x39
softclock(0,58,10,10,10) at softclock+0x22c
Xintrsoftclock() at Xintrsoftclock+0x56
--- interrupt ---
Xdoreti() at Xdoreti+0x23
--- interrupt ---
apm_cpu_idle(0,0,0,0,0) at apm_cpu_idle+0x4a
have the machine running on uniprocessor kernel
now and it's been stable for past 2 days ( previous
max uptime on .mp was always 1d )
we're looking at moving it to 3.9, but trying to root
around cvs{@,web} to see if we can find a commit that
smells like it might be a fixing winner before going
back to an MP kernel again.
--
jared
[ openbsd 3.9-current GENERIC ( mar 15 ) // i386 ]
--
paranoic mickey (my employers have changed but, the name has remained)
Re: Locking processes/users to CPUs in SMP systems
On Thu, Mar 23, 2006 at 09:48:05PM -0500, rjn wrote: I was just wondering, is it possible to lock a process or user to a specific CPU in an SMP system? Say for example, I had a database and a web server and I wanted to lock each one to a CPU. Or that I only wanted user 'johndoe' to be able to use a second CPU? not really. even worse -- we have no cpu affinity at all (: this is on my todo list though so maybe in 4.0 . cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: openbsd and the money -solutions
On Fri, Mar 24, 2006 at 08:40:59AM -0300, Andr?s Delfino wrote: Please, stop wanting companies to support you. It doesn't work that way. To develop an OS under a licence like the ISC has a big hole: funding. You can't just go: Hey, you use the implementation that I develop and give away for free, you should pay me!. If the pay you, OK, if the don't, well, that's OK too, and more realistic. One thing you can do, is to maintain OpenBSD free as in freedom, but not as in free bear. The CVS access would be the same as now, but no more FTP downloads with ISOs or install sets. sorry dude but you are full of shit. for example from history: how do you think bsd was developped originally at the ucb? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: openbsd and the money -solutions
On Fri, Mar 24, 2006 at 09:36:01AM -0300, Andr?s Delfino wrote: It was the unique Unix-like OS with that licence. Right now, there are tons of other systems. Companies want to invest in Linux-based systems, because of marketing. what are you smoking dude? what unique? there was not att unix and no hpux and no sunos and nothing else? ibm did not make its own os either? all those huge moose financed bsd at the same time because they were interested in using shit from it. cu On 3/24/06, mickey [EMAIL PROTECTED] wrote: On Fri, Mar 24, 2006 at 08:40:59AM -0300, Andr?s Delfino wrote: Please, stop wanting companies to support you. It doesn't work that way. To develop an OS under a licence like the ISC has a big hole: funding. You can't just go: Hey, you use the implementation that I develop and give away for free, you should pay me!. If the pay you, OK, if the don't, well, that's OK too, and more realistic. One thing you can do, is to maintain OpenBSD free as in freedom, but not as in free bear. The CVS access would be the same as now, but no more FTP downloads with ISOs or install sets. sorry dude but you are full of shit. for example from history: how do you think bsd was developped originally at the ucb? cu -- paranoic mickey (my employers have changed but, the name has remained) -- paranoic mickey (my employers have changed but, the name has remained)
Re: openbsd and the money -solutions
On Fri, Mar 24, 2006 at 10:10:36AM -0300, Andr?s Delfino wrote: As I have said before, BSD was the unique Unix-like operative system with a ISC-style license. That's why, IMHO, companies invested in it. they supported it because they used it for their own product. so what has changed in 'em now? they use it but they do not support it. they make you and me simple folks and small companies to pay our money to make software for 'em. and we continue doing so for at least stuff we get to use for living has decent shit in it. cu On 3/24/06, Damien Miller [EMAIL PROTECTED] wrote: On Fri, 24 Mar 2006, Andris Delfino wrote: Please, stop wanting companies to support you. It doesn't work that way. To develop an OS under a licence like the ISC has a big hole: funding. You can't just go: Hey, you use the implementation that I develop and give away for free, you should pay me!. If the pay you, OK, if the don't, well, that's OK too, and more realistic. Even if we were to accept your pessimistic worldview that organisational gratitude is only a myth, then it is still in companies who use OpenBSD or OpenSSH interest to contribute - funding committed and internally-motivated developers to improve components of your product is far less expensive than recruiting, training, paying and providing office space for semi-motivated staff who crank out code of varying quality for financial reward alone. BTW, your linkage between the license and a lack of funding is specious, and there exist plenty of counter examples - including BSD itself. -d -- paranoic mickey (my employers have changed but, the name has remained)
