Re: ASDM and linux emulation?
On Thu, 27 Jan 2000, F. Heinrichmeyer wrote: I would like to use an ASDM (backup software) with linux-emulation. I get the following in /var/log/messages: es-i2 /kernel: linux: syscall setresuid is obsoleted\ or not implemented (pid=41052) Jan 27 13:12:42 es-i2 /kernel: pid 41052 (dsm), \ uid 0: exited on signal 11 (core dumped) What FreeBSD is this? I've run the v3 client under linux mode without bad syscalls (just that silly pathmunging stuff that I need to renew the fight over). I have a hacked linux.ko that lets dsmc backup what you think it will back up, but the SCO version is a better fit. I should try it on my workstation. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release failure
Hi. I just tried a ,make release' with USA_RESIDENT set to NO. It failed with --- crunchide -k _crunched_grep_stub grep.lo cc -static -o fixit_crunch fixit_crunch.o cat.lo chmod.lo chroot.lo cp.lo dd.lo df.lo echo.lo expr.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo rm.lo rmdir.lo sleep.lo sync.lo chown.lo clri.lo disklabel.lo dmesg.lo fdisk.lo mknod.lo mount.lo reboo t.lo restore.lo swapon.lo umount.lo mount_msdos.lo mount_cd9660.lo ftp.lo more.l o telnet.lo vi.lo grep.lo -lcrypt -ltelnet -lutil -ll -lm -lcurses -ltermcap -le dit -lgnuregex -lkvm -lz telnet.lo: In function `setpolicy': telnet.lo(.text+0x22af): undefined reference to `ipsec_set_policy' telnet.lo(.text+0x22c0): undefined reference to `ipsec_strerror' telnet.lo(.text+0x2303): undefined reference to `ipsec_get_policylen' *** Error code 1 Stop in /usr/obj/usr/src/release/fixit_crunch. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. --- Perhaps that part of the release is not aware that something exists outside of USA_RESIDENT=YES. -- German Tischler, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] Bruce Evans writes: : So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I've done the build on 3.3 and it works. It does break cross compilation. There is a tool (fini) that gets built on the host with the host libraries and run on the host to generate some files and this during the last phase of the build. Maybe the right thing to do for make depend is to somehow arrange for all things needed to build depend get built with the host compiler and if host != target they get deleted before the actual build with the tools. Of course, hours before the code freeze is an inauspicious time to make such sweeping declaration. This automates much of the tools problem... I will back it out until after 4.0 so this change can be analized in more detail. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
Hi.
I just tried a ,make release' with USA_RESIDENT set to NO. It failed with
dit -lgnuregex -lkvm -lz
telnet.lo: In function `setpolicy':
telnet.lo(.text+0x22af): undefined reference to `ipsec_set_policy'
telnet.lo(.text+0x22c0): undefined reference to `ipsec_strerror'
telnet.lo(.text+0x2303): undefined reference to `ipsec_get_policylen'
*** Error code 1
Stop in /usr/obj/usr/src/release/fixit_crunch.
*** Error code 1
Stop in /usr/src/release.
*** Error code 1
Stop in /usr/src/release.
Sorry for the problem. Could you try with this patch for now?
Yoshinobu Inoue
--- usr.bin/telnet/Makefile.origThu Jan 27 15:04:00 2000
+++ usr.bin/telnet/Makefile Sun Jan 30 03:19:31 2000
@@ -40,12 +40,12 @@
CFLAGS+=-DENV_HACK
CFLAGS+=-DSKEY
CFLAGS+=-I${.CURDIR}/../../lib
-CFLAGS+=-DIPSEC -DINET6
+CFLAGS+=-DINET6
#CFLAGS+= -DKRB4
-DPADD= ${LIBTERMCAP} ${LIBTELNET} ${LIBIPSEC}
-LDADD= -ltermcap -ltelnet -lipsec
+DPADD= ${LIBTERMCAP} ${LIBTELNET}
+LDADD= -ltermcap -ltelnet
#DPADD+= ${LIBKRB} ${LIBDES}
#LDADD+= -lkrb -ldes
@@ -57,7 +57,14 @@
CRYPT_SRC+= ring.c ring.h telnet.c terminal.c utilities.c Makefile
NOCRYPT_DIR=${.CURDIR}/Nocrypt
+.if !defined(RELEASE_CRUNCH)
+CFLAGS+=-DIPSEC
+DPADD= ${LIBIPSEC}
+LDADD= -lipsec
+.endif
+
.include bsd.prog.mk
nocrypt:
@echo "Encryption code already removed."
+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
On Sat, 29 Jan 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Bruce Evans writes: : So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I've done the build on 3.3 and it works. It does break cross compilation. There is a tool (fini) that gets built on the host with the host libraries and run on the host to generate some files and this during the last phase of the build. Right. Maybe the right thing to do for make depend is to somehow arrange for all things needed to build depend get built with the host compiler and if host != target they get deleted before the actual build with the tools. Of course, hours before the code freeze is an inauspicious time to make such sweeping declaration. This automates much of the tools problem... David committed Marcel's workaround for the problem with make depend in f771 2 weeks ago. I don't know why you still have problems. Deleting things is another workaround. The correct fix is to build tools in separate directories and not build these directories for cross-building. I will back it out until after 4.0 so this change can be analized in more detail. Thanks. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] Bruce Evans writes: : David committed Marcel's workaround for the problem with make depend in : f771 2 weeks ago. I don't know why you still have problems. No. I'm not having problems there. I was just making observations. : Deleting things is another workaround. The correct fix is to build : tools in separate directories and not build these directories for : cross-building. Yes. The tools for building things often assume too much. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
Sorry for the problem. Could you try with this patch for now?
Last patch was bad. Please try this one instead.
Yoshinobu Inoue
--- usr.bin/telnet/Makefile.orig Thu Jan 27 15:04:00 2000
+++ usr.bin/telnet/MakefileSun Jan 30 04:28:44 2000
@@ -40,12 +40,12 @@
CFLAGS+=-DENV_HACK
CFLAGS+=-DSKEY
CFLAGS+=-I${.CURDIR}/../../lib
-CFLAGS+=-DIPSEC -DINET6
+CFLAGS+=-DINET6
#CFLAGS+= -DKRB4
-DPADD= ${LIBTERMCAP} ${LIBTELNET} ${LIBIPSEC}
-LDADD= -ltermcap -ltelnet -lipsec
+DPADD= ${LIBTERMCAP} ${LIBTELNET}
+LDADD= -ltermcap -ltelnet
#DPADD+= ${LIBKRB} ${LIBDES}
#LDADD+= -lkrb -ldes
@@ -57,7 +57,14 @@
CRYPT_SRC+= ring.c ring.h telnet.c terminal.c utilities.c Makefile
NOCRYPT_DIR=${.CURDIR}/Nocrypt
+.if !defined(RELEASE_CRUNCH)
+CFLAGS+=-DIPSEC
+DPADD+= ${LIBIPSEC}
+LDADD+= -lipsec
+.endif
+
.include bsd.prog.mk
nocrypt:
@echo "Encryption code already removed."
+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
Hi, ... thanks for your assistance. I On Fri, Jan 28, 2000 at 08:22:32AM -0800, Rodney W. Grimes wrote: Next step is run the ``save'' fsck: fsck -n /scratch /someplacewithspace 21 there is some illuminated filesystem-hacker who would like to take a peek. (I would allow ssh-access to the box ...) $1.00/MB for me to recover it ... I was used to this kind of service for hosed FAT-filesystems and hosed partition tables ;) ... (I did it by stuffing the 'hosed disks' into one of my unix-boxes and working on the raw devices ...) if you need it. ... fortunately not. Just have a look at the mountpoint's name I don't do it for fun. ... understandable :), I made the offer just for the case anybody wants to track down a potential bug. But as it comes out I had (in fact :( ) a typo in the disklabel. I checked the disklabel two times before my post to -current, but I had obviously a little problem with my 'eye-brain-interlink'. I really shouldn't admit this in this forum, should I? ... But in relabeling the disk I left the disklabel as follows: #size offsetfstype [fsize bsize bps/cpg] b: 10485760 swap# (Cyl.0 - 65*) c: 179124120unused0 0 # (Cyl.0 - 1114*) g: 1791241204.2BSD 1024 819216 # (Cyl.0 - 1114*) Sorry for bothering all of you, feeling soo stultified and the big and heavy hat (with a certain pattern on it) weighs on my head ... Thanks, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/: : PGP-Key:http://www.tse-online.de/~ab/public-key: : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
On Sat, Jan 29, 2000 at 07:14:48PM +0900, Yoshinobu Inoue wrote: Sorry for the problem. Could you try with this patch for now? It might be easier to just commit it if `make buildworld' passes. With the double CVS checkout required in `make release' I don't know an easy good way to apply patches in the second checkout. Since `make release' is already broken, you cannot break it worse. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release failure
It might be easier to just commit it if `make buildworld' passes. OK, but now I have middle class speed machine at hand, and maybe it takes 2 or 3 hours. Also, do other apps which use libipsec will need same kind of change? (There is one under usr.bin, and several under usr.sbin.) Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ASDM and linux emulation?
Fritz Doug,
Doug White [EMAIL PROTECTED] writes:
On Thu, 27 Jan 2000, F. Heinrichmeyer wrote:
I would like to use an ASDM (backup software) with linux-emulation. I
get
the following in /var/log/messages:
es-i2 /kernel: linux: syscall setresuid is obsoleted\
or not implemented (pid=41052)
Jan 27 13:12:42 es-i2 /kernel: pid 41052 (dsm), \
uid 0: exited on signal 11 (core dumped)
What FreeBSD is this? I've run the v3 client under linux mode without bad
syscalls (just that silly pathmunging stuff that I need to renew the fight
over).
Perhaps you are running the backup as root while Fritz has a setuid
root program? In any case, please find attacked a patch that
implements setresuid. The patch is relative to 3.3 but should port
pretty easily to current.
Fritz, if this cures your problems, please drop me a note.
Cheers,
Björn
--
_ _ ,___.
Bjorn Gronvall (Björn Grönvall)/___/|
Swedish Institute of Computer Science | ||
PO Box 1263, S-164 29 Kista, Sweden| Schroedingers ||
Email: [EMAIL PROTECTED], Phone +46 -8 633 15 25 | Cat |/
Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---'
--- linux_misc.c2000/01/29 10:23:54 1.1
+++ linux_misc.c2000/01/29 11:40:28
@@ -797,6 +797,44 @@
}
int
+linux_setresuid(p, uap)
+ struct proc *p;
+ struct linux_setresuid_args *uap;
+{
+ struct setreuid_args bsd_args;
+
+ /* Allow setresuid iff the saved effective uid is left unchanged. */
+ if (uap-suid != -1 uap-suid != p-p_cred-p_svuid) {
+ printf("Linux-emul(%d): setresuid(%d, %d, %d) not supported\n",
+ p-p_pid, uap-ruid, uap-euid, uap-suid);
+ return ENOSYS;
+ }
+ bsd_args.ruid = uap-ruid;
+ bsd_args.euid = uap-euid;
+ /* uap-suid is unchanged */
+ return setreuid(p, bsd_args);
+}
+
+int
+linux_setresgid(p, uap)
+ struct proc *p;
+ struct linux_setresgid_args *uap;
+{
+ struct setregid_args bsd_args;
+
+ /* Allow setresgid iff the saved effective gid is left unchanged. */
+ if (uap-sgid != -1 uap-sgid != p-p_cred-p_svgid) {
+ printf("Linux-emul(%d): setresgid(%d, %d, %d) not supported\n",
+ p-p_pid, uap-rgid, uap-egid, uap-sgid);
+ return ENOSYS;
+ }
+ bsd_args.rgid = uap-rgid;
+ bsd_args.egid = uap-egid;
+ /* uap-sgid is unchanged */
+ return setregid(p, bsd_args);
+}
+
+int
linux_msync(struct proc *p, struct linux_msync_args *args)
{
struct msync_args bsd_args;
--- linux_proto.h 2000/01/29 10:28:59 1.1
+++ linux_proto.h 2000/01/29 11:08:53
@@ -402,6 +402,16 @@
int new_len;char new_len_[PAD_(int)];
int flags; char flags_[PAD_(int)];
};
+struct linux_setresuid_args {
+ int ruid; char ruid_[PAD_(int)];
+ int euid; char euid_[PAD_(int)];
+ int suid; char suid_[PAD_(int)];
+};
+struct linux_setresgid_args {
+ int rgid; char rgid_[PAD_(int)];
+ int egid; char egid_[PAD_(int)];
+ int sgid; char sgid_[PAD_(int)];
+};
struct linux_rt_sigaction_args {
int sig;char sig_[PAD_(int)];
struct linux_new_sigaction *act;char act_[PAD_(struct
linux_new_sigaction *)];
@@ -528,6 +538,8 @@
intlinux_sched_setscheduler __P((struct proc *, struct
linux_sched_setscheduler_args *));
intlinux_sched_getscheduler __P((struct proc *, struct
linux_sched_getscheduler_args *));
intlinux_mremap __P((struct proc *, struct linux_mremap_args *));
+intlinux_setresuid __P((struct proc *, struct linux_setresuid_args *));
+intlinux_setresgid __P((struct proc *, struct linux_setresgid_args *));
intlinux_rt_sigaction __P((struct proc *, struct linux_rt_sigaction_args *));
intlinux_rt_sigprocmask __P((struct proc *, struct linux_rt_sigprocmask_args *));
intlinux_chown __P((struct proc *, struct linux_chown_args *));
--- linux_syscall.h 2000/01/29 10:43:49 1.1
+++ linux_syscall.h 2000/01/29 11:09:30
@@ -162,7 +162,9 @@
#defineLINUX_SYS_sched_rr_get_interval 161
#defineLINUX_SYS_nanosleep 162
#defineLINUX_SYS_linux_mremap 163
+#defineLINUX_SYS_linux_setresuid 164
#defineLINUX_SYS_poll 168
+#defineLINUX_SYS_linux_setresgid 170
#defineLINUX_SYS_linux_rt_sigaction174
#defineLINUX_SYS_linux_rt_sigprocmask 175
#defineLINUX_SYS_linux_chown 182
--- linux_sysent.c 2000/01/29 10:06:22 1.1
+++ linux_sysent.c 2000/01/29 11:06:51
@@ -178,13 +178,13 @@
{ 2, (sy_call_t *)sched_rr_get_interval }, /* 161 =
sched_rr_get_interval */
Re: make release failure
On Sat, Jan 29, 2000 at 10:11:05AM +0100, Yoshinobu Inoue wrote: Sorry for the problem. Could you try with this patch for now? Thank you, it worked, at least for completing the interupted release build. I have not tested in which way the patch affects building the world though. -- German Tischler, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote: Is it possible to bump the revision of libstdc++ (and perhaps others) so that existing programs can continue to function? Nope. This is -CURRENT and this type of thing happens. And with a RELEASE about to happen, I don't want people continually asking for these old libs. Well, OK, I can deal with this myself. I'm just concerned about the folks who will eventually upgrade from 3.4 to 4.0, and have their C++ programs stop working. libstdc++ is version 2 in -stable. louie -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
On Fri, Jan 28, 2000 at 11:19:37PM -0500, Louis A. Mamakos wrote: Well, OK, I can deal with this myself. I'm just concerned about the folks who will eventually upgrade from 3.4 to 4.0, and have their C++ programs stop working. There will be the same problem WRT C++ when upgrading from 3.4 to 4.0 either way. Both "g++-2.95.2 -fno-vtable-thunks" and "g++-2.95.2 -fvtable-thunks" are incompatible C++ platforms from G++ 2.7.x. People wishing to use C++ programs compiled on FreeBSD 3.x need to install the ``compat3x'' distribution to get the libstdc++.so.? compatibility library. For ports those same people will have to keep their 3.x compiled C++ libs (in /usr/local/lib /usr/X11R6/lib) around how ever they like. Again, this requirement would be the same with or w/o the C++ ABI change I just made. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
install(1) installed too late in world
The following occured during a world build after this morning's CVSUP: === bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 An install in usr.bin/xinstall fixed the problem. Last world build was two days ago. Regards, Scott -- Scott G. Akmentins-Taylor InterNet: [EMAIL PROTECTED] MRY Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sat, Jan 29, 2000 at 02:35:43AM +0100, Ollivier Robert wrote: [I said about ntpd usage of sched_* functions:] We should make them standard IMO. According to John Polstra: I agree. BTW, as the sched_* POSIX functions are now standard in GENERIC, I've decided along with the upgrade to ntpd 4.0.99b to re-enable them. Be aware that the sched_* functions are somewhat broken. Peter Dufault had some patches that fixed them. I also had a later version of them. When Julian inquired about committing my later version, Peter indicated he was re-working the patches and communicating with bde about them. This was about 1-2 months ago. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm - stutters
I too notice these problems of mpg123 skipping during disk activity or X graphics ops but I have always had these problems, both with -STABLE and -CURRENT. I notice this with xmms too. So this is nothing new. Isn't this simply a typical issue of IDE hardware? I too notice xmms skipping on heavy disk activity (typically the find command that runs from cron at 01:59). This happens even though I have two processors and a disk that can do 16 Mb/sec on UDMA66. One would expect such a system to be able to do a find and play mp3's simultaneously. Pressing Ctrl-Z repeats the same quarter second fragment forever. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm - stutters
Nick Hibma wrote: Pressing Ctrl-Z repeats the same quarter second fragment forever. I know the pcm driver uses a circular buffer. Maybe a small chunk of the sound gets stuck in the buffer, and when you press ^Z, the app is unable to tell the sound driver to break out of the loop. Also, RealPlayer still repeats a small fragment over and over when the data flow is interrupted due to net congestion. This is RealPlayer 5, though... - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm - stutters
On Sat, 29 Jan 2000, Nick Hibma wrote: I too notice these problems of mpg123 skipping during disk activity or X graphics ops but I have always had these problems, both with -STABLE and -CURRENT. I notice this with xmms too. So this is nothing new. Isn't this simply a typical issue of IDE hardware? I too notice xmms skipping on heavy disk activity (typically the find command that runs from cron at 01:59). This happens even though I have two processors and a disk that can do 16 Mb/sec on UDMA66. One would expect such a system to be able to do a find and play mp3's simultaneously. Pressing Ctrl-Z repeats the same quarter second fragment forever. And 'fg' doesn't always make it continue properly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
:But as it comes out I had (in fact :( ) a typo in the disklabel. : :I checked the disklabel two times before my post to -current, but :I had obviously a little problem with my 'eye-brain-interlink'. : :I really shouldn't admit this in this forum, should I? ... But :in relabeling the disk I left the disklabel as follows: : :#size offsetfstype [fsize bsize bps/cpg] : b: 10485760 swap# (Cyl.0 - 65*) : c: 179124120unused0 0 # (Cyl.0 - 1114*) : g: 1791241204.2BSD 1024 819216 # (Cyl.0 - 1114*) : : :Sorry for bothering all of you, feeling soo stultified :and the big and heavy hat (with a certain pattern on it) weighs :on my head ... : : :Thanks, :Andreas Heh! Don't feel bad, the only reason I thought it was a disklabel problem is because I've done the same thing myself in the past, with similar results! What we really need to do is fix disklabel to at least warn of overlaps. The only reason I don't make the same mistakes these days is because every time I run the beast I check my calculations 6 ways from sunday, forwards and backwards. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In article [EMAIL PROTECTED], Warner Losh [EMAIL PROTECTED] wrote: I will back it out until after 4.0 so this change can be analized in more detail. What a perfect Freudian slip! Does this mean you plan to, er, put it where the sun don't shine? :-) John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] John Polstra writes: : In article [EMAIL PROTECTED], : Warner Losh [EMAIL PROTECTED] wrote: : : I will back it out until after 4.0 so this change can be analized in : : more detail. : : What a perfect Freudian slip! Does this mean you plan to, er, put it : where the sun don't shine? :-) Ummm, errr, ahhh, no. Other members of this community may, but it was a simple typo. Honest. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PAIN
What's the current wuildworld times for a 486DX2-66 + 12M RAM over NFS? I have a small box that I'd like to torture test before putting into service and thought this would make a good week long test. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OHCI patch for ohci_hash_find_td panic
Everyone who has seen the ohci_hash_find_td not found panic should try
this one and let me know whether the machine panics or not and
where. This patch is against CURRENT.
It looks like the hardware kind of deviates from the OHCI spec when
putting things on the Done queue in case of an error.
Important: Your system will panic and completely destroy your
filesystem. If it doesn't you got lucky.
Cheers,
Nick
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] USB project
http://www.etla.net/~n_hibma/
Index: ohci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
retrieving revision 1.36
diff -w -u -r1.36 ohci.c
--- ohci.c 2000/01/29 16:25:55 1.36
+++ ohci.c 2000/01/29 17:04:44
@@ -91,7 +91,7 @@
#ifdef OHCI_DEBUG
#define DPRINTF(x) if (ohcidebug) logprintf x
#define DPRINTFN(n,x) if (ohcidebug(n)) logprintf x
-int ohcidebug = 0;
+int ohcidebug = 1;
#else
#define DPRINTF(x)
#define DPRINTFN(n,x)
@@ -417,6 +417,7 @@
usbd_status err;
int i, offs;
usb_dma_t dma;
+ int s;
if (sc-sc_freetds == NULL) {
DPRINTFN(2, ("ohci_alloc_std: allocating chunk\n"));
@@ -436,6 +437,11 @@
sc-sc_freetds = std-nexttd;
memset(std-td, 0, sizeof(ohci_td_t));
std-nexttd = NULL;
+
+ s = splusb();
+ ohci_hash_add_td(sc, std);
+ splx(s);
+
return (std);
}
@@ -444,6 +450,12 @@
ohci_softc_t *sc;
ohci_soft_td_t *std;
{
+ int s;
+
+ s = splusb();
+ ohci_hash_rem_td(sc, std);
+ splx(s);
+
std-nexttd = sc-sc_freetds;
sc-sc_freetds = std;
}
@@ -1127,7 +1139,8 @@
#ifdef OHCI_DEBUG
if (ohcidebug 10) {
DPRINTF(("ohci_process_done: TD done:\n"));
- ohci_dump_tds(sdone);
+ for (std = sdone; std; std = std-dnext)
+ ohci_dump_td(sdone);
}
#endif
@@ -1135,7 +1148,16 @@
xfer = std-xfer;
stdnext = std-dnext;
DPRINTFN(5, ("ohci_process_done: std=%p xfer=%p hcpriv=%p\n",
- std, xfer, xfer-hcpriv));
+ std, xfer, (xfer? xfer-hcpriv:NULL)));
+ if (xfer == NULL || (std-flags OHCI_TD_HANDLED)) {
+ /* xfer == NULL: There seems to be no xfer associated
+* with this TD. It is tailp that happened to end up on
+* the done queue.
+* flags OHCI_TD_HANDLED: The TD has already been
+* handled by process_done and should not be done again.
+*/
+ continue;
+ }
cc = OHCI_TD_GET_CC(LE(std-td.td_flags));
usb_untimeout(ohci_timeout, xfer, xfer-timo_handle);
if (xfer-status == USBD_CANCELLED ||
@@ -1156,7 +1178,6 @@
xfer-status = USBD_NORMAL_COMPLETION;
usb_transfer_complete(xfer);
}
- ohci_hash_rem_td(sc, std);
ohci_free_std(sc, std);
} else {
/*
@@ -1172,16 +1193,23 @@
OHCI_TD_GET_CC(LE(std-td.td_flags)),
ohci_cc_strs[OHCI_TD_GET_CC(LE(std-td.td_flags))],
xfer));
+
+ /* Mark all the TDs in the done queue for the current
+* xfer as handled
+*/
+ for (p = stdnext; p; p = p-dnext) {
+ if (p-xfer == xfer)
+ p-flags |= OHCI_TD_HANDLED;
+ }
- /* remove TDs */
+ /* remove TDs for the current xfer from the ED */
for (p = std; p-xfer == xfer; p = n) {
n = p-nexttd;
- ohci_hash_rem_td(sc, p);
ohci_free_std(sc, p);
}
-
- /* clear halt */
opipe-sed-ed.ed_headp = LE(p-physaddr);
+
+ /* XXX why is this being done? Why not OHCI_BLF too */
OWRITE4(sc, OHCI_COMMAND_STATUS, OHCI_CLF);
if (cc == OHCI_CC_STALL)
@@ -1462,10 +1490,6 @@
/* Insert ED in schedule */
s = splusb();
- ohci_hash_add_td(sc, setup);
- if (len != 0)
- ohci_hash_add_td(sc, data);
- ohci_hash_add_td(sc, stat);
sed-ed.ed_tailp = LE(tail-physaddr);
opipe-tail.td = tail;
pcm
Just to let someone know, my ViBRA16X is still having the problem with static. Basically at random whenever xmms or any other program that uses sound opens dsp, it plays loud static instead of the actual sound. I was just wondering if anyone was looking into this problem... = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
More breakages
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel textdata bss dec hex filename 1807056 139340 115448 2061844 1f7614 kernel chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel /kernel /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 This is from a cvsup I just performed minutes ago, FYI. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More breakages
It looks like your last make world or make installworld did not complete. There is an install problem with installworld bootstrapping itself. New libraries are installed before the install binary is installed. When they try to use the "-fschg" option, you get that error. (installworld aborts at rcp with the same problem.) Simple recompile and install /usr/src/usr.bin/xinstall to fix both of these problems. Jim Bloom [EMAIL PROTECTED] Forrest Aldrich wrote: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel textdata bss dec hex filename 1807056 139340 115448 2061844 1f7614 kernel chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel /kernel /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 This is from a cvsup I just performed minutes ago, FYI. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm
Just to let someone know, my ViBRA16X is still having the problem with static. i've replicated it, but have no idea of the cause. i'll probably rework the sb driver when i rip it and the ess driver apart, but that will wait until i get an ess card. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
In article [EMAIL PROTECTED], Warner Losh [EMAIL PROTECTED] wrote: What's the current wuildworld times for a 486DX2-66 + 12M RAM over NFS? Dunno yet. I started one in late 1997 but it's still running. I'll let you know when it finishes. :-) John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
INET6 and fxp
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for FreeBSD on an OpenBSD mailinglist :-) http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html Something better than that is probably needed in the long run. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, Jan 27, 2000 at 06:53:51PM -0800, Mike Smith wrote: The only argument for having a dysfunctional hostname of the variety you describe is vanity, which is not a valid engineering constraint. Or that you're behind a dialup connection that dynamically assigns IPs. -- Giorgos Keramidas, keramida @ ceid . upatras . gr "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
_KPOSIX_VERSION=199309L in GENERIC is redundant
In revision 1.230 of src/sys/i386/conf/GENERIC, jkh added: optionsP1003_1B#Posix P1003_1B real-time extentions options_KPOSIX_PRIORITY_SCHEDULING options_KPOSIX_VERSION=199309L But I think the definition of _KPOSIX_VERSION is redundant, because it is already the default in src/sys/sys/param.h: #ifdef P1003_1B #define _P1003_1B_VISIBLE #ifndef _KPOSIX_VERSION #define _KPOSIX_VERSION 199309L #endif #endif Am I right, or am I missing something? John --- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
What's the current wuildworld times for a 486DX2-66 + 12M RAM over
NFS? I have a small box that I'd like to torture test before putting
into service and thought this would make a good week long test.
'torture test' is an understatement.
This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and
both src and obj on the same local disk (softupdates enabled):
Script started on Thu Jan 20 01:01:00 2000
backup# cd /usr/src
backup# /usr/bin/time make buildworld
--
Cleaning up the temporary elf build tree
--
mkdir -p /usr/obj/citus/src/tmp
chflags -R noschg /usr/obj/citus/src/tmp/
rm -rf /usr/obj/citus/src/tmp
...
gzip -cn /citus/src/usr.sbin/wlconfig/wlconfig.8 wlconfig.8.gz
=== etc
=== etc/sendmail
rm -f freebsd.cf
(cd /citus/src/etc/sendmail m4
-D_CF_DIR_=/citus/src/etc/sendmail/../../contrib/sendmail/cf/
/citus/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) freebsd.cf
chmod 444 freebsd.cf
54172.61 real 39360.42 user 6506.89 sys
backup#
Script done on Thu Jan 20 16:22:31 2000
Warner
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
In message [EMAIL PROTECTED] Andy Farkas writes: : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and : both src and obj on the same local disk (softupdates enabled): I'm doing this over NFS and only have 12MB of RAM. : Scriptdone on Thu Jan 20 16:22:31 2000 : Script started on Thu Jan 20 01:01:00 2000 15:21:31. Hmmm, no wonder things have been taking a while... The crypto file that's building now has been going for about 15 minutes now... I think that I'll get my whole week at this rate. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
Just imagine, too bad its not an 8086 or a 286 prolly take a month or so. Warner Losh wrote: In message [EMAIL PROTECTED] Andy Farkas writes: : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and : both src and obj on the same local disk (softupdates enabled): I'm doing this over NFS and only have 12MB of RAM. : Scriptdone on Thu Jan 20 16:22:31 2000 : Script started on Thu Jan 20 01:01:00 2000 15:21:31. Hmmm, no wonder things have been taking a while... The crypto file that's building now has been going for about 15 minutes now... I think that I'll get my whole week at this rate. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel breakage from ipfw6?
I get this whenever I try and build a kernel (with or without IPFIREWALL): linking kernel.debug ip6_fw.o: In function `ip6_fw_init': /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18a4): undefined reference to `ip6_fw_chk_ptr' /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18ae): undefined reference to `ip6_fw_ctl_ptr' *** Error code 1 1 error I've just verified my sources are up-to-date from cvsup3. Kernel config: #$Id: GENERIC,v 1.130 1998/11/03 22:01:21 des Exp $ machine i386 cpu I586_CPU ident MORDEN maxusers32 makeoptions DEBUG="-g" #Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE # Include this file in kernel options MAXMEM="(48*1024)" options COMPAT_43 options USER_LDT#allow user-level control of i386 ldt options CPU_FASTER_5X86_FPU options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION options MSGBUF_SIZE=65536 options SYSVSHM options SYSVSEM options SYSVMSG options INVARIANTS options INVARIANT_SUPPORT options MD5 options VESA# needs VM86 defined too!! options DDB options KTRACE #kernel tracing options UCONSOLE options INET#Internet communications protocols options INET6 options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_IPV6FWD #IP security tunnel for IPv6 options IPSEC_DEBUG #debug for IP security options PPP_FILTER #enable bpf filtering (needs bpfilter) options PPP_DEFLATE #PPP zlib/deflate/gzip support options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped #packets #optionsIPFILTER #optionsIPFILTER_LOG options ICMP_BANDLIM options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT#FFS usable as root device options SOFTUPDATES options NSWAPDEV=4 options MAXCONS=12 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines options COMPAT_LINUX options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options TCP_RESTRICT_RST options TCP_DROP_SYNFIN options ICMP_BANDLIM pseudo-device loop#Network loopback device pseudo-device bpf 4 #Berkeley packet filter pseudo-device tun 2 #Tunnel driver (user process ppp(8) pseudo-device ppp 2 pseudo-device pty 32 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip#Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 1 #Snoop device - to look at pty/vty/etc.. pseudo-device splash #device pnp0 device isa0 device pci0 device npx0at nexus? port IO_NPX flags 0x0 irq 13 device ata0 device atadisk0 device atapicd0 options ATA_STATIC_ID device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device scbus0 #base SCSI code device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device ahc0 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device pcm0 device sbc0 device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts device sc0 at isa? "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel breakage from ipfw6?
The problem here is that ip6_fw.c is dependent upon INET6 instead of IPv6FIREWALL. I sent mail to shin a little while ago about the problem. If you want to compile a kernel in the interim, change the line for ip6_fw.c in sys/conf/files to netinet6/ip6_fw.c optional ipv6firewall I believe this is the correct fix in any case. Jim Bloom [EMAIL PROTECTED] Kris Kennaway wrote: I get this whenever I try and build a kernel (with or without IPFIREWALL): linking kernel.debug ip6_fw.o: In function `ip6_fw_init': /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18a4): undefined reference to `ip6_fw_chk_ptr' /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18ae): undefined reference to `ip6_fw_ctl_ptr' *** Error code 1 1 error I've just verified my sources are up-to-date from cvsup3. Kernel config: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
In message [EMAIL PROTECTED] Greg Lehey writes: : I did a make world on my PDP-11 yesterday. It took less than a day. : But that's 2.11BSD. Turns out that 12MB + 30MB of swap isn't enough to build world. I ran out of swap and the machine rebooted (at least that's what I think happened, since it silently rebooted). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On Sun, Jan 30, 2000 at 02:12:45PM +1030, Greg Lehey wrote: On Saturday, 29 January 2000 at 20:04:18 -0500, TrouBle wrote: Just imagine, too bad its not an 8086 or a 286 prolly take a month or so. I did a make world on my PDP-11 yesterday. It took less than a day. ... to parse the Makefile :-) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On Saturday, 29 January 2000 at 20:48:29 -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Greg Lehey writes: : I did a make world on my PDP-11 yesterday. It took less than a day. : But that's 2.11BSD. Turns out that 12MB + 30MB of swap isn't enough to build world. I ran out of swap and the machine rebooted (at least that's what I think happened, since it silently rebooted). [123] root-- uname -a 2.11BSD pdp11.lemis.com 2.11BSD 2.11 BSD UNIX #3: Sat Mar 7 15:25:50 CST 1998 [EMAIL PROTECTED]:/usr/src/sys/GRANDPA PDP11 [124] root-- pstat -s 15/103 swapmap entries 845 kbytes swap used, 7514 kbytes free Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel breakage from ipfw6?
On Sat, 29 Jan 2000, Jim Bloom wrote: The problem here is that ip6_fw.c is dependent upon INET6 instead of IPv6FIREWALL. I sent mail to shin a little while ago about the problem. If you want to compile a kernel in the interim, change the line for ip6_fw.c in sys/conf/files to netinet6/ip6_fw.c optional ipv6firewall I believe this is the correct fix in any case. Thanks, this fixes it, but I have INET6 anyway.. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
"Chris" == Chris Costello [EMAIL PROTECTED] writes: Chris On Saturday, January 29, 2000, David Gilbert wrote: When this happens, the entire machine freezes until someone feeds the printer --- the momment it starts printing again, the computer unfreezes. ChrisCould it be a printer-specific (or printer-compatibility) Chris problem? My HP DeskJet 880C does not have that problem at all: To my mind, the printer shouldn't be able to hang the comptuer ... no matter what it does. My biggest problem is that it hangs the system. To your lack of problem, all I can say is that you might not have the conditions to notice it. To see the problem, you need the printer to fail to pick up paper (or to run out of paper) while the job is still being fed by the computer (does not count if the job is entirely within the printer when it runs out of paper). Now... I'm running LPRng, and it appears that only things printed by Samba clients (as opposed to local jobs which go through a gs filter first) hang the printer --- but this may be a red herring (that is all jobs might have the possibility to hang the printer, it's simply in our experience that lpr-submitted jobs havn't ... but then the sample of lpr jobs is very small compared to the sample of samba jobs). Regardless... the fact that the printer is hard to get working is a minor problem. The fact that it hangs the whole system is a MAJOR problem. (This is a real hard hang. Durning the hang no mouse/X response and no network (not even ping) response) When the printer is given paper, this problem disappears. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel breakage from ipfw6?
The problem here is that ip6_fw.c is dependent upon INET6 instead of IPv6FIREWALL. I sent mail to shin a little while ago about the problem. If you want to compile a kernel in the interim, change the line for ip6_fw.c in sys/conf/files to netinet6/ip6_fw.c optional ipv6firewall I believe this is the correct fix in any case. Jim Bloom [EMAIL PROTECTED] Kris Kennaway wrote: I get this whenever I try and build a kernel (with or without IPFIREWALL): Thanks for checking it! I fixed and committed it. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 and fxp
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for FreeBSD on an OpenBSD mailinglist :-) http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html Something better than that is probably needed in the long run. Yes, I am trying to repeat it in my environment. (But it doesn't necessarily happens on all card which use fxp driver. Also, seems to happen with some delicate timing...) I heard that changing driver not to use interrupt is complete fix, though I am not so good at driver issue. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
Louis A Mamakos writes:
I just put a new -current on my test machine, and watched a bunch of stuff
fall over and die due to the new C++ implementation.
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function? I fear I will be
tracking down occasional broken C++ programs for days now.
The solution I adopted is to keep the old libstdc++.so.3 and rename it
libstdc++.so.1. Then you just have to modify your executable so that
it looks for libstdc++.so.1 instead of libstdc++.so.3 (script below
:-))
Jean-Marc
#!/usr/bin/perl
if (!$ARGV[0] || $ARGV[0] eq "-h") {
print STDERR "usage: $0 file...\n";
exit 1;
}
foreach (@ARGV) {
if (! -f $_) {
print STDERR "$_: not found\n";
} else {
($s) = `file $_`;
if ($s !~ /: ELF.*dynamically linked/) {
print STDERR "$_: bad format\n$s";
} else {
@h = `objdump -h $_`;
$done = 0;
foreach $s (@h) {
if ($s =~ /dynstr/) {
edit ($_, $s);
$done = 1;
}
}
if (!$done) {
print STDERR "$_: no .dynstr section\n";
}
}
}
}
sub edit {
$f = shift;
$_ = shift;
split;
$len = hex ($_[2]);
$skip = hex ($_[5]);
if (!open (F, $f)) {
print STDERR "$f: $!\n";
return;
}
$n = sysread (F, $a, $skip);
if ($n != $skip) {
print STDERR "$f: short read\n";
return;
}
$n = sysread (F, $_, $len);
if ($n != $len) {
print STDERR "$f: short read\n";
return;
}
if (! /libstdc\+\+.so.3/) {
print STDERR "$f: libstdc++.so.3 not used\n";
return;
}
s/libstdc\+\+.so.3/libstdc++.so.1/;
if (!open (G, "$f.1")) {
print STDERR "can't create $f.1\n";
close F;
return;
}
syswrite (G, $a, $skip);
syswrite (G, $_, $len);
while ($n != 0) {
$n = sysread (F, $_, 10);
if ($n 0) {
print STDERR "$f: read error\n";
close F;
close G;
return;
}
if ($n != 0) {
$w = syswrite (G, $_, $n);
if ($n $w) {
print STDERR "$f.1: write error\n";
close F;
close G;
return;
}
}
}
close F;
close G;
system ("mv $f $f.backup mv $f.1 $f");
}
--
Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
"Sean" == Sean O'Connell [EMAIL PROTECTED] writes: Sean On 2000 Jan 29, David Gilbert opined: "Sean" == Sean O'Connell [EMAIL PROTECTED] writes: Sean lptcontrol -p I will try this. It still seems that there's a misfeature that it just doesn't work by default. Sean Yep. It is odd that it completely locks your box waiting for Sean paper. I have seen other printers which end up printing garbage Sean after this but never a locked box. That's a different problem... That problem has something to do with flow control... and I've had that happen, too. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On 30-Jan-00 Warner Losh wrote: In message [EMAIL PROTECTED] Greg Lehey writes: : I did a make world on my PDP-11 yesterday. It took less than a day. : But that's 2.11BSD. Turns out that 12MB + 30MB of swap isn't enough to build world. I ran out of swap and the machine rebooted (at least that's what I think happened, since it silently rebooted). Warner I tried on a 486dx66, 8mb 100mb swap (I forgot to take my medication that day).. At some stage I got the slient reboot aswell. So now world builds are happily crunching away on the p90 32mb which was sitting right next to it :)The p90 is actually in a NX (Neptune) chipset board, so once I source a 2nd p90 I'll be trying dual cpu builds :) /me looks at the bunch of 386 mobo's... lets not go there.. :) Kent Ibbetson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sun, 30 Jan 2000, David Gilbert wrote: "Sean" == Sean O'Connell [EMAIL PROTECTED] writes: Sean On 2000 Jan 29, David Gilbert opined: "Sean" == Sean O'Connell [EMAIL PROTECTED] writes: Sean lptcontrol -p I will try this. It still seems that there's a misfeature that it just doesn't work by default. Sean Yep. It is odd that it completely locks your box waiting for Sean paper. I have seen other printers which end up printing garbage Sean after this but never a locked box. And notice it's not for everyone. I don't know why yours locks up and mine doesn't, but my printer, in the last month, has begun to occaisonally fail to pick up a sheet of paper. It stops the print, but nothing worse than that. I haven't really investigated it, and for me, since I don't see your problem, the fix is a couple of suitably applied alcohol wipes, probably. What I'm saying is, don't start trying to over-generalize your problem. It'll make it harder for you to find, and give FreeBSD an unnecessarily bad rep over that. BTW, that lptcontrol -p means you have something wrong with your parallel interface, because it's not responding to interrupts. This often means you have some IO card you forgot (like a sound card) sitting unbeknownst to you on IRQ 7, messing up the printer. The -p means it just polls the printer to pass in new characters, instead of reacting by interrupt. If the -p thing works for you, I would go looking at hardware, myself. Sheesh. This is a FreeBSD-questions type thing, not current. That's a different problem... That problem has something to do with flow control... and I've had that happen, too. Dave. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Loader.rc: unknown command
Hi, With a new installed world I get this message at boot: \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loader.rc: unknown command
On Sun, 30 Jan 2000, Jean-Marc Zucconi wrote: Hi, With a new installed world I get this message at boot: \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? Jean-Marc Try rebuilding and re-installing the loader. - | Bosko Milekic | Coffee vector: 1.0i+1.0j+1.0k | | Email: [EMAIL PROTECTED] | Sleep vector: -1.0i-1.0j-1.0k | | WWW: http://pages.infinit.net/bmilekic/ | Resulting life: 0i+0j+0k (DNE)| - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loader.rc: unknown command
Hi, On Sun, Jan 30, 2000 at 06:28:14AM +0100, Jean-Marc Zucconi wrote: With a new installed world I get this message at boot: \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? AOLMe too!/AOL The loader.* files in /boot dont seem to be the latest ones from /usr/src/...??? -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 and fxp
On Sat, 29 Jan 2000, Mattias Pantzare wrote: If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for FreeBSD on an OpenBSD mailinglist :-) http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html Something better than that is probably needed in the long run. FWIW this doesn't happen with my card: fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40 f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found 'course I don't actually use the card for internet access, just a local lan and the occasional IPv6 testing. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: More world breakage
On 29-Jan-00 Bruce Evans wrote: On Fri, 28 Jan 2000, John Baldwin wrote: ... Solution: We need statically built install tools just like we have build tools. I think we should use the newer versions (i.e. static versions of the ones we just built under /usr/obj during buildworld that are linked against the new libraries), rather than doing some fancy footwork to Using the newer version would be even more broken, since they may be for another arch, or may just use new syscalls that don't exist in the host kernel. Hmm, ok. I think my terminology may have been poor. I meant that the new sources should have been used to build the tools, but using the existing machine headers/libraries to build the static binaries. One question though, what architecture *should* the install-tools be? Normally, one would run installworld on the target machine and not necessarily the host machine. For example, if I was cross-building an axp world on my x86 machine, then I would want to run 'make buildworld' on the x86, but would want to run 'make installworld' on the axp. Thus, the build tools in that case need to be x86 binaries, but the install tools need to be axp binaries. Of course, in that case you can't use the build machine's header files or libraries to build the install tools. Thus, you could use the headers/binaries in the source tree, except that you might then end up linking against a newer libc that needs a newer kernel to run. The other choice is to build the install tools during installworld using the target machine's headers/libraries, but then installworld would no longer be a read-only operation. :( make the existing binaries work. We already do this with the build tools. By using the newer binaries we only have to maintain one interface in our Makefiles to the install tools: whatever their current interface is in /usr/src. The build-tools are carefully built so that work in the host environment. Essentially the same thing needs to be done for installation tools. Agreed. Bruce -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On Sun, 30 Jan 2000, kibbet wrote: /me looks at the bunch of 386 mobo's... lets not go there.. :) /me looks at the stack of 386sx chips he has and wonders why no-one did 8 way SMP with these! - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 and fxp
FWIW this doesn't happen with my card: fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40 f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found 'course I don't actually use the card for internet access, just a local lan and the occasional IPv6 testing. (from what I've heard) the symptom highly depends on chip revision so you are lucky. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 and fxp
Yes, I am trying to repeat it in my environment. (But it doesn't necessarily happens on all card which use fxp driver. Also, seems to happen with some delicate timing...) I heard that changing driver not to use interrupt is complete fix, though I am not so good at driver issue. More precisely, "changing driver not to use interrupt during multicast filter setup". netbsd - fxp driver does not use interrupt during multicast filter setup so it is not affected openbsd - includes workaround in sys/net/if.c (as referenced in the thread) itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: _KPOSIX_VERSION=199309L in GENERIC is redundant
On Sat, 29 Jan 2000, John Polstra wrote: In revision 1.230 of src/sys/i386/conf/GENERIC, jkh added: optionsP1003_1B#Posix P1003_1B real-time extentions options_KPOSIX_PRIORITY_SCHEDULING options_KPOSIX_VERSION=199309L But I think the definition of _KPOSIX_VERSION is redundant, because it is already the default in src/sys/sys/param.h: That particular definition is redundant, but we really ought to support POSIX.1-1996, and this support should not be optional. The ifdefs are messy enough when it is non-optional. It's a historical accident that some parts of the support (sys/posix4) are controlled by twisty mazes of options while other, larger parts (vfs_aio) are standard. sys/posix4 was developed in an optional module which hasn't been committed to FreeBSD, and twisty options are obviously required to putting some features in the kernel a proper and some in the module. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loader.rc: unknown command
Jean-Marc Zucconi wrote: With a new installed world I get this message at boot: \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? The \ command is not working correctly, resulting in the "Loader.rc" comment being executed instead of ignored. Why? I don't have a clue. Is *ANYONE* being able to reproduce this problem? If so, please contact me ASAP, since we have almost no time to fix this before 4.0-RELEASE. Jean, I need more information about your setup. What was it running before? How did you install this new world? Did you ever touch any file in /boot? Can you give me a date of your world source? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 and fxp
On Sun, 30 Jan 2000 [EMAIL PROTECTED] wrote: FWIW this doesn't happen with my card: fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40 f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found 'course I don't actually use the card for internet access, just a local lan and the occasional IPv6 testing. (from what I've heard) the symptom highly depends on chip revision so you are lucky. As it seems it's also probably quite timing dependant too. Right now I'm glad I've only got one PCI card that is giving me a hard time. - alex who hates SIIGnificantly crappy IDE controllers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
Chuck Robey wrote: Sheesh. This is a FreeBSD-questions type thing, not current. I disagree. It is obvious that something is getting locked inside the kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his machine locked whenever the printer went out of paper, and *stayed* locked, I'd be willing to believe the problem was caused by hardware. That's not what was reported. What was reported is rather (better) explained by some kernel code waiting indefinitely for an event, while preventing anything else from executing. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
In the cross-build case, I would guess that the 'make installworld' could be run on either machine. It would depend upon which way the mounts are done. Is the host machine mounted on the target machine or the other way around. Some people strongly believe it should be one way or the other. Optimally, both cases should be handled correctly. Jim Bloom [EMAIL PROTECTED] John Baldwin wrote: Hmm, ok. I think my terminology may have been poor. I meant that the new sources should have been used to build the tools, but using the existing machine headers/libraries to build the static binaries. One question though, what architecture *should* the install-tools be? Normally, one would run installworld on the target machine and not necessarily the host machine. For example, if I was cross-building an axp world on my x86 machine, then I would want to run 'make buildworld' on the x86, but would want to run 'make installworld' on the axp. Thus, the build tools in that case need to be x86 binaries, but the install tools need to be axp binaries. Of course, in that case you can't use the build machine's header files or libraries to build the install tools. Thus, you could use the headers/binaries in the source tree, except that you might then end up linking against a newer libc that needs a newer kernel to run. The other choice is to build the install tools during installworld using the target machine's headers/libraries, but then installworld would no longer be a read-only operation. :( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 and fxp
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for FreeBSD on an OpenBSD mailinglist :-) http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html Something better than that is probably needed in the long run. Let me confirm it. Does this also fix your problem on your freebsd-current? Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loader.rc: unknown command
At 02:50 PM 1/30/00 +0900, Daniel C. Sobral wrote: Jean-Marc Zucconi wrote: With a new installed world I get this message at boot: \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? The \ command is not working correctly, resulting in the "Loader.rc" comment being executed instead of ignored. Why? I don't have a clue. Is *ANYONE* being able to reproduce this problem? If so, please contact me ASAP, since we have almost no time to fix this before 4.0-RELEASE. Jean, I need more information about your setup. What was it running before? How did you install this new world? Did you ever touch any file in /boot? Can you give me a date of your world source? I'm seeing the same thing here with current world build as of a few minutes ago. I blew away /boot/* and reinstalled fresh still the same Manfred = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Loader.rc: unknown command
On Sun, 30 Jan 2000, Daniel C. Sobral wrote: Then, please send me the same information: how did you upgrade? what did you have before? what's the date of your present world? Make installworld, dunno but it was at least a few weeks old, and the present world was built last night. Anyway... nothing can actually explain the problem reported. :-( In theory, it's impossible for such a problem to happen unless someone introduced a bug in loader/FICL (or managed to disable FICL altogether). I would vote for FICL bug, as I tried updating my "scripts" too, and that didn't solve my problem. Perhaps there's a bug in reading the file off the disk. Needless to say it works, but give that strange error/warning at the beginning. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
identcpu.c change causes panic
This commit causes my P5 to panic at boot: kato2000/01/28 23:49:03 PST Modified files: sys/i386/i386identcpu.c Log: Simplify messages of Pentium II, Pentium II Xeon, Celeron, Pentium III and Pentium III Xeon CPUs. If a CPU is one of Pentium II, Pentium II Xeon and Celeron, the message is always "Pentium II/Pentium II Xeon/Celeron". If a CPU is one of Pentium III and Pentium III Xeon, the message is always "Pentium III/Pentium III Xeon". Revision ChangesPath 1.80 +5 -12 src/sys/i386/i386/identcpu.c Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #16: Sat Jan 29 22:48:36 PST 2000 [EMAIL PROTECTED]:/usr5/src2/src/sys/compile/MORDEN Timecounter "i8254" frequency 1193593 Hz Timecounter "TSC" frequency 120041220 Hz CPU: Pentium/P54C (120.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Still problems with latest ATA
My CDROM still refuses to work with cdcontrol, although the 30-seconds of kernel spinning is now fixed. Trying to play a track gives: acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 One of my WDC's still falls back to PIO mode at boot time (see previous messages, nothing has changed). If anything has changed in the verbose boot I can provide a copy of it, otherwise all my relevant details are in the archives from previous messages.. Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
