mar...@duskware.de (Martin Husemann) writes:
>Did you run a forced fsck on the file system?
I just got this panic running 10.99.10 in qemu.
[ 4.0895156] panic: ffs_blkfree_common: freeing free frag: dev = 0x1300,
+block = 135894, fs = /
This happened after a clean reboot, after the rc
pr...@welche.eu (Patrick Welche) writes:
>In fact, the difference is between "-t" and "-rt":
>I deem "-t" output to be correct (and matches what I had in /etc/diskpart)
The in-kernel disklabel gets the RAW_PART from by the disk geometry
and if RAW_PART == 3, it gets d_partitions[2] from the
p...@whooppee.com (Paul Goyette) writes:
>> Does anyone have an example of how to configure raid0 on a GPT disk?
For a manual setup, you can just reference the wedges like:
# raidctl config file for /dev/rraid0
START array
# numRow numCol numSpare
1 2 0
START disks
NAME=raid0.0
NAME=raid0.1
p...@whooppee.com (Paul Goyette) writes:
>as soon as you proceed past this point (including normal non-single-
>user boot), the dwiic starts spewing time-out messages. These
>messages come every 0.5 second or so, and there's usually a hundred
>or more messages before they stop; in some cases
the disk was offline). This is different from disklabels that
are fetched by the first opener (and are usually dropped with
the last close, except traditionally for vnd).
You can manually trigger autodetection with
dkctl sd0 makewedges
Greetings,
--
Michael van Elst
Intern
p...@whooppee.com (Paul Goyette) writes:
>[ 29641.773703] umass0 at uhub11 port 4 configuration 1 interface 0
>[ 29641.773703] umass0: Western Digital (0x1058) Elements 2621 (0x2621), rev
>3.20/10.34, addr 4
>[ 29641.773703] umass0: using SCSI over Bulk-Only
>[ 29641.793714] scsibus0 at umass0:
roland.il...@gmx.de (Roland Illig) writes:
>That's this line:
>> unit =3D *(const int *)newp;
>I don't know at which point newp is validated; maybe that validation is
>missing in this case, although I'd expect it to be in the common sysctl
>infrastructure code.
newp is valid, it's a userland
w...@netbsd.org (Thomas Klausner) writes:
>ftp: Receiving HTTP reply: Input line is too long
#define FTPBUFLEN (4 * MAXPATHLEN)
char buf[FTPBUFLEN];
That's 4kB.
>curl -v https://sourceforge.net/projects/courier/files/courier-unicode/2.3.=
>0/courier-unicode-2.3.0.tar.bz2
This
fails badly.
Mike
---
Michael L. Hitchmhi...@montana.edu
Operations Consulting, Information Technology Center
Montana State University, Bozeman, MT USA
kar...@netbsd.org (Frank Kardel) writes:
>As you said a "couple of years ago" I assume those CPUs where not
>Zen4-architecture.
The new pkgbuilder is Zen3, so still too old.
shev.vt1...@gmail.com (Vitaly Shevtsov) writes:
>When I'm listening to music I get this error after some time:
>audio1(hdafg1): audio_write: device timeout, seq=16987,
>usrbuf=60224/H60224, outbuf=8192/8192
You get timeouts when the backend driver (hdafg1) doesn't
finish playing buffers. So
9 axen_uno_rx_loop#0@0: 0400e00b 400657b9 c0a80104
> 0bf0 <-- garbage -->
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mak...@ki.nu (Makoto Fujiwara) writes:
>I've compared to openbsd: if_axen.c
> https://raw.githubusercontent.com/openbsd/src/master/sys/dev/usb/if_axen.c
>to N, and there are so many differencies.
>Does this (N) if_axen.c works on any installation ?
axen seems to work, but I can see that the
g...@lexort.com (Greg Troxel) writes:
>> vnd opens the backing file when the unit is created and closes
>> the backing file when the unit is destroyed. Then you can access
>> the file again.
>Is there a guarantee of cache consistency for writes before and reads
>after?
Before the unit is
w...@netbsd.org (Thomas Klausner) writes:
>I read about a new microcode update for the AMD Zen family, downloaded
>the linux firmware repository and tried to apply it.
We don't support microcode updates for Zen (just some older AMD model).
g...@lexort.com (Greg Troxel) writes:
>I dimly knew this, but keep forgetting. Reading vndconfig(8), it does
>not explain that the normal path leads to incorrect behavior (stale
>reads from file cache even after closing the vnd, mtime).
vnd opens the backing file when the unit is created and
w...@netbsd.org (Thomas Klausner) writes:
>For a cgd in a file that I mount via vnd+cgd, the file system contents
>inside may change, but the actual file on the hard disk outside only
>has 'access' time changes. So "smart" backup programs that check
>timestamps to find out if they need to re-hash
w...@netbsd.org (Thomas Klausner) writes:
>Follow up question because it just happened to me:
>I have a USB Disk with ffs-on-cgd. I unmounted the ffs but forgot
>unconfiguring the cgd before unplugging the disk.
>Can this cause problems? What kinds?
Shouldn't do any harm, there is no state on
bou...@antioche.eu.org (Manuel Bouyer) writes:
>But the clock softint shouldn't be locked out for 16s, ever.
Then the clock softint must have a higher priority than
everything else including hard interrupts.
Obviously that's not how the system is designed, there
are no limits on how long
mar...@duskware.de (Martin Husemann) writes:
>On Fri, Sep 15, 2023 at 12:17:58PM +0900, Masanobu SAITOH wrote:
>> I think it would be good to change the default behavior from
>> panic to something others because GENERIC kernel enables HEARTBEAT.
>> by default. One of idea is to print warning
bsieg...@gmail.com (Benny Siegert) writes:
>>=20
>> Unfortunately the additional shared library changes require another =
>round
>> of package rebuilds from scratch. Everyond building packages against
>> netbsd-10: please start a new round from scratch.
>Does that mean the pkgsrc-2023Q2 binary
k...@munnari.oz.au (Robert Elz) writes:
>So my current guess (and it is no more than that) would be that if
>powerd happens to notice that happening, which would require it to
>look at just the right time, then powerd does a system shutdown.
>If powerd doesn't notice quickly enough, the CPU (or
ginal, and
> only seems to affect things in turbo mode (higher power draw), as
> this is a new phenomenom in the past month or so.
It's also possible that the heat sink needs attention (re-apply thermal
paste or similar), this might prevent the CPU from reaching a critical
temperature.
Greeting
k...@munnari.oz.au (Robert Elz) writes:
> | You can probably avoid this, if you limit the chip to performance of the
> | non-selected die (in real applications it will probably lose 1-5%). The
> | BIOS should have a setting for the cTDP value that you can play with.
>If I am understanding
k...@munnari.oz.au (Robert Elz) writes:
>I have been running that kernel now for approaching 18 hours. At boot
>time (when coretemp is being attached) Tjmax was read as 115 (on all cores,
>I don't know if that's supposed to be a per-core value, or not, but that
>doesn't matter), and nothing I
es between
both threads:
cpu0: Cluster/Package ID 0
cpu0: Core ID 0
cpu0: SMT ID 0
cpu1: Cluster/Package ID 0
cpu1: Core ID 0
cpu1: SMT ID 1
cpu2: Cluster/Package ID 0
cpu2: Core ID 1
cpu2: SMT ID 0
cpu3: Cluster/Package ID 0
cpu3: Core ID 1
cpu3: SMT ID 1
I expect this to be replaced with som
On Thu, Jun 29, 2023 at 06:01:28PM +0700, Robert Elz wrote:
> It is, and I'm aware of it. I'm not sure why Michael wanted to know
> whether the speed was actually being altered or not,
One possibility would be that the 3401 mode didn't enable turbo frequencies
but actually throttled t
out 40C
when clocked at minimum 800, but heats up to 47C when idling at 3300 and
there is no difference to 3301.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
cessarily for the important workloads.
It now handles big.little configurations independent of cpu numbers,
but probably only on arm.
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
k...@munnari.oz.au (Robert Elz) writes:
> | When this happens, is the machine actually running at 3400 MHz?
>How do I tell?
You could run a benchmark like 'openssl speed sha256' and compare
the 3400 MHz target and the target and step lower.
> | >The motherboard is an AsRock Z690 Taichi.
> |
k...@munnari.oz.au (Robert Elz) writes:
>When the
>cpu frequency target is changed to 3400, all the core temp values drop
>to lower than room air temp (which according to my probably inaccurate
>desk lamp, is currently 22.5, the coretemp values are all in the 15-18
>range at the minute).
When
k...@munnari.oz.au (Robert Elz) writes:
>cpu0: "12th Gen Intel(R) Core(TM) i9-12900KS"
The chip apparently reports a Tjmax of 100 C (as for the non-selected chip)
but actually has a real Tjmax of 115 C.
There are two caveats:
Our driver ignores Tjmax of > 110 C (and uses 100 C as default). If
k...@munnari.oz.au (Robert Elz) writes:
>sysctl -w machdep.cpu.frequency.target=3D2500
>(reducing from the apparent max, 3401) the temps dropped (almost
>instantly) from upper 30's (C) to low 40's, down to the high teens
>or very low 20's.
coretemp temperatures in that range are unlikely to be
r...@sdf.org (RVP) writes:
>I don't get that: there's no pipe there when you do `> file'. So how come
>a Broken pipe still?
It's the communication between ssh and sshd where ssh can no longer write
to a network connection closed by sshd. The problem is to find out why
the connection got closed.
w...@netbsd.org (Thomas Klausner) writes:
>Hi!
>When I try to recursively copy a directory with "scp -r" or sftp's
>"put -Rp" between a -current and a NetBSD 9, I see:
># scp -r a netbsd-9:
>scp: realpath ./a: No such file
>scp: upload "./a": path canonicalization failed
>scp: failed to upload
urrent" but seems something is not right. Does this qualify for a PR or am
> I doing something wrong?
Something surely goes wrong.
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
bbartlomiej.m...@gmail.com (Bartek Krawczyk) writes:
>My /boot/cmdline.txt has only:
>root=NAME=netbsd-root
You can use'ofctl /chosen' to find out what bootargs
are passed to the kernel.
bbartlomiej.m...@gmail.com (Bartek Krawczyk) writes:
>[ 1.4967611] ld0: 117 GB, 15371 cyl, 255 head, 63 sec, 512 bytes/sect
>x 246947840 sectors
>[ 1.5157040] dk0 at ld0: "EFI", 163840 blocks at 32768, type: msdos
>[ 1.5157040] dk1 at ld0: "netbsd-root", 246743040 blocks at 196608,
>[
mar...@duskware.de (Martin Husemann) writes:
> > c++ -dM -E - < /dev/null | fgrep __STDC_VERSION__
>#define __STDC_VERSION__ 201710L
> > c++ -dM -E - < /dev/null | fgrep __ISO
There is magic involved.
% touch c.c
% ls -l c.c
-rw-r--r-- 1 mlelstv staff 0 Mar 31 17:28 c.c
% c++ -dM -E - < c.c
w...@netbsd.org (Thomas Klausner) writes:
>> Make sure c++ with using at least -std=c++11?
>Same error, also with c++17 and gnu++17. Probably lua does something
>weird.
lua defines _XOPEN_SOURCE in lprefix.h:
#if !defined(_XOPEN_SOURCE)
#define _XOPEN_SOURCE 600
#elif _XOPEN_SOURCE
rela...@gmail.com (Greywolf) writes:
>Greetings; I have a couple RPi that I will refer to here as 'thing1'
>and 'thing2'. Both are running evbarm-earmv7h, NetBSD 10-BETA.
The carp driver sent advertising packets through the carp interface
which sets the source MAC address to the CARP virtual
net...@precedence.co.uk (Stephen Borrill) writes:
> Current CritMax WarnMax WarnMin CritMin Unit
>[ipmi0]
>11-LOM-CORE:59.2530.000 110.471degC
>Seen on 9.3_STABLE, but also in 10 BETA.
>I suppose one simple fix would be to ensure
On Sun, Mar 05, 2023 at 10:56:31PM +0100, Michael van Elst wrote:
> On Mon, Mar 06, 2023 at 07:44:20AM +1030, Brett Lymn wrote:
> > On Sun, Mar 05, 2023 at 03:01:02PM -, Michael van Elst wrote:
> > >
> > > - if (guid != NULL && len == 16)
> >
On Mon, Mar 06, 2023 at 07:44:20AM +1030, Brett Lymn wrote:
> On Sun, Mar 05, 2023 at 03:01:02PM -0000, Michael van Elst wrote:
> >
> > - if (guid != NULL && len == 16)
> > + if (guid == NULL || len == 16)
> > +
>
> Shouldn't tha
mlel...@serpens.de (Michael van Elst) writes:
>On Sun, Mar 05, 2023 at 12:56:29PM +, Chavdar Ivanov wrote:
>[ 1.3797015] dk0 at sd0: "EFI system", 262144 blocks at 2048, type:
>msdos
>[ 1.3897890] dk1 at sd0: "cc8f4a89-edc0-48d1-b9ce-b40d227a4a07",
>
;
if (guid != NULL && len == 16)
booted_device = dev;
return;
}
this matches anything.
In this case, the first "ld", "sd" or "wd" device matches as soon
as a netbsd,gpt-guid is passed by the bootloader
ci4...@gmail.com (Chavdar Ivanov) writes:
>Since my last aarch64 build yesterday, 03/03/2023, my machine no
>longer boots automatically,
sys/arch/evbarm/fdt/fdt_machdep.c 1.100
changed how the boot disk is determined. Apparently it now fails for you.
nathanialsl...@yahoo.com.au (Nat Sloss) writes:
>The solution is to use bta2dpd with the pad(4) device which is throttled
>sending only the required amount of audio data in the right time.
In current or in netbsd-9 ?
w...@netbsd.org (Thomas Klausner) writes:
>> The biggest change recently is probably that my bulk build switched
>> from ghc92 to ghc94, but I don't know if that could cause this.
>Next bulk build, next panic, quite reliably. Has anyone else seen this?
Not yet, maybe this is the first use of
mayur...@acm.org (Mayuresh) writes:
>What do I miss if I don't give dri permission? E.g. would firefox be
>terribly slower?
It is slower, and much slower for anything using video content or
things like WebGL.
>I can already see that I can't even run xscreensaver-demo. I can
>understand
mayur...@acm.org (Mayuresh) writes:
>Can someone throw some light on whether wheel membership is mandatory for
>dri? And about the crash if such permission is given?
It's the opposite, the DRI device needs to be accessible to users
that should be allowed to use it. You could create a 'drm'
mayur...@acm.org (Mayuresh) writes:
>On Tue, Dec 27, 2022 at 07:35:56PM +0530, Mayuresh wrote:
>> Is N supported on 10.0 BETA? Is some configuration required to enable the
>> same?
>Which component decides this - firmware? driver? kernel? something else?
All of them.
>Is Wireless N generally
t...@netbsd.org (Tobias Nygren) writes:
>$ nc -n -v 127.0.0.1 1234
># hangs forever in connect(2) instead of exiting w/ connection refused.
The logic in tcp_drop() got reversed:
@@ -1042,17 +1017,12 @@ tcp_newtcpcb(int family, void *aux)
struct tcpcb *
tcp_drop(struct tcpcb *tp, int errno)
{
ozak...@netbsd.org (Ryota Ozaki) writes:
>I've committed a possible fix. Could you try it?
>Thanks,
> ozaki-r
I just got a NULL pointer dereference in tcp_ctloutput where
the previous check for inp == NULL is also missing.
[ 24837.756043] fp c0016794db70 tcp_ctloutput() at
buh...@nfbcal.org (Brian Buhrow) writes:
> 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
buh...@nfbcal.org (Brian Buhrow) writes:
>Then, to record:
>cat /dev/sound2 > rawrecordingfile
Can you just try the audiorecord command instead of 'cat' ?
buh...@nfbcal.org (Brian Buhrow) writes:
> hello. thanks for the feedback. In my case, recording doesn't work
> for hdaudio or uaudio
>devices. What's strange is that I would expect data to be taken from the
>wrong input,
>resulting in a file of silence, but I wouldn't expect kernel
r...@sdf.org (RVP) writes:
>Perhaps the correct ADC was not selected? See Section 10.6.1 in the Guide[1].
If I follow this and use "all available sources", I get twice the
amount of data, the sources are interleaved in the input stream.
hdafg0: ADC02 2ch: Mic In [Jack]
hdafg0: ADC03 2ch: Mic
a...@sdf.org (adr) writes:
>On Mon, 3 Oct 2022, Michael van Elst wrote:
>>>> Yes, almost all USB audio devices work. We don't support the audio 2.0
>>>> standard (that's the >= 192kHz 24bit devices).
>>>>
>>> Ok, thanks for the info.
>>
a...@sdf.org (adr) writes:
>On Mon, 3 Oct 2022, Michael van Elst wrote:
>> a...@sdf.org (adr) writes:
>>
>>> Are usb audio devices working in other machines? I've been looking
>>> at the tech-kern archives and I don't see any recent discussion on
>>&
a...@sdf.org (adr) writes:
>Are usb audio devices working in other machines? I've been looking
>at the tech-kern archives and I don't see any recent discussion on
>this.
Yes, almost all USB audio devices work. We don't support the audio 2.0
standard (that's the >= 192kHz 24bit devices).
a...@sdf.org (adr) writes:
>By the way, this is on an rpi4.
xhci(4) still has issues with isochronous transfers, in particular with
the USB3 chip used by rpi4.
ll...@must-have-coffee.gen.nz (Lloyd Parkes) writes:
>HÃ¥vard's email about his G4 Mac Mini is an excellent example
>of a problem. A problem I have experienced in the past was a program
>failing with out of memory errors while processing 128MB of data on a
>system with 256MB of RAM. A problem
sparc64 with 12GB RAM - firefox and claws
would get swapped out while the buffer cache would stay at 8GB or more,
with a couple cc1plus instances fighting over the remaining RAM.
have fun
Michael
p...@whooppee.com (Paul Goyette) writes:
>I have completely disconnected the wd0 and wd1 hard drives, and now
>the motherboard/BIOS can't find something (primary boot?). It does
>not give any helpful messages (no messages at all), but just goes
>back to the interactivve BIOS screens.
It's
jo...@bec.de (Joerg Sonnenberger) writes:
>On Sat, Sep 03, 2022 at 10:00:04AM +1200, Lloyd Parkes wrote:
>> Does anyone know of a maintained DHCP relay implementation?
>The better question for me is: are DHCP relayer server still in use?
Yes.
clays.sh...@sdf.org (Clay Daniels) writes:
>On 8/29/22 12:32 AM, Michael van Elst wrote
>> It should work, but how does it perform?
>Are there any specific tests I can perform? I have working NetBSD install.
Any effects should be mostly visible by copying large-enough files with sc
On Mon, Aug 29, 2022 at 04:57:44AM +, Clay Daniels wrote:
> On Sat, 27 Aug 2022, Michael van Elst wrote:
>
> > Date: Sat, 27 Aug 2022 22:21:17 - (UTC)
> > From: Michael van Elst
> > To: current-users@netbsd.org
> > Newsgroups: lists.netbsd.current-u
clays.sh...@sdf.org (Clay Daniels) writes:
>home. I would love to help test what I can. Do I need to get a more
>recent snapshot? I see one on the server that is 27 Aug 07:34. Would
>that one work?
The next snapshot will have it.
buh...@nfbcal.org (Brian Buhrow) writes:
> 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?
With only the client using HPN, you can tune the client receive buffer,
which may or may not
In https://mail-index.netbsd.org/current-users/2017/09/20/msg032361.html
there was a discussion about effectiveness of the "High Performance
Networking" patch to OpenSSH that we keep in our tree.
Details about the HPN patch can be found at:
https://www.psc.edu/hpn-ssh-home/hpn-ssh-faq/
This led
out possible HZ values.
But I doubt these issues are difficult to find and to fix.
Providing a common boot parameter over all ports and port masters
on the other hand starts with the question what color it should be
painted.
Greetings,
--
Michael van Els
k...@munnari.oz.au (Robert Elz) writes:
>Pity this won't help with PR 43997 - but I conclude from your response about
>that, that if the host running qemu had HZ set significantly higher than 100
>then qemu (hosting a kernel with HZ==100) would probably work just fine?
Yes.
FreeBSD has the
s...@stix.id.au (Paul Ripke) writes:
>This is likely somewhat similar to what I reported here:
>http://mail-index.netbsd.org/current-users/2019/07/29/msg036293.html
>tl;dr: weird clock behaviour on GCE micro instances. This at least
>provides a nice easy testbed.
| ACPI-Safe: ntp syncs fine,
some interval), but that's a different problem.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mlel...@serpens.de (Michael van Elst) writes:
>In your case, you say it takes ~6 minutes between attachment and
>calibration and your hpet runs at 19.2MHz.
>This is enough for HPET_MCOUNT_LO to overflow.
This patch adds a separate delay of ~0.1 seconds to calibrate
the timers. Th
On Sun, Aug 14, 2022 at 02:38:07AM +0700, Robert Elz wrote:
> Date:Sat, 13 Aug 2022 17:41:05 +0200
> From: Michael van Elst
> Message-ID:
>
> | If you boot the kernel in debug mode (netbsd -x),
>
> I did.
>
> | you may
e. It's
also the only place that could have been influenced by e.g. console
output.
If you have a working HPET, the second calibration should be better.
Here it always returns exactly the same number.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
k...@munnari.oz.au (Robert Elz) writes:
>vpanic()
>kern_assert()
>_bus_dmamem_unmap.constprop.0() at +0x157
That panic should be fixed by now, it was an inverted assertion.
k...@munnari.oz.au (Robert Elz) writes:
>Date:Thu, 4 Aug 2022 12:49:35 - (UTC)
>From:mlel...@serpens.de (Michael van Elst)
>Message-ID:
> | The measurement runs with enabled interrupts. If you have lots of
> interrupts
> | or interrupts t
k...@munnari.oz.au (Robert Elz) writes:
>The issue only occurs when I boot a kernel with options PCI_CONFIG_DUMP
>enabled, which is (one way or the other) almost certainly responsible for
>the issue - though the problem you mention may be involved in the kernel's
>failure to detect that the TSC
dholland-curr...@netbsd.org (David Holland) writes:
>On Thu, Jul 14, 2022 at 08:59:25PM +0700, Robert Elz wrote:
> > I just booted a kernel that I built (from up to date at the time)
> > HEAD sources about 24 hours ago.
> >
> > Everything seemed to be working fine - until I noticed that all of
>
t; the new xorg-server.
>
> there are probably a few build issues left to find
> across all ports, and perhaps some run-time ones too
> but basic testing looks fine for me.
Alright, I'll check all my weirdo drivers!
have fun
Michael
r...@sdf.org (RVP) writes:
>Unsurprisingly, EFI also has a colour-index similar to VGA (see:
>/usr/src/sys/external/bsd/gnu-efi/dist/inc/eficon.h). I tried fixing the
>indexes like this, but, it doesn't for some (autoconfig?) reason. Can
>only look into this after I come back from my road-trip.
k...@munnari.oz.au (Robert Elz) writes:
> | Heh. It's not just Cyan/Yellow; Red and Blue are swapped too, because:
> |
> | /usr/src/sys/dev/wscons/wsdisplayvar.h and
> | /usr/src/sys/dev/ic/pcdisplay.h have different values for those colour=
>s.
>If that is all it is, it is barely worth
m...@eterna.com.au (matthew green) writes:
>FWIW, i've been using 64K block *and frag size FFS for over
>a decade without any problem, on a file system that almost
>always has extremely large files on it.
>so, this should be fixed in the manual i guess.
The manual just lists the default values
ha...@espresso.rhein-neckar.de (Hauke Fath) writes:
>Jul 10 22:56:18 pizza istgt[9108]:=20
>istgt_iscsi.c:4165:istgt_iscsi_op_nopout: ***ERROR*** CmdSN(24873146)=20
>error ExpCmdSN=3D24873145=20
>Jul 10 22:56:18 pizza istgt[9108]:=20
>istgt_iscsi.c:5045:istgt_iscsi_execute: ***ERROR***
ha...@espresso.rhein-neckar.de (Hauke Fath) writes:
>I would like to set up an iscsi target backed by a zfs zvol, to serve=20
>as a Mac time machine volume.
Independent of your problem you should use 'istgt' from pkgsrc.
r...@sdf.org (RVP) writes:
>@@ -255,7 +255,7 @@
> echo ${bar} Populating ffs filesystem ${bar}
> ${MAKEFS} -rx ${endian} -N ${release}/etc -t ffs \
> -O ${ffsoffset} \
>- -o d=4096,f=8192,b=65536 -b $((${extra}))m \
>+ -o d=8192,f=2048,b=16384 -b
k...@munnari.oz.au (Robert Elz) writes:
>Does someone know of a reason for a setting for the rc.conf
>(rc.d/*) variable raidframeparity to be omitted from rc.defaults/rc.conf ?
>To me that looks like an oversight.
raidframeparity has no rcvar switch, it's always started.
m...@petermann-it.de (Matthias Petermann) writes:
>since some time I noticed that on several of my systems with=20
>NetBSD/amd64 9.99.97/98 after longer usage the kernel process pgdaemon=20
>completely claims a CPU core for itself, i.e. constantly consumes 100%.
>The affected systems do not have
campbell+netbsd-current-us...@mumble.net (Taylor R Campbell) writes:
>This would need to be integrated into autoconf/specfs to avoid races
>in config_pseudo_spawn, sc->sc_configured, and config_pseudo_unspawn,
vnd is peculiar in that it spawns a unit whenever it is opened and
removes it again
bou...@antioche.eu.org (Manuel Bouyer) writes:
>Hello,
>do you have an idea on the problem in this thread:
>http://mail-index.netbsd.org/port-xen/2022/05/27/msg010213.html
[...]
>I can't reproduce this when using vnd from userland.
You can replicate it by addressing the block device with
k...@munnari.oz.au (Robert Elz) writes:
>My suspicion when I first saw this was that in legacy mode
>the BIOS is doing some console graphics init (and leaving it
>that way) which NetBSD is depending upon, which at least
>some firmware either does not do at all, or undoes, or
>fails to pass along
rnes...@mac.com (Robert Nestor) writes:
>Following Michael=92s advice I added this line to sys/dev/usb/usbdevs =
>where other Prolific devices were defined:
> product PROLIFIC PL2303Y 0x23c3 PL2303 Serial adapter (Null =
>modem)
I've now added a few models to usbdevs...
&g
rnes...@mac.com (Robert Nestor) writes:
>capture system). The USB-Serial device shows up on boot on the capture =
>system as:
>ugen0: Prolific Technology Inc. (0x67b) USB-Serial Controller (0x23c3), =
>rev 2.00/3.05, addr 1
Means, it doesn't really show up.
>I=92m thinking I need to build a
mlel...@serpens.de (Michael van Elst) writes:
>I'm currently testing:
>Index: lib/libpthread/pthread.c
>===
>RCS file: /cvsroot/src/lib/libpthread/pthread.c,v
>retrieving revision 1.153.2.1
>diff -p -u -r1.153.2.1
w...@netbsd.org (Thomas Klausner) writes:
>With a quite recent 9.99.96/amd64 kernel, when deleting ~800GB of data =
>on an ffs2 on a mostly empty 8TB file system, I just saw this panic:
>panic: kernel diagnostic assertion =E2=80=9C(wapbl_transaction_len(wl) =
><=3D (wl->wl_circ_size -
mlel...@serpens.de (Michael van Elst) writes:
>c...@chuq.com (Chuck Silvers) writes:
>>> would this apply to netbsd-9 too ? The hang I'm seeing is on a system
>>> with a HEAD kernel and a netbsd-9 userland
>>it looks like the diff won't apply as-is, but I think t
c...@chuq.com (Chuck Silvers) writes:
>> would this apply to netbsd-9 too ? The hang I'm seeing is on a system
>> with a HEAD kernel and a netbsd-9 userland
>it looks like the diff won't apply as-is, but I think the concept still
>applies.
I'm currently testing:
Index:
1 - 100 of 411 matches
Mail list logo
