Hi,
On Wed, Dec 06, 2023 at 09:52:54AM +0100, Reinoud Zandijk wrote:
> On Mon, Dec 04, 2023 at 04:15:39PM +0100, Reinoud Zandijk wrote:
> > On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> > > my old videocard died and I replaced it with a slightly newer one b
Hi,
On Wed, Dec 06, 2023 at 09:52:54AM +0100, Reinoud Zandijk wrote:
> On Mon, Dec 04, 2023 at 04:15:39PM +0100, Reinoud Zandijk wrote:
> > On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> > > my old videocard died and I replaced it with a slightly newer one b
Hi,
On Wed, Dec 06, 2023 at 09:52:54AM +0100, Reinoud Zandijk wrote:
> On Mon, Dec 04, 2023 at 04:15:39PM +0100, Reinoud Zandijk wrote:
> > On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> > > my old videocard died and I replaced it with a slightly newer one b
Hi,
On Wed, Dec 06, 2023 at 09:52:54AM +0100, Reinoud Zandijk wrote:
> On Mon, Dec 04, 2023 at 04:15:39PM +0100, Reinoud Zandijk wrote:
> > On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> > > my old videocard died and I replaced it with a slightly newer one b
On Mon, Dec 04, 2023 at 04:15:39PM +0100, Reinoud Zandijk wrote:
> On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> > my old videocard died and I replaced it with a slightly newer one but it
> > isn't
> > recognized and nothing other than vga0 attaches. I
On Tue, Jun 23, 2020 at 01:26:21PM +0200, Reinoud Zandijk wrote:
> Hi folks,
>
> my old videocard died and I replaced it with a slightly newer one but it isn't
> recognized and nothing other than vga0 attaches. Its an Gigabyte Radeon RX460
> with 2 GB ram.
>
> 002:00:0: AT
Hi,
On Thu, Oct 19, 2023 at 11:20:02AM +0200, Mateusz Guzik wrote:
> Running 20 find(1) instances, where each has a "private" tree with
> million of files runs into trouble with the kernel killing them (and
> others):
> [ 785.194378] UVM: pid 1998.1998 (find), uid 0 killed: out of swap
> [
Hi,
On Mon, Jun 26, 2023 at 06:13:17PM -0400, Theodore Preduta wrote:
> Is it possible to create a vnode for a regular file in a file system without
> linking the vnode to any directory, so that it disappears when all open file
> descriptors to it are closed? (As far as I can tell, this isn't
Dear Brian,
On Wed, Mar 22, 2023 at 12:21:41PM -0700, Brian Buhrow wrote:
> Hello. Recently I saw a panic on two different 9.2_stable machines
> involving the
> filesystem. The two machines in question are virtual machines, running under
> Xen, but I don't
> think that's relevant here.
Oops, wrong list, sorry. Although its supposed to compile on NetBSD 9.3 I
still wonder if this really is a good idea.
On Wed, Jan 18, 2023 at 01:28:12PM +0100, Reinoud Zandijk wrote:
> Hi folks,
>
> will this create an issue worthy of reporting to qemu?
>
> With reg
, "Daniel P. Berrangé" , Thomas Huth
,
Ira Weiny , Paolo Bonzini ,
Kamil Rytarowski , Reinoud Zandijk ,
Jonathan
Cameron
Subject: Re: [PATCH v3 0/6] qemu/bswap: Use compiler __builtin_bswap()
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbi
Hi,
On Fri, Sep 23, 2022 at 03:51:26PM +0200, Patryk wrote:
> is this item already developed in netBSD or should I start looking into it ?
> https://wiki.netbsd.org/projects/project/ffs-fallocate/
AFAIK, its not implemented yet in NetBSD. I guess it got a bit on the back
burner due to the
On Mon, Jun 06, 2022 at 09:12:58AM -0400, Mouse wrote:
> > It sortof have to. Since if you've done various work, and others
> > have done various work on the same files, and both have done commits,
> > it might not be possible to merge as is.
>
> Yes, merging can require manual assistance. git
On Tue, Mar 22, 2022 at 06:17:50PM +0100, Rhialto wrote:
> On Sun 20 Mar 2022 at 23:17:57 -0400, Mouse wrote:
> > clang is - or at least was last I checked - under the impression that
> > nested functions are little-used and thus are not worth supporting.
>
> I guess they can think so because
Hi Mario,
On Tue, Jan 11, 2022 at 11:05:54PM +0100, Mario Marietto wrote:
> I'm trying to create a small group of developers to work on adding the VT-D
> support for NVMM. I would like to create a mixed group : a bhyve
> developer,a DFLY developer and a NetBSD developer,since the NVMM code is
>
On Tue, Dec 14, 2021 at 05:52:54PM -0500, Michael Pratt wrote:
> On Tue, Dec 14, 2021 at 1:06 PM Michael Pratt wrote:
> >
> > [This is a reply to
> > https://mail-index.netbsd.org/tech-kern/2021/12/01/msg027830.html. I
> > just joined the mailing list and can't seem to find the metadata
> >
On Mon, Oct 03, 2011 at 04:02:16PM -0400, Mouse wrote:
> One of my correspondents at work has exactly this problem when I send
> nicely formatted text.
>
> > This is, admittedly, less evil than the Android mail client's
> > unalterable behavior of base64-encoding *all* message data, even that
> >
On Mon, Oct 03, 2011 at 02:36:37PM -0400, Thor Lancelot Simon wrote:
> On Mon, Oct 03, 2011 at 11:31:17AM -0700, Erik Fair wrote:
> >
> > On Oct 3, 2011, at 00:56 , Mouse wrote:
> >
> > > [Do you really mean to use paragraph-length lines? I'd suggest against
> > > it; they impair readability
On Fri, Jun 24, 2011 at 04:39:13PM +, David Holland wrote:
> On Fri, Jun 24, 2011 at 11:33:51AM -0400, der Mouse wrote:
> > >> Oh, I was talking about current NetBSD where block devices are a
> > >> second class citizen, soon to be abolished if someone finds enough
> > >> round tuits.
> >
Hi Chris,
On Wed, Dec 16, 2020 at 01:08:23AM -0800, Chris Hanson wrote:
> NetBSD could also use a VirtIO console device, since that’s all
> Virtualization.framework offers on macOS 11 (whether on x86-64 or Apple
> Silicon).
>From what I see in videos on youtube, the tooklit displays a standard
On Wed, Nov 04, 2020 at 10:55:12AM +0100, Reinoud Zandijk wrote:
> qemu-system-x86_64 -accel nvmm \
> -device virtio-net-pci \
> -device virtio-rng \
> -drive id=mydrive,file=./dummy.fs,format=raw,if=nonea\
> -device virtio-blk-pci,drive=mydrive
> -cdrom boot-
Dear folks,
On Thu, Oct 29, 2020 at 09:54:02PM +0100, Reinoud Zandijk wrote:
> i stumbled on an instruction that NVMM couldn't code and thus couldn't
> emulate either. It was as stated the REPE CMPS (0xF3A7) instruction as stated
> in https://c9x.me/x86/html/file_module_x86_id
On Wed, Nov 11, 2020 at 10:58:25AM -0600, Robert Nestor wrote:
> > I have never tried to boot MacOS-X with qemu+nvmm. I think lots of other
> > things will need to be prepared for qemu to even start.
> >
> > Do you know of other possible (more recent) OSs I could try to boot?
>
> I’m no expert
On Sat, Oct 31, 2020 at 11:16:52AM -0500, Robert Nestor wrote:
> Apologies if this isn’t the proper place to bring this up, but the
> discussion on this brings two questions to mind:
>
> 1) Since the proposed patch isn’t correct and was reverted, and assuming
> there is a problem with this
On Wed, Nov 11, 2020 at 05:20:53AM -, Michael van Elst wrote:
> VGA has only 8 colors and an intensity attribute. You cannot select
> the "light" ANSI colors. The VGA driver will fail attempts to
> allocate such color attributes, so you get white on black instead.
...
> When DRM takes over,
On Thu, Nov 05, 2020 at 08:05:12AM -, Michael van Elst wrote:
> mar...@duskware.de (Martin Husemann) writes:
> >We could create a new PR about rump devices and sector size, if wanted.
>
> rump does this via environment variables. E.g.:
>
> env RUMP_BLKSECTSHIFT=11 mount -o rump -t udf -r
The issue in this PR is resolved by setting the sector size using vnconfig and
then mounting it normally.
What remains is how to specify this when using the rump. mount_udf(8) has no
option to set the sector size since its size is dictated by the media as per
UDF specification and is inquired on
On Mon, Nov 02, 2020 at 07:54:02PM +, co...@sdf.org wrote:
> touch myfile
> qemu-system-x86_64 \
> -device virtio-net-pci,disable-legacy=on \
> -device virtio-rng,disable-legacy=on \
> -drive id=mydrive,file=./myfile,if=none \
> -device virtio-blk-pci,drive=mydrive,disable-legacy=on \
>
On Wed, Nov 04, 2020 at 03:41:34AM +0100, Kamil Rytarowski wrote:
> On 03.11.2020 23:20, co...@sdf.org wrote:
> > On Tue, Nov 03, 2020 at 10:42:27PM +0100, Martin Husemann wrote:
> > The QEMU people mentioned that even if "legacy virtio" IDs are used,
> > there's a bit to show that it's compatible
On Mon, Nov 02, 2020 at 07:54:02PM +, co...@sdf.org wrote:
> On Tue, Sep 01, 2020 at 01:28:44PM +, co...@sdf.org wrote:
> > - 1af4:1044 VirtIO 1.0 random number generator
> > - 1af4:1042 VirtIO 1.0 block device
> > - 1af4:1041 VirtIO 1.0 network device
> >
> > Offer valid until 1 January
Dear folks,
I've reworked the patch using the feedback I got from Maxime and had to
refactor some minor parts in the other code. I'm in the process of writing the
test-cases now but would like feedback for this solution in the meantime. It
ought now give a proper REPE memory assist
Dear Maxime,
On Sat, Oct 31, 2020 at 08:24:05AM +0100, Maxime Villard wrote:
> Le 29/10/2020 à 21:54, Reinoud Zandijk a écrit :
> > i stumbled on an instruction that NVMM couldn't code and thus couldn't
> > emulate either. It was as stated the REPE CMPS (0xF3A7) instruction
Dear folks,
i stumbled on an instruction that NVMM couldn't code and thus couldn't
emulate either. It was as stated the REPE CMPS (0xF3A7) instruction as stated
in https://c9x.me/x86/html/file_module_x86_id_279.html and confirmed by
disassembly by ndisasm (from nasm).
Appended is the
ern/kern_softint.c:814
#11 0x80220e3f in Xsoftintr ()
(gdb)
------
I'll keep the coredumps and kernel around if someone want to extract more info
out of it :)
With regards,
Reinoud Zandijk
signature.asc
Description: PGP signature
Hi folks,
On Sun, Oct 11, 2020 at 04:10:00PM +0200, Reinoud Zandijk wrote:
> qemu-system-x86_64 -m 4096 -accel nvmm -smp cpus=2 -drive \
> file=work/wd0.img,format=raw -nographic -gdb tcp::1234 -net nic -net \
> tap,ifname=tap0,script=no
>
> Now is this an qemu related prob
On Wed, Sep 16, 2020 at 12:09:43PM +0200, Martin Husemann wrote:
> On Wed, Sep 16, 2020 at 12:05:26PM +0200, Anthony Mallet wrote:
> > I was also wondering if it would be possible to pass arguments to the
> > primary or secondary bootloader via reboot(2) and the boothowto
> > flags. But this
On Thu, Jul 23, 2020 at 11:06:27AM +0200, Hauke Fath wrote:
> On Thu, 23 Jul 2020 07:45:08 +0200, Michał Górny wrote:
> > How does that compare to the level of damage non-journaled FFS takes?
>
> From then on, the sandbox was easily recoverable after every panic. It
> turned out fsck times on a
Hi folks,
while trying to investigate the RIRB storm i stumbled on the following panic
during autoconfiguration on NetBSD/amd64 running 9.99.68 (22 jun) :
http://www.netbsd.org/~reinoud/IMG_20200719_134013.jpg
I was hinted that it might be a corruption so i tried out a few sanitiser
Hi folks,
my old videocard died and I replaced it with a slightly newer one but it isn't
recognized and nothing other than vga0 attaches. Its an Gigabyte Radeon RX460
with 2 GB ram.
002:00:0: ATI Technologies Radeon RX460 (VGA display, revision 0xcf)
002:00:1: ATI Technologies Radeon RX
On Fri, Jun 19, 2020 at 08:37:53AM +0200, Martin Husemann wrote:
> On Thu, Jun 18, 2020 at 10:26:10PM +, Taylor R Campbell wrote:
> > # cpuctl identify 0 | grep -w AES
> > cpu0: features1 0x7fbae3bf
> > ^^^
> > The highlighted part in `features1' is the
On Mon, Jun 15, 2020 at 05:16:01PM -, Christos Zoulas wrote:
> In article <20200615120806.gb1...@diablo.13thmonkey.org>, Reinoud Zandijk
> wrote:
> >LLVM code and its fuzzing tools should be in tree anyway so it can be
> >created there on the fly too if requeste
On Mon, Jun 15, 2020 at 02:58:31PM +0200, Kamil Rytarowski wrote:
> LLVM is an external project and only in a special case part of the
> basesystem. While there, there is the same issue with GCC sanitizers. We
> definitely don't want to request regular LLVM or GCC users building the
> toolchain to
On Mon, Jun 15, 2020 at 02:06:00PM +0200, Kamil Rytarowski wrote:
> On 15.06.2020 13:44, Reinoud Zandijk wrote:
> > No need to install it in base. The resulting files can then be committed
> > as `regen' just like the pcidevs variants.
>
> I disagree as we don't wan
Small addendum,
On Mon, Jun 15, 2020 at 01:44:19PM +0200, Reinoud Zandijk wrote:
> What about not installing it at all? Its only going to be used during
> definition updates or fixes. Compare it to the pcidevs.h and pcidevs_data.h
> creation only this time it creates the relevant ke
On Sun, Jun 14, 2020 at 09:07:45PM +, David Holland wrote:
> As I mentioned a few days ago the reason I was prodding
> makesyscalls.sh is that I've been looking at generating more of the
> system call argument handling code.
...
> This raises two points that need to be bikeshedded:
>
> (1)
On Wed, Jun 10, 2020 at 08:58:57AM +, David Holland wrote:
> On Wed, Jun 10, 2020 at 01:25:03AM -0400, Thor Lancelot Simon wrote:
> > Could you translate your prototype into a
> > different language, one that's less basically hostile to our build system
> > and its goals and benefits?
>
>
Hi folks,
as you might know, i'm currently working on NetBSD/usermode.amd64 but I can
use some help with the following linking issue:
`./build.sh ... kernel=GENERIC_USERMODE' now compiles the kernel fine and
(with a little hack) links it fine. Going to the directory and executing the
resulting
On Mon, Jun 25, 2018 at 10:29:30PM +0200, Kamil Rytarowski wrote:
> I'm usually going the other direction. If I hit a problem and an issue
> is not visible from a multi-job build (multiple processes print onto the
> same screen concurrently), I go for -j1. If this is still no enough I
> change the
the patch:
Index: build.sh
===
RCS file: /cvsroot/src/build.sh,v
retrieving revision 1.327
diff -u -p -r1.327 build.sh
--- build.sh2 May 2018 07:34:44 - 1.327
+++ build.sh25 Jun 2018 18:26:34 -
@@ -1027,7
On Sun, Jun 24, 2018 at 10:01:42PM +0200, Reinoud Zandijk wrote:
> On Wed, May 30, 2018 at 07:11:19PM +0800, Harry Pantazis wrote:
> > Continuing..
> >
> > This first errors are located in
> > src/sys/external/bsd/drm2/dist/drm/i915/intel_ddi.c and are specific
Recapping my issues, i had an hdaudio interrupt storm and serious issues with
i915 graphics.
I now run a 8.99.8 kernel but also tested an 8-release kernel. They both have
the same behaviour for what its worth.
Having a 7.1 kernel, userland and X gives rise to the problems I mentioned. X
is
On Fri, Dec 01, 2017 at 10:34:27PM +0100, Reinoud Zandijk wrote:
> DRM error in i915_hangcheck_elapsed: Hangcheck timer elapsed... blitter ring
> idle
>
> when starting X, so there sure is something wrong with the i915 code :-/
I explcitly disabled acceleration :
And I nee
On Fri, Dec 01, 2017 at 10:25:24PM +0100, Reinoud Zandijk wrote:
> On Fri, Dec 01, 2017 at 02:38:46PM +0100, Reinoud Zandijk wrote:
> > - when starting X it works fine but I can get "DRM error in
> > hsw_unclaimed_reg_clear: Unknown unclaimed register before writing to ...&qu
On Fri, Dec 01, 2017 at 02:38:46PM +0100, Reinoud Zandijk wrote:
> my new x86_64 (ASUS VivoPC VC62B) machine has arrived and I installed
> NetBSD-7.1/amd64 on it. All seems to work fine but for some oddities:
>
> - it has an interrupt storm on ioapic0 pin 16 for hdaudio0. It gives
&
Dear folks,
my new x86_64 (ASUS VivoPC VC62B) machine has arrived and I installed
NetBSD-7.1/amd64 on it. All seems to work fine but for some oddities:
- it has an interrupt storm on ioapic0 pin 16 for hdaudio0. It gives
"hdaudio0: RIRB timeout" twice and then generates an sustained impressive
Hi,
On Wed, Jun 28, 2017 at 09:07:18PM +0200, Jarom?r Dole?ek wrote:
> during my testing on jdolecek-ncq branch, I found that when I attach the
> ATAPI device via a port multiplier, the device is never actually detected.
> The behaviour I see is that atapibus is detected on the port, but not the
Hi Matt,
On Sun, Jun 21, 2015 at 01:42:38PM -0700, Matt Thomas wrote:
On Jun 21, 2015, at 12:02 PM, Reinoud Zandijk rein...@netbsd.org wrote:
On Sun, Jun 21, 2015 at 08:01:47AM -0700, Matt Thomas wrote:
IMO, softints are an abberation and should really be thread priorities
and dealt
Hi Matt,
On Sun, Jun 21, 2015 at 08:01:47AM -0700, Matt Thomas wrote:
IMO, softints are an abberation and should really be thread priorities and
dealt by the thread scheduler.
Each level of softint as a kernel thread that gets woken up by condition
variables?
Could in a virtualisation context
Hi folks,
while investigating running my NetBSD system under Xen, i was struck by the
sheer number of ways to partition discs. Most are not compatible with
eachother and all have the same function, splitting up and identifying parts.
We have amongs others, MBR, GPT, disklabels, (sun-)disklabels,
Hi Taylor,
On Thu, Mar 26, 2015 at 12:13:56PM +, Taylor R Campbell wrote:
Various DRM graphics drivers, including Intel, Radeon, and Nouveau,
sometimes need to unmap all virtual mappings of certain physical
pages for which there is no struct vm_page. The issue is explained in
detail
Hiya Matt,
On Sat, Jul 27, 2013 at 11:52:20PM -0700, Matt Thomas wrote:
I have several SoC targets that I've stalled on due to the need of writing
a tty driver. Sure I could cut paste from another driver but having to
do that 3+ times seems inordinately stupid. So I've been thinking of
Hi folks,
well the title already tells all really. How hard would it be to get Xen Dom0
(with hardware virtualisation, HVM IIRC i.e. also possible to run Win7) as a
loadable kernel module? Would it need drastic measures? Having a Xen
hypervisor that only runs Xen aware OSs might be a lot more
Hi!
On Wed, Oct 24, 2012 at 12:07:21AM +0100, Mindaugas Rasiukevicius wrote:
Easy to diagnose problems? Plain false. The lock naming you are talking
about would give no *more* information than it is a vnode lock, and one
can guess already that it is most likely the case here (what a
hi folks,
sorry i'm so late :)
On Fri, Jun 08, 2012 at 01:35:44PM -0700, Israel Jacquez wrote:
When I invoke dmesg(8): dmesg | grep -E '^com', I get the following:
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
com0: kgdb
and thats the issue: you are multiplexing
Hi Manuel, hi folks,
On Sat, Jun 23, 2012 at 06:01:28PM +0200, Manuel Bouyer wrote:
I've been working on support for SATA port multiplier in the siisata driver
(ahcisata should be coming soon as well, but hardware for tests is a bit
tricky to set up). This requires some changes to the atabus
Hi Joerg, hi folks,
On Fri, Dec 30, 2011 at 03:49:06PM +0100, Joerg Sonnenberger wrote:
On Thu, Dec 22, 2011 at 08:22:17PM +0400, Valeriy E. Ushakov wrote:
On Thu, Dec 22, 2011 at 15:31:45 +, David Holland wrote:
Consequently, the changes should be reverted, at least until the
design
On Mon, Oct 03, 2011 at 06:18:42PM +, David Holland wrote:
the normal FFS code works but their indirect blocks, when addressed
with their disc addresses, are not up-to-date.
...so read them out of the cache.
easier to say than to do. Calculating and referring to the negative block
On Mon, Oct 03, 2011 at 08:33:06AM +0200, Alan Barrett wrote:
So, if I am reverse engineering the code correctly, the design is
like this:
There are no new VOP calls.
correct
There are two new ioctls, FIOSEEKDATA and FIOSEEKHOLE. Each
file system may provide its own implementation.
Hi Marc,
On Wed, Sep 28, 2011 at 10:05:31PM +0200, Marc Balmer wrote:
Marc
sorry :-D
On Sun, Sep 25, 2011 at 11:42:11AM +0200, Marc Balmer wrote:
I'd like to be able to set the PWM indepentently for each pin! say
specifying
70/256 on and otherwise off.
That is what gpiopwm(4)
Hi Mark, hi folks,
On Sun, Sep 25, 2011 at 11:42:11AM +0200, Marc Balmer wrote:
attached to an individual pin. gpioctl(8) will keep the pulse keyword,
as this is needed for hardware pulsating devices. The interface to the
gpiopwm(4) driver could be realized using three sysctl variables:
$*/
+
+/*
+ * Copyright (c) 2011 Reinoud Zandijk
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
On Mon, Aug 08, 2011 at 12:15:03AM +, David Holland wrote:
struct range range;
while (pos len) {
fgetrange(fd, pos, range);
if (range.r_type == RANGE_DATA) {
amount = range.r_end - pos;
if (amount sizeof(buf)) {
ufs_strategy(void *);
===
--- /dev/null 2011-08-07 03:51:18.0 +0200
+++ sys/ufs/ufs/ufs_seek.c 2011-08-06 12:13:03.0 +0200
@@ -0,0 +1,330 @@
+/* $NetBSD$*/
+
+/*
+ * Copyright (c) 2011 Reinoud Zandijk
Hi David, hi folks,
On Sun, Aug 07, 2011 at 02:14:50PM +, David Holland wrote:
On Sun, Aug 07, 2011 at 09:52:11AM +0200, Reinoud Zandijk wrote:
i've implemented the SEEK_HOLE / SEEK_DATA additions to lseek() as
introduced by Solaris for ZFS.
What does this operation have to do
Hi David, hi folks,
On Sun, Aug 07, 2011 at 05:06:16PM +, David Holland wrote:
On Sun, Aug 07, 2011 at 06:52:03PM +0200, Reinoud Zandijk wrote:
i've implemented the SEEK_HOLE / SEEK_DATA additions to lseek() as
introduced by Solaris for ZFS.
One `seeks' the next hole of data
Dear Mouse,
On Sun, Oct 10, 2010 at 04:41:40AM -0400, der Mouse wrote:
I was looking at improving if_sl.c to support encapsulating normal
serial data on the SLIP's tty as packets, thus merging it into the
packet stream. I ran into some problems, but think I can handle them;
I'm writing to
76 matches
Mail list logo
