solved: [Re: CURRENT doesn't recognise synaptics touchpad]

orks. cheers! Michael On Thu, Mar 3, 2022 at 9:06 PM Michael Schuster wrote: > Hi all, > > I have another issue with my recent re-installation to Current: touchpad > support seems to have vanished. I know it works because the keyboard lights > up when I touch it, it also works unde

CURRENT doesn't recognise synaptics touchpad

Hi all, I have another issue with my recent re-installation to Current: touchpad support seems to have vanished. I know it works because the keyboard lights up when I touch it, it also works under linux (dual-boot), and it worked with the previous installation of FreeBSD, where I installed iichid

Error building openoffice in current

gmake[1]: Leaving directory '/usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/sw' sw deliver deliver -- version: 275594 COPY: build.lst -> /usr/ports/editors/openoffice-4/work/aoo-4.1.11/main/solver/4111/unxfbsdx.pro/inc/sw/build.lst LOG: writing /usr/ports/editors/openoffice-4/work/aoo-4.1.

Re: "linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT

to respond to myself: I bit the bullet and installed one of the latest memstick images of -CURRENT , and am back up and running - with amdgpu and drm-current, and KDE (which had stopped working for me on the previous setup a while ago). Sorry if anyone's gone to any lengths here, though I d

"linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT

Hi, I'm currently running on -CURRENT from November, though I think the message for amdgpu.ko ("kernel: linker_load_file: /boot/modules/amdgpu.ko - unsupported file type") started to appear as early as last August. Since this isn't my daily driver (yet!), I didn't noti

Re: Panic, CURRENT, yesterday

. Yet another one: ❯ more core.txt.3 borg.lerctr.org dumped core - see /var/crash/vmcore.3 Sat Feb 19 00:42:59 CST 2022 FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #56 ler/freebsd-main-changes-n253181-c140933ef40: Tue Feb 15 12:26:23 CST 2022 r...@borg.lerctr.org:/usr/obj/usr

Re: USB Disk Stalls on -current

I think I'm going to grab one of these fancy 5-disk USB 3 enclosures I see on the Internet.  ;-) Most of the consumer grade units seem to have one or more issues (no NCQ depth more than 1, loud/bad fans, hard to get a real JBOD mode, JBOD mode eats serial numbers making ID hard). I t

Re: Panic, CURRENT, yesterday

On 02/08/2022 1:51 pm, Larry Rosenman wrote: I got the following last night while doing a poudriere run as well as a full bacula backup: borg.lerctr.org dumped core - see /var/crash/vmcore.0 Mon Feb 7 23:05:48 CST 2022 FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #54 ler/freebsd

Panic, CURRENT, yesterday

I got the following last night while doing a poudriere run as well as a full bacula backup: borg.lerctr.org dumped core - see /var/crash/vmcore.0 Mon Feb 7 23:05:48 CST 2022 FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #54 ler/freebsd-main-changes-n252969-5e5fd0c788c: Sat Feb 5

Re: USB Disk Stalls on -current

On 2/6/22 10:14, Sean Bruno wrote: I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I have here at the house to provide me with a nice little NAS at home. I'm using 2x USB2 external disks as the mirror. I noted that the two USB2 disks I'm using in a mirror seem to "sta

FreeBSD guests behaving as if their boot disks have disappeared (was: USB Disk Stalls on -current)

On 06/02/2022 18:20, Warner Losh wrote: … So there's some tools you can use. For usb, there's usbdump that can get you the USB transactions. I've not used it enough to give more details here. This will let you

Re: USB Disk Stalls on -current

ximum on file reads though, but the current USB daisychaining I use isn't ideal. (Each raw disk individually give 150MB/s) The only issue I have is occasionally the main USB hub craps out, and all the disks disappear for a few seconds. When it recovers, and the OS sees the disks again, thi

Re: USB Disk Stalls on -current

On Mon, Feb 7, 2022, 12:51 AM grarpamp wrote: > Yes, some USB hw is very flaky, > but ZFS can work great on these... > > https://www.youtube.com/watch?v=7z526m1jvls > https://www.youtube.com/watch?v=dougISKs2vQ > https://vimeo.com/13758987 > https://www.youtube.com/watch?v=1zIoK_9UzHk Doesn't h

Re: USB Disk Stalls on -current

Yes, some USB hw is very flaky, but ZFS can work great on these... https://www.youtube.com/watch?v=7z526m1jvls https://www.youtube.com/watch?v=dougISKs2vQ https://vimeo.com/13758987 https://www.youtube.com/watch?v=1zIoK_9UzHk

Re: USB Disk Stalls on -current

On Sun, Feb 6, 2022 at 11:32 PM grarpamp wrote: > > Feb 6 11:56:43 alice kernel: (da0:umass-sim1:1:0:0): READ(10). CDB: 28 > > 00 36 69 02 6e 00 00 80 00 > > Feb 6 11:56:43 alice kernel: (da0:umass-sim1:1:0:0): CAM status: CCB > > request completed with an error > > Feb 6 11:56:43 alice kernel

Re: USB Disk Stalls on -current

> Feb 6 11:56:43 alice kernel: (da0:umass-sim1:1:0:0): READ(10). CDB: 28 > 00 36 69 02 6e 00 00 80 00 > Feb 6 11:56:43 alice kernel: (da0:umass-sim1:1:0:0): CAM status: CCB > request completed with an error > Feb 6 11:56:43 alice kernel: (da0:umass-sim1:1:0:0): Retrying command, > 2 more tries r

Re: USB Disk Stalls on -current

On 06/02/2022 17:14, Sean Bruno wrote: … the clanking/grinding sound of the spinning rust on my desk completely stops, the encoding of the video files stops (so its waiting for a read to complete)… On 06/02/2022 19:02, Sean Bruno wrote: … assuming that I have a fairly dodgy USB device, as th

Re: USB Disk Stalls on -current

On Sun, Feb 6, 2022 at 10:11 PM Warner Losh wrote: > > > On Sun, Feb 6, 2022 at 12:02 PM Sean Bruno wrote: > >> >> >> > >> > >> > So there's some tools you can use. For usb, there's usbdump that can >> > get you the USB transactions. I've not used it enough to give more >> details >> > here. Thi

Re: USB Disk Stalls on -current

On Sun, Feb 6, 2022 at 12:02 PM Sean Bruno wrote: > > > > > > > > So there's some tools you can use. For usb, there's usbdump that can > > get you the USB transactions. I've not used it enough to give more > details > > here. This will let you know what's going on, and when, on the USB > endpoint

Re: USB Disk Stalls on -current

So there's some tools you can use. For usb, there's usbdump that can get you the USB transactions. I've not used it enough to give more details here. This will let you know what's going on, and when, on the USB endpoint. You can also enable the CAM_IOSCHED stuff. This will allow you to get

Re: USB Disk Stalls on -current

On Sun, Feb 6, 2022 at 10:15 AM Sean Bruno wrote: > I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I > have here at the house to provide me with a nice little NAS at home. > I'm using 2x USB2 external disks as the mirror. > > I noted that the two USB2 disks I'm using in a

Re: USB Disk Stalls on -current

On 2/6/22 10:52, Mehmet Erol Sanliturk wrote: On Sun, Feb 6, 2022 at 8:15 PM Sean Bruno > wrote: I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I have here at the house to provide me with a nice little NAS at home. I'm usin

Re: USB Disk Stalls on -current

On Sun, Feb 6, 2022 at 8:15 PM Sean Bruno wrote: > I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I > have here at the house to provide me with a nice little NAS at home. > I'm using 2x USB2 external disks as the mirror. > > I noted that the two USB2 disks I'm using in a m

USB Disk Stalls on -current

I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I have here at the house to provide me with a nice little NAS at home. I'm using 2x USB2 external disks as the mirror. I noted that the two USB2 disks I'm using in a mirror seem to "stall" from time to time and its not clea

Re: randomdev hangs during initial boot of -current on Raspberry Pi

On 03.02.2022 02.06, Kyle Evans wrote: On Wed, Feb 2, 2022 at 10:50 AM Kyle Evans wrote: On Wed, Feb 2, 2022 at 3:41 AM Jesper Schmitz Mouridsen wrote: On 31.01.2022 22.20, Mark Millard wrote: Mike Karels wrote on Date: Mon, 31 Jan 2022 12:27:41 -0600 : A bisect would be rather labor

Re: randomdev hangs during initial boot of -current on Raspberry Pi

On Wed, Feb 2, 2022 at 10:50 AM Kyle Evans wrote: > > On Wed, Feb 2, 2022 at 3:41 AM Jesper Schmitz Mouridsen > wrote: > > > > > > > > On 31.01.2022 22.20, Mark Millard wrote: > > > Mike Karels wrote on > > > Date: Mon, 31 Jan 2022 12:27:41 -0600 : > > > > > >> A bisect > > >> would be rather l

Re: randomdev hangs during initial boot of -current on Raspberry Pi

On Wed, Feb 2, 2022 at 3:41 AM Jesper Schmitz Mouridsen wrote: > > > > On 31.01.2022 22.20, Mark Millard wrote: > > Mike Karels wrote on > > Date: Mon, 31 Jan 2022 12:27:41 -0600 : > > > >> A bisect > >> would be rather laborious, building a modified SD card each time, > >> even if just testing

Re: randomdev hangs during initial boot of -current on Raspberry Pi [main 74cf7cae4d22 issue]

[Forwarding to John Baldwin, who authored and comitted: https://cgit.freebsd.org/src/commit/?id=74cf7cae4d22 "softclock: Use dedicated ithreads for running callouts." Also including text from the original message: https://lists.freebsd.org/archives/freebsd-current/2022-January/0

Re: randomdev hangs during initial boot of -current on Raspberry Pi

On 31.01.2022 22.20, Mark Millard wrote: Mike Karels wrote on Date: Mon, 31 Jan 2022 12:27:41 -0600 : A bisect would be rather laborious, building a modified SD card each time, even if just testing kernel changes. Any other suggestions? Historically I've used: https://artifact.ci.freebs

Re: randomdev hangs during initial boot of -current on Raspberry Pi

Mike Karels wrote on Date: Mon, 31 Jan 2022 12:27:41 -0600 : > A bisect > would be rather laborious, building a modified SD card each time, > even if just testing kernel changes. Any other suggestions? Historically I've used: https://artifact.ci.freebsd.org/snapshot/main/?C=M&O=D and the like

randomdev hangs during initial boot of -current on Raspberry Pi

I hadn't updated my Raspberry Pi 4B running -current for a couple of months, so I booted the latest snapshot (Jan 27). It hangs when it does the "growfs" step, expanding the root partition and fs to fill the SD card. When it hangs, it prints this every 10 seconds or

14-CURRENT doesn't like it when kern.vt.splash_cpu is set to 1.

A 14-CURRENT system completely hangs in both the single and multi-user modes when kern.vt.splash_cpu=1. Did you guys notice it? 13-STABLE doesn't have this problem.

Re: My -CURRENT crashes....

On Mon, Dec 27, 2021 at 09:15:53PM +0200, Konstantin Belousov wrote: > On Mon, Dec 27, 2021 at 10:58:02AM -0800, Gleb Smirnoff wrote: > > On Mon, Dec 27, 2021 at 01:43:01PM -0500, Alexander Motin wrote: > > A> > This allows us to deduct that the callout belongs to proc subsystem and > > A> > we can

Re: My -CURRENT crashes....

On Mon, Dec 27, 2021 at 10:58:02AM -0800, Gleb Smirnoff wrote: > On Mon, Dec 27, 2021 at 01:43:01PM -0500, Alexander Motin wrote: > A> > This allows us to deduct that the callout belongs to proc subsystem and > A> > we can retrieve the proc it points to: c_lock - 0x128 = > 0xf8030521e548 > A>

Re: My -CURRENT crashes....

On Mon, Dec 27, 2021 at 01:43:01PM -0500, Alexander Motin wrote: A> > This allows us to deduct that the callout belongs to proc subsystem and A> > we can retrieve the proc it points to: c_lock - 0x128 = 0xf8030521e548 A> > It is ccache in PRS_NORMAL state. And the "tmp" in our stack frame is it

Re: My -CURRENT crashes....

On 27.12.2021 12:31, Gleb Smirnoff wrote: > On Fri, Dec 17, 2021 at 01:27:11PM -0600, Larry Rosenman wrote: > L> Can someone look at the messages I posted to -CURRENT, most recent > L> today, with random > L> Callout(?) crashes after long (>6 hour) poudriere runs?

Re: My -CURRENT crashes....

On Fri, Dec 17, 2021 at 01:27:11PM -0600, Larry Rosenman wrote: L> Can someone look at the messages I posted to -CURRENT, most recent L> today, with random L> Callout(?) crashes after long (>6 hour) poudriere runs? L> L> I have core's available. I asked Larry to obtain

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

Confirmed. The kernel at .. FreeBSD 14.0-CURRENT #0 f06f1d1fdb9: Mon Dec 20 12:24:51 EST 2021 .. boots successfully. The kernel at .. FreeBSD 14.0-CURRENT #1 553af8f1ec7: Tue Dec 21 15:16:10 EST 2021 .. fails immediately after printing something like .. Timecounters tick every 1.000 msec

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

rote: > Hi Larry, > > This looks like some use-after-free or otherwise corrupted callout > structure.  Unfortunately the backtrace does not tell what was the > callout.  When was the previous update to look what could change? > > On 10.12.2021 11:24, Larry Rosenman wrote: >&g

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

read selected. (kgdb) fr 8 No thread selected. (kgdb) On 12/10/2021 10:36 am, Alexander Motin wrote: > Hi Larry, > > This looks like some use-after-free or otherwise corrupted callout > structure. Unfortunately the backtrace does not tell what was the > callout. When was the previous upda

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

> > > > This looks like some use-after-free or otherwise corrupted callout > > structure. Unfortunately the backtrace does not tell what was the > > callout. When was the previous update to look what could change? > > > > On 10.12.2021 11:24, Larry Rosenma

Re: build failure on -current

On Fri, 17 Dec 2021 09:44:20 -0800 Chuck Tuffli wrote: > When building current from git, I keep hitting the error below. This > is with meta-mode, but I've also tried deleting the object directory. > The system also has a couple of tweaks to src-env.conf that were an > attempt

build failure on -current

When building current from git, I keep hitting the error below. This is with meta-mode, but I've also tried deleting the object directory. The system also has a couple of tweaks to src-env.conf that were an attempt to avoid building any (most?) of clang. Relevant system information: $ uname

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

14.0-CURRENT FreeBSD 14.0-CURRENT #15 main-n251537-ab639f2398b: Thu Dec  9 19:45:37 CST 2021 r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL  amd64 VMCORE *IS* available. Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12:

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

e use-after-free or otherwise corrupted callout structure. Unfortunately the backtrace does not tell what was the callout. When was the previous update to look what could change? On 10.12.2021 11:24, Larry Rosenman wrote: FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #15 main-n2

Re: CURRENT: llvm13 seem to miscompile dns/bind916 (9.16.23)

On 15 Dec 2021, at 18:44, FreeBSD User wrote: > > On Fri, 10 Dec 2021 19:41:07 +1030 > Daniel O'Connor via freebsd-current wrote: >>> On 25 Nov 2021, at 18:50, FreeBSD User wrote: ... > >>> Since then named is crashing with a mysterious segmentation f

Re: CURRENT: ZFS freezes system beyond reboot

On 15/12/2021 19:55, FreeBSD User wrote: It is spooky, if not to say "buggy", if ZFS is capable of freezing the whole box even if the essential operating system stuff is isolated on a dedicated UFS filesystem. I do not think that this is the case. Commands that do not access anything on ZFS or

L2ARC: inexplicable disappearance of cache device (was: CURRENT: ZFS freezes system beyond reboot)

On 15/12/2021 17:55, FreeBSD User wrote: … SSD, partioned into two halfes, one for ZIL, the other for L2ARC. When showing "zpool status", the RAIDZ's HDDs (Hitachi/Seagate 4 TB NAS HDD) where "online", ZIL was "online" and L2ARC device/vdev showd - nothing. … The 'nothing' aspect reminds me of

Re: CURRENT: ZFS freezes system beyond reboot

From: FreeBSD User wrote on Date: Wed, 15 Dec 2021 18:55:09 +0100 : > . . . > > It is spooky, if not to say "buggy", if ZFS is capable of freezing the whole > box even if > the essential operating system stuff is isolated on a dedicated UFS > filesystem. I would guess that, for ZFS being in u

Re: CURRENT: ZFS freezes system beyond reboot

On Mon, 13 Dec 2021 09:30:50 +0200 Andriy Gapon wrote: > On 12/12/2021 18:45, Alan Somers wrote: > > You need to look at what's causing those errors. What kind of disks > > are you using, with what HBA? It's not surprising that any access to > > ZFS hangs; that's what it's designed to do when a

Re: CURRENT: llvm13 seem to miscompile dns/bind916 (9.16.23)

On Fri, 10 Dec 2021 19:41:07 +1030 Daniel O'Connor via freebsd-current wrote: > > On 25 Nov 2021, at 18:50, FreeBSD User wrote: > > > > Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov > > 22 > > 18:17:54 CET 2021 amd64) trou

Re: CURRENT: ZFS freezes system beyond reboot

On 12/12/2021 18:45, Alan Somers wrote: You need to look at what's causing those errors. What kind of disks are you using, with what HBA? It's not surprising that any access to ZFS hangs; that's what it's designed to do when a pool is suspended. However, a pool does not have to be suspended o

Re: CURRENT: ZFS freezes system beyond reboot

On Sun, Dec 12, 2021 at 2:22 AM FreeBSD User wrote: > > Running CURRENT (FreeBSD 14.0-CURRENT #52 main-n251260-156fbc64857: Thu > Dec 2 14:45:55 CET 2021 amd64), out of the sudden the ZFS RAIDZ pool > suffered from an error: > > Solaris: WARNING: Pool 'POOL00' has en

CURRENT: ZFS freezes system beyond reboot

Running CURRENT (FreeBSD 14.0-CURRENT #52 main-n251260-156fbc64857: Thu Dec 2 14:45:55 CET 2021 amd64), out of the sudden the ZFS RAIDZ pool suffered from an error: Solaris: WARNING: Pool 'POOL00' has encountered an uncorrectable I/O failure and has been suspended. The system does n

Re: 14-current: unable to boot after upgrade (installworld)

On 2021-12-10 08:01, Michael Gmelin wrote: On 10. Dec 2021, at 16:57, Chris wrote: On 2021-12-09 05:36, Sergey V. Dyatko wrote: Hi, Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh 14-current from git,it looked like this: 1) git pull https://git.freebsd.org/src.git /usr

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

llout structure. Unfortunately the backtrace does not tell what was the callout. When was the previous update to look what could change? On 10.12.2021 11:24, Larry Rosenman wrote: FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #15 main-n251537-ab639f2398b: Thu Dec  9 19:45:37 CST 2021 

Re: Panic: Page Fault in Kernel: Yesterday's CURRENT

Hi Larry, This looks like some use-after-free or otherwise corrupted callout structure. Unfortunately the backtrace does not tell what was the callout. When was the previous update to look what could change? On 10.12.2021 11:24, Larry Rosenman wrote: > FreeBSD borg.lerctr.org 14.0-CURR

Re: 14-current: unable to boot after upgrade (installworld)

Since it was booting before, does the old loader start? I see the iKVM windo does have record menu entry, can it be used to record whole incident? rgds, toomas > чт, 9 дек. 2021 г. в 18:19, Toomas Soome : > >> >> >>> On 9. Dec 2021, at 20:06, Sergey Dyatko wrote

Panic: Page Fault in Kernel: Yesterday's CURRENT

FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #15 main-n251537-ab639f2398b: Thu Dec 9 19:45:37 CST 2021 r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL amd64 VMCORE *IS* available. Unread portion of the kernel message buffer: kernel trap 12 with

Re: 14-current: unable to boot after upgrade (installworld)

> On 10. Dec 2021, at 16:57, Chris wrote: > > On 2021-12-09 05:36, Sergey V. Dyatko wrote: >> Hi, >> Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh >> 14-current from git,it looked like this: >> 1) git pull https://git.freebsd.org/s

Re: 14-current: unable to boot after upgrade (installworld)

On 2021-12-09 05:36, Sergey V. Dyatko wrote: Hi, Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh 14-current from git,it looked like this: 1) git pull https://git.freebsd.org/src.git /usr/src 2) cd /usr/src ; make buildworld; make kernel Not sure you didn't actual

Re: CURRENT: llvm13 seem to miscompile dns/bind916 (9.16.23)

> On 25 Nov 2021, at 18:50, FreeBSD User wrote: > > Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov > 22 18:17:54 > CET 2021 amd64) troubles me with our DNS server/service. > Aproximately the same time we switched on CURRENT to the CURRENT LLV

Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress

