Re: ERRATA: 12.0-CURRENT binaries 'stat' errors.
On 14 Jun 2017, at 13:51, Jeffrey Bouquet wrote: > > ne > /usr/local/bin/ne: Undefined symbol "stat" > ktrace -di ne > /usr/local/bin/ne: Undefined symbol "stat" Be sure to exactly follow the procedure mentioned in /usr/src/UPDATING entry 20170523. My guess is that you do not have COMPAT_FREEBSD11 in your kernel configuration. If so, add that option, then rebuild and reinstall your kernel. -Dimitry signature.asc Description: Message signed with OpenPGP
ERRATA: 12.0-CURRENT binaries 'stat' errors.
ne /usr/local/bin/ne: Undefined symbol "stat" ktrace -di ne /usr/local/bin/ne: Undefined symbol "stat" I may have posted in error an 'fstat' instead, unsure, to the ports list just yesterday or so. A workaround is to use pkg.freebsd.org to attain compat11x binaries which run. This is a showstopper here otherwise as some large ports, do not build on the legacy desktop [ 2004 ] that has been updated numerous times, and for which I do not wish to reinstall. And, pkg gives conflicting messages, as pkg binaries are shown ABI v12 whereas if I do build from ports, the ports are shown as v11 ABI. Also, ABI changed: 'freebsd:12:x86:32' > 'freebsd:12:*' upgrades are requested making things so I have to lock many ports at v11 as the newer have the 'stat' or 'fstat' error. So more than one issue, I think maybe three in tandem making 'which to tackle first' even problematic. Any advices? even a binary editor to examine the /ne for 'stat' code ? Apologies for not being knowledgeable in many of the ways to code a solution or even coding... ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ATAng probe updated please test (ERRATA)
>I upgraded, and now my DVDROM (ata1-slave) is working again, but >my Plextor 8/4/32A CDRW (ata1-master) still won't probe >correctly. > >atacontrol list appears to send out the same message as before. > >dmesg & atacontrol list output attached. > >Andrew Lankford Crap, I attached the wrong file (an earlier boot). Sorry about that. Here we go again: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #23: Mon Sep 1 10:32:42 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARL5KERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc04e4000. Preloaded elf module "/boot/kernel/vesa.ko" at 0xc04e4228. Preloaded elf module "/boot/kernel/miibus.ko" at 0xc04e42d4. Preloaded elf module "/boot/kernel/if_sis.ko" at 0xc04e4380. Preloaded elf module "/boot/kernel/if_xl.ko" at 0xc04e442c. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc04e44d8. Preloaded elf module "/boot/kernel/snd_es137x.ko" at 0xc04e4584. Preloaded elf module "/boot/kernel/usb.ko" at 0xc04e4634. Preloaded elf module "/boot/kernel/ums.ko" at 0xc04e46dc. Preloaded elf module "/boot/kernel/agp.ko" at 0xc04e4784. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04e482c. Calibrating clock(s) ... i8254 clock: 1193162 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 737022114 Hz CPU: Intel Pentium III (737.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 535736320 (510 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0050b000 - 0x1f5c9fff, 520876032 bytes (127167 pages) avail memory = 515022848 (491 MB) bios32: Found BIOS32 Service Directory header at 0xc00f1430 bios32: Entry = 0xf0bf0 (c00f0bf0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xdf0 pnpbios: Found PnP BIOS data at 0xc00fc070 pnpbios: Entry = f:c0a0 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: null: random: mem: Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 10 00 53 25 2e 01 00 01 40 01 00 01 63 01 00 01 1c 01 09 01 0a 01 0b 01 0c 01 1d 01 0e 01 00 01 27 01 28 01 01 01 10 01 11 01 12 01 02 01 VESA: 20 mode(s) found VESA: v3.0, 1024k memory, flags:0x1, mode table:0xc0400c62 (122) VESA: Intel(R) 810, Intel(R) 815 Chipset Video BIOS VESA: Intel Corporation Intel(R) 810, Intel(R) 815 Chipset Hardware Version 0.0 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=11308086) pcibios: BIOS version 2.10 Using $PIR table, 10 entries at 0xc00f1360 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs slot 72540A 0x60 3 4 5 7 9 10 11 12 slot 72540B 0x61 3 4 5 7 9 10 11 12 embedded02A 0x60 3 4 5 7 9 10 11 12 embedded0 31A 0x60 3 4 5 7 9 10 11 12 embedded0 31B 0x61 3 4 5 7 9 10 11 12 embedded0 31C 0x6b 3 4 5 7 9 10 11 12 embedded0 31D 0x63 3 4 5 7 9 10 11 12 slot 1 19A 0x69 3 4 5 7 9 10 11 12 slot 1 19B 0x6a 3 4 5 7 9 10 11 12 slot 1 19C 0x6b 3 4 5 7 9 10 11 12 slot 1 19D 0x68 3 4 5 7 9 10 11 12 slot 2 1 10A 0x6a 3 4 5 7 9 10 11 12 slot 2 1 10B 0x6b 3 4 5 7 9 10 11 12 slot 2 1 10C 0x68 3 4 5 7 9 10 11 12 slot 2 1 10D 0x69 3 4 5 7 9 10 11 12 slot 3 1 11A 0x6b 3 4 5 7 9 10 11 12 slot 3 1 11B 0x68 3 4 5 7 9 10 11 12 slot 3 1 11C 0x69 3 4 5 7 9 10 11 12 slot 3 1 11D 0x6a 3 4 5 7 9 10 11 12 slot 4 1 12A 0x68 3 4 5 7 9 10 11 12 slot 4 1 12B 0x69 3 4 5 7 9 10 11 12 slot 4 1 12C 0x6a 3 4 5 7 9 10 11 12 slot 4 1 12D 0x6b 3 4 5 7 9 10 11 12 slot 5 1 13A 0x69 3 4 5 7 9 10 11 12 slot 5 1 13B 0x6a 3 4 5 7 9 10 11 12 slot 5 1 13C 0x6b 3 4 5 7 9 10 11 12 slot 5 1 13D 0x68 3 4 5 7 9 10 11 12 slot 6 1 14A 0x62 3 4 5 7 9 10 11 12 slot 6 1 14B 0x63 3 4 5 7 9 10 11 12 slot 6 1 14C 0x60 3 4 5 7 9 10 11 12 slot 6 1 14D 0x61 3 4 5 7 9 10 11 12 embedded18A 0x68 3 4 5 7 9 10 11 12 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 3, max = 786, width = 783 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks BAD min =
Re: re current errata info for os-4.2
In the last episode (Jul 28), MR. C. WILLIAM HURST said: > How do I the curent errata text data for my version-4.2 of freebsd? > thanks There were no errata for 4.2 at the time 4.3 was released. You can probably consider all security advisories for 4.[3456] to apply to 4.2, though: http://www.freebsd.org/releases/4.3R/errata.html http://www.freebsd.org/releases/4.4R/errata.html http://www.freebsd.org/releases/4.5R/errata.html http://www.freebsd.org/releases/4.6R/errata.html -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
re current errata info for os-4.2
How do I the curent errata text data for my version-4.2 of freebsd? thanks C Hurst
Errata
PLIS ERRATA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenBSD errata 008 also applies to FreeBSD
> > It appears msdosfs is using a vnode after having released its reference on > > it, which could lead to a bad things under high load. I've patched the > > OpenBSD errata to apply cleanly to FreeBSD. > > Yes, I remember you bringing this up a while back. I don't see anything > wrong with the patch, and the last time I applied it and tested it my > box stopped panicing under a test. :) ISTR having made it available from home.eunet.no/~mbendiks as well, together with some other patches. I was planning on submitting them to the PR system RSN. Marius To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenBSD errata 008 also applies to FreeBSD
On Fri, Jul 07, 2000, Marius Bendiksen wrote: > It appears msdosfs is using a vnode after having released its reference on > it, which could lead to a bad things under high load. I've patched the > OpenBSD errata to apply cleanly to FreeBSD. Yes, I remember you bringing this up a while back. I don't see anything wrong with the patch, and the last time I applied it and tested it my box stopped panicing under a test. :) Adrian -- Adrian Chadd"The main reason Santa is so jolly is <[EMAIL PROTECTED]> because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OpenBSD errata 008 also applies to FreeBSD
It appears msdosfs is using a vnode after having released its reference on
it, which could lead to a bad things under high load. I've patched the
OpenBSD errata to apply cleanly to FreeBSD.
--- msdosfs_vnops.c.origMon Jun 26 06:10:40 2000
+++ msdosfs_vnops.c Mon Jun 26 07:10:17 2000
@@ -1095,9 +1095,9 @@
newparent = 1;
vrele(fdvp);
if (doingdirectory && newparent) {
if (error) /* write access check above */
- goto bad;
+ goto bad1;
if (xp != NULL)
vput(tvp);
/*
* doscheckpath() vput()'s dp,
@@ -1123,22 +1123,22 @@
*/
if (xp->de_Attributes & ATTR_DIRECTORY) {
if (!dosdirempty(xp)) {
error = ENOTEMPTY;
- goto bad;
+ goto bad1;
}
if (!doingdirectory) {
error = ENOTDIR;
- goto bad;
+ goto bad1;
}
cache_purge(tdvp);
} else if (doingdirectory) {
error = EISDIR;
- goto bad;
+ goto bad1;
}
error = removede(dp, xp);
if (error)
- goto bad;
+ goto bad1;
vput(tvp);
xp = NULL;
}
@@ -1148,9 +1148,9 @@
* file/directory.
*/
error = uniqdosname(VTODE(tdvp), tcnp, toname);
if (error)
- goto abortit;
+ goto bad1;
/*
* Since from wasn't locked at various places above,
* have to do a relookup here.
@@ -1189,9 +1189,8 @@
if (xp != ip) {
if (doingdirectory)
panic("rename: lost dir entry");
vrele(ap->a_fvp);
- VOP_UNLOCK(fvp, 0, p);
if (newparent)
VOP_UNLOCK(fdvp, 0, p);
xp = NULL;
} else {
@@ -1214,9 +1213,8 @@
if (error) {
bcopy(oldname, ip->de_Name, 11);
if (newparent)
VOP_UNLOCK(fdvp, 0, p);
- VOP_UNLOCK(fvp, 0, p);
goto bad;
}
ip->de_refcnt++;
zp->de_fndoffset = from_diroffset;
@@ -1224,9 +1222,8 @@
if (error) {
/* XXX should really panic here, fs is corrupt */
if (newparent)
VOP_UNLOCK(fdvp, 0, p);
- VOP_UNLOCK(fvp, 0, p);
goto bad;
}
if (!doingdirectory) {
error = pcbmap(dp, de_cluster(pmp, to_diroffset), 0,
@@ -1234,9 +1231,8 @@
if (error) {
/* XXX should really panic here, fs is corrupt */
if (newparent)
VOP_UNLOCK(fdvp, 0, p);
- VOP_UNLOCK(fvp, 0, p);
goto bad;
}
if (ip->de_dirclust == MSDOSFSROOT)
ip->de_diroffset = to_diroffset;
@@ -1263,9 +1259,8 @@
NOCRED, &bp);
if (error) {
/* XXX should really panic here, fs is corrupt */
brelse(bp);
- VOP_UNLOCK(fvp, 0, p);
goto bad;
}
dotdotp = (struct direntry *)bp->b_data + 1;
putushort(dotdotp->deStartCluster, dp->de_StartCluster);
@@ -1273,21 +1268,21 @@
putushort(dotdotp->deHighClust, dp->de_StartCluster >> 16);
error = bwrite(bp);
if (error) {
/* XXX should really panic here, fs is corrupt */
- VOP_UNLOCK(fvp, 0, p);
goto bad;
}
}
- VOP_UNLOCK(fvp, 0, p);
bad:
+ VOP_UNLOCK(fvp, 0, p);
+ vrele(fdvp);
+bad1:
if (xp)
vput(tvp);
vput(tdvp);
out:
ip->de_flag &= ~DE_RENAME;
- vrele(fdvp);
vrele(fvp);
return (error);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ERRATA on the 4.0-20000307-CURRENT release candidate (#3)
There were a couple of sysinstall related bogons, one related to variable toggling in rc.conf and another related to the crypto distribution (it was still looking in des/). Both of these have been fixed and rolled into the updated boot floppies as well as the ISO images, which are still uploading. The next errata item has to do with the rsaref package, which will not display its license properly when added through sysinstall. I understand the problem and am working on a fix right now. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ERRATA NOTICE: FreeBSD 3.1-RELEASE
At 6:00 am -0700 17/3/99, freebsd-errata-upd...@roguetrader.com wrote: >** >** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE ** >** >[etc] Er, why is this sent to -current? I would have thought this is -announce material. -- Bob Bishop (0118) 977 4017 international code +44 118 r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
ERRATA NOTICE: FreeBSD 3.1-RELEASE
** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE ** ** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.1-RELEASE/ERRATA.TXT The last update was sent: Sat Mar 13 03:20:55 1999 This update is sent: Wed Mar 17 06:00:48 1999 -- SYSTEM ERRATA INFORMATION: o DOS installation fails when you actually follow the instructions to install stuff under C:\FREEBSD\BIN\... and so on. Fix: The instructions are correct but the code was wrong in 3.1-RELEASE, sysinstall looking instead directly under C:\ (e.g. C:\BIN\...) or under C:\RELEASES\ (C:\RELEASES\BIN\... and so on). Fixed in 3.1-STABLE. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
ERRATA NOTICE: FreeBSD 3.1-RELEASE
** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE ** ** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.1-RELEASE/ERRATA.TXT The last update was sent: Mon Feb 15 17:42:32 1999 This update is sent: Sat Mar 13 06:00:32 1999 -- SYSTEM ERRATA INFORMATION: o Kernel change information is not saved in the new kernel, even though this is claimed to work in the docs. Fix: The change information is being written out, in fact, but to the wrong location. move /kernel.config to /boot/kernel.conf (if it exists, otherwise there were no changes to save) and add the following lines to /boot/loader.rc: load /kernel load -t userconfig_script /boot/kernel.conf autoboot 5 This will cause the kernel change information to be read in and used properly (and you just learned a little about the new 3-stage loader in the process, so the exercise wasn't a total loss). To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
