Re: assfail
Hi! > Boots from a Samsung SSD 840EVO. Can you check smart values ? smartctl -a /dev/ada0 (or whatever drive you have) ? If it's that old, maybe the SSD wear leveling comes to its ends ? -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: assfail
On 1/09/2020 12:38 pm, Eugene Grosbein wrote: You should describe your system: OS version and disk/file system setup, It says it right there: FBSD 10.3-RELEASE-p6 Boots from a Samsung SSD 840EVO. because the screenshot shows ZFS-related assertion failure after GELI initialization, so your setup seems to be non-trivial. Setup is bog-standard. In what way could it be otherwise? Perhaps, your system experienced unclean reboot before this problem? Maybe you'll need to use "zpool import -F" or even "zpool import -F -X" for "extreem rewind" (-X is not documented). Pretty sure no unclean reboots.. although as I said, it's been giving me problems lately, Will try 'zpool import -F' Will let you know... -andyf ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: assfail
01.09.2020 8:35, Andy Farkas wrote: > My normally very reliable PC now panics in 'assfail+0x1d' > Any idea why (or what!) this is? > Imge of panic screen: https://imgur.com/1vRpkgW You should describe your system: OS version and disk/file system setup, because the screenshot shows ZFS-related assertion failure after GELI initialization, so your setup seems to be non-trivial. Perhaps, your system experienced unclean reboot before this problem? Maybe you'll need to use "zpool import -F" or even "zpool import -F -X" for "extreem rewind" (-X is not documented). ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
01.09.2020 6:50, Charles Lecklider via freebsd-stable wrote: > On 2020-08-31 21:51, Christoph Moench-Tegeder wrote: >> Given that the hardware notes >> https://www.freebsd.org/releases/11.4R/hardware.html#proc-i386 >> explicitely claim 80486 compatibility, I'd guess this was not a >> consciuous decision but a blunder which wasn't caught > > Hmm I'd assumed that each release was at least *booted* on a real > 486, but obviously not. > >> (perhaps as >> hardware of that vintage is getting rare these days. That box >> must be old enough to buy alcohol by now?). > > Yes, I first built it in 1998 IIRC; it ran Windows for a few years > (desktop, gaming) then FreeBSD from about 2002. It's been in nearly > continuous operation since, although I did have to replace the PSU last > year ;-) Just for the record, I still run AMD Geode-based FreeBSD 11.3-STABLE as my home WiFi Access Point. This fanless system has 500Mhz 32-bit only i586-class CPU, 1GB RAM (no swap), two 100M wired NICs vr0/vr1 onboard and Atheros 5212 ath0 wireless mini-PCI card (not PCI-E) that supports multiple WLANs. It has CompactFlash slot for ada0 occupied with 16GB CF card at boot device (nanobsd, r/o mounted) plus ada1 2.5" PATA HDD WDC WD2500BEVE (250G) as additional storage. Until recently is also served as PPPoE client (mpd5 kernel level) for uplink with ipfw nat being able to saturate 100MBit/s uplink connection despite of NAT+PPPoE overhead. CPU: Geode(TM) Integrated Processor by AMD PCS (499.91-MHz 586-class CPU) Origin="AuthenticAMD" Id=0x5a2 Family=0x5 Model=0xa Stepping=2 Features=0x88a93d AMD Features=0xc040 Of course, its NanoBSD image is built with CPUTYPE=i586 as well as installed packages. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
assfail
My normally very reliable PC now panics in 'assfail+0x1d' Any idea why (or what!) this is? Imge of panic screen: https://imgur.com/1vRpkgW -andyf ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
On 2020-08-31 21:51, Christoph Moench-Tegeder wrote: > Given that the hardware notes > https://www.freebsd.org/releases/11.4R/hardware.html#proc-i386 > explicitely claim 80486 compatibility, I'd guess this was not a > consciuous decision but a blunder which wasn't caught Hmm I'd assumed that each release was at least *booted* on a real 486, but obviously not. > (perhaps as > hardware of that vintage is getting rare these days. That box > must be old enough to buy alcohol by now?). Yes, I first built it in 1998 IIRC; it ran Windows for a few years (desktop, gaming) then FreeBSD from about 2002. It's been in nearly continuous operation since, although I did have to replace the PSU last year ;-) -C ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading, 11.4 -> 12.1
On 2020-08-31 16:28, Kevin Oberman wrote: > [...] > This question would be both more appropriate and more likely to get a > knowledgeable response if submitted to x11@. [...] While waiting in vain for a response, I resorted to reading /usr/ports/UPDATING and the install message for xorg-server. After installing x11-drivers/xf86-input-libinpout and making sure kern.evdev.rcpt_mask was set correctly, my problem was fixed. Let this be a lesson to me!-- George signature.asc Description: OpenPGP digital signature
Re: Cannot find announcement that min supported i386 CPU is now i686
On 2020-08-31 22:59, Eugene Grosbein wrote: > https://www.freebsd.org/releases/12.1R/relnotes.html section 11.1 discusses > the topic > in context of upcoming FreeBSD 13. And that makes sense - 12.x EOL is a few years out. > There was some discussion on the topic in the freebsd-arch mailing list about > a year ago: > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=75083+0+archive/2019/freebsd-arch/20191006.freebsd-arch Yes, and there was a commitment to an announcement in that thread too. > It seems there was no announcement on the change for 11.x branch. No, and that's the problem: had I know I'd have just compiled it up, but I didn't and now I need to rebuild it > I wonder how much RAM does your Pentium 233 MMX have and what part of the RAM > is cacheable by the chipset? :-) 512MB ECC, and all of it, at least according to the BIOS. -C ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
01.09.2020 1:00, Charles Lecklider via freebsd-stable wrote: > Having just trashed my dual Pentium 233 MMX by installing 11.4 I went > digging to find the cause - and I found it. > > As you can see from objdump below, clearly a decision was made that 11.4 > would no longer support anything before a i686. > > Ignoring for a moment the wisdom of making breaking changes to a minor > version, please could someone tell me where the announcement was made? https://www.freebsd.org/releases/12.1R/relnotes.html section 11.1 discusses the topic in context of upcoming FreeBSD 13. There was some discussion on the topic in the freebsd-arch mailing list about a year ago: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=75083+0+archive/2019/freebsd-arch/20191006.freebsd-arch It seems there was no announcement on the change for 11.x branch. I wonder how much RAM does your Pentium 233 MMX have and what part of the RAM is cacheable by the chipset? :-) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
On 2020-08-31 21:54, Warner Losh wrote: > The default is to compile for i686. That does seem to be the case for 11.4, but that wasn't the case for 11.3, and I cannot find an announcement for that change anywhere. Had I seen one ... > However, you can still roll your own if you need anything back to i486. ... that's what I would have done. -C ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
## Warner Losh (i...@bsdimp.com):
> The default is to compile for i686.
That's really not obvious from the obvious documentation.
Both Hardware Notes and the Handbook ("2.2. Minimum Hardware Requirements")
state support for 486 and up, but there's no hint that you had to
roll you own distribution set for anything below 686. Also, GENERIC's
conf on i386 has flags I486_CPU and up.
Regards,
Christoph
--
Spare Space
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
On Mon, Aug 31, 2020 at 2:51 PM Christoph Moench-Tegeder wrote: > ## Charles Lecklider via freebsd-stable (freebsd-stable@freebsd.org): > > > As you can see from objdump below, clearly a decision was made that 11.4 > > would no longer support anything before a i686. > > Given that the hardware notes > https://www.freebsd.org/releases/11.4R/hardware.html#proc-i386 > explicitely claim 80486 compatibility, I'd guess this was not a > consciuous decision but a blunder which wasn't caught (perhaps as > hardware of that vintage is getting rare these days. That box > must be old enough to buy alcohol by now?). > The default is to compile for i686. However, you can still roll your own if you need anything back to i486. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Cannot find announcement that min supported i386 CPU is now i686
## Charles Lecklider via freebsd-stable (freebsd-stable@freebsd.org): > As you can see from objdump below, clearly a decision was made that 11.4 > would no longer support anything before a i686. Given that the hardware notes https://www.freebsd.org/releases/11.4R/hardware.html#proc-i386 explicitely claim 80486 compatibility, I'd guess this was not a consciuous decision but a blunder which wasn't caught (perhaps as hardware of that vintage is getting rare these days. That box must be old enough to buy alcohol by now?). Regards, Christoph -- Spare Space ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading, 11.4 -> 12.1
On Mon, Aug 31, 2020 at 1:05 PM Kurt Jaeger wrote: > Hi! > > > > I'm guessing: Do you have the dbus and hald daemon running ? > > > > > > hald_enable="YES" > > > dbus_enable="YES" > > > > > > in /etc/rc.conf ? > > > > > Yes, I do. Should I disable them, then? -- George > > No, they are needed. > > You mentioned that you build the x11 stuff on 11.3. I do not know > if this works, I have my doubts. > > -- > p...@opsec.eu+49 171 3101372Now what ? > This question would be both more appropriate and more likely to get a knowledgeable response if submitted to x11@. X is not part of the base system although a base system upgrade did trigger the problem. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading, 11.4 -> 12.1
Hi! > > I'm guessing: Do you have the dbus and hald daemon running ? > > > > hald_enable="YES" > > dbus_enable="YES" > > > > in /etc/rc.conf ? > > > Yes, I do. Should I disable them, then? -- George No, they are needed. You mentioned that you build the x11 stuff on 11.3. I do not know if this works, I have my doubts. -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading, 11.4 -> 12.1
On 2020-08-31 15:48, Kurt Jaeger wrote: > Hi! > [...] > > I'm guessing: Do you have the dbus and hald daemon running ? > > hald_enable="YES" > dbus_enable="YES" > > in /etc/rc.conf ? > Yes, I do. Should I disable them, then? -- George signature.asc Description: OpenPGP digital signature
Re: Upgrading, 11.4 -> 12.1
On 2020-08-31 15:47, Navdeep Parhar wrote: > On 8/31/20 12:44 PM, George Mitchell wrote: >> 1. Is there a way to shut "make delete-old" up? For most minor >> upgrades, of course, it never says anything. But for an upgrade such >> as this, it forces me to type "y" upwards of a hundred times. >> All the things it's deleting look plausible to me and I've never had >> occasion to tell it NOT to delete a file. Is there a way to tell it >> to just assume "y"? > > Use "make -DBATCH_DELETE_OLD_FILES ...". See build(7) for details. > > Regards, > Navdeep > Thank you, Navdeep and Lukasz! -- George signature.asc Description: OpenPGP digital signature
Re: Upgrading, 11.4 -> 12.1
Hi! > 1. Is there a way to shut "make delete-old" up? For most minor > upgrades, of course, it never says anything. But for an upgrade such > as this, it forces me to type "y" upwards of a hundred times. I use: yes | make delete-old > Does this mean I need to provide a configuration file? Where are the > input drivers it couldn't find? Since I have so far tried the upgrade > on only one machine, the X server was compiled under 11.3: I'm guessing: Do you have the dbus and hald daemon running ? hald_enable="YES" dbus_enable="YES" in /etc/rc.conf ? -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading, 11.4 -> 12.1
W dniu 2020-08-31 o 21:44, George Mitchell pisze: > 1. Is there a way to shut "make delete-old" up? For most minor > upgrades, of course, it never says anything. But for an upgrade such > as this, it forces me to type "y" upwards of a hundred times. > All the things it's deleting look plausible to me and I've never had > occasion to tell it NOT to delete a file. Is there a way to tell it > to just assume "y"? yes | make delete-old or make delete-old -DBATCH_DELETE_OLD_FILES -- best regards, Lukasz Wasikowski ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading, 11.4 -> 12.1
On 8/31/20 12:44 PM, George Mitchell wrote: > 1. Is there a way to shut "make delete-old" up? For most minor > upgrades, of course, it never says anything. But for an upgrade such > as this, it forces me to type "y" upwards of a hundred times. > All the things it's deleting look plausible to me and I've never had > occasion to tell it NOT to delete a file. Is there a way to tell it > to just assume "y"? Use "make -DBATCH_DELETE_OLD_FILES ...". See build(7) for details. Regards, Navdeep ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Upgrading, 11.4 -> 12.1
1. Is there a way to shut "make delete-old" up? For most minor upgrades, of course, it never says anything. But for an upgrade such as this, it forces me to type "y" upwards of a hundred times. All the things it's deleting look plausible to me and I've never had occasion to tell it NOT to delete a file. Is there a way to tell it to just assume "y"? 2. I run X with no explicit configuration file, and this has gone very well so far, but not today. X starts up the display with no problem, but it can't find any input devices. The relevant part of the server log says: [16.719] (II) config/devd: probing input devices... [16.719] (II) config/devd: EVDEV_SUPPORT is enabled, ignoring device atkbd0 [16.719] (II) config/devd: detected event input: System keyboard multiplexer, bustype=0006, vendor=, product=, version= [16.719] (II) config/devd: adding input device /dev/input/event0 [16.719] (**) System keyboard multiplexer: Applying InputClass "Evdev keyboard" [16.719] (II) No input driver specified, ignoring this device. [16.719] (II) This device may have been added with another device file. [16.719] (EE) config/devd: error 1 adding device /dev/input/event0 [16.719] (II) config/devd: detected event input: System mouse, bustype=0006, vendor=, product=, version= [16.719] (II) config/devd: adding input device /dev/input/event1 [16.719] (II) No input driver specified, ignoring this device. [16.719] (II) This device may have been added with another device file. [16.719] (EE) config/devd: error 1 adding device /dev/input/event1 [16.719] (II) config/devd: detected event input: AT keyboard, bustype=0011, vendor=0001, product=0001, version= [16.719] (II) config/devd: adding input device /dev/input/event2 [16.719] (**) AT keyboard: Applying InputClass "Evdev keyboard" [16.719] (II) No input driver specified, ignoring this device. [16.719] (II) This device may have been added with another device file. [16.719] (EE) config/devd: error 1 adding device /dev/input/event2 [16.719] (II) This device may have been added with another device file. [16.719] (EE) config/devd: error 1 adding device /dev/input/event3 [16.719] (II) config/devd: EVDEV_SUPPORT is enabled, ignoring device kbdmux0 [16.719] (II) config/devd: EVDEV_SUPPORT is enabled, ignoring device sysmouse [16.719] (II) config/devd: detected USB HID of unknown type [16.719] (II) config/devd: [sysctl] usb_id: 0x046d:0xc31c [16.719] (II) config/devd: [sysctl] vendor: USB, product: Keyboard [16.719] (II) config/devd: adding input device /dev/uhid0 [16.719] (II) No input driver specified, ignoring this device. [16.719] (II) This device may have been added with another device file. [16.719] (EE) config/devd: error 1 adding device /dev/uhid0 [16.719] (II) config/devd: EVDEV_SUPPORT is enabled, ignoring device ukbd0 Does this mean I need to provide a configuration file? Where are the input drivers it couldn't find? Since I have so far tried the upgrade on only one machine, the X server was compiled under 11.3: X.Org X Server 1.20.8 X Protocol Version 11, Revision 0 [11.901] Build Operating System: FreeBSD 11.3-RELEASE-p12 amd64 [11.901] Current Operating System: FreeBSD court 12.1-RELEASE-p8 FreeBSD 12.1-RELEASE-p8 r364978 M5P amd64 [11.901] Build Date: 26 August 2020 10:56:12AM Help ...-- George signature.asc Description: OpenPGP digital signature
Cannot find announcement that min supported i386 CPU is now i686
Having just trashed my dual Pentium 233 MMX by installing 11.4 I went digging to find the cause - and I found it. As you can see from objdump below, clearly a decision was made that 11.4 would no longer support anything before a i686. Ignoring for a moment the wisdom of making breaking changes to a minor version, please could someone tell me where the announcement was made? Thanks! ~/ISO/FreeBSD-11.3/bin $ objdump -d -f ls | grep cmov ~/ISO/FreeBSD-11.3/bin $ ~/ISO/FreeBSD-11.4/bin $ objdump -d -f ls | grep cmov 804974c: 0f 48 c6cmovs %esi,%eax 8049765: 0f 48 c6cmovs %esi,%eax 80497a3: 0f 48 c6cmovs %esi,%eax 80497b5: 0f 48 c6cmovs %esi,%eax 8049807: 0f 48 cecmovs %esi,%ecx 8049818: 0f 49 f0cmovns %eax,%esi 804a303: 0f 45 d9cmovne %ecx,%ebx 804a30d: 0f 45 d9cmovne %ecx,%ebx 804a318: 0f 45 d9cmovne %ecx,%ebx 804a366: 0f 44 cbcmove %ebx,%ecx 804a3a5: 0f 49 c8cmovns %eax,%ecx 804a3da: 0f 45 cbcmovne %ebx,%ecx 804a41d: 0f 45 cbcmovne %ebx,%ecx 804a451: 0f 44 c8cmove %eax,%ecx 804a48b: 0f 45 c1cmovne %ecx,%eax 804a50d: 0f 44 c8cmove %eax,%ecx 804a55d: 0f 45 f0cmovne %eax,%esi 804a567: 0f 45 f0cmovne %eax,%esi 804af65: 0f 44 c8cmove %eax,%ecx 804ba4c: 0f 44 c1cmove %ecx,%eax 804bd24: 0f 44 f8cmove %eax,%edi 804be33: 0f 44 d1cmove %ecx,%edx 804be3e: 0f 45 d1cmovne %ecx,%edx 804c2dd: 0f 44 c8cmove %eax,%ecx 804c444: 0f 44 d8cmove %eax,%ebx 804c4b8: 0f 44 5d e4 cmove -0x1c(%ebp),%ebx 804c505: 0f 44 c1cmove %ecx,%eax 804c573: 0f 45 c8cmovne %eax,%ecx 804c5c7: 0f 47 d1cmova %ecx,%edx 804c5d0: 0f 47 c8cmova %eax,%ecx 804c6a0: 0f 44 d1cmove %ecx,%edx 804c6a5: 0f 45 d3cmovne %ebx,%edx 804c749: 0f 44 d7cmove %edi,%edx 804c74e: 0f 45 d1cmovne %ecx,%edx 804c7a4: 0f 44 f8cmove %eax,%edi 804ca2d: 0f 44 d1cmove %ecx,%edx 804ca32: 0f 45 d7cmovne %edi,%edx 804cb93: 0f 44 d6cmove %esi,%edx 804cb9e: 0f 45 d1cmovne %ecx,%edx 804cd0c: 0f 44 cacmove %edx,%ecx 804cd11: 0f 45 c8cmovne %eax,%ecx ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