On 12/09, Mark Johnston wrote: > On Thu, Dec 09, 2021 at 07:37:18PM +0100, Kirill Ponomarev wrote: > > On 12/08, Mark Johnston wrote: > > > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > > > Building recent 13-STABLE sources on a recent 14-CURRENT

Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress

On Thu, Dec 09, 2021 at 07:37:18PM +0100, Kirill Ponomarev wrote: > On 12/08, Mark Johnston wrote: > > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > > 14.0-CURRENT > > &

Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress

Am Wed, 8 Dec 2021 10:43:41 -0500 schrieb Mark Johnston : > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > 14.0-CURRENT #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET > > 2021

Re: 14-current: unable to boot after upgrade (installworld)

help in some way? чт, 9 дек. 2021 г. в 18:19, Toomas Soome : > > > > On 9. Dec 2021, at 20:06, Sergey Dyatko wrote: > > > > I was sure the installer did it when I reinstalled the system from > scratch. I > > can load 14-current successfully after boot via PXE and

Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress

On 12/08, Mark Johnston wrote: > On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD > > 14.0-CURRENT > > #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with > >

Re: 14-current: unable to boot after upgrade (installworld)

> On 9. Dec 2021, at 20:06, Sergey Dyatko wrote: > > I was sure the installer did it when I reinstalled the system from scratch. I > can load 14-current successfully after boot via PXE and installworld with > 13-current > now I did the following: > 1) boot from HDDs Fr

