Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
Hello Glen, On Wed, 30 May 2018 15:50:39 +, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). on Thinkpad T420s mini image boots in both UEFI and Legacy modes, but UEFI is considerably faster. > > Thanks, > > Glen > -- Best Regards. Christopher Hall. ___ 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: Suspected KBI breakage between FreeBSD 11.1-p9 and FreeBSD 11.2-BETA3
On Fri, Jun 1, 2018 at 12:19 AM, Kevin Oberman wrote: > On Thu, May 31, 2018 at 3:43 AM, Ka Ho Ng wrote: >> >> Hi folks, >> >> After an upgrade from 11.1-p9 to 11.2-BETA3, vboxdrv and nvidia no longer >> works. `kldload vboxdrv` will throw kernel panic immediately. >> >> Here are the corresponding bugzilla tickets: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 >> >> Since these two kmod work after rebuilding the package, I suspect the >> issue >> is due to KBI breakage. >> >> Could anyone take a look into the issue? >> >> Thanks, >> Ka Hothe BETA > > > This is a long-standing issue with ports that build kernel modules, > especially virtualbox-ose-kmod. nvidia has also been touched by this, though > not as often. Kernel modules are part of the kernel and often make use of > variables in the in kernel memory that are not part of the formal KBI. > (sysutils/lsof is not a kernel module, but has many of the same issues and > the documentation clearly states that the kernel sources at port build time > MUST match the running kernel.) I don't think there's really a clear guideline on categorizing what is supposed to be part of public KBI. Let's take https://groups.google.com/forum/#!topic/muc.lists.freebsd.stable/am9fSti2wQU as an example to the issue: vm_map_min/max/pmap is documented KPI and they were made to be inline routines, but they were broken due to possible layout changes in vm_map_t . In such case how are you going to define public KBI? Is the inline routine and the layout of memory structure be considered public KBI ? What if not? If there are modules that make use of non-public KBI but there exists an alternatives which is considered public KBI of course these modules should be blamed that violate the coding guidelines and common practices in FreeBSD kernel code. But in case if there either exists no corresponding public KBIs that can be used as substitution, then the public KBI set may need to be extended and the commit which tampers the layout should be reverted/fixed, same applies to the case of the routines mentioned above. > > It has long been suggested that any port that installs a kernel module be > added to PORTS_MODULES in /etc/src.conf so that they will be rebuilt > whenever a kernel is built This does not play well with packages during the > release cycle for a new FreeBSD version, as the packages for he modules will > lag behind BETA builds. The only way I see around this is to have full > kernel sources available and manually build the modules for BETA releases. > packages are rebuilt for the actual release, so this problem only impacts > systems running STABLE or CURRENT. > > Perhaps a policy of generating new packages for the small number of ports > where this is an issue for each BETA and RC would fix it of logistical > issues are tractable. > -- > 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: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
Hi, On Thu, 31 May 2018 15:37:46 +0100 tech-lists wrote: > Hello lists, > > context: 11.2-PRERELEASE #0 r333458 / ports r471194 > > with xpdf I get the following error: > > Cannot mix incompatible Qt library (version 0x50904) with this > library (version 0x50a01),Abort (core dumped) > > I seem to have both qt4-4.8.7 and qt5-5.10.1 installed. I didn't > install these directly though, seems they've been installed as > dependencies of other ports. I'm using MATE desktop. > > I've tried reinstalling xfdf via pkg and the port with the same > result. Is this a known problem/how can I fix? Have found no fix yet > from GIS, most seem to point to deleting and reinstalling everything. > > thanks, portupgrade from the ports tree will be your good friend. It will either fix all problems or at least list the problematic ports. There are some other applications in the tree which do the same. So, you are spoiled for choice to get this problem fixed. Erich ___ 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: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
On Wed, May 30, 2018 at 9:50 AM, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > > No problems with a System76 Lemur in both UEFI and non-UEFI mode. It's a SkyLake-based system. ___ 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 mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
On 31/05/2018 11:57, Rod Person wrote: I ended up having to rebuild everything single qt5 library installed on my system...pretty painful. Hi, Just to update, I fixed the problem by doing this: 1. portupgrade -f "qt4*" 2. portupgrade -f "qt5*" Hopefully others will find this useful. Thanks again for the tip. -- J. ___ 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: FreeBSD 11.2-BETA3 Kernel Panic (Page Fault) when loading kernel module "vboxdrv.ko"
See my response of a few minutes ago the another report of this issue. 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: Suspected KBI breakage between FreeBSD 11.1-p9 and FreeBSD 11.2-BETA3
On Thu, May 31, 2018 at 3:43 AM, Ka Ho Ng wrote: > Hi folks, > > After an upgrade from 11.1-p9 to 11.2-BETA3, vboxdrv and nvidia no longer > works. `kldload vboxdrv` will throw kernel panic immediately. > > Here are the corresponding bugzilla tickets: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 > > Since these two kmod work after rebuilding the package, I suspect the issue > is due to KBI breakage. > > Could anyone take a look into the issue? > > Thanks, > Ka Hothe BETA > This is a long-standing issue with ports that build kernel modules, especially virtualbox-ose-kmod. nvidia has also been touched by this, though not as often. Kernel modules are part of the kernel and often make use of variables in the in kernel memory that are not part of the formal KBI. (sysutils/lsof is not a kernel module, but has many of the same issues and the documentation clearly states that the kernel sources at port build time MUST match the running kernel.) It has long been suggested that any port that installs a kernel module be added to PORTS_MODULES in /etc/src.conf so that they will be rebuilt whenever a kernel is built This does not play well with packages during the release cycle for a new FreeBSD version, as the packages for he modules will lag behind BETA builds. The only way I see around this is to have full kernel sources available and manually build the modules for BETA releases. packages are rebuilt for the actual release, so this problem only impacts systems running STABLE or CURRENT. Perhaps a policy of generating new packages for the small number of ports where this is an issue for each BETA and RC would fix it of logistical issues are tractable. -- 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: aesni on i386 w/gcc breaks 11-STABLE kernel build
> On 30 May 2018, at 12:13 PM, Dimitry Andric wrote: > > Probably only the module should be disabled, I did this my deleting a few lines from /usr/src/sys/modules/Makefile, and everything works well now! A fully gcc-based 11-STABLE i386 machine. (The builds go SO much faster with gcc rather than clang!) So there are still two bugs: 1) I think there should be a check in /usr/src/sys/modules/Makefile for the lack of clang that disables building the aesni module. 2) Upon boot there is a progress line right at the start that still says clang 6.0.0, even though clang does not exist on the machine. This should print gcc on a system configured like mine. Here is my src.conf: WITH_GCC=1 WITH_GCC_BOOTSTRAP=1 WITHOUT_BHYVE=1 WITHOUT_CAPSICUM=1 WITHOUT_CDDL=1 WITHOUT_CLANG=1 WITHOUT_CLANG_BOOTSTRAP=1 WITHOUT_CLANG_EXTRAS=1 WITHOUT_CLANG_FULL=1 WITHOUT_CROSS_COMPILER=1 WITHOUT_DEBUG_FILES=1 WITHOUT_EXAMPLES=1 WITHOUT_HYPERV=1 WITHOUT_JAIL=1 WITHOUT_LOCALES=1 WITHOUT_PROFILE=1 WITHOUT_QUOTAS=1 WITHOUT_TESTS=1 Dan ___ 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 mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
On 31/05/2018 11:57, Rod Person wrote: I just fixed this a few week or two ago on my system. The problem is you have difference version numbers within the qt5 library, not having qt4 and qt5. Thanks for the tip. Yes, there are versions of all kinds of qt4/5 programs that are not in complete version number agreement, on this system. I don't usually run pkg installs although I think libreoffice was installed as a package. currently running portupgrade -f "qt4*" thanks again, -- J. ___ 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 mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
On Thu, 31 May 2018 15:37:46 +0100 tech-lists wrote: > Hello lists, > > context: 11.2-PRERELEASE #0 r333458 / ports r471194 > > with xpdf I get the following error: > > Cannot mix incompatible Qt library (version 0x50904) with this > library (version 0x50a01),Abort (core dumped) > > I seem to have both qt4-4.8.7 and qt5-5.10.1 installed. I didn't > install these directly though, seems they've been installed as > dependencies of other ports. I'm using MATE desktop. > > I've tried reinstalling xfdf via pkg and the port with the same > result. Is this a known problem/how can I fix? Have found no fix yet > from GIS, most seem to point to deleting and reinstalling everything. > > thanks, I just fixed this a few week or two ago on my system. The problem is you have difference version numbers within the qt5 library, not having qt4 and qt5. I ended up having to rebuild everything single qt5 library installed on my system...pretty painful. Here is the text of a reply to me from Mark Mollering, that help me to track things down. Good Luck! Wow, I literally just finished fixing this with Lumina I did a pkg info | more and noticed that, even though I upgraded the qt5 [meta] version, there are some qt5 libraries that do not, automatically, upgrade. I then did a manual pkg upgrade qt5-[package] I know i had to do dbus, x11extras, svg, and a number of others. I just kept at it, until they were all upgraded to the same release. For Lumina, specifically, I had to do a pkg delete of all of the packages for it (such as lumina-core, etc) I then did a pkg clean -a (not sure if that was necessary) and pkg install. Finally, it was back to normal. -- Rod http://www.rodperson.com You can never get enough of what you don't need. -- David Morgan ___ 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"
Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped)
Hello lists, context: 11.2-PRERELEASE #0 r333458 / ports r471194 with xpdf I get the following error: Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50a01),Abort (core dumped) I seem to have both qt4-4.8.7 and qt5-5.10.1 installed. I didn't install these directly though, seems they've been installed as dependencies of other ports. I'm using MATE desktop. I've tried reinstalling xfdf via pkg and the port with the same result. Is this a known problem/how can I fix? Have found no fix yet from GIS, most seem to point to deleting and reinstalling everything. thanks, -- J. ___ 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"
FreeBSD 11.2-BETA3 Kernel Panic (Page Fault) when loading kernel module "vboxdrv.ko"
Caused by KBI change (Does not kernel panic after rebuild) This problem is reproducible System: FreeBSD 11.2-BETA3 Runs on: Oracle VirtualBox dmesg: (recorded with script(1) + telnet(1)) ===|cut here|=== Script started on Thu May 31 19:49:21 2018 Command: telnet localhost 4997 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Copyright (c) 1992-2018 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-BETA3 #0 r334196: Fri May 25 05:32:45 UTC 2018 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) VT(efifb): resolution 1024x768 CPU: Intel(R) Core(TM) i5-4210Y CPU @ 1.50GHz (1496.61-MHz K8-class CPU) Origin="GenuineIntel" Id=0x40651 Family=0x6 Model=0x45 Stepping=1 Features=0x783fbff Features2=0x5eda220b AMD Features=0x28100800 AMD Features2=0x21 Structured Extended Features=0x2421 TSC: P-state invariant real memory = 1073479680 (1023 MB) avail memory = 994013184 (947 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard Timecounter "TSC" frequency 1496606870 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0x80ff4540, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) hpet0: iomem 0xfed0-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 cpu0: on acpi0 attimer0: port 0x40-0x43,0x50-0x53 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.00s Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: mem 0x8000-0x80ff at device 2.0 on pci0 vgapci0: Boot video device em0: port 0xc180-0xc187 mem 0x8140-0x8141 irq 19 at device 3.0 on pci0 em0: Ethernet address: 08:00:27:5e:70:df em0: netmap queues/slots: TX 1/256, RX 1/256 pcm0: port 0xc000-0xc0ff,0xc100-0xc13f irq 21 at device 5.0 on pci0 pcm0: pci0: at device 7.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xc178-0xc17f,0xc18c-0xc18f,0xc170-0xc177,0xc188-0xc18b,0xc160-0xc16f mem 0x81424000-0x81425fff at device 31.2 on pci0 ahci0: Failed to allocate MSI/MSI-x, falling back to INTx ahci0: AHCI v1.10 with 2 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ohci0: mem 0x81426000-0x81426fff at device 31.4 on pci0 usbus0 on ohci0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (115200,n,8,1) acpi_acad0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xc-0xc7fff on isa0 ppc0: cannot reserve I/O port range Timecounters tick every 10.000 msec pcm0: measured ac97 link rate at 77035 Hz usbus0: 12Mbps Full Speed USB v1.0 ada0 at ahcich1 bus 0 scbus1 target 0 lun 0 ada0: ATA-6 SATA 2.x device ada0: Serial Number VB5418cc6c-20aa28bc ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 16384MB (33554432 512 byte sectors) ugen0.1: at usbus0 uhub0: on usbus0 cd0 at ahcich0 bus 0 scbus0 target 0 lun 0 cd0: Removable CD-ROM SPC-3 SCSI device cd0: Serial Number VB0-1a2b3c4d cd0: 300.000MB/s transfers (SATA 2.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ada0p2 [rw]... Setting hostuuid: c60b9c00-49a8-47b0-89b3-332b9620fa47. Setting hostid: 0xe919aad2. Starting file system checks: /dev/ada0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p2: clean, 3522780 free (460 frags, 440290 blocks, 0.0% fragmentation) Mounting local filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat random: unblocking device. 32-bit compatibility ldconfig path: /usr/lib32 Setting hostname: TEST_KERNEL_PANIC. Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: uhub0: 12 ports with 12 removable, self powered . em0: link state changed to UP Starting Network: lo0 em0. lo0: flags=8049 metric 0 mtu 16384 options=63 inet6
Suspected KBI breakage between FreeBSD 11.1-p9 and FreeBSD 11.2-BETA3
Hi folks, After an upgrade from 11.1-p9 to 11.2-BETA3, vboxdrv and nvidia no longer works. `kldload vboxdrv` will throw kernel panic immediately. Here are the corresponding bugzilla tickets: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 Since these two kmod work after rebuilding the package, I suspect the issue is due to KBI breakage. Could anyone take a look into the issue? Thanks, Ka Ho ___ 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: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted
Hi Tested both images in both modes on: Supermicro X9SCL-F E3-1230 CPU Work perfectly Glen Barber wrote: GB> Hi, GB> GB> Could folks please help boot-test the most recent 12.0-CURRENT amd64 GB> memstick images on various hardware? Note, this is not a request to GB> install 12.0-CURRENT, only a boot-test with various system knobs GB> tweaked. GB> GB> The most recent images are available at: GB> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img GB> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img GB> GB> We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we GB> would like to get this included in the upcoming 11.2-RELEASE if the GB> change that had been committed addresses several boot issues reported GB> recently. GB> GB> Please help test, and report back (both successes and failures). GB> GB> Thanks, GB> GB> Glen GB> ___ 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"
