That's what I assume too. But, should normal commands really get access
to those fds?
Frank
On 09/01/13 14:06, Christos Zoulas wrote:
In article 522317ab.1020...@netbsd.org,
Frank Kardel kar...@netbsd.org wrote:
While building a release I saw in fstat that commands started from make
had many
Great,
should I make the rest if the list from my build available ?
Frank
On 10/11/13 13:18, Roy Marples wrote:
On 05/10/2013 19:10, Frank Kardel wrote:
My build is now at 6681/11478 and I see these link errors so far:
./audio/alsa-utils/.broken.html:ld: note: 'ceil' is defined in DSO
/usr
See the link problems thread for more issues and discussed/planned fixes.
Frank
On 10/13/13 00:18, Ryo ONODERA wrote:
From: Ryo ONODERA ryo...@yk.rim.or.jp, Date: Sat, 12 Oct 2013 21:56:15 +0900
(JST)
Hi,
From: Thomas Klausner w...@netbsd.org, Date: Sat, 12 Oct 2013 14:49:03 +0200
Hi!
Hi,
with a -current as of 2014-01-12 I don't see
on wm0 for 'ifconfig wm0 alias 10.200.10.2 netmask 0xff00'
a RTM_NEWADDR for 10.200.10.2 in 'route monitor'.
but I see for 'ifconfig wm0 10.200.10.2 delete':
got message of size 88 on Mon Jan 20 19:53:01 2014
RTM_DELADDR: address being
Hello Dave !
I tripped yesterday over a merge mishap concerning libntp/atouint.c and
fixed that.
It could be that this is related to what you see. Can you
checkout/recompile libntp/ and recompile ntpq?
Best regards,
Frank
On 04/02/14 00:36, Dave Tyson wrote:
I've noticed that the recent
Hi !
It seems MAP5_CM_L3INIT_SATA_CLKCTRL is inconsistently defined in
src/sys/arch/arm/omap/omap2_reg.h.
compile TISDP2420_INSTALL/obio_com.o
compile TISDP2420_INSTALL/obio_mputmr.o
compile TISDP2420_INSTALL/omap2_gpio.o
compile TISDP2420_INSTALL/obio_wdt.o
compile
Great ! Thanks - works again.
Frank
On 04/06/14 14:43, Nick Hudson wrote:
On 04/06/14 13:01, Frank Kardel wrote:
Hi,
I see a long stream of
fixup: pd
fixup: pde ... nothing to do
lines scrolling (forever?) after the initial boot kernel messages.
The boot process does not seem to make
Hi Christos !
Bringing the functionality back would be good - I have yet to find a
replacement.
Frank
On 04/24/14 14:44, Christos Zoulas wrote:
In article 5358fd54.1060...@netbsd.org,
Frank Kardel kar...@netbsd.org wrote:
Hi,
once upon a time (NetBSD 6.x and before) the command
netstat
On 04/24/14 16:56, Christos Zoulas wrote:
On Apr 24, 2:57pm, kar...@netbsd.org (Frank Kardel) wrote:
-- Subject: Re: netstat routing table (verbose) output
| Hi Christos !
|
| Bringing the functionality back would be good - I have yet to find a
| replacement.
Fixed,
christos
Thanks
On 04/24/14 20:45, Frank Kardel wrote:
On 04/24/14 16:56, Christos Zoulas wrote:
On Apr 24, 2:57pm, kar...@netbsd.org (Frank Kardel) wrote:
-- Subject: Re: netstat routing table (verbose) output
| Hi Christos !
|
| Bringing the functionality back would be good - I have yet to find
Hi,
I have two observations on 6.99.44 (amd64/evbarm) where a wm-interface
send-queue is filled to the max. sendto()-calls terminate with ENOBUFS.
net.interfaces.wm3.sndq.len = 256
net.interfaces.wm3.sndq.maxlen = 256
net.interfaces.wm3.sndq.drops = 20007
the interface status is:
wm3:
On 05/12/14 22:39, Manuel Bouyer wrote:
On Mon, May 12, 2014 at 09:56:30PM +0200, Frank Kardel wrote:
[...]
traceroute packets from outside look like the are anwsered, but ICMP ECHO is
not answered.
The interface recovers with an ifconfig wmX down/up.
While I do not know how to provoke
The recent dhcpcd version (-current around 20140927) seems to be looping
on ppp* interfaces.
Sep 28 15:14:11 Andromeda dhcpcd[3259]: ppp0: unknown carrier
Sep 28 15:14:11 Andromeda dhcpcd[3259]: ppp0: carrier_status:
Inappropriate ioctl for device
Sep 28 15:14:11 Andromeda dhcpcd[3259]: ppp0:
On 09/28/14 23:17, Roy Marples wrote:
On Sunday 28 Sep 2014 22:06:47 Roy Marples wrote:
Going to guess that ppp0 doesn't have a carrier status OR IFF_RUNNING set?
The attached patch should reduce the log spam, let me know how it works out.
Errm, this patch should do better!
Roy
Well, less
Much better now.
The busy wait loop is now gone.
Thanks !
Frank
On 09/29/14 14:03, Roy Marples wrote:
On 2014-09-29 11:33, Roy Marples wrote:
Going to guess that ppp0 doesn't have a carrier status OR
IFF_RUNNING set?
The attached patch should reduce the log spam, let me know how it
works
Hi !
I just try out -current (20141229 evbarm/earmv7hf) and see the boot
constantly looping like this:
U-Boot SPL 2014.04-10733-gea1ac32 (Nov 24 2014 - 09:46:23)
Board: Bananapi
DRAM: 1024 MiB
CPU: 96000Hz, AXI/AHB/APB: 3/2/2
spl: not an uImage at 1600
U-Boot 2014.04-10733-gea1ac32 (Nov
Spot on - work with the other port. I was just too used to the RPI.
Thank for the hint.
Best regards,
Frank
On 12/31/14 09:05, Nick Hudson wrote:
On 12/30/14 11:44, Frank Kardel wrote:
Hi,
motg0 at awinio0: OTG
motg0: interrupting at irq 70
It appears to be rebooting here - my guess
Hi,
I tried out the GENERIC kernel of current-201501242100. The good news is
that the KMS seems to work:
...
match_bootwedge: unable to read block 65 of dev dk6 (5)
boot device: sd2
root on sd2a dumps on sd2b
root file system type: ffs
kern.module.path=/stand/amd64/7.99.4/modules
drm:
On 04/20/15 11:06, k...@wide.ad.jp wrote:
Folks,
Is anybody working to support 12Gbps SAS version of LSI MegaRAID
SAS3108 based card on NetBSD-current, -7Beta, or even 6.1?
It seems that SAS3108 is supported in latest versions of OpenBSD and
FreeBSD.
-- Akira Kato
I have one of those on my
On 04/25/15 02:10, Michael van Elst wrote:
There is no safe way to identify the boot disk from information passed
by the BIOS. Here is what the MD code for x86 does: 1. BTINFO_ROOTDEVICE
3. BTINFO_BOOTDISK
a) ...
b) ...
c) bootloader passed BIOS disk number for a CD
Search for the
Using an USB-Serial adapter I experience ucb lockups in 7.99.9.
Device (from dmesg):
uslsa0 at uhub1 port 3 configuration 1 interface 0
uslsa0: Silicon Labs ELV USB-WDE1 WetterdatenempfM-CM-$nger, rev
1.10/1.00, addr 4
ucom0 at uslsa0: Silicon Labs CP210x
Symptoms:
rpi$ cu -l /dev/ttyU0 -s
On 06/03/15 21:30, Christos Zoulas wrote:
In article 20150603122110.5f267ef8@taliesin-2.local,
Harry Waddell wadd...@caravan-epub.com wrote:
On Wed, 3 Jun 2015 18:27:44 + (UTC)
chris...@astron.com (Christos Zoulas) wrote:
In article 20150603111042.4fad14b2@taliesin-2.local,
Harry Waddell
On 06/03/15 20:27, Christos Zoulas wrote:
In article 20150603111042.4fad14b2@taliesin-2.local,
Harry Waddell wadd...@caravaninfotech.com wrote:
On Tue, 2 Jun 2015 16:13:07 +0100 (BST)
Stephen Borrill net...@precedence.co.uk wrote:
Anyone working on adding support for SYMBIOS MEGARAID 3108
Hi,
I just built 2015Q1/amd64 for 7.99.16.
The good news is KMS seems to work for my ATI Radeon HD 5450.
However there seems to be quite some trouble with the X server when glx
is not disabled. For a while everything seems to work smoothly (glxgears
is fine, most glx screensavers work -
With -current as of 20160526T13Z and if_wm.c 1.410
a stuck interface is abserved on following hardware
wm1 at pci11 dev 0 function 0: Intel i82583V (rev. 0x00)
wm1: interrupting at ioapic0 pin 18
wm1: PCI-Express bus
wm1: 2048 words FLASH, version 1.10.0, Image Unique ID
wm1:
FWIW, a Lenovo W510 also panics.
Frank
On 03/05/16 16:06, Tom Ivar Helbekkmo wrote:
Taylor R Campbell writes:
I have a pretty similar machine with a pretty similar issue -- a T61p
with some kind of nvidia graphics (not sure the marketing number). If
you see something
Hi *!
I am currently observing that dhcpcd does not seem to obtain an ip
address at boot on awge0.
ifconfig shows status active, but no ip address. Shortly after the
ifconfig the ip address is optained though.
Doing ifconfig seems to get things unwedged. It looks like dhcpcd does
not
Hi !
When running a -current i386 kernel as of 20160902 (own and daily
builds) and a 7.99.16 userland the tun interface seem broken.
Data received via vtund (tty side) is seen and correctly received
(routes are recognized, tcpdump works)
Interfaces seem correctly configured:
Gateway#
Hi !
running the -current (7.99.36) with 7.99.16 userland reliably traps at:
src/sys/netinet/ip_mroute.c:1751
on an multi-homed i386 system running mrouted.
A 7.99.16 kernel survives that fine. Do we have a userland dependency or
is this a new regression from the network stack
Hi !
There has be quite some work going on for wm interfaces.
When testing current kernels I found that some time after
if_wm.c:1.347 the WOL functionality has stopped working
on my ASRock 990FX Extreme 9 wm interfaces (PHYs are down
after "shutdown -p").
Compiling if_wm.c with "options
(rtm->rtm_flags & RTF_LLINFO) continue;)?
The RTF_LLINFO is set when looking at the route monitor trace.
Best regards,
Frank
On 12/11/16 09:04, Ryota Ozaki wrote:
Hi,
Thank you for the report.
On Mon, Dec 5, 2016 at 11:47 PM, Frank Kardel <kar...@netbsd.org> wrote:
Hi !
when t
Hi !
Reverting that change (1.24->1.25) and using RTF_LLDATA instead of
RTF_LLINFO seems to solve the problem.
Is this correct or am I overlooking something?
Frank
On 12/11/16 11:38, Frank Kardel wrote:
Hi,
thanks for your reply.
As for backward compatibility: An old userland rou
ank
On 12/12/16 01:36, Ryota Ozaki wrote:
Hi,
Thank you for the investigation.
On Sun, Dec 11, 2016 at 9:08 PM, Frank Kardel <kar...@netbsd.org> wrote:
Hi !
Reverting that change (1.24->1.25) and using RTF_LLDATA instead of
RTF_LLINFO seems to solve the problem.
Is this correct or
Hi !
when trying out a -current from 20161127 (7.99.42) I see issues with routed.
On configuration of an interface address A.B.C.D/m the local network address
A.B.C.D is correctly entered with a loopback host route for the local address
in the routing table.
Also the network route via the
and possibly
recent mount update (-u) changes,
Other ideas ?
Frank
On 03/14/17 08:56, Masanobu SAITOH wrote:
Hi.
On 2017/03/14 16:36, Frank Kardel wrote:
Has anyone seen this panic recently?
Seen in -current-20170311, i386, Soekris 6501.
panic: kernel diagnostic assertion "
Has anyone seen dns dynamic updates from dhcpd working?
A previously working config (working in 7.99.71) does not seem to do dns
dynamic updates at my netbsd-8 installation.
Could this be a fall-out/regression from updating dhcpd or bind (dhcpd
relies on libdns from bind - and debugging
Hi,
has anybody had any experience with -current on the new AMD generation
like Ryzen 7 1800X? Is there any motherboard that booted up and if so
what devices were supported?
Best regards,
Frank
e missing I would have expected a 'not found'
instead of 'illegal partition'.
Did I miss something? Is the UEFI install image known to work elsewhere?
Frank
On 10/22/17 19:14, Michael van Elst wrote:
kar...@netbsd.org (Frank Kardel) writes:
booting hd0a:netbsd - starting in 0 seconds
open betb
on this machine (possibly others)
Frank
On 10/22/17 09:12, Martin Husemann wrote:
On Sat, Oct 21, 2017 at 07:11:38PM +0200, Frank Kardel wrote:
Manual transcription:
NetBSD/x86 EFI Bott (x86), Revision 1.0 (..) (from NetBSD 8.0_BETA)
Memory: 252/1971496 k
Press...
booting hd0a:netbsd - starting in 0
That may also be related with the symptoms I see when booting 8.99.9 on
amd64 while dhcpcd attempts to solicit a router - it gets stuck in route
code on psref_release() - needless to say the machine is wedged at that
point.
Frank
db{0}> mach cpu 1
using CPU 1
db{0}> bt
psref_release() at
I just got a A2SDi-2C-HLN4F on my desk.
I have not been able to boot NetBSD-current/-8 on this device with
following symptoms:
1) pxeboot is loaded successfully via network and ignored
2) loading efibootx64.efi via network work and runs - failing to access
any file systems (bad
Hi !
I just tried to upgrade from 8.99.14 to 8.99.18 (amd64).
Sadly this version does lock up (not console input, no net, no disk
activity) when running the DB phase of bacula (backup program). Seems
the intensive i/o of postgres triggers this lock up.
Unfortunately I cannot enter DDB via
I am currently collecting information on failure modes on a
Ryzen 7 1800X ASUS Crosshair Hero VI system 64Gb.
Since August 2017 this system has been unreliable to put it nicely.
Most of the time it just seemed locked up. The CPU was replaced by AMD
due to the SEGFAULT issue. Now as there is a
On 02/06/18 13:16, m...@netbsd.org wrote:
upon further reading it's probably not related but it bugs me that this
patch/similar hack is still not in.
Yes - I have been running with XSAVEOPT disable since mlelstx sent that
observation. I still have
Lockups - the Ryzen machine is difficault
Hi!
It may be a fix/safeguard for a reload prolem I discussed with rmind@
and christos@ in May 2017:
To quote my analysis:
OK, I got the time to dig into it and found the cause.
Silly me has (now had) a configuration like this:
group "a" on if1 {
ruleset "blacklistd"
...
}
group
Hi,
using -current as of 20180421 (NetBSD 8.99.14 (GENERIC) #0: Sat Apr 21
23:01:29 UTC 2018
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64)
no cloning interfaces are visible:
gateway# ifconfig -l
ixg0 ixg1 ixg2 ixg3 lo0 tun0 tun1
gateway# ifconfig -C
ifconfig:
00:34, Robert Swindells wrote:
Frank Kardel <kar...@netbsd.org> wrote:
using -current as of 20180421 (NetBSD 8.99.14 (GENERIC) #0: Sat Apr 21
23:01:29 UTC 2018
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64)
no cloning interfaces are visible:
gateway# ifconfig -
:56, Roy Marples wrote:
On 24/04/2018 08:26, Martin Husemann wrote:
On Tue, Apr 24, 2018 at 07:30:04AM +0200, Frank Kardel wrote:
syslogd has sometimes issues with /var/run/log
2018-04-24T05:13:34.542548+00:00 gateway syslogd 408 - - recvfrom()
unix
`/var/run/log': No buffer space a
On 03/21/19 07:00, John Nemeth wrote:
On Mar 21, 6:48am, Frank Kardel wrote:
}
} As I wrote, extending MTIO ioctls to support more mt commands is not a
} real issue (e. g. add access to the LOCATE command). We just need to
} decide which features are useful to support and find the time
currently sitting in my tree.
Frank
On 03/21/19 04:27, John Nemeth wrote:
On Mar 20, 8:08pm, Frank Kardel wrote:
}
} This seems to be a long standing deficiency of the driver. Looking at
} the SCSI spec it is recommended to issue a READ POSITION command
I did read a book about SCSI sometime
Hi!
I just committed fetching device specific timeout values from SCSI devices.
The benefit is that we do not abort a perfectly running SCSI commands
with device reset before its device provided timeout and thus gain
more reliability with slower devices.
The timeout values are loaded at
Hi John !
This seems to be a long standing deficiency of the driver. Looking at
the SCSI spec it is recommended to issue a READ POSITION command
get the current position. Looking at the spec and code it should be
possible to handle the SP_EOM case better with respect to the position
/20/19 21:09, Adrian Bocaniciu wrote:
On Wed, 20 Mar 2019 20:08:17 +0100
Frank Kardel wrote:
This seems to be a long standing deficiency of the driver. Looking at
the SCSI spec it is recommended to issue a READ POSITION command
get the current position. Looking at the spec and code it should
Hi Adrian!
No worries. I am just trying to separate useful features from bugs and
unnecessary deficiencies that can be fixed quickly without disturbing
APIs and compatibility.
On 03/22/19 05:54, Adrian Bocaniciu wrote:
On Thu, 21 Mar 2019 06:48:22 +0100
Frank Kardel wrote:
For Bacula
Same EFI issue here: EFI/GK208B [GeForce GT 710] gets stuck when
attempting to configure the card.
Booting via CSM or EFI and nouveau disabled gets the machine up and
nouveau works fine with acceleration in the CSM case.
Looking at the PCI configuration the main difference is that the CSM
Hi !
It was not committed as up to now. I just committed the simple fix to
-current.
I am in the middle of upgrading the positioning code so more changes may
come time permitting.
Frank
On 05/19/19 09:35, Staffan Thomén wrote:
Frank Kardel wrote:
Hi Adrian!
I just finished implementing
I tried -current with my Bananapi an had limited success:
Using the first steps copying the image armv7 and the 2018.05 u-boot I
found the u-boot load attempting to perform a dhcp boot as nothing was
found on the mmc drive in autoboot. Did I miss somethnig to set up there ?
I finally got a
mode without taking
its own capabilities into consideration.
On Wed, 1 May 2019, Frank Kardel wrote:
I tried -current with my Bananapi an had limited success:
Using the first steps copying the image armv7 and the 2018.05 u-boot
I found the u-boot load attempting to perform a dhcp boot
ttp://www.invisible.ca/arm> that has U-Boot
already applied for your board.
Hope this helps!
Jared
On May 1, 2019, at 5:07 PM, Frank Kardel <mailto:kar...@netbsd.org>> wrote:
Thanks - that got me beyond screen initialization.
but
bootm 8200 - $fdt_addr_r root=ld0a co
Hi Thomas,
glad that this is observed elsewhere.
Maybe following bugs could resonate with your observations:
kern/54207 [serious/high]:
-current locks up solidly when pkgsrc building
adapta-gtk-theme-3.95.0.11
looks like locking issue in layerfs* (nullfs). (AMD 1800X, 64GB)
I just tripped over:
pass in final pcap-filter "ip multicast or ip6 multicast"
flawlessly compiles ... but:
pass in final pcap-filter "ip broadcast"
gives in "npf validate"
/etc/npf.conf:xx:9: invalid pcap-filter(7) syntax
although man 7 pcap-filter says otherwise and tcpdump gladly
...@netbsd.org (Frank Kardel) writes:
I just tripped over:
pass in final pcap-filter "ip multicast or ip6 multicast"
flawlessly compiles ... but:
pass in final pcap-filter "ip broadcast"
gives in "npf validate"
/etc/npf.conf:xx:9: invalid pcap-filter(7) syntax
a
On 08/22/19 17:44, Michael van Elst wrote:
On Thu, Aug 22, 2019 at 04:02:43PM +0200, Frank Kardel wrote:
I found that in the mean time - thanks for looking.
That leaves me probably with no generic way in npf to detect/determine
broadcast addresses.
NPF does not seem to have PF's :network
When bulk building pkgsrc boost libs 1.71.0 fails to compile with:
In file included from /usr/include/stddef.h:37,
from /usr/include/g++/cstddef:50,
from ./boost/config/compiler/gcc.hpp:165,
from ./boost/config.hpp:39,
from
Thanks for the hint. Will rebuild with current pkgsrc.
Frank
On 11/06/19 21:49, Kamil Rytarowski wrote:
On 06.11.2019 21:03, Frank Kardel wrote:
When bulk building pkgsrc boost libs 1.71.0 fails to compile with:
In file included from /usr/include/stddef.h:37,
from /usr
Hi,
I just had fun with NetBSD 9 gpt migrate.
After creating some space at the end of an MBR partitioned disk I
invoked "gpt migrate wd0".
This shows error messages that the wedges cannot be created (errno 22 I
believe).
After that, there is a PMBR and gpt refuses any work chanting:
wd0:
hi,
While bulk building pkgsrc with 9.99.42 from Jan 25t I see
panic:kernel diagnostic assertion "curcpu()->ci_biglockcount == 0"
failed: ..kern_exit.c, line 209 kernel lock leaked
That happens every couple of thousand packages - sorry no dump (locking
against myself as expected).
Frank
Hi !
Does anybody have experience with NetBSD on Supermicro H11SSW-NT
mainboard like in 2113S-WN24RT system with an EPYC 7302P?
I assume the the BCM57416 10GE is not yet supported when looking at our
code.
Best regards,
Frank
Yepp - I had two of those also
Frank
On 02/16/20 12:27, Thomas Klausner wrote:
Hi!
I just updated -current and quite soon had a panic:
cpu1: Begin traceback...
vpanic()
kern_assert
schend_lendpri
turnstile_block
rw_vector_enter
genfs_lock
layer_bypass
VOP_LOCK
vn_lock
layerfs_root
VFS_ROOT
This is my first XEN setup so I may have misconfigured something:
I have a 4G DOM0 on a 512G System with a EPYC 7302P 16-Core Processor.
On that I configured a 400G DOMU with 12 vcpus. like this:
name = "system"
kernel = "/netbsd-XEN3_DOMU.gz"
memory = 40
cpus="all"
vcpus=4
maxvcpus=12
vif
4.0000 0.000 0.0000 0.000
0.0000 0.000 0 0 0 0 100
To me it looks more like locking issues or xen scheduling features.
It makes progress, but very very slowly.
Frank
On 03/10/20 18:14, Manuel Bouyer wrote:
On Tue, Mar 10, 2020 at 04:20:22PM +0100, Frank Kardel wrote
r 10, 2020 at 06:48:14PM +0100, Frank Kardel wrote:
[...]
To me it looks more like locking issues or xen scheduling features.
yes, that could be. does vmstat -i show anything about IPIs ?
Is the domU otherwise responsive ?
Hi Manuel !
I am running with this mornings -current and things seem to have
improved quite a bit. I see
some usable I/O performance to a DOMU load > 8 which is more like it.
Lets see how it progresses.
Frank
On 03/14/20 12:48, Manuel Bouyer wrote:
There have been scheduler-related fixes
Hi,
Running 9.99.60 XEN3_DOMU shows
[ 67264.313173] kobj_load, 444: [%M/bpfjit/bpfjit.kmod]: linker error:
out of memory
[ 67292.894143] kobj_load, 428: [%M/scsiverbose/scsiverbose.kmod]:
linker error: out of memory
and modload fails with the OOM error.
Is this an expected behavior or a
loads fail when
a certain amount or more of memory is available.
I switched to type=pvh new.
Frank
On 05/11/20 15:15, Stephen Borrill wrote:
On Fri, 8 May 2020, Manuel Bouyer wrote:
On Fri, May 08, 2020 at 02:55:10PM +0200, Frank Kardel wrote:
I checked to same kernel in an instance with m
of memory
modload: bpfjit: Cannot allocate memory
TEST-A#
So it seems to be linked to available memory.
The more you have the less you get for modload.
Frank
On 05/07/20 22:52, Manuel Bouyer wrote:
On Thu, May 07, 2020 at 09:50:18PM +0200, Frank Kardel wrote:
see here:
Alpine: 21:45 ~ [8
see any other
IPIs though.
Frank
On 03/10/20 19:52, Manuel Bouyer wrote:
On Tue, Mar 10, 2020 at 07:30:33PM +0100, Frank Kardel wrote:
No information about IPI in vmstat -i in DOM0 and DOMU.
the dom0 is not MP so I don't expect to see IPIs here.
But the domU is, so there should be IPIs here
/9.99.60/modules/pciverbose/pciverbose.kmod
Frank
On 05/07/20 17:40, Manuel Bouyer wrote:
On Thu, May 07, 2020 at 07:45:48AM +0200, Frank Kardel wrote:
Hi,
Running 9.99.60 XEN3_DOMU shows
[ 67264.313173] kobj_load, 444: [%M/bpfjit/bpfjit.kmod]: linker error: out
of memory
[ 67292.894143] kobj_load
Will test again with a newer kernel.
I forgot to mention the that DOMU is configured with memory=40.
I will also test with a lower memory value.
Frank
On 05/07/20 22:52, Manuel Bouyer wrote:
On Thu, May 07, 2020 at 09:50:18PM +0200, Frank Kardel wrote:
see here:
Alpine: 21:45 ~ [8
Yepp, Moving devpubd earlier (before mountall as that does the "zfs
mount -a" !) works.
Looks like we could refine the sequence here or pursue a variant of
devfs in the spare time :-).
Frank
On 09/28/20 19:41, Michael van Elst wrote:
kar...@kardel.name (Frank Kardel) writes:
I
Hi, is it normal that ZFS sort of forgets its cache configuration?
Given this configuration:
NAME SIZE ALLOC FREE EXPANDSZ FRAGCAP DEDUP
HEALTH ALTROOT
pool-18.94T 2.76T 6.17T - 5%30% 1.11x
ONLINE -
raidz1
Interesting - I am running 9.99.72 currently.
I was always wondering why the devices show no statistics. These are
simple gpt zfs wedges.
Any idea what is wrong there?
Frank
On 09/28/20 18:04, Michael van Elst wrote:
kar...@netbsd.org (Frank Kardel) writes:
After a boot it looks like
ever.
On Wed, Jul 8, 2020 at 9:03 AM Michael van Elst <mailto:mlel...@serpens.de>> wrote:
kar...@netbsd.org <mailto:kar...@netbsd.org> (Frank Kardel) writes:
>The next message is the setting of the maxiimum frequency which
hoses the
>RPI3B serial port spee
Using the image from
http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202007080050Z/evbarm-earmv7hf/binary/gzimg/armv7.img.gz
The bot succeeds, but after the message starting local daemons.
Setting securelevel: kern.securelevel: 0 -> 1
Starting virecover.
Starting devpubd.
Starting local
I am having trouble to get Raspberries o boot recent -current (9.99.69).
Raspberry Pi 2 Model B Rev 1.1
[ 1.030] genfb0 at simplebus1: switching to framebuffer console
[ 1.030] wsdisplay0 at genfb0 kbdmux 1: console (default, vt100
emulation)
[ 1.030] vchiq0 at simplebus1:
Thanks: RPI2 and RPI3 boot again !
Frank
On 07/19/20 13:50, Nick Hudson wrote:
On 17/07/2020 14:00, Frank Kardel wrote:
I am having trouble to get Raspberries o boot recent -current (9.99.69).
Should be fixed now with
src/sys/arch/arm/arm/armv6_start.S:1.21
src/sys/arch/arm
on the topology there can be at times route message floods.
Frank
On 01/31/21 09:33, Roy Marples wrote:
Hi Frank :)
On 31/01/2021 07:58, Frank Kardel wrote:
For example I fail to see how RTM_LOSING helps that because it won't
change
how ntpd would configure itself.
Well if I read the comment
Hi Brett !
A quick analysis leaves me to believe that the culprit is in this commit:
revision 1.234
date: 2018-03-24 09:08:19 +0100; author: mlelstv; state: Exp;
lines: +176 -134; commitid: xU4Kh6YFLfDywGvA;
branches: 1.234.2;
Use separate lock to protect internal state and
() here? */
goto out;
}
}
}
Frank
On 06/10/21 08:42, Brett Lymn wrote:
Hi Frank,
On Thu, Jun 10, 2021 at 07:45:25AM +0200, Frank Kardel wrote:
Could you check whether my suspicion that biodone() may be missing the
ststart1 function in the
It is
the patch as my machine with the tapes is remote and
has no remote console
and I don't want to brick that while being off-site.
Frank
On 06/10/21 04:53, Brett Lymn wrote:
Hi Frank,
On Wed, Jun 09, 2021 at 07:06:07PM +0200, Frank Kardel wrote:
A quick analysis leaves me to believe
Hi !
Look pretty good so far, ... can we remove following marked lines which
are already
taken care of in ststart1 complete case?
/*
* only FIXEDBLOCK devices have pending I/O or space operations.
*/
if (st->flags & ST_FIXEDBLOCKS) {
/*
Hi !
I assumed Michael was proposing a solution for the missing biodone() in
the fixed block path (though that part was missing in the patch).
We should try to fix both issues (write return code and missing biodone)
with hopefully minimal changes without sacrificing clarity and abstraction.
Hi !
ST_EOM_PENDING is set in st_interpret_sense()
- always for fixed block mode on EOM condition
- if EWARN enabled and EOM condition for variable block size
Frank.
On 06/10/21 23:59, Brett Lymn wrote:
On Thu, Jun 10, 2021 at 05:38:34PM +0200, Michael van Elst wrote:
Sorry, it
Hi !
Has anyone tried NetBSD with Lenovo ThinkPad P17 Gen 1 20SN ?
Initial digging makes me believe that the Intel integrated Graphic could
be working. NIVIDIA RTX{3,4,5}000 will probably not work.
Network should work, NVMe has a good chance also from what I could find.
Did anyone try this
Hi Jeff !
Yes, you can use wedge names.
you can configure thm like "zpool create tank raidz2 wedges/wedgename-a
wedges/wedgename-b wedges/wedgename-c wedges/wedgename-d wedges/wedgename-e"
For wedges to work you need to start devpubd (/etc/rc.conf: devpubd=YES)
before ZFS. Currently devpub
Hi Matthias !
See PR 55707
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=55707 , which
I do not considere fixed due to the pgdaemon issue. reverting arc.cto
1.20 will give you many xcalls, but the system stays more usable.
Frank
On 07/01/22 07:55, Matthias Petermann wrote:
to compile vchiq_arm.o with today's -current(2022-07-19)
/tmp//cc4Xs586.s: Assembler messages:
/tmp//cc4Xs586.s:1362: Error: selected processor does not support `dsb'
in ARM mode
/tmp//cc4Xs586.s:6689: Error: selected processor does not support `dsb'
in ARM mode
/tmp//cc4Xs586.s:6711: Error:
fixed with src/sys/external/bsd/common/include/asm/barrier.h 1.18
Frank
On 07/19/22 21:43, Frank Kardel wrote:
to compile vchiq_arm.o with today's -current(2022-07-19)
/tmp//cc4Xs586.s: Assembler messages:
/tmp//cc4Xs586.s:1362: Error: selected processor does not support
`dsb' in ARM mode
I'd vote for backing out the patch unless someone(TM) can find the
pgdaemon issue.
Best regards,
Frank
On 07/19/22 08:46, Matthias Petermann wrote:
Hello,
On 13.07.22 12:30, Matthias Petermann wrote:
I can now confirm that reverting the patch also solved my problem. Of
course I first
Hi !
Where do we collect i915 (-current) issues? We don't seem to have many
PRs in that area. I have a data point with a Thinkpad T15p where i915
almost works but has flickering dark dashes and massively delayed
keyboard input. Unfortunately I have to pass the notebook on to a college.
1 - 100 of 114 matches
Mail list logo