Re: 14-current: unable to boot after upgrade (installworld)

I was sure the installer did it when I reinstalled the system from scratch. I can load 14-current successfully after boot via PXE and installworld with 13-current now I did the following: 1) boot from HDDs FreeBSD 14.0-CURRENT #0 main-n251494-f953785b3df (with 'old' world) 2)run in

Re: 14-current: unable to boot after upgrade (installworld)

On Thu, Dec 9, 2021 at 7:58 AM Tomoaki AOKI wrote: > On Thu, 9 Dec 2021 13:36:10 + > "Sergey V. Dyatko" wrote: > > > Hi, > > > > Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh > > 14-current from git,it looked like th

Re: 14-current: unable to boot after upgrade (installworld)

On Thu, 9 Dec 2021 13:36:10 + "Sergey V. Dyatko" wrote: > Hi, > > Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh > 14-current from git,it looked like this: > 1) git pull https://git.freebsd.org/src.git /usr/src > 2) cd /usr/src ; make

Re: 14-current: unable to boot after upgrade (installworld)

On 09/12/2021 15:36, Sergey V. Dyatko wrote: Hi, Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh 14-current from git,it looked like this: 1) git pull https://git.freebsd.org/src.git /usr/src 2) cd /usr/src ; make buildworld; make kernel 3) shutdown -r now after that I

