hello. What happens if you build a custom kernel where only one
piixide device is
configured? I don't remember if you have disks on both piixide devices, but
it might be worth
trying, just to see what happens.
Given the rest of your details, this really sounds like a BIOS bu
hello. Can you tell which device is generating the interrupts and
where the interrupts
are being routed? When I've seen things like this in the past, I've found the
issue is often
that the interrupts aren't getting to the right driver, or they're going to no
driver, which
creates a lot
hello. While Intel isn't selling motherboards anymore, I've found they
usually have the
latest BIOS available on their web site for the boards they sold years ago. If
you haven't
already done so, I'd suggest visiting www.intel.com and searching for:
i965-ITE8712
to see what you get. I
hello. Thanks for the rclone suggestions. According to the
instructions, I can configure
rclone on another machine and copy the config to a non-browser capable machine.
Has anyone
done that when the other machine is a Windows machine?
-thanks
-Brian
hello. Thanks for the reply. What I'm looking for is some kind of
command line, or
perhaps a fuse mount for grafting Google drives into the filesystem tree. Is
anyone using the
Google drive program for Linux? If so, does it work in linux emulation mode?
-thanks
-Brian
Hello. Are there folks running Google drive from their NetBSD
installations? If so, what
is needed to get it working?
-thanks
-Brian
Hello. Are there pros to having the kernel do the CPU switching? You
don't seem to list
any, but there must be trade-offs. What are they?
-thanks
-Brian
Hello. I just did a quick scan of the telnetd sources from NetBSD-5
and there are
interesting notes in there about all of this and how urgent data is used, or
not used, in
different cases. A check of -current sources still have the same notes and
code regarding all
of this in telnetd.
On May 10, 10:14am, Roger Pau =?utf-8?B?TW9ubsOp?= wrote:
} Subject: Re: Xen-4.16.0 + FreeBSD-13.1 dom0 fails on large ADM64 system
} On Sun, May 05, 2024 at 12:52:39AM -0700, Brian Buhrow wrote:
} > hello Roger. After some further investigation, I found a solution.
The first is a l
hello Roger. After some further investigation, I found a solution.
The first is a link
to a bug report which demonstrates the problem. Then, I include the diff I made
to the ports
files which fixes the issue.
Note that the first link is a bug report for a different piece of software i
hello Roger. I figured out the magic phrase to put in /etc/make.conf
to force the system
to use python-3.9; it's:
DEFAULT_VERSIONS+=python=3.8
Unfortunately, that doesn't fix the issue. So, there is something definitely
strange about my
ports environment that isn't obvious to me. I'll
Hello Roger. In looking into this issue further, it appears that the
way python stores
info details for site packages has changed between pythonh3.8 and python3.9.
In python3.8,
info details appear to be stored in files, while in python3.9, theyre stored as
files in
directories with th
hello Roger. The xen4.18.2 kernel loads and runs with FreeBSD-13.1 on
this system. Thank
you for the help getting it going.
However, I've run into another issue. When building the xen-tools package,
when I try to
install the package, or build a pkg file, I get the error:
===> Buildin
hello Roger. Again, thank you for the hints.
In addition to the xvda syntax working, one can also use the hex values for the
device numbers,
separated by 16, allowing one to use absolute numbers, rather than remembering
letter to number
mappings. The following syntax, for example, als
hello Roger. Thanks for the quick reply. Okay. I'll try the
alternate lines.
Interestingly enough, I tried hda and hdb and they didn't work either. Also,
for NetBSD domu's
the 0x1,0x2 syntax works beautifuly, so I was surprised it didn't work with the
FreeBSD domu's.
-thanks
-Brian
Hello. I'm running FreeBSD-13.1 as a domu on xen-4.16.0 and I find I
cannot use multiple
virtual disks on the same virtual guest.
The problem appears to be related to the way the geom layer sorts the disks.
Somehow it thinks
the first and second disks are related.
Here is the conf
Hello. I'm trying to load xen on a large AMD64 server, with 600G of
RAM and 56 CPUs. I'm
using a xen-4.16 image with FreeBSD-13.1, a duplicate image, in fact, with a
couple of other
machines I have running in production and which have been running without
issues for a couple
of years.
hello. I built Brltty a number of years ago on NetBSD, which is a
close sibling of
FreeBSD. So, I think you'll find it pretty easy to accomplish the task.
-thanks
-Brian
On Apr 7, 3:25am, Alfonso Sabato Siciliano wrote:
} Subject: Re: [BRLTTY] brltty.app on FreeBSD
} --===5
Isn't it possible to do most of what Jason proposes by using the drvctl
interface to
detach a driver from a specific USB device? Then, some glue could be added to
the ugen driver
to allow it to be attached to arbitrary devices using the same drvctl
interface? That seems a
lot easier to
hello. If you put a gpt label on a raid set and add partitions to it,
those partitions
will show up as dkn devices automatically, when the raid set is configured.
This is true
whether the raid set is configured automatically by the kernel at boot or
manually via raidctl
-C or -c.
This
hello Peter. While I'm not super familiar with the Braille Blazer
specifically, I
believe the issue you're runing into is a printer setting issue, rather than a
problem with the
linux usb->serial driver. There should be a menu inside the Blazer that lets
you set various
things: i.e. pa
hello Ken. Yes, I missed that part of what you were trying to say.
You're right, I
didn't try that. I'm not sure that's possible when configuring SSL with
sendmail. I elected
to arrange for sendmail to hav access to valid public certificates so it could
present a
certificate both as
hello Ken. It may be that the RFC says the client need not present a
valid certificate, but
I have found that smtp clients I manage that want to send mail to Microsoft
managed domains
cannot set up an SSL encrypted smtp session unless the client presents a valid
certificate as
part of t
Hello Taylor. Just as a point of reference, smtp clients that connect
to domains hosted by
Microsoft, i.e. outlook.com and any other domains that use their infrastructure
for e-mail, will
have to present a valid SSL certificate in order to submit mail to their smtp
servers. But
that is
Module Name:src
Committed By: buhrow
Date: Wed Oct 25 00:21:49 UTC 2023
Modified Files:
src/sys/dev/pci: mpii.c
Log Message:
Fixes for PR kern/57133:
I can now explain why this assert is firing and have a fix for it. It is a
regression introduced in R1.22 of mpii.c.
Module Name:src
Committed By: buhrow
Date: Wed Oct 25 00:21:49 UTC 2023
Modified Files:
src/sys/dev/pci: mpii.c
Log Message:
Fixes for PR kern/57133:
I can now explain why this assert is firing and have a fix for it. It is a
regression introduced in R1.22 of mpii.c.
hello. As someone who regularly works on the kernel, yes, I have
kernel sources, but
having man pages that provide some explanation of various parts of the source
is very helpful.
So, I would support making man pages available as is proposed. Man pages are a
great
supplement to source
Hello. As a followup on this bug I now know what's causing the panic
to get triggered.
The issue is that if a request gets requeued requeud, resid gets set to 0,
which causes the
KASSERT to fire. So the question is, is it always the case that if a request
gets requeued,
resid gets set
Hello David. Does it always drift backward? And, it looks like it
drifted by one second.
Does it ever drift by more than one second?
If not, then a work around in your script would be to assume that if boottime
is less than 2
seconds from your stored time, then you haven't rebooted.
-B
hello. Following up on this thread, I have more diagnostic output.
The problem occurs when a call to scsipi_get_opcodeinfo() is made for a device.
By the time
the request hits the adapter, as shown in the below output, the discrepancy
between xs->resid
and xs->datalen has already occ
hello Edgar. I agree with your analysis. I'll put the check in and
recompile my test kernel
and see what we get. I suspect it is an error race in the mpii(4) driver. I
notice the call
to scsipi_get_opcodeinfo only happens if the device in question reports as a
SCSI V3 device.
Is ther
hello everyone! Recently I ran across the problem described in
kern/57133 with the
mpii(4) driver. I patched sys/dev/pci/mpii.c to provide more diagnostic
information when the
condition occurs and to avoid the panic. I also provided output showing the
SCSI command that
triggers the co
hello Edgar. What you could do to improve that situation is exactly
what you did, except
use raidctl -C on the last configuration step. Then, instead of having to
recopy the entire
contents of the array, all you need to do is recalculate the parity.
-thanks
-Brian
hello. Michael's e-mail explains the behavior I'm seeing with trying
different block
sizes with NetBSD and FreeBSD.
The scripts below show transfers of the same number of bytes using 1m and 64k
block sizes for
NetBSD-9.99.77/amd64 and FreeBSD-13.1/amd64. NetBSD is using SATA3 disks w
hello. I know that this has ben a very long term project, but I'm
wondering about the
status of this effort? I note that FreeBSD-13 has a Maxphys value of 1048576
bytes.
Have we found other ways to get more throughput from ATA disks that obviate the
need for this
setting which I'm not
hello. The error says you ran out of memory. My guess is your machine
has been running
for a while and the amount of contiguous memory available for the kernel to
allocate has
fragmented, leading to the issue. I seem to remember versions of NetBSD ealier
than V8 were
prone to this iss
hello. What about having the ability to have multiple clip boards?
Then, if you want to paste multiple blocks into a text area, youjust paste
multiple clip boards
into that area. For example, vi (vim) allows you to use up to 10 buffers or
clip boards.
-thanks
-Brian
___
hello. Yes, this behavior is expected. It ensures that there is no
conflict between the
device on the domu end of the vif port and the device on the dom0 end. This is
more
sane behavior than FreeBSD, which zeros out the MAC address on the dom0 side of
the vif.
-thanks
-Brian
hello. A couple of quick questions based on the convrsation and the
snippets of logs
shown in the e-mails.
1. Is the MAC address shown in the ARP replies the correct one for the dom0?
No reason it
should be wrong, but it's worth verifying, just in case there is an unknown
host replyi
hello. Because the Orbits refresh left to right, if what you're
looking for is toward the
left half of the display when scrolling down some text, the refresh rate isn't
really an issue.
the Orbit 40's refresh two cells simultaneously, starting at cell 1 and cell 21
respectively,
helping
Hello. Here are the network configuration settings I've been using for
a number of years,
all the way through -current.
net.inet.tcp.recvbuf_auto=1
net.inet.tcp.sendbuf_auto=1
net.inet.tcp.sendbuf_max=16777216
net.inet.tcp.recvbuf_max=16777216
-thanks
-Brian
Hello. The ARP cache timeout used to be 1200 seconds or 20 minutes,
hard coded. Now, it
looks like it's either 1200 seconds or 300 seconds, I'm not sure after a quick
romp through the
kernel source. In any case, The fact that you're getting regular delays on
your pings suggests
there
Hello. I've used many displays over the years. Most suffer from weak
or broken dots
after a short time, if not other issues. Six years ago, I bought two Orbit
Reader 20's.
Except for a battery issue with one of them, I've had no hardware trouble with
them what so
ever! They have tra
hello. My understanding is that the arp caching mechanism works
regardless of whether
you use static MAC addresses or dynamically generated ones. The reason is that
arp bridges the
gap between the layer 2 network, i.e. the MAC addresses, and the layer 3
network, i.e. the IP
addresses t
hello. Actually, on the server side, where you get the "host is down"
message, that is a
system error from the network stack itself. I've seen it when the arp cache
times out and
can't be refreshed in a timely manner. What happens if you run an extended
ping session
between the dom0 a
hello. You probably already researched this, but it looks like
newterm() is in the curses
library in NetBSD-5, so getting it to work in NetBSD-1.4T shouldn't be that
difficult.
-Brian
Hello. Yes, I realized the error I'd made after I sent you the e-mail.
I wonder if you
could utilize a pty to do what you need to get two different tty structures,
one blocking for
curses, and the other non-blocking?
-thanks
-Brian
hello. I may be missing something in your curses non-blocking case,
but can't you work
around the issue by setting up an independent file descriptor, and hence tty
structure, by
performing a dup2(2) on stdin and then closing the original stdin file
descriptor?
Then, of course, you can d
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. While I'm not sure what the initial panic message
was, since they
were rebooted by
hello. I regularly build kernels outside of the /usr/src location. My
technique is to
install the source in some location: /usr/local/netbsd/src-91, for example,
then put my
configuration file in: /usr/local/netbsd/src-91/sys/arch//conf/
Then
cd /usr/local/netbsd/src-91/sys/arch//conf
c
Hello. I'm running a series of machines, both Xen VM machines and
machines running on
bare metal, and I notice that on my systems running NetBSD-9.99.77, vmstat -s
shows that
local-cpu page allocations are never available on the xen VM's, see below.
Yet, on machines
running on bare met
Module Name:src
Committed By: buhrow
Date: Mon Feb 13 19:07:14 UTC 2023
Modified Files:
src/sys/kern: subr_devsw.c
Log Message:
When a device driver calls devsw_attach() it has the option of
attaching a block device
structure and a character device structure, or,
Module Name:src
Committed By: buhrow
Date: Mon Feb 13 19:07:14 UTC 2023
Modified Files:
src/sys/kern: subr_devsw.c
Log Message:
When a device driver calls devsw_attach() it has the option of
attaching a block device
structure and a character device structure, or,
hello Matthew. That line assures that if a device driver has unloaded
and reloaded its
bdevw or cdevw interfaces, it gets assigned the same major numbers that they
had when they
were first loaded on the system. If a device driver has never loaded its
bdevsw or cdevsw
interfaces on a sy
hello. Following up on this issue, I've discovered the problem with
devsw_attach is that
if one is reattaching a previously detached driver and that driver does not
implementa bdev
interface, devsw_attach returns an EINVAL error. The following patch fixes
this problem. Any
reason I sh
Hello. I've seen this issue and I believe I understand the problem,
though I don't have
a driver fix at this time.
The issue is that the audio output jack on modern Reltek sound chips
can be configured for
a number of purposes: mono or stereo, line out or speaker out. Some chip
hello. I really don't know what's wrong, but I wonder if the xen logs
show the domu
runing some instruction that's trapped by xen, flagged as dangerous and xen is
then faulting
the vcpu with an illegal instruction error? I would expect to see that error
in the xen log
for the specific
Hello. I've found that after I perform a modunload on the module I'm
working on, I cannot
then modload the module because devsw_attach fails to attach the same module
again. And, yes,
the module calls devsw_detach before it unloads.
I'm runing NetBSD-9.99.77, which pre
hello. Okay. That is helpful. Passing -1 in as the cmajor number to
the devsw_attach()
function does, in fact, assign a reasonable major number which seems to work.
I use the
cdevsw_lookup_major() function to retrieve the assigned number and print it for
the user.
So, thankfully, thi
hello. Mouse's question is the same as mine. It's fine to have a
dynamically assigned
major number for the module, but since we don't have a dynamic /dev, that
number needs to be
static enough so that devices can be created in the /dev tree. The idea that
one can request a
prefered maj
hello Brad. I thought the idea behind modules was that you didn't need
to rebuild a
kernel to add devices to the ioconf table? And, in fact, under the old module
framework, that
is, NetBSD-5 and earlier, you could add devices and major numbers to the table
without having
to rebuild the
hello. Following up on my own post, I found the mechanism by which the
cdevsw structure
gets tied to the ioconf table in NetBSD-5. It's done with:
MOD_DEV("zaptel", "zaptel", NULL, -1, &zaptel_cdevsw, ZT_MAJOR)
This macro has been removed from the new module framework. Can someone po
hello. Following up on my module question of last night, I now have
the module loading
and unloading successfully. However, when I try to open the devices I've
associated with the
module, I get a device not configured error.
Under NetBSD-5, Major number 196 was available, and the ope
hello. Thank you so much for the answer. Yes, the problem was that I
had two source
files that declared they wer a module. Since they were modules of different
names, I assumed
they could all be compiled into one object file. A small change to the code
has allowed me to
compile the
Hello. I'm working on porting an old zaptel kernel module which I've
used under NetbSD-3
and NetBSd-5 for years to a version 9-current from January 2021. I have the
module built,
using the bsd.module.mk make file from /usr/share, but when I try to perform a
modload on the
final .kmod f
hello Brad. In reading about your panics on day 6 of uptime, I wonder
if the issue might
be related to memory allocation? Specifically, by day 6, I expect that memory
allocations in
the system are pretty fragmented and thus more CPU time is spent doing things
like cleaning
memory, free
Hello Joel. I'm not sure this is a new problem. I've seen similar
behavior on NetBSD-5.2. It seems to happen on systems where there is a
good deal of traffic traversing the network at the time the stop is
requested.
-thanks
-Brian
hello. I used brltty-5.4 successfully under NetBSD, using the patches
to screen to get a
working brltty terminal. So, unless the USB code is drastically different in
6.x, it should be
pretty easy to get working under OpenBSD.
-thanks
-Brian
_
hello. Just as a matter of consistency, it seems like using network
byte order would b a
better choice, since it would match other interfaces on the system.
-thanks
-Brian
hello Michael. Here is a demonstration of the issue I'm seeing, using
audiorecord with
two audio devices on the same machine. The audio1 device is a USB C-Media
audio dongle.
The audio0 device is a Realtek, Product ID: 0255, built into this Dell Optiplex
5050 desktop
machine.
hello. The hdaudio driver I'm using is a locally patched version to
work around an issue
where the driver doesn't configure the headphone jack correctly. Specifically,
it seems
the default configuration configures the jack for use with a microphone, rather
than with just
a headset, wh
hello. Just to clarify, I'm not trying to use two audio devices for
recording at the same
time. What I was doing was something like:
#set up the audio device first
audioctl -d /dev/sound2 -w record.rate=44100 record.channels=2
record.precision=16 \
record.encoding=slinear_le
#Now, th
der -current?
} On Tue, 25 Oct 2022, Brian Buhrow wrote:
}
} > Is anyone using the audio(4) driver for recording successfully under
-current?
} >
}
} audiorecord worked for me on 9.99.102:
}
} ```
} hdaudio0 at pci0 dev 27 function 0: HD Audio Controller
} hdaudio0: interrupting at msi1 v
hello. Is anyone using the audio(4) driver for recording successfully
under -current?
I'm using an an admittedly older -current (9.99.77), but a browsing of the cvs
logs doesn't
suggest any fixes have been committed since the version I'm runing, audio.c,
rev 1.86. The
symptom is that
hello. Thanks for the pointers. The following lines in my .Xresources
file fixed things
up, mostly. It looks like all is working as I expect, except I can't seem to
generate
an alt-return key sequence. I just get a bell when I try to do this and the
application I'm
using doesn't rece
hello. I'm using both the text consoles and the X display on my
NetBSD-9 based machine
and I'm running into an issue with the keyboard that I think should be simple
to figure out,
but which I'm finding a bit confusing.
Using a USB attached keyboard, when I'm running in the consoles, the
hello. Another thing to try is to see if you can get to the boot
prompt and boot the
kernel with various options, i.e. -a, -c, and possibly -2, to disable acpi. If
-c gets you to
a driver selection prompt, then you know the kernel is loaded and ready for you
to disable
drivers. If you
hello. How hard would it be to add ssh/scp to the install image that
gets brafted into the
netbsd-INSTALL kernel? Is it not there because we don't have room on the
install image?
Not having ssh capabilities from the install miniroot environment is becoming a
real impediment
to doing ne
hello. Refresh my memory. Is it the case that the HPN code
only runs if both ends
of the ssh connection support HPN and have it turned on? I've been using it
for a very long
time under NetBSD-5, but I notice that newer versions of openssh as shipped on
FreeBSD don't
show HPN s
hello. that's interesting. Do the cores used for the vms also get
used for the host os?
Can you arrange things so that the host os gets dedicated cores that the vms
can't use? If you
do that, do you still see a performance drop when you add cores to the vms?
-thanks
-Brian
hello. If you want to use zfs for your storage, which I strongly
recommend, lose the
zvols and use flat files inside zfs itself. I think you'll find your storage
performance goes
up by orders of magnetude. I struggled with this on FreeBSD for over a year
before I found the
myriad of t
hello. Following up on my own post, by porting the latest fixes to the
scsipi sources and
the vioscsi driver with respect to probing discontiguous luns, I am now able to
utilize all the
virtual disks I created for my virtual machine. It would be nice if these
fixes could be back
ported
hello. I just spun up a Linode server, which I think is also running a
Q35 virtual chip
set and it seems to work just fine, except that in paravirtual mode it doesn't
detect all the
disks. Is that the issue you all are seeing?
-thanks
-Brian
NetBSD 9.99.77 (LINODE) #0: Fri Aug 12 20:
hello. Thanks to help from folks on this list, I was able to get a
virtual machine up and
running on Linode through the Linode command line tools. Now that I have a
working machine,
I've noticed something strange with the virtio(4) behavior. If I assign
multiple disks to a
virtual mac
hello. thanks so much for your reply and the link to your blog post.
I'm almost there,
but I've run into something that seems very simple, but is currently tripping
me up.
How do I specify "Direct Disk" as a kernel in the configuration creation or
update step? I'm
using something like
hello. Is there anyone on this list using NetBSD on Linode? I see
some folks have done
it in the past, but I don't see anything current. Also, are there instructions
on how to build
a custom image for uploading?
Any help on this would be greatly appreciated.
-thanks
-Brian
hello. Is your git process multithreaded, or just forking in the
traditional manner? If
it's multithreaded, then you'll want stack traces for each thread. To check
for this, I'd
check to see if your process is linked against libpthread, just in case
something is spawning
threads witho
Hello. As I remember, and the web can probably confirm, running
lockdebug under 5.x
doesn't work at all!
I think you'll find a question on this very point from me some years ago n our
archives.
-thanks
-Brian
My read/write performance jumped by a factor of 5,
which really
astounded me.
-thanks
-Brian
On Jul 16, 10:32pm, Brad Spencer wrote:
} Subject: Re: iscsi target on a zfs zvol?
} Brian Buhrow writes:
}
} > hello. Yes, I was vaguely aware of the lack of extended attributes for
NetBSD-Zfs,
hello. Yes, I was vaguely aware of the lack of extended attributes for
NetBSD-Zfs, but
what I was suggesting was just using a flat file, exported via iscsi through
istgt or your
initiator of choice, on top of zfs, rather than a zvol, because you'll find the
read/write speed
to be so muc
hello. If memory serves correct, this problem was discussed relative
to NetBSD-5 when
Andrew Doran was working on the smp improvements to the kernel. As manu
pointed out, it could
be a result of a number of scenarios. My take away from all the discussion was
that the best
way to find
hello Roger. I am running the C version of xenstored, the oxenstored
file is not
installed on my server. With that said, I have figured out that the queue
length on the
xenstored socket is 2, meaning there can be no more than 3 xl commands runing
simultaneously on
a given xen installat
hello. Recently, I've started seeing messages like the following:
sonewconn: pcb 0xf801074d7800 (local:/var/run/xenstored/socket): Listen
queue overflow: 2
alread
y in queue awaiting acceptance (1 occurrences)
I figured out what causes this. I have a number of automated scripts that
Hello. While this is orthogonal to the task you're working on in this
e-mail, I'll note
that you'll get much better read-write performance if you create a standard zfs
filesystem for
your time machine backup, then create a regular file in it which you export via
iscsi. I
discovered thi
hello. I don't have a lot more details on the issue, but under
xen-4.15 and xen-4.16 with
freeBSD-12 and FreeBSD-13, it's pretty easy to end up with zombie domu's that
are unkillable
and unrestartable. Even worse, the block devices associated with these
not-quite-gone domus'
are unusabl
hello. In looking at my vmstat-m output, I see:
mclpl 211228146028146 14109 1407435 187 0 524288 35
I see no failures and the number of nmbclusters is: 524288
yet, this machine has displayed this message about 6 times since it was
rebooted about 5 hours
ago
hello. One strange thing I notice on this particular system that seems
to be different
from the other systems I'm running is that the request count on the mclpl line
is incrementing
at a pretty fast rate, where as on other systems, the request rate is, more or
less, constant
over time,
hello. In looking at the if_xennet_xenbus.c file, I see where the
if_xennetrxbuf_cache is
initialized, but I don't see where data is put into it before it's requested.
Is the idea that
the items in the cache are supposed to be provided by the backend, i.e. the
dom0? Is it
possible tha
Hello. I'm running a number of NetBSD-9 and -current as of 99.77
amd/64 domu machines on
a couple of different servers with FreeBSD as dom0. I'm getting the following
messages from
the kernel:
xennet0: rx no cluster
Much of the time, these messages seem harmless, but occasionally, the
hello. Given that the system was running fine under 9.2 and you
haven't updated anything
immediately before it began hanging, I'm inclined to think you have a hardware
issue. Some
questions:
1. Does the raid card have any battery backed up cache on it? If so, what is
the state of th
1 - 100 of 640 matches
Mail list logo
