Cdrecord broken with 5.2Beta and ATAPICAM
Hi all, Since the ATAnG commit I'm no longer able to burn any Cd's. 5.X, 5.1R did work. scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 pregap1: -1 Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM Using libscg version 'schily-0.7' Driveropts: 'burnfree' atapi: 0 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'QSI ' Identifikation : 'DVD/CDRW SBW-161' Revision : 'SX14' Device seems to be: Generic mmc2 DVD-ROM. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1605632 = 1568 KB FIFO size : 4194304 = 4096 KB Track 01: data 450 MB padsize: 30 KB Total size: 517 MB (51:16.50) = 230738 sectors Lout start: 517 MB (51:18/38) = 230738 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -11607 (97:27/18) ATIP start of lead out: 359849 (79:59/74) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 18 Manufacturer: Plasmon Data systems Ltd. Blocks total: 359849 Blocks current: 359849 Blocks remaining: 129111 Starting to write CD/DVD at speed 16 in real SAO mode for single session. Waiting for reader process to fill input buffer ... input buffer ready. cdrecord: WARNING: Drive returns wrong startsec (0) using -150 BURN-Free is ON. Performing OPC... Sending CUE sheet... Writing pregap for track 1 at -150 cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error write track pad data: error after 0 bytes CDB: 2A 00 FF FF FF 6A 00 00 1F 00 BFree: 1568 K BSize: 1568 K status: 0x2 (CHECK CONDITION) Starting new track at sector: 0 Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 1.675s timeout 200s cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.192s timeout 200s Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR or panic with ips driver (was Re: cvs commit:src/sys/dev/ips ips.c ips.h ips_commands.c)
Hi, After seeing this commit message, I've upgraded -CURRENT installed on NetFinity 6000R(with ServeRAID 4H) to catch up with the recent changes. However, LOR or panic still persists. You can panic your -CURRENT machine by creating a log of files in a directory. You can do it with a simple shell script like this: $ mkdir foo; i=0; while :; do echo $i foo/$i; i=$(($i+1)); done Just tested this bug on our ServeRaid 5i, it doesn't happen here. The machines just runs out of inodes. Anyone else with a ServeRAID 4H can try this ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: yppasswd fails on 5.1 box
hi, Yppasswd fails on my 5.1 box (has always worked on 4.5 to 5.0) with yppasswd: pam_chauthtok(): error in service module 5.1 Release or 5.1 CURRENT ? I've fixed several errors since 5.1R so it should work now in CURRENT. There's also a syslog message: Nov 4 22:54:54 *** yppasswd: in pam_sm_chauthtok(): yppasswd_local(): failed to connect to rpc.yppasswdd: ***: RPC: Program not registered Yet rpcinfo -p shows: 191 udp821 yppasswdd 191 tcp 1010 yppasswdd You are missing the following entry (just use rpcinfo without -p) 19 1 local /var/run/ypasswdd.sock Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: yppasswd fails on 5.1 box
Hi, I'm on 5.1-RELEASE I still need to upgrade, I have the sources via cvsup, but it will be my first build/installworld ... 5.1R is broken. You should upgrade :) Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
re: StarOffice 6 under CURRENT
Hi, FreeBSD bart 5.1-CURRENT FreeBSD 5.1-CURRENT #2: Sat Sep 20 20:34:05 PDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BART i386 I am having problems running staroffice under current. My question is is anyone else eperiencing this problem? The initial ports install runs fine but when running setup.bin(via executible staroffice6) it fails: pid 657 (setup.bin), uid 1002: exited on signal 6 Any help is greatly appreciated! Sounds like linprocfs is not running anymore ? linprocfs on /usr/compat/linux/proc (linprocfs, loc Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: route problems in 5.1-RELEASE
Hi, Normally, if I want to swap from wi0 to fxp0, all I have to do is: killall dhclient ifconfig wi0 down ifconfig fxp0 up dhclient fxp0 Why don't you just update to 5.X, run mergemaster- Then just remove the wi0 card and plug in a ethernet cable to the internal NIC ? This works wonderful here. No manual interaction needed anymore. Dhclient had a bunch of fixes for this problem, the rc system had it too. All of them are fixed. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient bug
Hi, with a missing dhcpserver or non-existent interface, this works. however, it does not when i unplug the ethernet cable. in that case, i get back true after the timeout, not 2. can someone verify this? is it a bug that must be fixed from the freebsd side or should a bug report to the isc-dhcp people? This is a FreeBSD bug, I'll fix it later today. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make buildworld errors (amd/doc)
Hi, make buildworld fails (cvsup from about 2 hours ago), it looks like the amd import caused this: /usr/src/usr.sbin/amd/doc/../../../contrib/amd/doc/am-utils.texi:45: @include version.texi: No such file or directory Fixed 30 minutes ago. Please re-cvsup. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: inetd unknown rpc/udp or rpc/tcp
Hi, Sep 2 23:09:18 iso inetd[703]: unknown rpc/udp or rpc/tcp Looks like /etc/netconfig is missing or rpcbind is not running at all. Inetd has rpc support and I guess when rpc is turned all of you'll get this message. But it's harmless. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Davicom DM910X, DM90XX card owners, please help testing
Hi all, I fixed yesterday the if_dc driver to make this card working again. I'm happy if you could do some testing there if the card does now work for you. I just fixed the DM9102A case, so I'm very very interested if it is also needed for the other cards. I need someone who owns a DM9102 or a DM9100 or DM90XX card. If you have such a card, can ypu please test if you can ping ? The problem has been the 'zero copy' network code commit by luigi in late 2001, where the alignment of the TX mbufs has been removed generally and (accidently) did not got restored for this card. Because if this, FreeBSD R4.5 - R4.8 had broken Davicom cards. It will be fixed in FreeBSD 4.9R. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just fine. with the freebsd dhclient, or a unmodified V3.0.1rc9 one ? For some reason Cisco dhcp server doesn't like FreeBSD anymore if connect comes from an0 driver :-) Can you test the V3.0.1rc9 one at home too ? Tomppa Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, | I was ready to say that it's not working but then ipv6 came up | automatically. I didn't look this before but now it looks that | dhclient don't get address but if manually set v4 address it works. | I've to check how it works with older kernel because until now I only | checked that I didn't get address from dhcp. There have been some changes to dhclient (link detection) that might have some interaction side effects. Not blaming dhclient but that is something to be aware of. How old is your CURRENT installation ? Can you run dhclient in verbose mode and in foreground (-d -v) and maybe compile if with -DDEBUG ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 212.226.167.254 bound to 212.226.167.247 -- renewal in 228123 seconds. So the first time it works ? You get an IP here ... an0: Found Link on interface DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. Why don't you get an IP here ? Does the server see your requests ? If not, the an0 driver is broken for your card. IMHO it's not dhclient fault here. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, Did you look Cisco's dump where Windows DHCPDISCOVER appears as 0100.4096.3856.e7 but FreeBSD is 0040.9638.56e7? That's strange indeed. But 0040.9638.56e7 looks correct to me. Can you tell me why the server does not send anything back ? Why does it happen to be 01 before the mac if you use windows ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with dhclient wi0 on resume.
Hi, Unfortunately this system hasn't worked for me. As it is I have a script Have you tested it and included theses commands in rc.resume and rc.suspend ? which lives in rc.d which starts up dhclient with the appropriate wireless options. Unfortunately after each suspend and resume this is what I have to use. If anyone comes up with a solution to this it'd be much appreciated. Which script do you use ? The dhclient script in /etc/rc.d ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
Hi, Here is the output of dhclient -v -d xl0 I I checked. Dhclient still initializes the interface and brings it up itself. So there is only one possibility: You don't have a working link. Maybe it helps if you add a interface define in /etc/dhclient.conf wit the possible media. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
Argl, of course the patch was wrong. Ok, this should work
now ...
--- contrib/isc-dhcp/client/dhclient.c.orig Thu Aug 7 16:58:46 2003
+++ contrib/isc-dhcp/client/dhclient.c Sat Aug 9 21:47:14 2003
@@ -3288,19 +3288,24 @@
return (HAVELINK);
}
}
+ /*
+* If dhclient.conf contains media settings, we cannot
+* abort if the interface is not set to active mode.
+*/
+ if (ip - havemedia ip - client - state != S_BOUND)
+ return (HAVELINK);
+ } else {
+ /*
+* IFM_AVALID is not set. We cannot check
+* the link state. Assume HAVELINK.
+*/
+ return (HAVELINK);
}
-
- /*
-* If dhclient.conf contains media settings, we cannot
-* abort if the interface is not set to active mode.
-*/
- if (ip - havemedia ip - client - state != S_BOUND)
- return (HAVELINK);
-
/*
* We really have no link.
*/
return (NOLINK);
+
#else /* ifdef __FreeBSD__ */
/*
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Several panics during unload of netgraph related klds
Hi all, I've just noticed that I cannot unload 81 0xc4226000 4000 if_tap.ko (panics) 93 0xc435 12000netgraph.ko (unloads, but is still there) 101 0xc4222000 4000 ng_ether.ko (reports busy) 111 0xc41a7000 5000 ng_bridge.ko (works) 121 0xc421e000 4000 ng_socket.ko (reports busy) A bogus message is also available: kernel: kldunload: attempt to unload file that was loaded by the kernel If a network module is loaded before these module, the system panics if one tries to unload the kernel module. Unfortunatly I cannot provide panic dumps, something in savecore seems broken since yesterday. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
Hi, Adapted to the newst source-version, the patch will look like this. After I got home, I'll test it. Martin Index: client/dhclient.c === RCS file: /home/ncvs/src/contrib/isc-dhcp/client/dhclient.c,v retrieving revision 1.30 diff -u -r1.30 dhclient.c --- client/dhclient.c 7 Aug 2003 14:58:46 - 1.30 +++ client/dhclient.c 9 Aug 2003 16:20:22 - @@ -3288,19 +3288,21 @@ return (HAVELINK); } } - } - /* -* If dhclient.conf contains media settings, we cannot -* abort if the interface is not set to active mode. -*/ - if (ip - havemedia ip - client - state != S_BOUND) - return (HAVELINK); + /* +* If dhclient.conf contains media settings, we cannot +* abort if the interface is not set to active mode. +*/ + if (ip - havemedia ip - client - state != S_BOUND) + return (HAVELINK); - /* -* We really have no link. -*/ - return (NOLINK); + /* +* We really have no link. +*/ + return (NOLINK); + } + + return (HAVELINK); #else /* ifdef __FreeBSD__ */ /* @@ -3310,6 +3312,7 @@ return (HAVELINK); #endif /* Other OSs */ } + #ifdef __FreeBSD__ void Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with dhclient wi0 on resume.
Hi,
Can you please try the attached patch ? There was one mayor
typo ...
- for _if in _active_list ; do
+ for _if in ${_active_list} ; do
I also found two other bugs. And there is still one
if we get 2 pccards at the same time configured with dhcp.
But I think this setting is used very rarly.
Martin
--- etc/pccard_etherTue Aug 12 14:14:13 2003
+++ etc/pccard_etherTue Aug 12 14:43:31 2003
@@ -8,48 +8,55 @@
#
stop_dhcp() {
+ # If dhclient is already running, record
+ # it's interfaces.
+ if [ -x /usr/bin/grep ]; then
+ eval _active_list=\`/bin/ps -axwww | \
+ /usr/bin/grep dhclient | \
+ /usr/bin/grep -v grep | \
+ /usr/bin/sed -e 's|^.*dhclient||' | \
+ /usr/bin/awk '{for (i=1;i=NF;i++) \
+ { if ($i~/[a-zA-Z].[0-9]$/) \
+ { printf( %s,$i) } }}'` \
+ \
+ fi
+
+ _aprefix=
+ for _if in ${_active_list} ; do
+ _test_if=`ifconfig ${_if} 21`
+ case $_test_if in
+ ifconfig: interface $_if does not exist)
+ ;;
+ ${interface})
+ # Don't record the same device twice.
+ ;;
+ *)
+ _dhcplist=${_dhcplist}${_aprefix}${_if}
+ [ -z $_aprefix ] _aprefix=' '
+ ;;
+ esac
+ done
if [ -s /var/run/dhclient.${interface}.pid ]; then
pidfile=/var/run/dhclient.${interface}.pid
elif [ -s /var/run/dhcpc.${interface}.pid ]; then
pidfile=/var/run/dhcpc.${interface}.pid
elif [ -s /var/run/dhclient.pid ]; then
- # If dhclient is already running, record
- # it's interfaces.
- if [ -x /usr/bin/grep ]; then
- eval _active_list=\`/bin/ps -axwww | \
- /usr/bin/grep dhclient | \
- /usr/bin/grep -v grep | \
- /usr/bin/sed -e 's|^.*dhclient||' | \
- /usr/bin/awk '{for (i=1;i=NF;i++) \
- { if ($i~/[a-zA-Z].[0-9]$/) \
- { printf( %s,$i) } }}'` \
- \
- fi
-
- _aprefix=
- for _if in _active_list ; do
- _test_if=`ifconfig ${_if} 21`
- case $_test_if in
- ifconfig: interface $_if does not exist)
- ;;
- *)
- _dhcplist=${_dhcplist}${_aprefix}${_if}
- [ -z $_aprefix ] _aprefix=' '
- ;;
- esac
- done
-
pidfile=/var/run/dhclient.pid
else
return
fi
kill `cat ${pidfile}`
rm -f ${pidfile}
- sh `/etc/rc.d/dhclient start`
+ case ${startstop} in
+ [Ss][Tt][Oo][Pp])
+ sh `/etc/rc.d/dhclient start`
+ ;;
+ *)
+ ;;
+ esac
}
start_dhcp() {
- stop_dhcp
case ${pccard_ether_delay} in
[Nn][Oo])
;;
@@ -57,6 +64,7 @@
sleep ${pccard_ether_delay}
;;
esac
+ stop_dhcp
[ -n $dhcp_program ] dhclient_program=$dhcp_program
[ -n $dhcp_flags ] dhclient_flags=$dhcp_flags
if [ -x ${dhclient_program} ]; then--- etc/pccard_etherTue Aug 12 14:14:13 2003
+++ etc/pccard_etherTue Aug 12 14:43:31 2003
@@ -8,48 +8,55 @@
#
stop_dhcp() {
+ # If dhclient is already running, record
+ # it's interfaces.
+ if [ -x /usr/bin/grep ]; then
+ eval _active_list=\`/bin/ps -axwww | \
+ /usr/bin/grep dhclient | \
+ /usr/bin/grep -v grep | \
+ /usr/bin/sed -e 's|^.*dhclient||' | \
+ /usr/bin/awk '{for (i=1;i=NF;i++) \
+ { if ($i~/[a-zA-Z].[0-9]$/) \
+ { printf( %s,$i) } }}'` \
+ \
+ fi
+
+ _aprefix=
+ for _if in ${_active_list} ; do
+ _test_if=`ifconfig ${_if} 21`
+ case $_test_if in
+ ifconfig: interface $_if does not exist)
+ ;;
+ ${interface})
+ # Don't record the same device twice.
+ ;;
+ *)
+ _dhcplist=${_dhcplist}${_aprefix}${_if}
+ [ -z $_aprefix ] _aprefix=' '
+ ;;
+ esac
+ done
if [ -s /var/run/dhclient.${interface}.pid ]; then
Re: dhclient problem with xl0
Hi, xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface Erm. What does 'ifconfig xl0' show you ? For dhclient it looks like you have no link. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
Have you done a ifconfig xl0 0.0.0.0 up before ? xl0: No Link on interface I think I'll have to support this, if the interface is not initialized. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with dhclient wi0 on resume.
Hi, I've got a toshiba portege 4000 with inbuilt wi0 wireless card. On resume dhclient kicks off straight away which then breaks as the card You mean dhclient gets killed ? One way could be to kill dhclient when you sleep. Afterwords, devd should restart it, right ? Unfortunatly I cannot test this myself as resume on my lapton is horribly broken. isn't loaded as yet. Is there anyway to specify a sleep value for dhclient on resume from suspend ? I'm running current from today, I should note I'm also seeing a bunch of wi0 bad_alloc messages as well with this card. It gets quite annoying to have to restart dhclient everytime I resume. There is one: /etc/dhclient.conf # # # omapi port 7911; /etc/sleep_dhclient #!/bin/sh omshell /dev/null EOF connect new control open set state = 3 update close /etc/wakeup_dhclient #!/bin/sh omshell /dev/null EOF connect new control open set state = 4 update close Please tell me if you have success with these. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
Hi, Except that you've added code to dhclient that makes poor assumptions about the ifmedia status word. Its optional; for hardware that you can detect media status it can be used to display the status. For other hardware, we shouldn't have to lie about media status; if the hardware doesn't support reporting media status then we shouldn't do anything with the status word. Isn't there a way to see that the card doesn't support reporting media status ? If the card does report this, I could add code to dhclient and all would be fine. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
Hi, dhclient is still relying on behavior from the kernel that isn't guaranteed. I know. But I'd consider that as a kernel bug, not dhclient fault. Would it help the set the card into promisc. mode anyway, even if we don't have link ? I posted a patch to if_xl.c that should correct the link status for cards with builtin non-MII PHYs. Ok. Thank you very much ! Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Make pccard.ether working if there is already a dhclient running
I have now fixed the remaining issues.
Comments are welcome.
Martin
--
Simplify the pccard dhcp handling a lot. There are now
many configurations which have a NIC on board, and
pccard slots. If a dhclient is running on the internal
nic, the user was forced to kill a running dhclient
manually.
If a pccard is included at startup time, /etc/rc.d/dhclient
start does include it into the startup list for dhcp devices.
That means you can you then dhcp on the internal and the
pccard device.
If the card is plugged in later, a running dhclient (working
for the internal interface only) is killed, and restarted,
but with the interface name of the new pccard.
Here is my example config which works really fine now:
ifconfig_sis0=DHCP
pccard_ifconfig=DHCP
removable_interfaces=an0 wi0
--- etc/pccard_etherThu Jun 26 04:44:08 2003
+++ etc/pccard_etherSat Aug 9 14:31:58 2003
@@ -12,11 +12,32 @@
pidfile=/var/run/dhclient.${interface}.pid
elif [ -s /var/run/dhcpc.${interface}.pid ]; then
pidfile=/var/run/dhcpc.${interface}.pid
+ elif [ -s /var/run/dhclient.pid ]; then
+ eval _active_list=\`/bin/ps -x | \
+ /usr/bin/grep dhclient | \
+ /usr/bin/grep -v grep | \
+ /usr/bin/sed -e 's|^.*dhclient||'`\
+
+ _aprefix=
+ for _if in _active_list ; do
+ _test_if=`ifconfig ${_if} 21`
+ case $_test_if in
+ ifconfig: interface $_if does not exist)
+ ;;
+ *)
+ _dhcplist=${_dhcplist}${_aprefix}${_if}
+ [ -z $_aprefix ] _aprefix=' '
+ ;;
+ esac
+ done
+
+ pidfile=/var/run/dhclient.pid
else
return
fi
kill `cat ${pidfile}`
rm -f ${pidfile}
+ sh `/etc/rc.d/dhclient start`
}
start_dhcp() {
@@ -35,7 +56,7 @@
pidfile=/var/run/dhclient.${interface}.pid
dhclient_flags=${dhclient_flags} -pf ${pidfile}
fi
- ${dhclient_program} ${dhclient_flags} ${interface}
+ ${dhclient_program} ${dhclient_flags} $_dhcplist ${interface}
else
echo ${dhclient_program}: DHCP client software not available
fi
--- etc/network.subrSat Aug 9 11:48:47 2003
+++ etc/network.subrSat Aug 9 14:10:59 2003
@@ -299,6 +299,24 @@
esac
done
+ case ${pccard_ifconfig} in
+ [Dd][Hh][Cc][Pp])
+ for _if in ${removable_interfaces} ; do
+ _test_if=`ifconfig ${_if} 21`
+ case $_test_if in
+ ifconfig: interface $_if does not exist)
+ ;;
+ *)
+ _dhcplist=${_dhcplist}${_aprefix}${_if}
+ [ -z $_aprefix ] _aprefix=' '
+ ;;
+ esac
+ done
+ ;;
+ *)
+ ;;
+ esac
+
case $type in
nodhcp)
echo $_nodhcplist
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dhclient fix for systems with media settings
Hi, Is this going to cure the cases where using DHCP results in my network link going dead about ~30 minutes after getting a lease? At that point it starts spitting out timeout errors and stuff, and i have to unplug/replug the card and re-start dhclient to get connectivity again.. Unless the lease time was ~30 minutes and you've changed networks, I doubt it. This sounds like a if_wi driver problem. Warner should be able to tell you more. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Dhclient fix for systems with media settings
Hi all,
If you used wi(4) or en(4) wavelan cards and you had problems with dhclient,
you should try this patch, which treats interfaces with media settings
differently.
http://people.freebsd.org/~mbr/patches/dhclient-interfacepolling-fixup.diff
I'll produce a more clean patch this evening, and also adapt the patch to
the ISC style, so it can be submitted again.
--- src/contrib/isc-dhcp/includes/dhcpd.h.orig Mon Aug 4 23:57:06 2003
+++ src/contrib/isc-dhcp/includes/dhcpd.h Mon Aug 4 23:57:37 2003
@@ -782,6 +782,7 @@
char name [IFNAMSIZ]; /* Its name... */
int linkstatus; /* Link status */
int ieee802;/* True if media is ieee802 */
+ int mediaflag; /* True if dhclient.conf has media settings */
int index; /* Its index. */
int rfdesc; /* Its read file descriptor. */
int wfdesc; /* Its write file descriptor, if
--- src/contrib/isc-dhcp/client/dhclient.c.orig Tue Aug 5 00:42:37 2003
+++ src/contrib/isc-dhcp/client/dhclient.c Tue Aug 5 10:01:17 2003
@@ -257,7 +257,9 @@
log_fatal (%s: interface name too long (max %ld),
argv [i], (long)strlen (argv [i]));
strlcpy (tmp - name, argv [i], IFNAMSIZ);
- set_ieee802(tmp);
+#ifdef __FreeBSD__
+ set_ieee80211(tmp);
+#endif
tmp-linkstatus = interface_active(tmp);
if (interfaces) {
interface_reference (tmp - next,
@@ -412,7 +414,16 @@
INTERFACE_AUTOMATIC)) !=
INTERFACE_REQUESTED))
continue;
- set_ieee802(ip);
+#ifdef __FreeBSD__
+ set_ieee80211(ip);
+#endif
+#ifdef ENABLE_POLLING_MODE
+ if (ip - client - config - media != NULL)
+ ip-mediaflag = 1;
+ else
+ ip-mediaflag = 0;
+#endif /* ifdef ENABLE_POLLING_MODE */
+
script_init (ip - client,
PREINIT, (struct string_list *)0);
if (ip - client - alias)
@@ -1385,9 +1396,6 @@
int interval;
int increase = 1;
- if (interface_active(client - interface) == 0)
- return;
-
/* Figure out how long it's been since we started transmitting. */
interval = cur_time - client - first_sending;
@@ -1427,6 +1435,9 @@
}
}
+ if (interface_active(client - interface) == 0)
+ return;
+
/* If we're supposed to increase the interval, do so. If it's
currently zero (i.e., we haven't sent any packets yet), set
it to one; otherwise, add to it a random number between
@@ -3215,14 +3226,29 @@
if (ifmr.ifm_status IFM_AVALID) {
if (ip-ieee802) {
if ((IFM_TYPE(ifmr.ifm_active) == IFM_IEEE80211)
-(ifmr.ifm_status IFM_ACTIVE))
+(ifmr.ifm_status IFM_ACTIVE)) {
+ if (ip-mediaflag
+ ip - client - state != S_BOUND)
+ return (2);
return (1);
+ }
} else {
- if (ifmr.ifm_status IFM_ACTIVE)
+ if (ifmr.ifm_status IFM_ACTIVE) {
+ if (ip-mediaflag
+ ip - client - state != S_BOUND)
+ return (2);
return (1);
+ }
}
}
+ /*
+* If dhclient.conf contains media settings, we cannot
+* abort if the interface is not set to active mode.
+*/
+ if (ip-mediaflag ip - client - state != S_BOUND)
+ return (1);
+
return (0);
#else /* ifdef __FreeBSD__ */
@@ -3231,7 +3257,7 @@
}
#ifdef __FreeBSD__
-set_ieee802 (struct interface_info *ip) {
+set_ieee80211 (struct interface_info *ip) {
struct ieee80211req ireq;
u_int8_tdata[32];
@@ -3267,12 +3293,20 @@
#endif /* __FreeBSD__ */
#ifdef ENABLE_POLLING_MODE
+/* Go to background after some time */
+void state_background (cpp)
+ void *cpp;
+{
+ go_daemon ();
+}
+
/* Check the state of the NICs if we have link */
void state_link (cpp)
void *cpp;
{
struct interface_info *ip;
struct client_state *client;
+ int result;
#ifdef DEBUG
printf(Polling interface status\n);
@@ -3281,7 +3315,11 @@
if (ip-linkstatus == 0 || doinitcheck == 0) {
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, I have the following dhclient.conf file that USED TO WORK to find the right SSID depending on where I am. It now doesn't. Yes, there have been some changes. The most important was the interface polling addition, but that should not make any difference here. Can you start dhclient with -d -v and see what it's doing ? And can you try the same with a old dhclient and see if the behaviour is different ? It could also help to compile dhclient with -DDEBUG and see if you get more information. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, polling addition, but that should not make any difference here. Read the code. dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. interface_active() doesn't bail out. It returns 1, which means ok, and all should be done like bevor. It only returns 0, if if (ifmr.ifm_status IFM_AVALID) is not true. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
hi, Listening on BPF/wi0/00:06:25:18:1a:37 Sending on BPF/wi0/00:06:25:18:1a:37 Sending on Socket/fallback Trying medium wepmode off ssid 'rednet' wepkey 1:- wepkey 2:- wepkey 3:- wepkey 4:- 1 DHCPDISCOVER on wi0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 207.136.3.254 DHCPREQUEST on wi0 to 255.255.255.255 port 67 DHCPACK from 207.136.3.254 bound to 207.136.3.72 -- renewal in 7726 seconds. ^C Dhclient is definitly NOT the problem here. As mentioned in another thread, there are some problems with the wi driver. Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=161994+0+current/freebsd-current Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, Please look if you can get a 2-3 month old dhclient and I'm sure you'll see the same behaviour there. Negative. It was working with the WI driver from 5.0 through 5.1-CURRENT until my make world last nite/this am. oh, and 4.6-4.8 as well. Ok, You told me that it is working the first time you try, right ? What exactly does not work then ? Renewing the lease, or just changeing the network ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, How could dhclient see then that you were in a new network ? Do you mean which dhclient was running changing networks ? Or kill dhclient and restart it ? reboot. I.E. I shutdown between home and office and vice versa. SOMETHING seriously changed here. Ahh ! I see now the change. The problem is that you aren't associated at the beginning, because the first wep-key is wrong. Before every key was tried and one did match. I do now know where the problem is. I'll have a fix ASAP. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi, dhclient.c:send_discover() bails out if interface_active() is false BEFORE iterating all the possible media settings. Ok, problem understood now. I'm working on a fix. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient/dhclient.conf change in -CURRENT?
Hi Larry, This patch should fix the issues. It is not perfect, because polling here is a bit complicated. Maybe it does the right thing, but I think dhclient should at least check if one of the conditions is suddenly right (we are associated, or we really have link). So this needs definitly some work, but it should fix your case. I'll fix the remaining issues tomorrow. Martin --- src/contrib/isc-dhcp/includes/dhcpd.h.orig Mon Aug 4 23:57:06 2003 +++ src/contrib/isc-dhcp/includes/dhcpd.h Mon Aug 4 23:57:37 2003 @@ -782,6 +782,7 @@ char name [IFNAMSIZ]; /* Its name... */ int linkstatus; /* Link status */ int ieee802;/* True if media is ieee802 */ + int mediaflag; /* True if dhclient.conf has media settings */ int index; /* Its index. */ int rfdesc; /* Its read file descriptor. */ int wfdesc; /* Its write file descriptor, if --- src/contrib/isc-dhcp/client/dhclient.c.orig Mon Jul 28 15:25:04 2003 +++ src/contrib/isc-dhcp/client/dhclient.c Mon Aug 4 23:56:04 2003 @@ -413,6 +413,11 @@ INTERFACE_REQUESTED)) continue; set_ieee802(ip); + if (ip - client - config - media != NULL) + ip-mediaflag = 1; + else + ip-mediaflag = 0; + script_init (ip - client, PREINIT, (struct string_list *)0); if (ip - client - alias) @@ -1385,9 +1390,6 @@ int interval; int increase = 1; - if (interface_active(client - interface) == 0) - return; - /* Figure out how long it's been since we started transmitting. */ interval = cur_time - client - first_sending; @@ -1427,6 +1429,9 @@ } } + if (interface_active(client - interface) == 0) + return; + /* If we're supposed to increase the interval, do so. If it's currently zero (i.e., we haven't sent any packets yet), set it to one; otherwise, add to it a random number between @@ -3222,6 +3227,13 @@ return (1); } } + + /* +* If dhclient.conf contains media settings, we cannot +* abort if the interface is not set to active mode. +*/ + if (ip-mediaflag) + return (1); return (0); #else /* ifdef __FreeBSD__ */ Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: STEP 2, fixing dhclient behaviour with multiple interfaces
Hi, Odd: %%% # cat /etc/sleep_dhclient #!/bin/sh omshell /dev/null EOF connect new control open set state = 3 update close EOF # cat /etc/wakeup_dhclient #!/bin/sh omshell /dev/null EOF connect new control open set state = 4 update close EOF %%% This was working fine for me a few months ago. It still does - my fault. Looks like I forgot update :P and with state 2 I did that. But the interface adding does still not work. Maybe a different syntax than this ? connect new interface open set rl0 = up; update close Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
STEP 2, fixing dhclient behaviour with multiple interfaces
Hi all, I't is my goal to make dhclient really functional, so it can not only be used with one interface, but several. On a well known OS this works just fine. A first interface gets initialized and the GW gets set as usual. But if a second interface gets added, and the first one is still active and has a working lease, the GW will not be overwriten. If you remove now the first interface, the default GW changes to the one of the second interface. X = Link on IF + = Interface gets added or has new link - = Interface gets removed or lost link IF1 IF2 GW1 GW2 --- X X X + X - X X + X X Too this functionality to dhclient, there is only one way to do it. the ISC-dhclient package offers a OMAPI Command Shell omsshell(1). There you can add new interfaces or even remove existing ones. The work that needs to be done is: - Adding a unix domain socket to OMAPI, so root (or a choosen user) can access dhclient (or dhcpd) on the local machine without authentification. - Providing the omshell scripts for adding and removing interfaces, adding new default gateways on interface removal etc ... - Change our infrastructure (devd, rc.d/dhclient script) to use them. If there are other ideas, I'm open to them. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: STEP 2, fixing dhclient behaviour with multiple interfaces
Hi, can access dhclient (or dhcpd) on the local machine without authentification. You can get omshell working without auth over tcp/ip - I managed this today when playing. But a unix domain socket would be nicer because the dhclient server binds to INADDR_ANY by default. Cool. Do you have any pointers for me to try ? Little example etc ? At present, dhclient gets given a list of interfaces at startup-time. Would it be better to start it in no-interfaces mode (-n -w) and dynamically add /all/ interfaces using omshell? Exactly. Starting dhclient as a daemon without any interfaces. And just use omshell to add/remove interfaces. Another (loosely related) thing is that we should be able to use omshell to tell dhclient to pause before going into suspend. This is hinted at in the dhclient man page, but it would be good to get it into the standard infrastructure. Yup, that makes sence. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: STEP 2, fixing dhclient behaviour with multiple interfaces
Hi Folks, I had a closer loom at the OMAPI stuff in dhclient. Just to say, I'm very disappointed. The only objects that exist are: control and interface. The later is not inplemented at all. It pretends to work, but if you look at the source there are stubs only :P. control does only release leases and exit (state 2), I never managed to make dhclient sleep (state 3) and wake up (state 2). It seems that the whole implementation is only a proof of concept and not very functional at all, at least for the client side, dhcpd may be different. I'll think about how we can solve this differently. This really sucks ! Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: broken world
I should sleep more ! /usr/src/contrib/isc-dhcp/common/dispatch.c:47: error: syntax error before string constant /usr/src/contrib/isc-dhcp/common/dispatch.c:44:1: unterminated #ifndef *** Error code 1 Sorry for the troubles I've caused. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
World is still broken. Please fix.
Is anybody testing his changes before he commits them ? In file included from /usr/obj/usr/src/i386/usr/include/sys/types.h:45, from /usr/src/usr.bin/xlint/llib/llib-lposix:39: /usr/obj/usr/src/i386/usr/include/sys/cdefs.h:148:2: #error FreeBSD alloca support needed for this compiler *** Error code 1 Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP: rpc.yppasswdd working again
Small, but important message for NIS users. All users who had problems with NIS should rebuild their world. Long outstanding problems have been fixed and rpc.yppasswdd allows root again to change passwords on ypmaster without knowledge of the users password. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: rpc.yppasswdd working again
hi, All users who had problems with NIS should rebuild their world. Long outstanding problems have been fixed and rpc.yppasswdd allows root again to change passwords on ypmaster without knowledge of the users password. Does this not create a vulnerability? Example: Bad Guy sets up a personal workstation with himself as root and steals an IP address from the machine he just switched off. Now he can change passwords on the server at will. It is only possible on the ypmaster server. And if you are root you can edit the password files directly, can't you :-) ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: rpc.yppasswdd working again
he can change passwords on the server at will. From the rpc.yppasswdd manpage: The FreeBSD version of rpc.yppasswdd also allows the super-user on the NIS master server to perform more sophisticated updates on the NIS passwd maps. The super-user can modify any field in any user's master.passwd entry in any domain, and can do so without knowing the user's existing NIS password (when the server receives a request from the super-user, the password authentication check is bypassed). Furthermore, if the server is invoked with the -a flag, the super-user can even add new entries to the maps using ypchpass(1). Again, this only applies to the super-user on the NIS master server: none of these special functions can be performed over the network. The rpc.yppasswdd utility can only be run on a machine that is an NIS master server. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
libevent for FreeBSD ?
Hi, Has anybody seen this the recent NetBSD posting about libevent ? http://mail-index.netbsd.org/tech-userlevel/2003/06/08/.html What do you think about it ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
How to kill a 5.0R installation with 5.1R
Folks, This is the second time that I have this happen here. I had a 5.0R installed on a box. After upgrading, (make world make kernel) the box crashes instantly in the boot loader and reboots itself. If I try to load the kernel manually, I get: Disk error 0x4, (lba=0xfc2247f) There should be at least a warning somewhere in UPDATING. This definitly sucks like hell. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to kill a 5.0R installation with 5.1R
Hi, This has been one of my laptops. It had three partitions on it, the first one FreeBSD. How does it crash? I have lilo installed. When I choose freebsd, I get the normal freebsd loader: FreeBSD/i386 BOOT After that, I see very fast a message scrolling over the screen, it turns black again, and voila, the box has rebooted. I've killed the second box the same way. After restoring boot0/boot1 I found that my disklables were nuked. Enjoy. You mean without loader? From the boot blocks? If so, the support for this has been broken for a long time. Ask BDE for patches. :-) Yes from the boot blocks. Also, have you tried the official 5.1-RELEASE bits, like booting from the installation CD-ROM? No, I just upgraded with RELENG_5_0_0 from source. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to kill a 5.0R installation with 5.1R
Hi, Have you tried loader.old? I personally also keep a loader.work copy on my systems - just in case. Whooo. Yes, loader.old did the trick. Wow :-) Thanky you very much ! I'm just curious now why the new loader instantly panics. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to kill a 5.0R installation with 5.1R
Hi, over the screen, it turns black again, and voila, the box has rebooted. I've killed the second box the same way. After restoring boot0/boot1 I found that my disklables were nuked. Enjoy. Um, so what do you use? lilo or boot0? :-) Lilo. And the first box I killed with just a upgrade had only FreeBSD and boot0. So I don't think it's related to linux. This is unsupported, sorry. As you have seen, loading -boot-loader.old fixed the crash. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
OpenOffice-devel: repeatable coredump with sun autodoc in libstd++
Hi all, I'm still working to get OpenOffice1.1Beta2 ready, but am now stuck with a segfault. The compile currently aborts on many places where -frtti is used, so everybody is using -fno-rtti these days. But here I get serious trouble with autodoc ... For some strange reason it didn't happen with -frtti, it happens only with -fno-rtti. Segmentation fault (core dumped) dmake: Error code 139, while making '../../unxfbsd.pro/bin/OpenOffice.org1.1_Beta_2_SDK/docs/common/ref/module-ix.html' ---* RULES.MK *--- ERROR: Error 65280 occurred while making /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/odk/pack/gendocu fuchur# gdb /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/solver/644/unxfbsd.pro/bin/autodoc ./pack/gendocu/autodoc.core GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... Core was generated by `autodoc'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libkse.so.1...done. Loaded symbols for /usr/lib/libkse.so.1 Reading symbols from /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/solver/644/unxfbsd.pro/lib/libstlport_gcc.so...done. Loaded symbols for /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/solver/644/unxfbsd.pro/lib/libstlport_gcc.so Reading symbols from /usr/lib/libstdc++.so.4...done. Loaded symbols for /usr/lib/libstdc++.so.4 Reading symbols from /usr/lib/libm.so.2...done. Loaded symbols for /usr/lib/libm.so.2 Reading symbols from /usr/lib/libc.so.5...done. Loaded symbols for /usr/lib/libc.so.5 Reading symbols from /usr/libexec/ld-elf.so.1...done. Loaded symbols for /usr/libexec/ld-elf.so.1 #0 __dynamic_cast (src_ptr=0x826c9d0, src_type=0x815baa8, dst_type=0x815ba9c, src2dst=0) at /usr/src/contrib/libstdc++/libsupc++/tinfo.cc:696 696 whole_type-__do_dyncast (src2dst, __class_type_info::__contained_public, (gdb) bt #0 __dynamic_cast (src_ptr=0x826c9d0, src_type=0x815baa8, dst_type=0x815ba9c, src2dst=0) at /usr/src/contrib/libstdc++/libsupc++/tinfo.cc:696 #1 0x081399cd in csi::dsapi::SapiDocu_PE::SetCurSeeAlsoAtTagLinkText(ary::info::DocuToken) (this=0x81a6500, [EMAIL PROTECTED]) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/parser_i/idoc/docu_pe2.cxx:393 #2 0x081394e0 in csi::dsapi::SapiDocu_PE::Process_Word(csi::dsapi::Tok_Word const) (this=0x81a6500, [EMAIL PROTECTED]) at d_token.hxx:101 #3 0x0813b58a in csi::dsapi::Tok_Word::Trigger(csi::dsapi::TokenInterpreter) const (this=0x826c850, [EMAIL PROTECTED]) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/parser_i/idoc/tk_docw2.cxx:79 #4 0x08137e46 in csi::dsapi::SapiDocu_PE::ProcessToken(csi::dsapi::Token) (this=0x81a6500, [EMAIL PROTECTED]) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/parser_i/idoc/docu_pe2.cxx:122 #5 0x08120643 in csi::uidl::TokenDistributor::Documentation::Receive(csi::dsapi::Token) (this=0x81b3584, [EMAIL PROTECTED]) at template/dyn.hxx:218 #6 0x08136720 in csi::dsapi::Context_Docu::PassNewToken() (this=0x0) at template/dyn.hxx:237 #7 0x0811cf09 in TokenParse2::GetNextToken() (this=0x821ff90) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/parser_i/tokens/tkp2.cxx:90 #8 0x0811fba5 in csi::uidl::TokenDistributor::TradeToken() (this=0x81b3544) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/parser_i/idl/distrib.cxx:102 #9 0x081343bf in autodoc::FileParsePerformers::ParseFile(char const*) (this=0x81b3500, i_sFullPath=0x81c8000 ./../../unxfbsd.pro/bin/OpenOffice.org1.1_Beta_2_SDK/idl/com/sun/star/beans/PropertySetInfoChangeEvent.idl) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/parser_i/idl/unoidl.cxx:178 #10 0x08133e5c in autodoc::IdlParser::Run(autodoc::FileCollector_Ifc const) (this=0x81b8670, [EMAIL PROTECTED]) at template/dyn.hxx:218 #11 0x08063de5 in autodoc::command::run::Parser::Perform() (this=0xbfbfe3d0) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/exes/adc_uni/cmd_run.cxx:156 #12 0x08061a58 in autodoc::command::Parse::do_Run() const (this=0x81b0180) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/exes/adc_uni/adc_cmd_parse.cxx:267 #13 0x0805e7af in autodoc::CommandLine::Run() const (this=0xbfbfe430) at adc_cmd.hxx:135 #14 0x0805e44c in main (argc=13, argv=0xbfbfe490) at /usr/ports/editors/openoffice-devel-fixed/work/oo_644_src/autodoc/source/exes/adc_uni/main.cxx:83 #15 0x0805e335 in _start () (gdb) frame 0 #0 __dynamic_cast (src_ptr=0x826c9d0, src_type=0x815baa8, dst_type=0x815ba9c,
Re: OpenOffice-devel: repeatable coredump with sun autodoc inlibstd++
Hi, -frtti is required for dynamic_castT(expr) to work. so if it is broken, then you've got big problems. Lokks like you are definitly right: grep dynamic `find ./ -name *.c*` ./source/ary/cpp/c_class.cxx:ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* (o_rOut); ./source/ary/cpp/c_define.cxx:ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* (o_rOut); ./source/ary/cpp/c_enum.cxx:ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* (o_rOut); ./source/ary/cpp/c_enuval.cxx:ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* (o_rOut); ./source/ary/cpp/c_funct.cxx:ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* (o_rOut); ./source/ary/cpp/c_macro.cxx:ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* (o_rOut); ./source/ary/cpp/c_namesp.cxx: ary::cpp::Display * pD = dynamic_cast ary::cpp::Display* Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenOffice-devel: repeatable coredump with sun autodocinlibstd++
Hi, I have seen this type of error and core dump with a new C++ and old rtti header files. Make sure you are not mixing them, since these header files definitely have to match the compiler. This is a fresh current 5.1RC1 ... Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vm-related panic with 5.1RC1
Hi, This is exactly the panic I am seeing on my dual-processor box. My current suspicion is that it somehow relates to the same pcb_ext being freed twice. I do not need OpenOffice to trigger the bug, on SMP configuration it happens all the time. In the meantime the box did not panic anymore. Can you look and try if limiting maxmem makes anything different on the SMP box ? cat /boot/loader.conf hw.physmem=256M I think it's coincidence, but who knows ... Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
vm-related panic with 5.1RC1
Hi all, I just got this panic during compile of openoffice Fatal trap 12 while in kernel mode fault virtual address = 0x68 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0271f4d stack pointer = 0x10:0xe6e51ab0 frame pointer = 0x10:0xe6e51ae0 code segement = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32, gran 1 processor flags = interrupt enabled, resume, IOPL =1 current process = 22362 kernel: type 12 trap, code=0 Stopped at _mtx_lock_sleep+0x16d: movl 0x68(%ecx),%edx db trace _mtx_lock_sleep(c082f0b0,0,0,0,c0678415) at _mtx_lock_sleep+0x16d vm_map_delete(c082f000, d0d0d000, d0d11000, e6effda0, c78d5720) at vm_map_delete+0x383) vm_map_remove(c082f000, d0d0d000, d0d11000, e6e51b9c, c03b247f) at vm_map_remove+0x58) kmem_free(c082f000, d0d0d000, 3000, 0, 80) at kmem_free+0x32 cpu_thread_clean(c78d54c0, e6e51bb4,c78d54c0, c78d54c0, e6e51be4) at cpu_thread_clean+0x7f thread_free(c78d54c0, e6e51bd0, c0275839, c67a3000, c6abf030) at thread_free+0x14 thread_reap(c78d55f0) at thread_reap+0x16c thread_wait(c656b000, , 0, c03feb34,0) at thread_wait+0x55 wait1(c6569980, e6e51d10, 0, e6e51d40, c03b0dfa) at wait1+0x738 wait5(c6569980, e6e51d10, 10, c6569980, 4) at wait4+0x20 syscall(2f, 2f, 2f, bfbff074, 325) at syscall+0x2aa Xint0x80_syscall() at Xint0x80_syscall()+0x1d --- syscall (7, FreeBSD ELF32, wait4) eip = 0x807b28b, esp = 0xbfbfefbc, ebp = 0xbfbfefd8) Unfortunatly my partition was too small, so I could not get a dump. I've adjusted this now and the next time it panics I'll have one ready. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
vm-related panic with 5.1RC1
Hi all, I just got this panic during compile of openoffice Fatal trap 12 while in kernel mode fault virtual address = 0x68 fault code= supervisor read, page not present instruction pointer = 0x8:0xc0271f4d stack pointer = 0x10:0xe6e51ab0 frame pointer = 0x10:0xe6e51ae0 code segement = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32, gran 1 processor flags = interrupt enabled, resume, IOPL =1 current process = 22362 kernel: type 12 trap, code=0 Stopped at _mtx_lock_sleep+0x16d: movl 0x68(%ecx),%edx db trace _mtx_lock_sleep(c082f0b0,0,0,0,c0678415) at _mtx_lock_sleep+0x16d vm_map_delete(c082f000, d0d0d000, d0d11000, e6effda0, c78d5720) at vm_map_delete+0x383) vm_map_remove(c082f000, d0d0d000, d0d11000, e6e51b9c, c03b247f) at vm_map_remove+0x58) kmem_free(c082f000, d0d0d000, 3000, 0, 80) at kmem_free+0x32 cpu_thread_clean(c78d54c0, e6e51bb4,c78d54c0, c78d54c0, e6e51be4) at cpu_thread_clean+0x7f thread_free(c78d54c0, e6e51bd0, c0275839, c67a3000, c6abf030) at thread_free+0x14 thread_reap(c78d55f0) at thread_reap+0x16c thread_wait(c656b000, , 0, c03feb34,0) at thread_wait+0x55 wait1(c6569980, e6e51d10, 0, e6e51d40, c03b0dfa) at wait1+0x738 wait5(c6569980, e6e51d10, 10, c6569980, 4) at wait4+0x20 syscall(2f, 2f, 2f, bfbff074, 325) at syscall+0x2aa Xint0x80_syscall() at Xint0x80_syscall()+0x1d --- syscall (7, FreeBSD ELF32, wait4) eip = 0x807b28b, esp = 0xbfbfefbc, ebp = 0xbfbfefd8) Unfortunatly my partition was too small, so I could not get a dump. I've adjusted this now and the next time it panics I'll have one ready. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Apache2 in per-child mode (was Re: libthr and 1:1 threading)
Hi all, Just a note. Apache2 in per-child mode now works with freebsd, while it deadlocked in the old libc_r on STABLE and CURRENT. Thank you very much ! Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
C++ Exception handling with shared libs in current is broken again
Hi all,
I do know now why I have again problems with building openoffice.
It seems that exceptions over shared libraries are broken again in
CURRENT.
Alexander, do you have a idea why this got broken again ?
Attached is your test programm ...
Martin
STABLE:
[EMAIL PROTECTED]:~/cxxtest$ export LD_LIBRARY_PATH=.
[EMAIL PROTECTED]:~/cxxtest$ ./arf
calling foo
in baz
foo caught Bax thowing...
returned from foo
CURRENT:
[EMAIL PROTECTED]:~/cxxtest$ export LD_LIBRARY_PATH=.
[EMAIL PROTECTED]:~/cxxtest$ ./arf
abort trap
... The exception is not catched at all ...
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering sh file. Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# Makefile
# foo.cc
# main.cc
#
echo x - Makefile
sed 's/^X//' Makefile 'END-of-Makefile'
XCXX=g++
XLD=ld
XCXXFLAGS=-g -fpic -fexceptions
X
Xall: arf
X
Xarf: main.o foo.so
X ${CXX} -o arf main.o foo.so
X
X
Xfoo.so: foo.o
X ${LD} -Bshareable -o foo.so foo.o
X
Xclean:
X rm -f arf *.o *.so
END-of-Makefile
echo x - foo.cc
sed 's/^X//' foo.cc 'END-of-foo.cc'
X#include stdio.h
X
Xint Foo ();
X
Xint Baz ()
X{
Xchar *msg = Bax thowing...;
Xprintf (in baz\n);
Xthrow msg;
Xprintf (baz should not be here.\n);
X}
X
X
Xint Foo ()
X{
Xtry {
XBaz ();
X} catch (char *msg) {
Xprintf (foo caught %s\n, msg);
X}
X}
END-of-foo.cc
echo x - main.cc
sed 's/^X//' main.cc 'END-of-main.cc'
X#include stdio.h
X
Xint Foo ();
X
Xint
Xmain ()
X{
Xtry {
Xprintf (calling foo\n);
XFoo ();
Xprintf (returned from foo\n);
X} catch (char *msg) {
Xprintf (exception from foo: %s\n, msg);
X} catch (...) {
Xprintf (unknown exception\n);
X}
X}
END-of-main.cc
exit
Re: C++ Exception handling with shared libs in current is brokenagain
Hi all, [EMAIL PROTECTED]:~/cxxtest$ export LD_LIBRARY_PATH=. [EMAIL PROTECTED]:~/cxxtest$ ./arf abort trap rtld from 19.October has the same problem. I guess it must be gcc3.2 which is the problem. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ld -Bsharable broken in CURRENT ?
See testcase
STABLE:
[EMAIL PROTECTED]:~/cxxtest2$ export LD_LIBRARY_PATH=.
[EMAIL PROTECTED]:~/cxxtest2$ ./a.out
cought string: x == 1
bar: cought string: x == 1
[EMAIL PROTECTED]:~/cxxtest2$ ./b.out
cought string: x == 1
bar: cought string: x == 1
CURRENT:
[EMAIL PROTECTED]:~/cxxtest2$ ./a.out
cought string: x == 1
bar: cought string: x == 1
[EMAIL PROTECTED]:~/cxxtest2$ ./b.out
Abort trap (core dumped)
cxxtest2/Makefile
CXX=g++
LD=ld
CXXFLAGS=-fpic -fexceptions
all: a.out b.out
#
# Works
#
a.out: main.o foo.so bar.so
${CXX} -o a.out main.o foo.so bar.so
#
# Broken
#
b.out: main.o foo2.so bar2.so
${CXX} -o b.out main.o foo2.so bar2.so
#
# Works
#
bar.so: bar.o
${CXX} -shared -o bar.so bar.o
foo.so: foo.o
${CXX} -shared -o foo.so foo.o
#
# Broken
#
bar2.so: bar.o
${LD} -Bshareable -o bar2.so bar.o
foo2.so: foo.o
${LD} -Bshareable -o foo2.so foo.o
clean:
rm -f a.out *.o *.so
cxxtest2/bar.cc
/* compile with g++ -shared -fPIC -o bar.so bar.cc */
#include iostream
#include string
using namespace std;
using std::cerr;
extern void foo(int);
void bar(int x)
{
try {
foo(x);
} catch (string s) { cerr bar: cought string: s endl;
} catch (int i) { cerr bar: cought int: i endl;
} catch (...) { cerr bar: cought something endl;
}
}
cxxtest2/foo.cc
/* compile with g++ -shared -fPIC -o foo.so foo.cc */
#include string
using namespace std;
void foo(int x)
{
switch(x) {
case 1:
throw string(x == 1);
case 2:
throw int(2);
default:
throw float(3.1415);
}
}
cxxtest2/main.cc
/* compile with g++ main.cc ./foo.so ./bar.so */
#include string
#include iostream
using namespace std;
extern void foo(int);
extern void bar(int);
main(int argc, char *argv[])
{
try {
foo(argc);
} catch (string s) { cerr cought string: s endl;
} catch (int i) { cerr cought int: i endl;
} catch (...) { cerr cought something endl;
}
bar(argc);
return 0;
}
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ld -Bsharable broken in CURRENT ?
Hi all, See testcase [EMAIL PROTECTED]:~/cxxtest2$ ./a.out cought string: x == 1 bar: cought string: x == 1 [EMAIL PROTECTED]:~/cxxtest2$ ./b.out Abort trap (core dumped) Looks like gcc2.9.x works, but it doesn't need to do this of course. Using ld without using the crt objects with gcc3.x produces a working binary, but exceptions over shared libs are broken in this case. So everything works as expected. I'll have to look where the real problem is for the openoffice-devel port. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: C++ Exception handling with shared libs in current is brokenagain
Hi, the gcc side of things, this is the only supported way to make a C++ shared image with gcc3 on modern ELF platforms: Thank you even I have found that out myself too :) Using ld directly is a no-go for a gcc3.2 platform. Linking with the crt files fixes the problem. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Sis chipset
Hi, Is there a chance to get the built in 100MBit network adapter in the chipset working somehow? I thought I've fixed the support so it should work ? If not, do you have a pciconf -lv output for me ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Sis chipset
Hi, [EMAIL PROTECTED]:8:0: class=0x02 card=0x chip=0x905010b7 rev=0x00 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905-TX Fast Etherlink XL PCI 10/100' class= network subclass = ethernet [EMAIL PROTECTED]:9:0: class=0x02 card=0x chip=0x802910ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8029 NE2000 compatible Ethernet' class= network subclass = ethernet There is no sis900 ethernet on your mainboard. It looks like you have a NE2000 compatible card. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
gethostbyname_r and realpath_r (FreeBSD or Linux for your MySQLServer)
Hi all, Have you already read this page ? (FreeBSD or Linux for your MySQL Server?) http://jeremy.zawodny.com/blog/archives/000203.html Many of you know that we still do not have threadsafe versions of gethostbyname and realpath. There are some patches around since a while. Nobody did commit them. Is someone working on this ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
background fsck deadlocks with ufs2 and big disk
Hi all, I just wanted to tell that I can deadlock one of my current boxes with a ufs2 filesystem on a 120GB ATA disk. I can reproduce the problem. The background fsck process hangs some time at the same place always at the same place, sometimes the box freezes after some time. The same box works fine with ufs1. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI: working ACPI vs broken ACPI
Hi all, I see these differences here in acpidump: Working board: PM2_GPE0_BLK=0xe428-0xe42f Broken board: PM2_GPE0_BLK=0x428-0x42f PM2_GPE1_BLK=0x528-0x52f, GPE1_BASE=32 And the broken board shows errors like this: The errors like: Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block1 defined as GPE32 to GPE63 ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT Wild guess: Seem to result from this. If I'm looking at NetBSD's http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/acpi/acpi_ec.c they have a lot done since they took acpi from us. I'm sure it works for netbsd. Is anybody working on this ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB kernel module broken ...
Sorry guys, take USB out of the GENERIC kernel. It should also not be enabled I had a bad days yesterday. Sorry for this mail ... If you have your birthday and a box refuses to work completly, it can really be frustrating. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
USB kernel module broken ...
One can not unload the thing ... Please fix. Or please take USB out of the GENERIC kernel. It should also not be enabled And I cannot reboot the box if USB is compiled in. It hangs solid then. No break into DDB possible anymore. # kldunload /boot/kernel/usb.ko kldunload: can't unload file: Device not configured The usb.ko got loaded it the multiuser state. # Feb 14 16:05:02 ibm-01 reboot: rebooted by root Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 s Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Reboot(8) when fsck_ufs is running ?
Hi all, I don't know what the behaviour should be, but when I try to reboot a box which has fsck_ufs is running, it doesn't reboot and I have to powercycle it. Looks also like it just hangs. Do you experience the same at your side ? Shouln't we abort the fsck_ufs and reboot ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB kernel module broken ...
Hi all, The problem is still there. I guess the SMM does not respond message leads to the kldunload failure. ibm-01# kldload usb ohci0: OHCI (generic) USB controller mem 0xeddff000-0xeddf irq 10 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ibm-01# ibm-01# kldunload usb kldunload: can't unload file: Device not configured # Feb 14 16:05:02 ibm-01 reboot: rebooted by root Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 s This one was ACPI. With acpi loaded, every reboot(8) hangs. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Invalid realloc size of 0: Unable to install CURRENT on a IBMx-series 305 Server
I've got more news about this. Fatal error: invalid realloc size of 0! Press key to reboot. 5.0R is fine. The bug seems to have been introduzed after 5.0R. I cannot install any 5.X snap on this box. I tried 3 different dates including today. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI problems: ACPI-1287: *** Error: Method execution failedAE_AML_BUFFER_LIMIT
This IBM X-Series 305 show these ACPI problems. And rebooting the box with ACPI enabled hangs it (deadlock). Feb 13 17:41:05 ibm-01 kernel: acpi0: IBMM51SLon motherboard Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block1 defined as GPE32 to GPE63 Feb 13 17:41:05 ibm-01 kernel: acpi0: power button is handled as a fixed feature programming model. Feb 13 17:41:05 ibm-01 kernel: Timecounter ACPI-safe frequency 3579545 Hz Feb 13 17:41:05 ibm-01 kernel: unknown: I/O range not supported Feb 13 17:41:05 ibm-01 kernel: unknown: I/O range not supported Feb 13 17:41:05 ibm-01 kernel: acpi_timer0: 32-bit timer at 3.579545MHz port 0x40c-0x40f on acpi0 Feb 13 17:41:05 ibm-01 kernel: acpi_cpu0: CPU on acpi0 Feb 13 17:41:05 ibm-01 kernel: pcib0: ACPI Host-PCI bridge on acpi0 Feb 13 17:41:05 ibm-01 kernel: ACPI-1287: *** Error: Method execution failed, AE_AML_BUFFER_LIMIT Feb 13 17:41:05 ibm-01 last message repeated 19 times Any way to work around this ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Invalid realloc size of 0: Unable to install CURRENT on a IBM x-series305 Server
Hi all, I've tested 5.0R and CURRENT from today on this server and it crashes in sysinstall. Message is: Fatal error: invalid realloc size of 0! Press key to reboot. I can prepare the install fine, newfs works and the box begins to install packets. After a while the message appears. It happens on UFS1 and UFS2. The drive is a 120GB big ata ar softraid mirror. Any ideas ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sysinstall disk mess
Hi all, I have a ar0 mirror with 120GB diskspace. I don't know if this is a known problem yet, but I had done the following steps which lead to a failure situation: 1.) Created a partition 2.) Created some slices 3.) Started a installation, abouted it because no net-device was found. 4.) Restarted sysinstall 5.) Reinit of slices 6.) Install fails with cannot write to ar0 ... 7.) Writeing disklabel, or anything fails on the disk. Only reboot solves the problem. Is this a known problem ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Link problems with BCM5703X Gigabit Ethernet on IBM X-Series 305
Hi all, I experience strange problems with this Gigabit card. It attaches correctly, but there is no activity until I set one time the promiscous mode, after that it works. So I wonder why this happens. Is something wrong with the filter ? Maybe we just have to turn on/off promiscous mode in bge_init(), so the card works as it should. Funny thing is that the link led doesn't work either ;) I guess we have to turn on some strange bit ;) I'll read the specs. If someone has a idea, I'd be happy. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi, It works here for both cases. I've done intensive testing, and I just cannot reproduce this bug. The list here just looks normal as it should be: localhost:/ on /a/localhost (nfs, nodev, nosuid) 127.0.0.1:/ on /a/127.0.0.1 (nfs, nodev, nosuid) levais:/ on /a/levais (nfs, nodev, nosuid) levais:/usr on /a/levais/usr (nfs, nodev, nosuid) 192.168.0.66:/ on /a/192.168.0.66 (nfs, nodev, nosuid) 192.168.0.66:/usr on /a/192.168.0.66/usr (nfs, nodev, nosuid) Can you send me both - tcpdump / ethereal dump of the failing request - amd, mountd configs (amd.*, /etc/exports) - a description of the mounted filesystems - how it fails ? what is the error message ? - run mountd in debug mode and keep the output ? Thank you very much Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: tired of crashes
Hi, Looks like bad hw. Have you run memtestx86 on this machine about 2-3 hours ? I had the same effects on one machine ... Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: trouble with ogle performance after going to 5.0-R
Hi, hw.ata.atapi_dma=1 ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NFS over TCP doesn't umount
Hi, # umount /mnt Bad MNT RPC: RPC: Timed out This behaviour is the same since we support NFS over TCP. The problem is, that the state of the nfs_mount isn't stored. That means that umount cannot look at the mountflags and decide what protocol it likes to use. Of course we can change this, but have to kill one existing mountflag because they are all used currently. I propose to remove MNT_EXKERB, since all the kerberos nfs stuff has been removed. Have a look at mount.h yourself. If this is generally ok'd, I'll make a patch and commit it. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI and suspend problems ...
Hi, I've got ACPI problems. First I've got a little note: acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND Wouldn't it be a lot more userfriendly to display: acpi0: Sleep mode type 1 not supported, available modes are: 0 3 4 5 or a similar error. Is such a patch trivial to do ? If so, I'll do it. Second, my display doesn't get waked up again. I just get a black screen. I read somewhere about setting: hw.syscons.sc_no_suspend_vtswitch=1 but it doesn't work. The screen stays black. And if I start X, I crash instantly. Then, the soundcard has no wakeup code: pcm0@pci0:2:7: class=0x040100 card=0x200017c0 chip=0x70121039 rev=0xa0 hdr=0x00 vendor = 'Silicon Integrated Systems (SiS)' device = 'SiS7012 PCI Audio Accelerator' class= multimedia subclass = audio Jan 28 16:28:13 kernel: pcm0: ac97 codec failed to reset extended mode (1, got 0) Jan 28 16:28:13 kernel: pcm0: CODEC semaphore timeout Jan 28 16:28:13 kernel: pcm0: ac97 codec reports dac not ready Jan 28 16:28:13 kernel: pcm0: CODEC semaphore timeout Jan 28 16:29:35 kernel: pcm0: Unhandled interrupt, gs_intr = 86 Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi, Can this please be committed to or at least prepared as a patch for RELENG_5_0? I myself consider fixing automount access to 5.0-RELEASE nfs Feel free to add this patch: http://people.freebsd.org/~mbr/patches/committed/patch-rpc_oldreply.diff servers a critical bugfix, but should RE's mileage vary, I'd really like a patch that I can apply on my server. There is also a PR open about this which could be closed, it's bin/47496. Thanks for the pointer, I'll close it. martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi, I don't know the problem is in amd or mountd. I fear other programs are broken with this commit... Mounting nfs volumes manually works, as other services work fine. I also tested other rpc-service and they seem to be fine. So we have to find out why mountd replies twice. With the committed change, mountd uses non-blocking rpc for tcp. If I can reproduce it, I'm a bit closer to solve it. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi, In my environment, server is 5.0-RELEASE and client is HEAD as of Jan 20th. Both have nfsd, rpc.lockd, rpc.statd and nfs client. Just tried to reproduce it again. I'm not able to reproduce it :-( Can you try to cvsup on both boxes and then manually rebuild libc, mountd, rpcbind, nfsd. I just tired udp and tcp automounts. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi, s-c MOUNT V1 EXPORT Reply (duplicate) I suspect timeouts or packet loss cause this together with the new nonblock code change. I just tried V2 (mountd -2) and amd with -2 option. The bug does not appear. If possible I'd like to reproduce packet loss with dummynet, has anyone the necessary commands at hand ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi all, We can end this tread. The bug has been found and fixed in HEAD. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: OpenOffice swriter working on -CURRENT
Hi, Sheldon Hearn wrote: Hi folks, Could someone with an up-to-date -CURRENT (as of anything since Wednesday last week) and OpenOffice let me know whether OpenOffice's swriter works? It definitly works. But before you update: I have a new version in the work-queue. 1.02 is almost out of the box, the port is almost ready: http://people.freebsd.org/~mbr/ports/openoffice-port-1.02.tgz There is one bug (crash) which I'd like to have fixed before I update the port. And OpenOffice.org needs to announce OpenOffice.org version 1.02 officially. Maybe you don't have procfs running ? The old packages still needs procfs, and crash without it. The new version (also the one in cvs doesn't need it. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: if_sis.c 1.61 breaks support for SiS630 chipset
Hi, Version 1.61 of if_sis.c breaks support for SiS630, or at least the one on my laptop. This has been noted before, in It seems that older SiS900 card don't work with this revision. Newer cards tough, seem only to work with the bitbang code. Can you post me a pciconf -lv I need the revision number of your integrated nic. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PANIC in tcp_syncache.c sonewconn() line 562
Hi Thomas,
s = splnet();
+ if (so-so_state (SS_ISCONNECTED | SS_ISCONNECTING)) {
+ splx(s);
+ return (EINVAL);
+ }
error = (*so-so_proto-pr_usrreqs-pru_listen)(so, td);
if (error) {
splx(s);
Can you commit this ? The fix looks appropriate, but the manpage should
also be changed to reflect the change.
ERRORS
Listen() will fail if:
[EBADF]The argument s is not a valid descriptor.
[ENOTSOCK] The argument s is not a socket.
[EOPNOTSUPP] The socket is not of a type that
supports the operation listen().
[EINVAL] Listen() has been already called on the socket.
Any objections from others ?
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
PANIC in tcp_syncache.c sonewconn() line 562
Hi all,
Two days before RELEASE, I have a nice announcement ...
Newest CURRENT ... Easy to reproduce:
Get http://people.freebsd.org/~mbr/ports/drac.tgz
Install the port.
Add
drac3/tcp
to /etc/services
Add
dracstream tcp nowait root/usr/local/sbin/rpc.dracd rpc.dracd
to /etc/inetd.conf
Restart inetd.
telnet localhost 3
BM
#10 0xc03df350 in trap (frame=
{tf_fs = 24, tf_es = -65520, tf_ds = 16, tf_edi = 2, tf_esi = -1031597312,
tf_ebp = -854635944, tf_isp = -854635988, tf_ebx = -1031595264, tf_edx = 4,
tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1071076206, tf_cs
= 8, tf_eflags = 66050, tf_esp = -1031595264, tf_ss =
0}) at /usr/src/sys/i386/i386/trap.c:445
#11 0xc03cf9f8 in calltrap () at {standard input}:98
#12 0xc02e1f3f in syncache_socket (sc=0xc2831300, lso=0xc2831300, m=0xc0ed9c00)
at /usr/src/sys/netinet/tcp_syncache.c:562
#13 0xc02e23e8 in syncache_expand (inc=0xcd0f4b4c, th=0xc0ed9c68,
sop=0xcd0f4b18, m=0xc0ed9c00)
at /usr/src/sys/netinet/tcp_syncache.c:781
#14 0xc02db779 in tcp_input (m=0xc0ed9c68, off0=20) at
/usr/src/sys/netinet/tcp_input.c:703
#15 0xc02d409b in ip_input (m=0xc0ed9c00) at /usr/src/sys/netinet/ip_input.c:923
#16 0xc02d4192 in ipintr () at /usr/src/sys/netinet/ip_input.c:941
#17 0xc02c1713 in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:97
#18 0xc0238df1 in ithread_loop (arg=0xc0eba000) at
/usr/src/sys/kern/kern_intr.c:535
#19 0xc0237cf3 in fork_exit (callout=0xc0238c20 ithread_loop, arg=0x0,
frame=0x0)
at /usr/src/sys/kern/kern_fork.c:873
562 so = sonewconn(lso, SS_ISCONNECTED);
Martin
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: PANIC in tcp_syncache.c sonewconn() line 562
Hi all, Two days before RELEASE, I have a nice announcement ... Newest CURRENT ... Easy to reproduce: Ah yes, it seems that the bug is present in STABLE too ... This was 4.7 RELEASE. Here you can just use the drac port from /usr/ports/mail/drac which does the right thing. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: SIS 962 chipset, problems ...
Good year everybody Luigi, I converted your patch to CURRENT, there were only minor changes to do and it seems to work ! sis0: SiS 900 10/100BaseTX port 0x2000-0x20ff mem 0xec005000-0xec005fff irq 1$ at device 4.0 on pci0 sis0: Ethernet address: 00:00:e2:94:66:99 miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto http://people.freebsd.org/~mbr/patches/ifsis-luigi.diff and added the Linux way of reading the eeprom. I guess we should make this the default for accessing the eeprom (for this chipset), since it is not only the mac address which gets read. Luigi: Or isn't this neccessary ? http://people.freebsd.org/~mbr/patches/ifsis-mbr.diff Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Firewire: fwohci0: cannot read phy
Hi all, Does anyone know why my firewire kld does not attach successfully ? Could this be related to the same problem I had with the sis900 nic ? Eeprom is shared between Firewire and NIC. fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xec00-0xec000fff irq 11 at device 2.3 on pci0 fwohci0: PCI bus latency was changing to 250. fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:01:24:10:32:0a:c0:30 fwohci0: cannot read phy fwohci0: Link 1394a available S400, 2 ports, maxrec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 firewire0: BUS reset firewire0: node_id = 0xc000ffc0, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: unrecoverable error Chipset is SiS962 with integrated USB, Firewire and NIC. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
SIS 962 chipset, problems ...
Hi all,
I'm trying to get my laptop running, with some success, but the
network card is not very friendly to me.
none3@pci0:4:0: class=0x02 card=0x105517c0 chip=0x09001039 rev=0x91 hdr=0x00
vendor = 'Silicon Integrated Systems (SiS)'
device = 'SiS900 Fast Ethernet/Home Networking Ctrlr'
class= network
subclass = ethernet
Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff
Dec 23 15:17:03 kernel: sis0: MII without any PHY!
Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach returned 6
Dec 23 15:17:03 kernel: sis0: SiS 900 10/100BaseTX port 0x2000-0x20ff mem
0xec005000-0xec005fff irq 11 at device 4.0 on pci0
Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff
Dec 23 15:17:03 kernel: sis0: MII without any PHY!
I thought first that this is a similar problem to the one where
the physical is at id 1, not 0. But it still doesn't work.
http://www.freebsd.org/cgi/query-pr.cgi?pr=30836
Then I tried another tip from google:
http://www.geocrawler.com/archives/3/152/2002/6/0/9065467/
No way ... I'll try some other tricks now ...
Other things I got running, like the ATA UDMA support. It seems
that many new chipsets are unsupported in FreeBSD ...
--- sys/pci/agp_sis.c.orig Mon Dec 23 14:34:30 2002
+++ sys/pci/agp_sis.c Mon Dec 23 14:34:32 2002
@@ -66,6 +66,8 @@
switch (pci_get_devid(dev)) {
case 0x00011039:
return (SiS 5591 host to AGP bridge);
+ case 0x06461039:
+ return (SiS 645DX host to AGP bridge);
};
if (pci_get_vendor(dev) == 0x1039)
--- sys/dev/ata/ata-dma.c.orig Mon Dec 23 14:44:39 2002
+++ sys/dev/ata/ata-dma.c Mon Dec 23 15:49:20 2002
@@ -632,7 +632,9 @@
ata_find_dev(parent, 0x06351039, 0) || /* SiS 635 */
ata_find_dev(parent, 0x06401039, 0) || /* SiS 640 */
ata_find_dev(parent, 0x06451039, 0) || /* SiS 645 */
+ ata_find_dev(parent, 0x06461039, 0) || /* SiS 646 */
ata_find_dev(parent, 0x06501039, 0) || /* SiS 650 */
+ ata_find_dev(parent, 0x06511039, 0) || /* SiS 651 */
ata_find_dev(parent, 0x07301039, 0) || /* SiS 730 */
ata_find_dev(parent, 0x07331039, 0) || /* SiS 733 */
ata_find_dev(parent, 0x07351039, 0) || /* SiS 735 */
--- sys/dev/ata/ata-pci.c.orig Mon Dec 23 16:40:04 2002
+++ sys/dev/ata/ata-pci.c Mon Dec 23 16:39:27 2002
@@ -188,7 +188,9 @@
ata_find_dev(dev, 0x06351039, 0) ||
ata_find_dev(dev, 0x06401039, 0) ||
ata_find_dev(dev, 0x06451039, 0) ||
+ ata_find_dev(dev, 0x06461039, 0) ||
ata_find_dev(dev, 0x06501039, 0) ||
+ ata_find_dev(dev, 0x06511039, 0) ||
ata_find_dev(dev, 0x07301039, 0) ||
ata_find_dev(dev, 0x07331039, 0) ||
ata_find_dev(dev, 0x07351039, 0) ||
Martin
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: SIS 962 chipset, problems ...
Hi, Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff Dec 23 15:17:03 kernel: sis0: MII without any PHY! Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach returned 6 Dec 23 15:17:03 kernel: sis0: SiS 900 10/100BaseTX port 0x2000-0x20ff mem 0xec005000-0xec005fff irq 11 at device 4.0 on pci0 Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff Dec 23 15:17:03 kernel: sis0: MII without any PHY! The linux driver tells me : /** * sis96x_get_mac_addr: - Get MAC address for SiS962 or SiS963 model * @pci_dev: the sis900 pci device * @net_dev: the net device to get address for * * SiS962 or SiS963 model, use EEPROM to store MAC address. And EEPROM * is shared by * LAN and 1394. When access EEPROM, send EEREQ signal to hardware first * and wait for EEGNT. If EEGNT is ON, EEPROM is permitted to be access * by LAN, otherwise is not. After MAC address is read from EEPROM, send * EEDONE signal to refuse EEPROM access by LAN. * The EEPROM map of SiS962 or SiS963 is different to SiS900. * The signature field in SiS962 or SiS963 spec is meaningless. * MAC address is read into @net_dev-dev_addr. */ So we definitly are missing the support for the SiS 962/963 southbridge. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SIS 962 chipset, problems ...
Hi Soeren, This does not work correctly, your ATA timings are way out of wack since botht ATA100 and ATA133 SiS chips uses different register layouts... I know. This is just a workaround. At least my box does not hang during boot and ATA100 seems to work. No crash since then. Do you have a more correct fix for the ATA133 chipset in work, or already ready so I could test it ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RC2 install report, three problems
Hi all, Trying to install 5.0 RC2 on my new laptop, it fails miserably on everything I try. Let me explain the three different problems. 1) ATA problem The laptop has as SIS chipset, and uses a SIS900 ATA controller. Disable ULTRA DMA does help. See this posting with a possible workaround. It would be nice if at least this workaround gets committed to 5.0R. http://www.freebsd.org/cgi/query-pr.cgi?pr=30836 2.) Failing to read MAC adresse, missing PHYS This PR should definitly be committed to 5.0, it's waiting since a long time. Without this patch, all laptop users with integrated nic and a SIS 642 chipset cannot use FreeBSD. http://www.geocrawler.com/archives/3/152/2002/6/0/9065467/ 3.) Unable to install from a Realtec pcmcia card (Realtek RTL8139) The card is properly detected, but it seems that it doesn't get power turned on. Looks like Warner needs to fix something here. All we get here are rl0: watchdog timeout. I'm willing to provide more informations about this issue. I gave up now after a very frustrating session. It seems that I'll have to install over parallel or serial IP connection again. Someone should definitly look at Wpauls PR's and commit the ones that are ready. It looks like work has stalled there for a long time. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: RC2 install report, three problems
Soeren, 1) ATA problem The laptop has as SIS chipset, and uses a SIS900 ATA controller. Disable ULTRA DMA does help. See this posting with a possible workaround. It would be nice if at least this workaround gets committed to 5.0R. http://www.freebsd.org/cgi/query-pr.cgi?pr=30836 Of course this link belongs to the NIC problem too. The correct link is: http://www.freebsd.org/cgi/query-pr.cgi?pr=43345 Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: RC2 install report, three problems
Hi, dmesg output here? Looks like there's no interrupts for the card. [...] cbb0: PCI-Cardbus Bridge at device 9.0 on pci0 cardbus0: CardBusbus on cbb0 pccard0: 16-bit PCCardbus on cbb0 pci_cfg_intr_virgin: using routable interrupt 4 pci_cfgintr: 0:9 INTA routed to irq 4 cbb1: PCI-Cardbus Bridge at device 9.0 on pci0 cardbus1: CardBusbus on cbb1 pccard1: 16-bit PCCardbus on cbb1 pci_cfg_intr_virgin: using routable interrupt 4 pci_cfgintr: 0:9 INTA routed to irq 4 [...] Manufacuture ID:1b02 Functions: Network adapter, Multi Functions Function extension: 0102 Function extension: 0280969800 Function extension: 0200e1f505 Product Version:5.0 Product Name: Cardbus PC Card Fast Ethernet Cardbus PCCard CIS Reading done: cbb1: Cardbus card activation failed. If I insert the card after probing and loading modules, the system freezes. If I let the card in, I get: rl0: RealTek 8139 10/100BaseTX port 0x1200-0x137f mem 0x88002000 - 0x8800217f irq 4 at device 0.0 on cardbus1 rl0: ethernet address 00:10:60:5a:bb:bd miibus0: MII bus on rl0 rlphy0 RealTek inter media interface on miibus0 The leds are turned of, dhclient fails. If I take the card out the system freezes. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ssh authentification broken, only public keys work
Hi, Disable ChallengeResponseAuthentication, set it to no and you'll have ssh again. -- Thanks, I'll try it at home this evening ... Shouldn't we fix this the default config ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ssh authentification broken, only public keys work
Hi all, Since yesterday I cannot login to my CURRENT machine anymore after a world and reboot ... I really hope this doesn't got MFC'd to RELENG_5_0 ... debug1: rcvd SSH_CMSG_AUTH_TIS debug3: mm_pam_init_ctx debug3: mm_request_send entering: type 42 debug3: monitor_read: checking request 42 debug3: mm_answer_pam_init_ctx debug3: mm_request_send entering: type 43 debug3: mm_request_receive entering debug3: mm_pam_init_ctx: waiting for MONITOR_ANS_PAM_INIT_CTX debug3: mm_request_receive_expect entering: type 43 debug3: mm_request_receive entering debug3: mm_pam_query debug3: mm_request_send entering: type 44 debug3: monitor_read: checking request 44 debug3: mm_answer_pam_query debug3: ssh_msg_recv entering debug3: ssh_msg_send: type 1 ssh_msg_send: write debug1: Calling cleanup 0x8061180(0x0) debug1: PAM: cleanup debug3: mm_pam_query: waiting for MONITOR_ANS_PAM_QUERY debug3: mm_request_receive_expect entering: type 45 debug3: mm_request_receive entering Then the connection times just out. The ssh_msg_send: write message appears without debug mode. Note that I did run mergemaster ... pam files are all on their place. Somthing is completly screwed up. There are a few posts in google indicating that other have this problem too. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
