Send EMaiL to over 400 miLLion People WORLDWIDE $139
400 MILLION Email Addresses in a 3 volume, 5-disk set ** Complete package only $139!! ** Reach categories Like: Business Opportunity seekers, MLM, Gambling, Adult, Auctions, Golf, Auto, Fitness Health, Investments, Sports, Phsychics, Opt-in Etc.. * ALSO FEATURING OVER 25 MILLION VERIFIED AOL, COMPUSERVE MCI ADDRESSES * MILLIONS OF RANDOM DOMAINS ORGANIZED BY DOMAIN NAME. * NEW * 7 Million Chinese speaking persons' email addresses. ** NEW ** EMAIL GOLD CD - 100 Million FRESHLY EXTRACTED EMAIL ADDRESSES The whole cd package is in TEXT file format and fully exportable to any software. You'll enjoy more responses than with any other advertising media! HOW THIS DIRECTORY WAS COMPILED: * Virtually every other email directory on the Internet was taken and put it through an extensive email verification process thus eliminating all the dead addressess. * Special software spiders through the web searching websites, newsgroups and many other online databases with given keywords like area codes, industries, city names etc.. to find millions of fresh new addresses every week. TURN YOUR PC INTO A CASH MACHINE! E-Mail turns your computer into a Money Machine by giving you FREE, immediate access to over 400 Million People. Don't you think some of these people would be interested in your products or Services? MUCH FASTER: With bulk E-mail you get responses back in 1 to 4 days instead of waiting weeks or months! You can begin filling orders the same day you send E-mail. FREE ADVERTISING WORTH MILLIONS: It costs millions of dollars to mail. DO NOT REPLY TO THIS EMAIL ADDRESS. TO ORDER, READ BELOW: ORDER BY FAX Simply complete the order form below and fax it back to 1-630-604-1030 Make sure that we have your email address so that we can send you a receipt for your transaction. ORDER BY MAIL: Print the form below and send it together with a money order payable to FT International for the balance to: 408-5863 Leslie St. Toronto, ON M2H-1J8 CANADA Please DO NOT send POSTAL Money Orders. FAX THIS ORDER FORM BACK TO 1-630-604-1030 or 1-443-659-0730 Please PRINT or TYPE clearly Full Name: Company Name:_ Telephone: Fax:__ Email Address:__* REQUIRED FIELD Shipping Address:__ City: State/Province: Country:_ZIP/Postal:_ Shipping Options: [] $7 Regular Mail (2 - 4 weeks) [] $15 Priority Mail (1 - 2 weeks) [] $30 Fedex (overnight) For US Canada Only - Other countries extra, please enquire by phone or email Product: (All prices are in US funds) [] Email Marketing CDROM with 100 million Addresses $69.00 [] 200 MILLION EMAIL ADDRESSES on 2 CD's $79.00 [] 1.5 Million USA Business Fax Numbers $49.00 [] COMBO PACKAGE A - ALL DIRECTORIES ABOVE (3 CDs) $99.00 [] Email Gold CD FRESHLY EXTRACTED 100 Million Addresses $99.00 [] 7 Million Chinese Email Addresses $99.00 [] COMBO PACKAGE B - ALL DIRECTORIES ABOVE (5 CDs) $139.00 TOTAL: $_ US Funds [] Paypal Order Please enter your email address for us to request payment from:__ (after faxing in your order you will receive an email requesting you to pay) [] Credit Card Order Card #:___ Expiry Date: __ Type of Card [] VISA [] MASTERCARD [] AMERICAN EXPRESS Name on Card:_ Billing Address:_ZIP/Postal: City:_State/Province:___ Country:_ Last 3 digits on reverse of card next to signature: [ ___ - ___ - ___ ] Cardholder Signature:__ Please note that FT International will appear on your statement. Please feel free to call us at 1-416-410-2136 for any questions or to order by phone. Note that the new Email Gold Cd cannot be ordered by phone yet. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Some problems with Orinoco card in -CURRENT
Hello, With OLDCARD there is no problem. boot -v attached. On Wed, 2002-11-06 at 23:45, Frode Nordahl wrote: Hey, On Wed, 2002-11-06 at 23:28, M. Warner Losh wrote: Strange. OLDCARD or NEWCARD? Send me a full dmesg for each case, since it is likely some resource conflict or another. I do what you've described hundreds of times over the past few months, so it has to be something weird with your computer. My computer might be wierd :) I have a problem with the BIOS not initializing the memory correctly (I often see dmesg output and post morten messages from previous boot). So I even did a __cold__ reboot (unplug AC, remove battery for a while) before this dmesg (boot -v). I only hav NEWCARD kernel available at this time, will post a OLDCARD boot -v ASAP. (See attachment) Warner. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Mon Nov 4 14:23:41 CET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SAMWISE Preloaded elf kernel /boot/kernel/kernel at 0xc05bc000. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc05bc0b4. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc05bc168. Preloaded elf module /boot/kernel/acpi.ko at 0xc05bc214. Calibrating clock(s) ... TSC clock: 1193637253 Hz, i8254 clock: 1193135 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter TSC frequency 1193693787 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1193.69-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 234881024 (229376K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x005e3000 - 0x0dee, 227594240 bytes (55565 pages) 0x0df0 - 0x0dff7fff, 1015808 bytes (248 pages) avail memory = 221925376 (216724K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7290 bios32: Entry = 0xfd6f0 (c00fd6f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6f0+0x11e pnpbios: Found PnP BIOS data at 0xc00f72f0 pnpbios: Entry = f:97e0 Rev = 1.0 Other BIOS signatures found: Initializing GEOMetry subsystem null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 73 80 00 c0 01 00 00 00 22 00 00 01 ef 01 00 01 57 79 00 c0 68 79 00 c0 70 79 00 c0 00 01 01 01 03 01 05 01 07 01 0e 01 0f 01 11 01 12 01 14 01 15 01 17 01 18 01 1a 01 1b 01 VESA: 39 mode(s) found VESA: v2.0, 31680k memory, flags:0x1, mode table:0xc04c36a2 (122) VESA: S3 Incorporated. Twister BIOS VESA: S3 Incorporated. VBE 2.0 Rev 1.1 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06051106) Using $PIR table, 8 entries at 0xc00fdf40 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded00A 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00B 0x56 3 4 5 6 7 9 10 11 12 14 15 embedded00C 0x57 3 4 5 6 7 9 10 11 12 14 15 embedded00D 0x55 3 4 5 6 7 9 10 11 12 14 15 embedded07C 0x56 5 embedded07D 0x57 11 embedded04A 0x55 10 embedded04B 0x56 11 embedded0 13A 0x56 5 embedded01A 0x55 10 embedded10A 0x55 10 embedded0 16A 0x57 11 embedded0 16B 0x56 11 embedded0 17A 0x56 11 embedded0 17B 0x57 11 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 ACPI timer looks GOOD min = 1, max = 2, width = 2 Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
On Thu, Nov 07, 2002 at 12:32:18AM +0100, Jens Rehsack wrote:
Hi,
there two open PR's (PR 44423 and PR 9) related to a problem with
audio/id3lib. I downloaded the new version (3.8.1) and made patches for
some files, so they should work fine with FreeBSD 5.0 (4.7 not tested, I
think gcc3 is required).
But I found out, that the libstdc++ which is installed by `make world`
doesn't have wchar-support enabled. I do not have expirience in changing
modules within freebsd world, so what do I have to do to add wchar-support?
Any help would be nice - I didn't had so much time for C/C++ programming
last year and I missed it. So I could do some more, too.
You could try the patch I've attached:
cd /usr/src
zcat c++-wchar.diff.gz | patch
cd gnu/lib/libstdc++
make
make install
It appears to work for simple programs like this:
#include fstream
#include iostream
#include string
using namespace std;
int
main()
{
wstring test(Lhello);
wofstream strm(test.txt);
strm test endl;
return (0);
}
... but I haven't tested much else; I haven't tried to build id3lib.
Tim
c++-wchar.diff.gz
Description: application/gunzip
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
Tim Robbins wrote: On Thu, Nov 07, 2002 at 12:32:18AM +0100, Jens Rehsack wrote: Hi, there two open PR's (PR 44423 and PR 9) related to a problem with audio/id3lib. I downloaded the new version (3.8.1) and made patches for some files, so they should work fine with FreeBSD 5.0 (4.7 not tested, I think gcc3 is required). But I found out, that the libstdc++ which is installed by `make world` doesn't have wchar-support enabled. I do not have expirience in changing modules within freebsd world, so what do I have to do to add wchar-support? Any help would be nice - I didn't had so much time for C/C++ programming last year and I missed it. So I could do some more, too. You could try the patch I've attached: cd /usr/src zcat c++-wchar.diff.gz | patch cd gnu/lib/libstdc++ make make install I'll try it this evening. How big is the chance to include it into FBSD 5.0-Current distribution. Jens -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: [EMAIL PROTECTED] Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libc size
On Tue, 05-Nov-2002 at 14:22:41 -0800, Tim Kientzle wrote: Andre Albsmeier wrote: I would like to compile the whole base system (maybe even the ports) without the whole setlocale stuff. Do you have any ideas of how to do this easily? Replace setlocale() in lib/libc/locale with a stub. That should do it. Of course, this doesn't really save you that much. Most binaries are dynamically linked, so this saves nothing on disk space for those executables. It's a couple of K for those statically-linked executables that use it, but there aren't that Yeah, you are right. I had a look at it and its size nearly doesn't count. many of them. If you're worried about disk space for the locale data itself, you can simply delete any locales you don't use from /usr/share/locale These are 548 files consuming 606 kB. Regarding the space it is not so much as well... BTW, I deleted the stuff in /usr/X11R6/lib/X11/locale/* one day and my X didn't start anymore. But for the stuff in the base system it might work... Thanks, -Andre It comes up in the context of 'cat' only because it more than doubles the size of an otherwise very small executable for a single option that is not standard and (probably) not ever used. This is a pretty unusual situation. Tim Kientzle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Thu Nov 7 03:05:17 PST 2002 -- Kernel build for GENERIC completed on Thu Nov 7 03:35:23 PST 2002 -- Kernel build for LINT started on Thu Nov 7 03:35:24 PST 2002 -- === vinum Makefile, line 4391: warning: duplicate script for target geom_bsd.o ignored cc1: warnings being treated as errors /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_alloc': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 3) /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 4) /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_init_scbdata': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4601: warning: unsigned int format, different type arg (arg 3) *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl5.6.1 wrapper
On Wed, Nov 06, 2002 at 05:47:51PM -0800, Kris Kennaway wrote:
Can someone explain why the perl wrapper needs to be hardlinked to
perl5.6.1?
The problem I am seeing is this:
USE_PERL5=yes in a port adds the following BUILD_DEPENDS:
enigma# make -V BUILD_DEPENDS
perl5.6.1:/usr/ports/lang/perl5
However 5.0 has perl5.6.1 in the base system still, so this dependency
is always satisfied, the perl port is never added and the port build
that relies on it will fail.
Change that to ${LOCALBASE}/bin/perl5.6.1:/usr/ports/lang/perl5 and you'll
be set.
-Maxim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: XFree
On Wed, 6 Nov 2002, Steve Kargl wrote: On Wed, Nov 06, 2002 at 09:34:39PM -0500, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. Is there a fix in sight, would be great help. I just rebuilt world and XFree86 4.2.1. I killed and restarted X several times while getting my fvwm2 desktop back to normal. I didn't have this black screen problem. How old is your X and desktop? -- Steve OS is from 11/6 . Built XFree86 core was from snapshot 6/11, rebuilt XFree86-Server last night, still the same problem. -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. Video card: Matrox MG 400 Max , box is double Athlon MP 2000+ on a Tyan Motherboard. --- Nov 7 07:26:52 salome kernel: drm0: Matrox G400/G450 (AGP) mem 0xf600-0xf 67f,0xf680-0xf6803fff,0xfc00-0xfdff irq 10 at device 5.0 on pci1 Nov 7 07:26:52 salome kernel: info: [drm] AGP at 0xf800 64MB Nov 7 07:26:52 salome kernel: info: [drm] Initialized mga 3.0.2 20010321 on min or 0 -- -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In message: [EMAIL PROTECTED]
Steven G. Kargl [EMAIL PROTECTED] writes:
: M. Warner Losh said:
: In message: [EMAIL PROTECTED]
: Steven G. Kargl [EMAIL PROTECTED] writes:
: : M. Warner Losh said:
: : In message: [EMAIL PROTECTED]
: : Steven G. Kargl [EMAIL PROTECTED] writes:
: : : Could someone add the following patch to UPDATING?
: : : Change the words to whatever suits your fancy.
: :
: : I'm trying to devise a good way to deal with this breakage and hope it
: : is transient. I'm not hopeful :-( I'll consider adding this to UPDATING.
: :
: :
: : Any user who installed DP1 and a bunch of ports will
: : have a unpleasant experience when they update to
: : post 20021031 sources. All their ports will stop
: : working and it isn't a simple matter to update
: : those ports.
:
: I thought DP1 didn't generate binaries or libraries that contained
: __sF.
:
:
: http://www.freebsd.org/releases/5.0R/schedule.html
:
: DP1 was released on 5 Apr 2002. This may have occurred during
: Peter's last attempt at killing __sF. DP2 is in progress
: according to the web page and __sF should not be present.
: There will also be that group of -current users who lag
: a few weeks behind in their buildworlds.
But std{in,out,err} #defines were changes from __sF to
__std{in,out,err}p almost a year ago. That's what causes __sF to
appear...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ssh-agent broken with pam_ssh for xdm (+ fix for ssh-agent.c)
Dag-Erling Smorgrav wrote: Markus Friedl writes: but shouldn't it do something like seteuid(getuid()); setuid(getuid()); executing ssh-agent? It should. It currently uses popen(3), which doesn't. It needs popen(3)-like functionality because it reads ssh-agent's output in order to set $SSH_AGENT_PID and $SSH_AUTH_SOCK. Rewriting it to use pipe(2) + fork(2) + execve(2) so it can frob the UID after forking but before exec'ing is possible and desirable but not trivial. I'll see what I can do later this week. There is code in sftp.c::connect_to_server() which does something close to this (pipe+fork+exec w/ args), adding uid frobbage should be easy. Though it doesn't do all the signal handling of popen()... -d To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. I have exactly the same problem on my NetBSD box but I haven't spent any time trying to fix it. I wonder if the console font color is being reset to black. You could try typing 'vidcontrol white black' to test that theory. Dunno what might be causing it, though. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Kernel not booting....Immediate crash
Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment= base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM/libdisk problem on pc98
In article [EMAIL PROTECTED]
Poul-Henning Kamp [EMAIL PROTECTED] writes:
I wonder at why pc98 disks don't have their type ('ty') in the result
of kern.geom.conftxt, but i386 disks have.
Feel free to fix this and submit patches to me for review: I want
to make sure we don't adversely affect the platforms which work at
this late point i the release-process.
I have fixed to support pc98. Please review the attached patch.
---
TAKAHASHI Yoshihiro [EMAIL PROTECTED]
Index: geom_bsd.c
===
RCS file: /home/ncvs/src/sys/geom/geom_bsd.c,v
retrieving revision 1.29
diff -u -r1.29 geom_bsd.c
--- geom_bsd.c 28 Oct 2002 07:50:47 - 1.29
+++ geom_bsd.c 7 Nov 2002 14:29:13 -
@@ -701,8 +701,13 @@
if (!error i != 165 flags == G_TF_NORMAL)
break;
+ error = g_getattr(PC98::type, cp, i);
+ if (!error i != 0xc494 flags == G_TF_NORMAL)
+ break;
+
ms-mbroffset = 0;
g_getattr(MBR::offset, cp, ms-mbroffset);
+ g_getattr(PC98::offset, cp, ms-mbroffset);
/* Get sector size, we need it to read data. */
secsize = cp-provider-sectorsize;
Index: geom_pc98.c
===
RCS file: /home/ncvs/src/sys/geom/geom_pc98.c,v
retrieving revision 1.17
diff -u -r1.17 geom_pc98.c
--- geom_pc98.c 4 Nov 2002 06:30:38 - 1.17
+++ geom_pc98.c 7 Nov 2002 14:22:59 -
@@ -32,53 +32,108 @@
* $FreeBSD: src/sys/geom/geom_pc98.c,v 1.17 2002/11/04 06:30:38 phk Exp $
*/
-
#include sys/param.h
-#include sys/stdint.h
#ifndef _KERNEL
+#include signal.h
#include stdio.h
-#include string.h
#include stdlib.h
-#include signal.h
+#include string.h
#include err.h
#else
#include sys/systm.h
#include sys/kernel.h
-#include sys/conf.h
-#include sys/bio.h
#include sys/malloc.h
+#include sys/bio.h
#include sys/lock.h
#include sys/mutex.h
#endif
-#include sys/stdint.h
+
+#include sys/diskpc98.h
#include geom/geom.h
#include geom/geom_slice.h
-#include machine/endian.h
#define PC98_CLASS_NAME PC98
+static void
+g_dec_dos_partition(u_char *ptr, struct dos_partition *d)
+{
+ int i;
+
+ d-dp_mid = ptr[0];
+ d-dp_sid = ptr[1];
+ d-dp_dum1 = ptr[2];
+ d-dp_dum2 = ptr[3];
+ d-dp_ipl_sct = ptr[4];
+ d-dp_ipl_head = ptr[5];
+ d-dp_ipl_cyl = g_dec_le2(ptr + 6);
+ d-dp_ssect = ptr[8];
+ d-dp_shd = ptr[9];
+ d-dp_scyl = g_dec_le2(ptr + 10);
+ d-dp_esect = ptr[12];
+ d-dp_ehd = ptr[13];
+ d-dp_ecyl = g_dec_le2(ptr + 14);
+ for (i = 0; i sizeof(d-dp_name); i++)
+ d-dp_name[i] = ptr[16 + i];
+}
+
struct g_pc98_softc {
- int foo;
+ int type [NDOSPART];
+ struct dos_partition dospart[NDOSPART];
};
static int
g_pc98_start(struct bio *bp)
{
+ struct g_provider *pp;
struct g_geom *gp;
- struct g_pc98_softc *ms;
+ struct g_pc98_softc *mp;
struct g_slicer *gsp;
+ int index;
- gp = bp-bio_to-geom;
+ pp = bp-bio_to;
+ index = pp-index;
+ gp = pp-geom;
gsp = gp-softc;
- ms = gsp-softc;
+ mp = gsp-softc;
+ if (bp-bio_cmd == BIO_GETATTR) {
+ if (g_handleattr_int(bp, PC98::type, mp-type[index]))
+ return (1);
+ if (g_handleattr_off_t(bp, PC98::offset,
+ gsp-slices[index].offset))
+ return (1);
+ }
return (0);
}
static void
-g_pc98_dumpconf(struct sbuf *sb, char *indent, struct g_geom *gp, struct g_consumer
*cp __unused, struct g_provider *pp)
+g_pc98_dumpconf(struct sbuf *sb, char *indent, struct g_geom *gp,
+ struct g_consumer *cp __unused, struct g_provider *pp)
{
+ struct g_pc98_softc *mp;
+ struct g_slicer *gsp;
+ gsp = gp-softc;
+ mp = gsp-softc;
g_slice_dumpconf(sb, indent, gp, cp, pp);
+ if (pp != NULL) {
+ if (indent == NULL)
+ sbuf_printf(sb, ty %d, mp-type[pp-index]);
+ else
+ sbuf_printf(sb, %stype%d/type\n, indent,
+ mp-type[pp-index]);
+ }
+}
+
+static void
+g_pc98_print(int i, struct dos_partition *dp)
+{
+
+ g_hexdump(dp, sizeof(dp[0]));
+ printf([%d] mid:%d(0x%x) sid:%d(0x%x),
+ i, dp-dp_mid, dp-dp_mid, dp-dp_sid, dp-dp_sid);
+ printf( s:%d/%d/%d, dp-dp_scyl, dp-dp_shd, dp-dp_ssect);
+ printf( e:%d/%d/%d, dp-dp_ecyl, dp-dp_ehd, dp-dp_esect);
+ printf( name:%s\n, dp-dp_name);
}
static struct g_geom *
@@ -88,19 +143,19 @@
struct g_consumer *cp;
struct g_provider *pp2;
int error, i, npart;
- u_char *buf, *p;
+ struct dos_partition dp[NDOSPART];
Re: XFree
Thanks for the tip, was my first idea too, because you can type blind. But it doesn't help, it still stays everything black. Remote login works fine, there are no suspicious processes running. -Horen On Thu, 7 Nov 2002, walt wrote: Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. I have exactly the same problem on my NetBSD box but I haven't spent any time trying to fix it. I wonder if the console font color is being reset to black. You could try typing 'vidcontrol white black' to test that theory. Dunno what might be causing it, though. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb %al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message yeah, I've been getting the same thing with 4.7 and 5.0 on a few machines What is the type of machine you are running on? Most of mine were IBM's. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha tinderbox failure
On Thu, Nov 07, 2002 at 03:40:27AM -0800, Dag-Erling Smorgrav wrote:
/h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_alloc':
/h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different
type arg (arg 3)
/h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different
type arg (arg 4)
/h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_init_scbdata':
/h/des/src/sys/dev/aic7xxx/aic79xx.c:4601: warning: unsigned int format, different
type arg (arg 3)
Since I've seen this particular error at least 10 times and it is
getting boring, here's an untested patch. Note that it requires the
currently latest version 1.90 of subr_prf.c. A '-' that should probably
be a '=' is fixed too.
Regards,
Stefan Farfeleder
Index: aic79xx.c
===
RCS file: /home/ncvs/src/sys/dev/aic7xxx/aic79xx.c,v
retrieving revision 1.4
diff -u -r1.4 aic79xx.c
--- aic79xx.c 26 Sep 2002 22:53:59 - 1.4
+++ aic79xx.c 7 Nov 2002 14:23:40 -
-4203,7 +4203,7
}
#ifdef AHD_DEBUG
if ((ahd_debug AHD_SHOW_MEMORY) != 0) {
- printf(%s: scb size = 0x%x, hscb size - 0x%x\n,
+ printf(%s: scb size = 0x%zx, hscb size = 0x%zx\n,
ahd_name(ahd), sizeof(struct scb),
sizeof(struct hardware_scb));
}
-4597,8 +4597,8
}
#ifdef AHD_DEBUG
if ((ahd_debug AHD_SHOW_MEMORY) != 0)
- printf(%s: ahd_sglist_allocsize = 0x%x\n, ahd_name(ahd),
- ahd_sglist_allocsize(ahd));
+ printf(%s: ahd_sglist_allocsize = 0x%llx\n, ahd_name(ahd),
+ (unsigned long long)ahd_sglist_allocsize(ahd));
#endif
scb_data-init_level++;
Re: alpha tinderbox failure
On Thu, Nov 07, 2002 at 04:22:07PM +0100, Stefan Farfeleder wrote: On Thu, Nov 07, 2002 at 03:40:27AM -0800, Dag-Erling Smorgrav wrote: /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_alloc': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 3) /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 4) /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_init_scbdata': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4601: warning: unsigned int format, different type arg (arg 3) Since I've seen this particular error at least 10 times and it is getting boring, here's an untested patch. Note that it requires the currently latest version 1.90 of subr_prf.c. A '-' that should probably be a '=' is fixed too. As I've told others, this file is shared with the Linux version of the driver, so any changes must be compatible with Linux printk(). We'll have a proper fix in the next code drop of this driver. Also, why does the '=' need to be changed to '-' ? Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 07 Nov 2002 10:29:29 -0500, David Rhodu [EMAIL PROTECTED] said: processsor eflags= interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 David yeah, I've been getting the same thing with 4.7 and 5.0 on a few machines David What is the type of machine you are running on? Most of mine were IBM's. Hi, Yes. My machine is an IBM too. It is an IBM Netvista. So, is this problem specific to IBM Machines ? Regards Sid -- A mathematician is a machine for converting coffee into theorems. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha tinderbox failure
On Thu, Nov 07, 2002 at 08:28:30AM -0700, Scott Long wrote: On Thu, Nov 07, 2002 at 04:22:07PM +0100, Stefan Farfeleder wrote: Since I've seen this particular error at least 10 times and it is getting boring, here's an untested patch. Note that it requires the currently latest version 1.90 of subr_prf.c. A '-' that should probably be a '=' is fixed too. As I've told others, this file is shared with the Linux version of the driver, so any changes must be compatible with Linux printk(). We'll have a proper fix in the next code drop of this driver. Fine. Also, why does the '=' need to be changed to '-' ? It's the other way round. printf(%s: scb size = 0x%x, hscb size - 0x%x\n, ^ this should be '='? Regards, Stefan Farfeleder To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM/libdisk problem on pc98
In message [EMAIL PROTECTED], Takahashi Yoshihiro writes: I have fixed to support pc98. Please review the attached patch. COOL! Thanks! The geom_bsd.c change looks entirely reasonable and is OK with me: commit it. The geom_pc98 change looks like a major step i the right direction, but I don't really have a chance to judge its correctness, so if you think it is an improvement, you just commit it. Thankyou very very much! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In article [EMAIL PROTECTED], M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] Steven G. Kargl [EMAIL PROTECTED] writes: : Could someone add the following patch to UPDATING? : Change the words to whatever suits your fancy. I'm trying to devise a good way to deal with this breakage and hope it is transient. I'm not hopeful :-( I'll consider adding this to UPDATING. FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on -current is to make __sF global again and arrange for: stdin == __sF[0] stdout == __sF[1] stderr == __sF[2] John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
On Thu, Nov 07, 2002 at 08:40:32AM -0800, John Polstra wrote: In article [EMAIL PROTECTED], M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] Steven G. Kargl [EMAIL PROTECTED] writes: : Could someone add the following patch to UPDATING? : Change the words to whatever suits your fancy. I'm trying to devise a good way to deal with this breakage and hope it is transient. I'm not hopeful :-( I'll consider adding this to UPDATING. FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on -current is to make __sF global again and arrange for: stdin == __sF[0] stdout == __sF[1] stderr == __sF[2] John, As the author of cvsup, I'm sure you know what is required. But, I rebuilt cvsup from net/cvsup yesterday on a new world, and it appears to be working fine. What problems should I expect? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In article [EMAIL PROTECTED], Steve Kargl [EMAIL PROTECTED] wrote: I rebuilt cvsup from net/cvsup yesterday on a new world, and it appears to be working fine. What problems should I expect? It's possible that if you already have a working installation of pm3 or ezm3, you'll be able to build CVSup on -current. But if you try to build pm3 or ezm3 from scratch, you'll find that the build fails. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
On Thu, Nov 07, 2002 at 09:21:53AM -0800, John Polstra wrote: In article [EMAIL PROTECTED], Steve Kargl [EMAIL PROTECTED] wrote: I rebuilt cvsup from net/cvsup yesterday on a new world, and it appears to be working fine. What problems should I expect? It's possible that if you already have a working installation of pm3 or ezm3, you'll be able to build CVSup on -current. But if you try to build pm3 or ezm3 from scratch, you'll find that the build fails. I removed all ports because of the __sF symbol problem. I simply did cd /usr/ports/net/cvsup ; make install and this automatically installed ezm3. pkg_info doesn't show pm3 installed on system. Perhaps, only pm3 is the port that will have the problem. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In article [EMAIL PROTECTED], Steve Kargl [EMAIL PROTECTED] wrote: On Thu, Nov 07, 2002 at 09:21:53AM -0800, John Polstra wrote: It's possible that if you already have a working installation of pm3 or ezm3, you'll be able to build CVSup on -current. But if you try to build pm3 or ezm3 from scratch, you'll find that the build fails. I removed all ports because of the __sF symbol problem. I simply did cd /usr/ports/net/cvsup ; make install and this automatically installed ezm3. pkg_info doesn't show pm3 installed on system. Perhaps, only pm3 is the port that will have the problem. That would surprise me, but I haven't tried it myself. Inspection of the ezm3 bootstrap shows that it has references to __sF. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In message: [EMAIL PROTECTED] John Polstra [EMAIL PROTECTED] writes: : In article [EMAIL PROTECTED], : M. Warner Losh [EMAIL PROTECTED] wrote: : In message: [EMAIL PROTECTED] : Steven G. Kargl [EMAIL PROTECTED] writes: : : Could someone add the following patch to UPDATING? : : Change the words to whatever suits your fancy. : : I'm trying to devise a good way to deal with this breakage and hope it : is transient. I'm not hopeful :-( I'll consider adding this to UPDATING. : : FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on : -current is to make __sF global again and arrange for: : : stdin == __sF[0] : stdout == __sF[1] : stderr == __sF[2] Why does cvsup need this to be the case? Now you have me curious. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code= user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
On Thu, Nov 07, 2002 at 09:35:19AM -0800, John Polstra wrote: In article [EMAIL PROTECTED], Steve Kargl [EMAIL PROTECTED] wrote: On Thu, Nov 07, 2002 at 09:21:53AM -0800, John Polstra wrote: It's possible that if you already have a working installation of pm3 or ezm3, you'll be able to build CVSup on -current. But if you try to build pm3 or ezm3 from scratch, you'll find that the build fails. I removed all ports because of the __sF symbol problem. I simply did cd /usr/ports/net/cvsup ; make install and this automatically installed ezm3. pkg_info doesn't show pm3 installed on system. Perhaps, only pm3 is the port that will have the problem. That would surprise me, but I haven't tried it myself. Inspection of the ezm3 bootstrap shows that it has references to __sF. Well, I just pkg_deinstall's both ezm3 and cvsup. I re-installed both without problems. I then used cvsup to pull down some source updates. However, here's the strange or maybe fortunate part troutmask:kargl[246] cd /usr/local/lib/m3 troutmask:kargl[247] find . -name \*.a | xargs nm -A | grep __sF ./pkg/m3core/FreeBSD4/libm3core.a:Cstdio.mo: U __sF troutmask:kargl[248] strings /usr/local/sbin/cvsupd | grep __sF troutmask:kargl[249] strings /usr/local/bin/cvsup | grep __sF -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl5.6.1 wrapper
On Wed, Nov 06, 2002 at 05:47:51PM -0800, Kris Kennaway wrote: Can someone explain why the perl wrapper needs to be hardlinked to perl5.6.1? revision 1.5 date: 2002-06-07 18:55:42; author: obrien; state: Exp; lines: +1 -0 Install a perl5.6.1 wrapper. I think this is going too far as now /usr/src has to carefully watch the Perl port to keep this in sync. But this is the only way I am allowed to fix the mozzila build (and other USE_PERL5 ports). Please feel free to back out rev 1.5 if it works better for you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x 73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment= base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Michael Petry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In article [EMAIL PROTECTED], Steve Kargl [EMAIL PROTECTED] wrote: On Thu, Nov 07, 2002 at 09:35:19AM -0800, John Polstra wrote: That would surprise me, but I haven't tried it myself. Inspection of the ezm3 bootstrap shows that it has references to __sF. Well, I just pkg_deinstall's both ezm3 and cvsup. I re-installed both without problems. I then used cvsup to pull down some source updates. However, here's the strange or maybe fortunate part troutmask:kargl[246] cd /usr/local/lib/m3 troutmask:kargl[247] find . -name \*.a | xargs nm -A | grep __sF ./pkg/m3core/FreeBSD4/libm3core.a:Cstdio.mo: U __sF troutmask:kargl[248] strings /usr/local/sbin/cvsupd | grep __sF troutmask:kargl[249] strings /usr/local/bin/cvsup | grep __sF Oh, I think I understand it now. PM3 uses shared libraries, so the undefined reference from libm3core.so matters. But ezm3 uses only static libraries, and Cstdio.mo probably isn't even included in the link (because nothing actually uses it). That explains why ezm3 works in spite of the fact that part of it references __sF. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In article [EMAIL PROTECTED], M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] John Polstra [EMAIL PROTECTED] writes: : FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on : -current is to make __sF global again and arrange for: : : stdin == __sF[0] : stdout == __sF[1] : stderr == __sF[2] Why does cvsup need this to be the case? Now you have me curious. It's not CVSup, it's Modula-3. It thinks it knows that stdin, stdout, and stderr are defined as above, but they're not any more. Because Modula-3 isn't C and doesn't use C header files, it cannot automatically track such changes like C programs do. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Try backing out 1.544 of src/sys/i386/i386/machdep.c You'll need to do it as a reversed patch or by hand, as there are some unrelated signal handling things in 1.545 which you'll really need. Drew Michael G. Petry writes: I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x 73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address= 0x9fdc8 fault code = user read, page not present instruction pointer = 0xf000:0x145e stack pointer= 0x0:0xfb4 frame pointer= 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags= interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Michael Petry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The same is there with 4.7-STABLE The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code= user read, page not present instruction pointer = 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process = 0 () kernel: type 12 trap, code=0 Stopped at0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? -- Dmitry Valdov mailto:dv;dv.ru CCNP To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? Typing blind starts X again. Do you have any idea what could be the problem. Thanks, -Horen It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. Video card: Matrox MG 400 Max , box is double Athlon MP 2000+ on a Tyan Motherboard. --- Nov 7 07:26:52 salome kernel: drm0: Matrox G400/G450 (AGP) mem 0xf600-0xf 67f,0xf680-0xf6803fff,0xfc00-0xfdff irq 10 at device 5.0 on pci1 Nov 7 07:26:52 salome kernel: info: [drm] AGP at 0xf800 64MB Nov 7 07:26:52 salome kernel: info: [drm] Initialized mga 3.0.2 20010321 on min or 0 -- -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
On Thu, Nov 07, 2002 at 07:44:43PM +1100, Tim Robbins wrote: You could try the patch I've attached: cd /usr/src zcat c++-wchar.diff.gz | patch cd gnu/lib/libstdc++ make make install Can you ask Kris to try this on the ports cluster before we commit it? I wonder how many ports this could break. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
Terry Lambert asked: Any chance we could get rid of all externally visable symbols that are not defined as being there by some standard, and not just __sF, since we are breaking the FORTRAN compiler and other third party code already? This cannot be entirely done if you still want to manage library bloat. In short, library routines have shared interfaces between them---common variables or common functions---that are internal to the library and should not be used by applications. To avoid this, you would have to bundle library functions together, which causes bloat. Worse, you would have to avoid or drastically limit your use of macros. (Any macro that uses one of these internal symbols generates a dependency in the compiled application.) It _would_ be a good idea to document any internal library symbols used by macros. Removing such symbols is a good way to break existing compiled applications. Library design involves a lot of tradeoffs. Tim Kientzle To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In message: [EMAIL PROTECTED] John Polstra [EMAIL PROTECTED] writes: : In article [EMAIL PROTECTED], : M. Warner Losh [EMAIL PROTECTED] wrote: : In message: [EMAIL PROTECTED] : John Polstra [EMAIL PROTECTED] writes: : : : FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on : : -current is to make __sF global again and arrange for: : : : : stdin == __sF[0] : : stdout == __sF[1] : : stderr == __sF[2] : : Why does cvsup need this to be the case? Now you have me curious. : : It's not CVSup, it's Modula-3. It thinks it knows that stdin, : stdout, and stderr are defined as above, but they're not any more. : Because Modula-3 isn't C and doesn't use C header files, it cannot : automatically track such changes like C programs do. Gotcha. I'm thinking very seriously about keeping __sF support (but creating no new binaries with it in it) and the freeze on sizeof(FILE) through the 5.x series of releases because we botched the compatibility stuff so badly to give people a chance to catch their breaths before that reorg can happen. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
walt wrote: Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. I have exactly the same problem on my NetBSD box but I haven't spent any time trying to fix it. I wonder if the console font color is being reset to black. You could try typing 'vidcontrol white black' to test that theory. Dunno what might be causing it, though. I had the same problem. I made it go away by turning off all acceleration, and then turning on accelleration options, one by one, until the problem reappeared, and then leaving the three that cuased problems off. It seems that the driver was written for a rev. 2 of the NeoMagic chip, and my laptop actually has rev. 3. Most likely, you will find that turning off all chip-specific options, and then turning on only those which actually reliably work, will fix your problem. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In article [EMAIL PROTECTED], M. Warner Losh [EMAIL PROTECTED] wrote: In message: [EMAIL PROTECTED] John Polstra [EMAIL PROTECTED] writes: : : It's not CVSup, it's Modula-3. It thinks it knows that stdin, : stdout, and stderr are defined as above, but they're not any more. : Because Modula-3 isn't C and doesn't use C header files, it cannot : automatically track such changes like C programs do. Gotcha. I'm thinking very seriously about keeping __sF support (but creating no new binaries with it in it) and the freeze on sizeof(FILE) through the 5.x series of releases because we botched the compatibility stuff so badly to give people a chance to catch their breaths before that reorg can happen. I'm kind of on the fence about it. The point of hiding __sF is to remove all dependencies on the size of the FILE structure from applications, and that's a very worthwhile thing to do. Modula-3 is a special case (and a pathological one), and it shouldn't influence the decision too much. I don't think there's a way to fix it entirely in the OS without re-establishing the dependency on the size of FILE. We are lucky that ezm3 just happens to work. The PM3 port can be fixed with a 5.0-specific patch or two, but ... not today. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Upgrade of port audio/id3lib - stdc++ wchar support missing
On Thu, Nov 07, 2002 at 01:17:58PM -0800, David O'Brien wrote: On Thu, Nov 07, 2002 at 07:44:43PM +1100, Tim Robbins wrote: You could try the patch I've attached: cd /usr/src zcat c++-wchar.diff.gz | patch cd gnu/lib/libstdc++ make make install Can you ask Kris to try this on the ports cluster before we commit it? I wonder how many ports this could break. I'm busy building 5.0-DP2 packages right now. I can give it a run after that though. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
duplicate lock
FreeBSD outel.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Nov 7 05:13:19 PST 2002 [EMAIL PROTECTED]:/disk2/usr.src/sys/i386/compile/testGeneric.nonsmp i386 acquiring duplicate lock of same type: inp 1st inp @ ../../../netinet/udp_usrreq.c:290 2nd inp @ ../../../netinet/udp_usrreq.c:290 this comes up once right after I boot up. searching archive yields this thread. 'Subject: /usr/src/sys/netinet/udp_usrreq.c:290' looks like I'm not the only one seeing this. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Horen wrote: How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? Typing blind starts X again. Do you have any idea what could be the problem. xset s off ? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Thanks, will check on that, hope it will help. -Horen On Thu, 7 Nov 2002, Terry Lambert wrote: Horen wrote: How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? Typing blind starts X again. Do you have any idea what could be the problem. xset s off ? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
dnet causes Hard Lock on SMP kernel? ( was 'Why is my -currentsystem Hard Locking?' )
I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. So the questions now are. 1.) What is dnet doing that is Hard Locking the system? 2.) Is the dnet problem the same as what has been causing my Hard Locks all along? 3.) What is the fix? ADVthaAnksNCE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
From [EMAIL PROTECTED] Thu Nov 7 18:00:10 2002 Date: Thu, 07 Nov 2002 14:47:03 -0800 From: Joel M. Baldwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. So the questions now are. 1.) What is dnet doing that is Hard Locking the system? 2.) Is the dnet problem the same as what has been causing my Hard Locks all along? Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
Tim Kientzle wrote: Terry Lambert asked: Any chance we could get rid of all externally visable symbols that are not defined as being there by some standard, and not just __sF, since we are breaking the FORTRAN compiler and other third party code already? This cannot be entirely done if you still want to manage library bloat. In short, library routines have shared interfaces between them---common variables or common functions---that are internal to the library and should not be used by applications. To avoid this, you would have to bundle library functions together, which causes bloat. Worse, you would have to avoid or drastically limit your use of macros. (Any macro that uses one of these internal symbols generates a dependency in the compiled application.) It _would_ be a good idea to document any internal library symbols used by macros. Removing such symbols is a good way to break existing compiled applications. Library design involves a lot of tradeoffs. I don't buy this. Specifically, I do not buy the idea that there is a necessity for the existance of data interfaces, as opposed to procedural interfaces. And procedural interfaces are fixable with weak symbols. The thing that's screwing us with __sF is that it is a data block that's directly referenced without the use of an accessor function, and thefore there are global data references, rather than accessor or mutator function references. As a result, when the underlying data changes, the code that has already been compiled to reference it, must also change. This problem has already been fixed with errno. It has already been fixed with strerror() (though unfortunately, the sys_errlist[] and sys_nerr references remain unwrapped). It has been fixed in many other places (e.g. the curses library used to export row and column count integers, and doesn't any more). It's very obvious to me that defining a *non-inline* function to return the correct __sF entry by entry ID will erase this problem for a future version of FreeBSD, while leaving the __sF invisible for a revision cycle, so that new applications will get the function reference, and old applications will get the __sF reference they expect, and continue to compile and link correctly. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current systemHard Locking?' )
Ray Kohler wrote: Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) That is, in fact, the case, at least with my system. It usually eventually unhangs on its own, but sometimes it's a hard wedge that only the reset button can fix. This is in -stable, btw. Is it happening in -current as well? -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
M. Warner Losh wrote: Gotcha. I'm thinking very seriously about keeping __sF support (but creating no new binaries with it in it) and the freeze on sizeof(FILE) through the 5.x series of releases because we botched the compatibility stuff so badly to give people a chance to catch their breaths before that reorg can happen. Redefining stdio as: #define stdin (__stdio(0)) #define stdout (__stdio(1)) #define stderr (__stdio(2)) And then defining an __stdio() function that returns a pointer to a struct FILE, would let you change the underlying implementation however you wanted, later, without disrupting newly compiled programs. This may not be entirely happy for static declarations: FILE *fp = stdin; /* default */ ...but that's a compiler problem (I think). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
From [EMAIL PROTECTED] Thu Nov 7 18:30:04 2002 Date: Thu, 07 Nov 2002 15:26:57 -0800 From: Terry Lambert [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [PATCH] note the __sF change in src/UPDATING Specifically, I do not buy the idea that there is a necessity for the existance of data interfaces, as opposed to procedural interfaces. And procedural interfaces are fixable with weak symbols. The thing that's screwing us with __sF is that it is a data block that's directly referenced without the use of an accessor function, and thefore there are global data references, rather than accessor or mutator function references. As a result, when the underlying data changes, the code that has already been compiled to reference it, must also change. This problem has already been fixed with errno. It has already been fixed with strerror() (though unfortunately, the sys_errlist[] and sys_nerr references remain unwrapped). It has been fixed in many other places (e.g. the curses library used to export row and column count integers, and doesn't any more). It's very obvious to me that defining a *non-inline* function to return the correct __sF entry by entry ID will erase this problem for a future version of FreeBSD, while leaving the __sF invisible for a revision cycle, so that new applications will get the function reference, and old applications will get the __sF reference they expect, and continue to compile and link correctly. Hear hear, I agree. There's no need to expose what ought to be private data to the world, especially when we can get the additional benefit here of letting us play with the implementation. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In message: [EMAIL PROTECTED]
Terry Lambert [EMAIL PROTECTED] writes:
: M. Warner Losh wrote:
: Gotcha. I'm thinking very seriously about keeping __sF support (but
: creating no new binaries with it in it) and the freeze on sizeof(FILE)
: through the 5.x series of releases because we botched the
: compatibility stuff so badly to give people a chance to catch their
: breaths before that reorg can happen.
:
: Redefining stdio as:
:
: #define stdin (__stdio(0))
: #define stdout(__stdio(1))
: #define stderr(__stdio(2))
:
: And then defining an __stdio() function that returns a pointer
: to a struct FILE, would let you change the underlying implementation
: however you wanted, later, without disrupting newly compiled programs.
:
: This may not be entirely happy for static declarations:
:
: FILE *fp = stdin; /* default */
:
: ...but that's a compiler problem (I think).
That's what __std{in,out,err}p do, and it saves function calls all
over the place. This patch just makes -stable more compatible with
current.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my-current system Hard Locking?' )
--On Thursday, November 07, 2002 6:07 PM -0500 Ray Kohler [EMAIL PROTECTED] wrote: From [EMAIL PROTECTED] Thu Nov 7 18:00:10 2002 Date: Thu, 07 Nov 2002 14:47:03 -0800 From: Joel M. Baldwin [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' ) The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. So the questions now are. 1.) What is dnet doing that is Hard Locking the system? 2.) Is the dnet problem the same as what has been causing my Hard Locks all along? Just a guess, but maybe your system locks up every time the CPU usage gets very high under SMP? That's one thing dnetc is guaranteed to do. Do other CPU-intensive operations do it? (Maybe you said earlier, but I haven't been following this thread.) - @ I've run dnet reliably before. I'm assuming the Hard Lock problem is threads related, but at this point who knows. A more heavily load system seems to increase the chances of a Hard Lock. But it HAS happened with nothing going on. Well, relatively nothing, this system does real work so its never completely idle. The important thing is I can now force a Hard Lock simply by running a program. This is something that shouldn't happen and needs to be solved. With any luck this will also solve my stability problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. I got same result on my box. Only solution I have is deinstall dnetc. :-) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Thu Nov 7 15:11:33 PST 2002 -- Kernel build for GENERIC completed on Thu Nov 7 15:48:23 PST 2002 -- Kernel build for LINT started on Thu Nov 7 15:48:24 PST 2002 -- === vinum Makefile, line 4413: warning: duplicate script for target geom_bsd.o ignored cc1: warnings being treated as errors /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_alloc': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 3) /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 4) /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_init_scbdata': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4601: warning: unsigned int format, different type arg (arg 3) *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate lock
Joel M. Baldwin wrote: acquiring duplicate lock of same type: inp 1st inp @ ../../../netinet/udp_usrreq.c:290 2nd inp @ ../../../netinet/udp_usrreq.c:290 I get this every tims samba starts. Jeffery Hsu stated that its benign. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: XFree
Tried all combinations. Disabled every chip related feature, that isn't required to bring X up. Screensaver is disabled. No way to get any readable display back without reboot. Installed a fresh XFree86 built from the ports tree, hour before updated. No luck :-( -Horen Thanks, will check on that, hope it will help. -Horen On Thu, 7 Nov 2002, Terry Lambert wrote: Horen wrote: How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? Typing blind starts X again. Do you have any idea what could be the problem. xset s off ? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Horen wrote: Tried all combinations. Disabled every chip related feature, that isn't required to bring X up. Screensaver is disabled. No way to get any readable display back without reboot. Installed a fresh XFree86 built from the ports tree, hour before updated. No luck :-( You stated Typing blind starts X again. Can you tell us what you mean by this? o It restarts X, as if you typed startx o It restarts X, as if you typed xinit o It restarts X, as in it comes back from video signal blanking o It doesn't really restart X, you were lying... (8-)) o Turning my monitor off, and back on works the same way o ...something else happens -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
From [EMAIL PROTECTED] Thu Nov 7 19:30:04 2002 Date: Thu, 07 Nov 2002 16:19:57 -0800 From: Terry Lambert [EMAIL PROTECTED] To: Horen [EMAIL PROTECTED] Cc: Eric Anholt [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: XFree Horen wrote: Tried all combinations. Disabled every chip related feature, that isn't required to bring X up. Screensaver is disabled. No way to get any readable display back without reboot. Installed a fresh XFree86 built from the ports tree, hour before updated. No luck :-( You stated Typing blind starts X again. Can you tell us what you mean by this? o It restarts X, as if you typed startx o It restarts X, as if you typed xinit o It restarts X, as in it comes back from video signal blanking o It doesn't really restart X, you were lying... (8-)) o Turning my monitor off, and back on works the same way o ...something else happens I think he meant Typing commands blind works, up to and including running `startx' to start X again. - @ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On Thu, 2002-11-07 at 04:40, Horen wrote: On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. I was asking if X has ever exited cleanly to console for you after logging out, and if it has, what you changed (particularly in your XFree86-Server version) between when it was working and when it wasn't. This is most likely just a failure of the driver to properly reset things for your card. Does disabling DRI in XF86Config help it exit cleanly? -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On Thu, 7 Nov 2002, Terry Lambert wrote: Horen wrote: Tried all combinations. Disabled every chip related feature, that isn't required to bring X up. Screensaver is disabled. No way to get any readable display back without reboot. Installed a fresh XFree86 built from the ports tree, hour before updated. No luck :-( You stated Typing blind starts X again. Can you tell us what you mean by this? o It restarts X, as if you typed startx Exactly that. -Horen o It restarts X, as if you typed xinit o It restarts X, as in it comes back from video signal blanking o It doesn't really restart X, you were lying... (8-)) o Turning my monitor off, and back on works the same way o ...something else happens -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On 7 Nov 2002, Eric Anholt wrote: On Thu, 2002-11-07 at 04:40, Horen wrote: On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. I was asking if X has ever exited cleanly to console for you after logging out, and if it has, what you changed (particularly in your XFree86-Server version) between when it was working and when it wasn't. This is most likely just a failure of the driver to properly reset things for your card. Does disabling DRI in XF86Config help it exit cleanly? X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. Nothing changed. -Horen -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my-current system Hard Locking?' )
--On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama [EMAIL PROTECTED] wrote: At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. I got same result on my box. Only solution I have is deinstall dnetc. :-) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. What motherboard/CPU is this on? Have you tried a nonSMP kernel? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Horen wrote: You stated Typing blind starts X again. Can you tell us what you mean by this? o It restarts X, as if you typed startx Exactly that. The problem is clearly in the X11 code, then, since it is not resetting the card to the video mode it was in before X started. You would do well to look at the XFree86 mailing list archives, since your answer is likely to be there (this is not a FreeBSD specific problem, if it is not happening because of FreeBSD specific code). The only possible way this could be a FreeBSD specific problem is if you were using, e.g., the AGP driver, and it wasn't working. You said it worked bofore; probably the place to start is what changed betewwn 'before' and 'now'?. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On Thu, 7 Nov 2002, Terry Lambert wrote: Horen wrote: You stated Typing blind starts X again. Can you tell us what you mean by this? o It restarts X, as if you typed startx Exactly that. The problem is clearly in the X11 code, then, since it is not resetting the card to the video mode it was in before X started. You would do well to look at the XFree86 mailing list archives, since your answer is likely to be there (this is not a FreeBSD specific problem, if it is not happening because of FreeBSD specific code). The only possible way this could be a FreeBSD specific problem is if you were using, e.g., the AGP driver, and it wasn't working. You said it worked bofore; probably the place to start is what changed betewwn 'before' and 'now'?. -- Terry On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work. Don't you think it is OS related. ? I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works. Only on FreeBSD 5,0 , it doesn't work. -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On Thu, 2002-11-07 at 16:56, Horen wrote: On 7 Nov 2002, Eric Anholt wrote: On Thu, 2002-11-07 at 04:40, Horen wrote: On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. I was asking if X has ever exited cleanly to console for you after logging out, and if it has, what you changed (particularly in your XFree86-Server version) between when it was working and when it wasn't. This is most likely just a failure of the driver to properly reset things for your card. Does disabling DRI in XF86Config help it exit cleanly? X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. Nothing changed. Exact same version of the X Server (pkg_info | grep XFree86-Server)? -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On 7 Nov 2002, Eric Anholt wrote: On Thu, 2002-11-07 at 16:56, Horen wrote: On 7 Nov 2002, Eric Anholt wrote: On Thu, 2002-11-07 at 04:40, Horen wrote: On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. I was asking if X has ever exited cleanly to console for you after logging out, and if it has, what you changed (particularly in your XFree86-Server version) between when it was working and when it wasn't. This is most likely just a failure of the driver to properly reset things for your card. Does disabling DRI in XF86Config help it exit cleanly? X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. Nothing changed. Exact same version of the X Server (pkg_info | grep XFree86-Server)? XFree86-Server-4.2.1_5 XFree86-4 X server and related programs -- Eric Anholt [EMAIL PROTECTED] http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
On 7 Nov 2002, Eric Anholt wrote: On Thu, 2002-11-07 at 16:56, Horen wrote: On 7 Nov 2002, Eric Anholt wrote: On Thu, 2002-11-07 at 04:40, Horen wrote: On 6 Nov 2002, Eric Anholt wrote: On Wed, 2002-11-06 at 18:34, Horen wrote: Posted a week ago the question, didn't get any reaction. Everything with current from last night works fine but killing X or logging out ends in a black screen. No way to activate the display without reboot. Remote login is fine. Typing blind works too. How long has this been going on? Did it start at any particular point (a specific kernel or XFree86 upgrade)? What video card do you use? Does starting X again not work? It started sometimes in Oct, switched back to 4.7 stable. Did yesterday an installation from scratch and built XFree86-Server after buildworld. I was asking if X has ever exited cleanly to console for you after logging out, and if it has, what you changed (particularly in your XFree86-Server version) between when it was working and when it wasn't. This is most likely just a failure of the driver to properly reset things for your card. Does disabling DRI in XF86Config help it exit cleanly? X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. Nothing changed. Exact same version of the X Server (pkg_info | grep XFree86-Server)? XFree86-Server-4.2.1_5 XFree86-4 X server and related programs Do you think, it makes sense, that I grab an other version, 4.2.0 or even 4.1.x to check ? -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
On Thu, 7 Nov 2002 10:24:23 -0800 (PST), Julian Elischer [EMAIL PROTECTED] said: Julian Are the modules also new? Hi, Yes, the modules are also new. But, I don't think it has anything to do with the modules, cause even if I load the kernel after removing the modules, I get the same crash. Regards Sid -- Anything free is worth what you pay for it. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
a queston about ACL acl_type_t
Hi, I am trying to understand the ACL implementation in FreeBSD-Current. I have a question about ACL. in acl.h, there are some acl_type_t value macro: /* * Possible valid values for acl_type_t arguments. */ #define ACL_TYPE_ACCESS 0x #define ACL_TYPE_DEFAULT 0x0001 #define ACL_TYPE_AFS 0x0002 #define ACL_TYPE_CODA 0x0003 #define ACL_TYPE_NTFS 0x0004 #define ACL_TYPE_NWFS 0x0005 But I am not sure what's means. in the 'setfacl' source, I found the usage: If we want to control a directory, acl[ACL_TYPE_DEFAULT] = acl_get_file(filename, ACL_TYPE_DEFAULT); if we want to sontrol a file, acl[DEFAULT_ACL] = NULL; Why? What's the difference among those macros? Why must a directory object reserve two acl_t_structs, and a file only need one? Thank you! Best Regards Ouyang Kai _ Ãâ·ÑÏÂÔØ MSN Explorer: http://explorer.msn.com/lccn/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
This kernel lacks ppp support?
I've just tried to start pppd on two different -CURRENT machines, one built on 26 October, the other on 5 November. In each case I get the following message: pppd: This system lacks kernel support for PPP. To include PPP support in the kernel, please follow the steps detailed in the README.bsd file in the ppp-2.2 distribution. Both kernel config files contain the requisite options ppp In addition, I don't see anything looking like ppp-2.2. Is this a bogon in the import of pppd? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Hi, Try backing out 1.544 of src/sys/i386/i386/machdep.c You'll need to do it as a reversed patch or by hand, as there are some unrelated signal handling things in 1.545 which you'll really need. Hmmm, I didn't notice that there is a BIOS which requires memory area below 640K even when calling INT 15H/E820. We cannot trust that today's BOISes have INT 12H, so it's difficult to determine base memory size w/o INT 15H/E820. OK, some questions: - What is the size of your base memory (reported by boot loader)? - Does attached patches solve your problem? - Is this problem specific to IBM Netvista? Thanks Index: locore.s === RCS file: /home/ncvs/src/sys/i386/i386/locore.s,v retrieving revision 1.160 diff -u -r1.160 locore.s --- locore.s25 Oct 2002 19:10:56 - 1.160 +++ locore.s8 Nov 2002 04:48:32 - @@ -851,6 +851,11 @@ movl$(KSTACK_PAGES), %ecx fillkptphys($PG_RW) +/* Map base memory */ + movl$0, %eax + movl$0xaPAGE_SHIFT, %ecx + fillkptphys($PG_RW|PG_U) + /* Map ISA hole */ movl$ISA_HOLE_START, %eax movl$ISA_HOLE_LENGTHPAGE_SHIFT, %ecx Drew Michael G. Petry writes: I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. Are the modules also new? On Thu, 7 Nov 2002, Sidcarter wrote: Hi Folks, I just did a cvsup and installed a kernel. I have been trying this from the past few days with the same error. I am copying this by hand, since it crashes immediately after loading the modules. The error message is here Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x 73b9/]\ Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9fdc8 fault code = user read, page not present instruction pointer= 0xf000:0x145e stack pointer = 0x0:0xfb4 frame pointer = 0x0:0xfca code segment = base 0x0, limit 0x0, type 0x0 DPL 0, pres 0, def32, gran 0 processsor eflags = interrupt enabled, resume, vm86, IOPL=0 current process= 0 () kernel: type 12 trap, code=0 Stopped at 0x145e: addb%al,0(%eax) db t (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e db uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 Any idea what could be wrong ? Becoz of this problem, I am also unable to do an install world as the it is looking for sigaction in the kernel. TIA Regards Sid To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Michael Petry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: This kernel lacks ppp support?
On Fri, Nov 08, 2002 at 12:31:13PM +1030, Greg 'groggy' Lehey wrote: I've just tried to start pppd on two different -CURRENT machines, one built on 26 October, the other on 5 November. In each case I get the following message: pppd: This system lacks kernel support for PPP. To include PPP support in the kernel, please follow the steps detailed in the README.bsd file in the ppp-2.2 distribution. Both kernel config files contain the requisite options ppp In addition, I don't see anything looking like ppp-2.2. Is this a bogon in the import of pppd? pppd's prior to Tue Nov 5 05:58:31 2002 UTC don't work with ppp(4) devices after the cloning conversion. If you upgrade it should work. As a workaround, you can do an ifconfig ppp0 create before running pppd. The change on the 5th was to test for ppp support by checking that the module was compiled in or loaded rather then testing for interfaces. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg46300/pgp0.pgp Description: PGP signature
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
On 07-Nov-2002, Joel M. Baldwin wrote: --On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama [EMAIL PROTECTED] wrote: At Thu, 7 Nov 2002 22:55:56 + (UTC), Joel M. Baldwin [EMAIL PROTECTED] wrote: I'm still pursuing the cause of the Hard Locks on my system. 1.) I have a serial console hooked up. Nothing appears on the console when a Hard Lock happens. No panic. 2.) Shorting IOCHK to ground on the ISA connector doesn't work on a ABIT BP6, so I can't force myself into ddb. The BIG thing is that I now have a sure fire way of forcing a Hard Lock. Every time I run the distributed.net client 'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! I have a non SMP kernel running and things so far seem stable. Running the system with only 1 CPU is slow, so it'll take a while for me to be sure. I got same result on my box. Only solution I have is deinstall dnetc. :-) -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. What motherboard/CPU is this on? Have you tried a nonSMP kernel? I noticed my machine started locking up almost a month ago and ended up removing all services on startup. Starting dnetc back up and the machine locks hard. Sorry for lack of info, but this appears to be just over a month old. The info I wrote down previously pointed to kern_fork.c and proctree function call. -- Scott DodsonPGP KEY id 0x5F9A9E5E [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
Thus spake Michael G. Petry [EMAIL PROTECTED]: I'm noticing the same behavior on a PPro system I have and am following the thread SMP broken on PPro. It looks like the problem is not SMP specific, but it does seem PPro centric. I observed the problem on a PPro as well, but it is not specific to PPros. It will occur on any BIOSes (mostly older ones) that use a small amount of memory right before the 640K mark. The problem is that the person who committed the broken change didn't understand that you have to map this region into virtual memory if you're going to call the BIOS in protected mode. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Minor size optimization
The attached diff shaves four bytes from every syscall wrapper (e.g., __sys_write, etc.) In looking carefully at library sizes, I became curious why a simple system call required 20 bytes; turns out a lot of that was alignment padding. Tim Kientzle Index: lib/libc/i386/SYS.h === RCS file: /mnt/cvs/src/lib/libc/i386/SYS.h,v retrieving revision 1.24 diff -c -r1.24 SYS.h *** lib/libc/i386/SYS.h 17 Sep 2002 01:48:51 - 1.24 --- lib/libc/i386/SYS.h 8 Nov 2002 06:15:21 - *** *** 48,54 .set CNAME(__CONCAT(_,x)),CNAME(__CONCAT(__sys_,x)); \ mov __CONCAT($SYS_,x),%eax; KERNCALL; jb 2b ! #define RSYSCALL(x) SYSCALL(x); ret #define PSEUDO(x) ENTRY(__CONCAT(__sys_,x)); \ .weak CNAME(__CONCAT(_,x)); \ --- 48,63 .set CNAME(__CONCAT(_,x)),CNAME(__CONCAT(__sys_,x)); \ mov __CONCAT($SYS_,x),%eax; KERNCALL; jb 2b ! /* Version 1: More compact source */ ! /* #defineRSYSCALL(x) SYSCALL(x); ret */ ! /* Version 2: More compact object code (fewer alignment requirements) */ ! #define RSYSCALL(x) ENTRY(__CONCAT(__sys_,x)); \ ! .weak CNAME(x); \ ! .set CNAME(x),CNAME(__CONCAT(__sys_,x));\ ! .weak CNAME(__CONCAT(_,x)); \ ! .set CNAME(__CONCAT(_,x)),CNAME(__CONCAT(__sys_,x)); \ ! mov __CONCAT($SYS_,x),%eax; KERNCALL; jb 2f; ret; \ ! 2: PIC_PROLOGUE; jmp PIC_PLT(HIDENAME(cerror)) #define PSEUDO(x) ENTRY(__CONCAT(__sys_,x)); \ .weak CNAME(__CONCAT(_,x)); \
Re: XFree
Horen wrote: On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work. Don't you think it is OS related. ? THere are a lot of MS-DOS programs that won't run on FreeBSD; I don't think that's FreeBSD-related, I think it's the code doing the wrong things to run on FreeBSD. I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works. Only on FreeBSD 5,0 , it doesn't work. Have you tried running the 4.x binaries on 5.x, or are you running different binaries? It could be that the code is broken in a way that exercises a complier error; 5.x uses a different compiler than 4.x. I would recommend you install the 4.x binaries on 5.x, rather than running 5.x binaries. If the binaries are exactly the same, then I will be willing to blame the OS, even though you are one of the few persons who are running into problems. As far as root cause analysis goes, you've given us a report that looks like it doesn't work. If you can make it so that the only thing that has changed is the OS, then it willbe much easier to blame the OS. I'm still not sure that it isn't the AGP driver being different. Have you tried an unaccelerated X server? I'm talking Xvga, not just turning off the acceleration in the config file... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Horen wrote: X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the Exact same version of the X Server (pkg_info | grep XFree86-Server)? XFree86-Server-4.2.1_5 XFree86-4 X server and related programs That's the version of the source code. Are you running the same binaries? Or were the broken binaries compiled on 5.x, with the new C compiler, etc.? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: XFree
Horen wrote: XFree86-Server-4.2.1_5 XFree86-4 X server and related programs Do you think, it makes sense, that I grab an other version, 4.2.0 or even 4.1.x to check ? No, I think the source code version is much less relevent than the platform and compiler which was used to compile the X11 binaries. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: This kernel lacks ppp support?
Greg 'groggy' Lehey wrote: I've just tried to start pppd on two different -CURRENT machines, one built on 26 October, the other on 5 November. In each case I get the following message: pppd: This system lacks kernel support for PPP. To include PPP support in the kernel, please follow the steps detailed in the README.bsd file in the ppp-2.2 distribution. This is a feature of the new code. You have to ifconfig the PPP interface to create it. See the recent discussion on the module loading of PPP, and whether it should be automatic, and the interface existance test code that was changes. It's in the -current archives from 2 weeks ago. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel not booting....Immediate crash
OK, some questions:
- What is the size of your base memory (reported by boot loader)?
- Does attached patches solve your problem?
- Is this problem specific to IBM Netvista?
Thanks
Index: locore.s
===
RCS file: /home/ncvs/src/sys/i386/i386/locore.s,v
Oops, not this file.
Thanks
Index: machdep.c
===
RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v
retrieving revision 1.545
diff -u -r1.545 machdep.c
--- machdep.c 25 Oct 2002 19:10:56 - 1.545
+++ machdep.c 8 Nov 2002 04:50:05 -
@@ -1513,6 +1513,7 @@
struct vm86context vmc;
vm_offset_t pa, physmap[PHYSMAP_SIZE];
pt_entry_t *pte;
+ pt_entry_t saved_pte[160];
char *cp;
struct bios_smap *smap;
@@ -1520,6 +1521,14 @@
bzero(physmap, sizeof(physmap));
basemem = 0;
+ for (pa = (4 PAGE_SHIFT); pa ISA_HOLE_START; pa += PAGE_SIZE)
+ pmap_kenter(KERNBASE + pa, pa);
+ pte = (pt_entry_t *)vm86paddr;
+ for (i = 4; i 160; i++) {
+ saved_pte[i] = pte[i];
+ pte[i] |= PG_V | PG_RW | PG_U;
+ }
+
/*
* map page 1 R/W into the kernel page table so we can use it
* as a buffer. The kernel will unmap this page later.
@@ -1629,6 +1638,12 @@
* pmap_mapdev, but since no memory needs to be
* allocated we simply change the mapping.
*/
+ pte = (pt_entry_t *)vm86paddr;
+ for (i = 4; i 160; i++)
+ pte[i] = saved_pte[i];
+ for (pa = (4 PAGE_SHIFT); pa ISA_HOLE_START; pa += PAGE_SIZE)
+ pmap_kremove(KERNBASE + pa);
+
for (pa = trunc_page(basemem * 1024);
pa ISA_HOLE_START; pa += PAGE_SIZE)
pmap_kenter(KERNBASE + pa, pa);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ssh-agent broken with pam_ssh for xdm (+ fix for ssh-agent.c)
Damien Miller wrote:
Dag-Erling Smorgrav wrote:
Markus Friedl writes:
but shouldn't it do something like
seteuid(getuid());
setuid(getuid());
executing ssh-agent?
It should. It currently uses popen(3), which doesn't. It needs
popen(3)-like functionality because it reads ssh-agent's output in
order to set $SSH_AGENT_PID and $SSH_AUTH_SOCK. Rewriting it to use
pipe(2) + fork(2) + execve(2) so it can frob the UID after forking but
before exec'ing is possible and desirable but not trivial. I'll see
what I can do later this week.
There is code in sftp.c::connect_to_server() which does something close
to this (pipe+fork+exec w/ args), adding uid frobbage should be easy.
Though it doesn't do all the signal handling of popen()...
This is such a common case, it seems to me that it should use
common code. See attached patch, which adds an supopen(3) to
libc.
The man page addition to popen(3) is left as an exercise for someone who
cares...
-- Terry
Index: lib/libc/gen/popen.c
===
RCS file: /cvs/src/lib/libc/gen/popen.c,v
retrieving revision 1.16
diff -c -r1.16 popen.c
*** lib/libc/gen/popen.c1 Feb 2002 01:08:48 - 1.16
--- lib/libc/gen/popen.c7 Nov 2002 19:03:34 -
***
*** 65,70
--- 65,81
popen(command, type)
const char *command, *type;
{
+ return( supopen( command, type, 0, 0, 0);
+ }
+
+
+ FILE *
+ supopen(command, type, set, uid, gid)
+ const char *command, *type;
+ int set;
+ uid_t uid;
+ gid_t uid;
+ {
struct pid *cur;
FILE *iop;
int pdes[2], pid, twoway;
***
*** 105,110
--- 116,127
return (NULL);
/* NOTREACHED */
case 0: /* Child. */
+ if (set) {
+ setegid( gid);
+ setgid( gid);
+ seteuid( uid);
+ setuid( uid);
+ }
if (*type == 'r') {
/*
* The _dup2() to STDIN_FILENO is repeated to avoid
Index: include/stdio.h
===
RCS file: /cvs/src/include/stdio.h,v
retrieving revision 1.50
diff -c -r1.50 stdio.h
*** include/stdio.h 14 Oct 2002 11:18:21 - 1.50
--- include/stdio.h 7 Nov 2002 18:55:49 -
***
*** 286,291
--- 286,294
#if __POSIX_VISIBLE = 199209
intpclose(FILE *);
FILE *popen(const char *, const char *);
+ #if !defined(_ANSI_SOURCE) !defined(_POSIX_SOURCE)
+ FILE *supopen(const char *, const char *, int, uid_t, gid_t);
+ #endif
#endif
#if __POSIX_VISIBLE = 199506
Re: duplicate lock
Joel M. Baldwin wrote: FreeBSD outel.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Nov 7 05:13:19 PST 2002 [EMAIL PROTECTED]:/disk2/usr.src/sys/i386/compile/testGeneric.nonsmp i386 acquiring duplicate lock of same type: inp 1st inp @ ../../../netinet/udp_usrreq.c:290 2nd inp @ ../../../netinet/udp_usrreq.c:290 this comes up once right after I boot up. searching archive yields this thread. 'Subject: /usr/src/sys/netinet/udp_usrreq.c:290' looks like I'm not the only one seeing this. This happens on my test machine directly after samba starts ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: [EMAIL PROTECTED] Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
In message: [EMAIL PROTECTED] Ray Kohler [EMAIL PROTECTED] writes: : Hear hear, I agree. There's no need to expose what ought to be : private data to the world, especially when we can get the additional : benefit here of letting us play with the implementation. -current already does this. The problem is that we're trying to shoot the bad access in the head, and that is what is screwing people. So the problem isn't that we're trying to export private data to the world. Quite the contrary, we're trying to eliminate it and having growing pains. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[no subject]
the ps aux command show some proceses started on dec 31 1969. this is -current from Nov 5th. attached is the log. If i compile daemon_saver in the kernel, somehow it get invoked even while the machine is booting. I have to manually press a key to see the boot messages. dheeraj USERPID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11 97.5 0.0 0 12 ?? RL 31Dec69 189:49.97 (idle) root 10 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00 (ktrace) root 1 0.0 0.3 688 212 ?? ILs 31Dec69 0:00.11 /sbin/init -- root 12 0.0 0.0 0 12 ?? WL 31Dec69 0:00.01 (swi1: net) root 13 0.1 0.0 0 12 ?? WL 31Dec69 1:17.90 (swi6: tty:sio cl root 2 0.0 0.0 0 12 ?? DL 31Dec69 0:08.54 (g_event) root 3 0.0 0.0 0 12 ?? DL 31Dec69 0:03.95 (g_up) root 4 0.0 0.0 0 12 ?? DL 31Dec69 0:04.98 (g_down) root 15 0.0 0.0 0 12 ?? DL 31Dec69 0:01.27 (random) root 18 0.0 0.0 0 12 ?? WL 31Dec69 0:01.43 (irq14: ata0) root 20 0.0 0.0 0 12 ?? WL 31Dec69 0:00.02 (irq11: ed0) root 21 0.0 0.0 0 12 ?? WL 31Dec69 0:00.03 (irq1: atkbd0) root 22 0.0 0.0 0 12 ?? WL 31Dec69 0:00.00 (irq6: fdc0) root 23 0.0 0.0 0 12 ?? WL 31Dec69 0:00.00 (irq7: ppc0) root 24 0.0 0.0 0 12 ?? WL 31Dec69 0:00.00 (swi0: tty:sio) root 5 0.0 0.0 0 12 ?? DL 31Dec69 0:00.41 (pagedaemon) root 6 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00 (vmdaemon) root 7 0.0 0.0 0 12 ?? DL 31Dec69 0:01.35 (pagezero) root 8 0.0 0.0 0 12 ?? DL 31Dec69 0:00.34 (bufdaemon) root 9 0.0 0.0 0 12 ?? DL 31Dec69 0:00.00 (vnlru) root 31 0.0 0.0 0 12 ?? DL 31Dec69 0:01.49 (syncer) root 32 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod 0) root 33 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod 1) root 34 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod 2) root 35 0.0 0.0 0 12 ?? IL 31Dec69 0:00.00 (nfsiod 3) root117 0.0 0.1 216 76 ?? Is3:28PM 0:00.00 adjkerntz -i root230 0.0 1.0 1124 612 ?? Ss8:28PM 0:00.36 /usr/sbin/syslogd root388 0.0 2.1 2508 1288 ?? Is8:28PM 0:01.30 /usr/sbin/sshd root393 0.0 2.9 2944 1752 ?? Ss8:28PM 0:02.23 sendmail: acceptin smmsp 396 0.0 2.7 2848 1664 ?? Is8:28PM 0:00.08 sendmail: Queue ru root420 0.0 0.8 1092 512 ?? Ss8:28PM 0:00.03 /usr/sbin/moused - root450 0.0 1.2 1192 720 ?? Ss8:28PM 0:00.41 /usr/sbin/cron root460 0.0 1.7 1504 1008 v0 Is8:28PM 0:00.25 login -p root root461 0.0 1.0 1136 620 v1 Is+ 8:28PM 0:00.04 /usr/libexec/getty root462 0.0 1.0 1136 620 v2 Is+ 8:28PM 0:00.04 /usr/libexec/getty root463 0.0 1.0 1136 620 v3 Is+ 8:28PM 0:00.04 /usr/libexec/getty root464 0.0 1.0 1136 620 v4 Is+ 8:28PM 0:00.04 /usr/libexec/getty root465 0.0 1.0 1136 620 v5 Is+ 8:28PM 0:00.04 /usr/libexec/getty root466 0.0 1.0 1136 620 v6 Is+ 8:28PM 0:00.04 /usr/libexec/getty root467 0.0 1.0 1136 620 v7 Is+ 8:28PM 0:00.04 /usr/libexec/getty root773 0.0 1.9 1468 1148 v0 S10:55PM 0:00.28 -csh (csh) root 0 0.0 0.0 0 12 ?? DLs 31Dec69 0:00.07 (swapper) root864 0.0 0.8 628 484 v0 R+ 11:40PM 0:00.01 ps aux
[no subject]
the ps aux command show some proceses started on dec 31 1969. this is -current from Nov 5th. attached is the log. If i compile daemon_saver in the kernel, somehow it get invoked even while the machine is booting. I have to manually press a key to see the boot messages. dheeraj To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [PATCH] note the __sF change in src/UPDATING
M. Warner Losh wrote: -current already does this. The problem is that we're trying to shoot the bad access in the head, and that is what is screwing people. So the problem isn't that we're trying to export private data to the world. Quite the contrary, we're trying to eliminate it and having growing pains. No, it's actually an attempt to change which private data is exported; the new code exports three private values, instead of an array of private values. Data interfaces are evil (proc size mismatch). Probably FILE * should be void *. 8-(. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