14-current: unable to boot after upgrade (installworld)

Hi, Yesterday I tried to upgrade old 13-current (svn rev r368473) to fresh 14-current from git,it looked like this: 1) git pull https://git.freebsd.org/src.git /usr/src 2) cd /usr/src ; make buildworld; make kernel 3) shutdown -r now after that I _successfully_ booted into 14-current and

Re: CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress

On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote: > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD 14.0-CURRENT > #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with > the > linker error shown below. > > Due to this err

CURRENT: can not build 13-STABLE: ld: error: undefined symbol: uncompress

Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD 14.0-CURRENT #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with the linker error shown below. Due to this error, no FreeBSD pkg base nor NanoBSD Image can be build. [...] cc -O2 -pipe -O3 -fno-common -I

CURRENT: llvm13 seem to miscompile dns/bind916 (9.16.23)

Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov 22 18:17:54 CET 2021 amd64) troubles me with our DNS server/service. Aproximately the same time we switched on CURRENT to the CURRENT LLVM13 version and also, after the compilation of a fresh OS with LLVM13, the upgrade

Re: 14.0-CURRENT panic in early boot

, esr 0x200 vt_conswindow() at vt_conswindow+0x10 (null)() at -0x4 (null)() at 0x0001 Uptime: 3s The full log is here: http://venus.morante.net/downloads/unibia/screenshots/freebsd/R281-T91/14-CURRENT-4082b189d2c/failed-boot1.txt On 11/18/2021 12:22 AM, Dustin Marquess wrote: I just up

Re: 14.0-CURRENT panic in early boot

Just a quick update.. A kernel built from today boots just fine, so whatever the problem was, it's already fixed :). -Dustin On Thu, Nov 18, 2021 at 3:54 PM Dustin Marquess wrote: > > It was 16 days ago, so just a tad over 2 weeks :). > > Indeed, I'll start a bisect here in a few and I'll updat

Re: 14.0-CURRENT panic in early boot

It was 16 days ago, so just a tad over 2 weeks :). Indeed, I'll start a bisect here in a few and I'll update as soon as I know. I figured I'd ask ahead of time before I did the work :). Thanks! -Dustin On Thu, Nov 18, 2021 at 12:29 PM Juraj Lutter wrote: > > > > On 18 Nov 2021, at 18:46, Karel

Re: 14.0-CURRENT panic in early boot

> On 18 Nov 2021, at 18:46, Karel Gardas wrote: > > > Completely speculating, but since you don't see ioapic's are you sure this is > just ~2 weeks old build? If not, then it may be relevant to: Bisecting would be a better approach. otis > > commit 1b7a2680fba589daf6f700565214919cb941ab56

Re: 14.0-CURRENT panic in early boot

Completely speculating, but since you don't see ioapic's are you sure this is just ~2 weeks old build? If not, then it may be relevant to: commit 1b7a2680fba589daf6f700565214919cb941ab56 Author: Jung-uk Kim Date: Thu Sep 30 16:23:21 2021 -0400 Import ACPICA 20210930 (cherry picke

14.0-CURRENT panic in early boot

I just updated a machine from a build that was ~2 weeks old. The latest commit when I built it was 2e946f87055. The system boots using UEFI, if that matters. The system is panicking pretty early in the boot, however: real memory = 137438953472 (131072 MB) avail memory = 133651496960 (127460 MB)

Re: FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

On Tue, 16 Nov 2021 at 23:22, Li-Wen Hsu wrote: > > You can use this command to list all the images built by re: > > gcloud compute images list --no-standard-images > --project=freebsd-org-cloud-dev Aside, it looks like we have many EOL images that are not marked as deprecated in the gcloud l

Re: sound on FreeBSD 14.0-CURRENT

> Hans Petter Selasky writes: > On 11/17/21 13:36, Ludovit Koren wrote: >> firefox plays via speakers > In firefox go to "about:config", then add this string: > media.cubeb.backend oss > Then restart firefox. yes, it plays via headphones thanks, lk

Re: sound on FreeBSD 14.0-CURRENT

> Jakob Alvermark writes: > On 11/17/21 11:03, Ludovit Koren wrote: >>> Hans Petter Selasky writes: >> > Hi, >> >> Still the same result... >> >> >> >> > Please show all commands you try! >> >> > Can you explain, which if these devices you want to re

Re: sound on FreeBSD 14.0-CURRENT

On 11/17/21 13:36, Ludovit Koren wrote: firefox plays via speakers In firefox go to "about:config", then add this string: media.cubeb.backend oss Then restart firefox. --HPS

Re: sound on FreeBSD 14.0-CURRENT

On 11/17/21 11:03, Ludovit Koren wrote: Hans Petter Selasky writes: > Hi, >> Still the same result... >> > Please show all commands you try! > Can you explain, which if these devices you want to receive audio > from, and which you want to transmit audio to:

Re: sound on FreeBSD 14.0-CURRENT

> Hans Petter Selasky writes: > Hi Ludovit, >> It does not work automatically on the new notebook. I suppose pcm1, >> is >> the output for the jack headphones. >> I just tried without virtual_oss, with virtual_oss, starting with -f >> /dev/dsp0; /dev/dsp1; /dev/dsp2; /

Re: sound on FreeBSD 14.0-CURRENT

On 17.11.2021 13:03, Ludovit Koren wrote: Hans Petter Selasky writes: > Hi, >> Still the same result... >> > Please show all commands you try! > Can you explain, which if these devices you want to receive audio > from, and which you want to transmit audio to:

Re: sound on FreeBSD 14.0-CURRENT

Hi Ludovit, It does not work automatically on the new notebook. I suppose pcm1, is the output for the jack headphones. I just tried without virtual_oss, with virtual_oss, starting with -f /dev/dsp0; /dev/dsp1; /dev/dsp2; /dev/dsp1.0; /dev/dsp2.0; then using virtual_oss_cmd using different devi

Re: sound on FreeBSD 14.0-CURRENT

> Hans Petter Selasky writes: > Hi, >> Still the same result... >> > Please show all commands you try! > Can you explain, which if these devices you want to receive audio > from, and which you want to transmit audio to: > pcm0: (play/rec) default > pcm1:

Re: sound on FreeBSD 14.0-CURRENT

Hi, Still the same result... Please show all commands you try! Can you explain, which if these devices you want to receive audio from, and which you want to transmit audio to: pcm0: (play/rec) default pcm1: (play) pcm2: (play) It might also be the mixer has the volume or recording

Re: FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

Thanks! That's just what I was looking for. On Tue, Nov 16, 2021 at 9:20 PM Li-Wen Hsu wrote: > > On Wed, Nov 17, 2021 at 11:56 AM Alan Somers wrote: > > > > Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and > > 13.0-RELEASE. Are there any imag

Re: FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

On Wed, Nov 17, 2021 at 11:56 AM Alan Somers wrote: > > Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and > 13.0-RELEASE. Are there any images for current snapshots, and if so > what are their names? > -Alan You can use this command to list all the ima

FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and 13.0-RELEASE. Are there any images for current snapshots, and if so what are their names? -Alan

Re: sound on FreeBSD 14.0-CURRENT

> Hans Petter Selasky writes: > On 11/16/21 20:59, Ludovit Koren wrote: >>> Hans Petter Selasky writes: >> > Hi, >> >> It is not working... >> >> Just a thought... Could not be the problem how are the apps built >> >> (chromium, firefox), i.e. which options are se

Re: sound on FreeBSD 14.0-CURRENT

On 11/16/21 20:59, Ludovit Koren wrote: Hans Petter Selasky writes: > Hi, >> It is not working... >> Just a thought... Could not be the problem how are the apps built >> (chromium, firefox), i.e. which options are set on? > No, the default should work out of the box.

Re: sound on FreeBSD 14.0-CURRENT

> Hans Petter Selasky writes: > Hi, >> It is not working... >> Just a thought... Could not be the problem how are the apps built >> (chromium, firefox), i.e. which options are set on? > No, the default should work out of the box. > What does "which virtual_oss_cmd" o

Re: sound on FreeBSD 14.0-CURRENT

>>>>> Goran Mekić writes: > On Tue, Nov 16, 2021 at 10:40:37AM +0100, Ludovit Koren wrote: >> >> Hi, >> >> I am running FreeBSD 14.0-CURRENT #0 main-n250646-c0525ab1d1c-dirty: Sat Nov 13 16:42:44 CET 2021 >>

Re: sound on FreeBSD 14.0-CURRENT

Hi, It is not working... Just a thought... Could not be the problem how are the apps built (chromium, firefox), i.e. which options are set on? No, the default should work out of the box. What does "which virtual_oss_cmd" output? Maybe /usr/local/bin is not in your PATH? regards, Can

<    1   2   3   4   5   6   7   8   9   10   >