No badness observed other than this spew in dmesg:
iwx0 at pci0 dev 20 function 3 "Intel Wi-Fi 6 AX201" rev 0x00, msix
iwx0: could not read firmware iwx-QuZ-a0-hr-b0-48 (error 2)
iwx0: failed to load init firmware
iwx0 at pci0 dev 20 function 3 "Intel Wi-Fi 6 AX201" rev 0x00, msix
iwx0: could not
On Tuesday, February 23, 2021 8:40 AM, Stuart Henderson
wrote:
[...]
> bios0: vendor coreboot version "4.0.7" date 02/28/2017
> bios0: vendor coreboot version "v4.12.0.1" date 05/29/2020
>
> Note that flashrom allows updating firmware on pcengines APU from OpenBSD.
> flashrom's pkg-readme file
Ashton Fagg writes:
> Ooh, yeah actually you are probably right.
>
> I also misread your initial email - you said "iscsictl should wait and
> fail", I read it as "iscsid should wait and fail". ;-)
>
> Sorry for the confusion. I'll experiment a bit and see if I can come up
> with a patch. I
> On Sun, Feb 21, 2021 at 04:45:19PM +, marfabastewart wrote:
>
> [...]
>
> > and this is the output of sendbug -P on an APU2
> > with the patch compiled in, after plugging in
> > the USB drive and rebooting. The USB drive is not
> > detected on the APU2 on boot, but the lines
> > from the
Claudio Jeker writes:
> Isn't that the 2nd iscsid that is started? IIRC your pictures showed that
> once you exited single user mode that another iscsid was started (but
> maybe I just interpreted the images wrong).
Ooh, yeah actually you are probably right.
I also misread your initial email -
On 2021/02/23 13:48, Marfaba Stewart wrote:
> > On Sun, Feb 21, 2021 at 04:45:19PM +, marfabastewart wrote:
> >
> > [...]
> >
> > > and this is the output of sendbug -P on an APU2
> > > with the patch compiled in, after plugging in
> > > the USB drive and rebooting. The USB drive is not
> > >
Synopsis: Basic Regular Expression (BRE) bug in \{m,n\} with \(\) and \n
Category: library
Environment:
System : OpenBSD 6.7
Details : OpenBSD 6.7 (GENERIC) #7: Wed Jan 6 15:19:25 MST 2021
On Tue, Feb 23, 2021 at 07:39:17AM -0500, Ashton Fagg wrote:
> Claudio Jeker writes:
>
> > I'm not sure. vscsi(4) is ready the moment the kernel starts init. So it
> > should not result in any problem for iscsid. What made you think this is
> > the issue?
>
> Yeah, so in /var/log/daemon, you
Claudio Jeker writes:
> I'm not sure. vscsi(4) is ready the moment the kernel starts init. So it
> should not result in any problem for iscsid. What made you think this is
> the issue?
Yeah, so in /var/log/daemon, you see this:
Feb 20 18:59:28 elara iscsid[52173]: startup
Feb 20 18:59:28 elara
On Tue, Feb 23, 2021 at 07:07:34AM -0500, Ashton Fagg wrote:
> Claudio Jeker writes:
>
> > Looking at the screenshot it seems there is a timing issue. The fsck -N
> > tries to run before the disk was actually attached. I guess the iscsid
> > startup script should wait to ensure the disks are
On 2021/02/22 14:55, Theo de Raadt wrote:
> There are a bunch of problems being caused by some sort of kernel
> memory exhaustion.
>
> Whatever it is, I think it was introduced back around November
6.8 on mine
> My point is this is unrecoverable. It seems to happen quite suddenly.
>
>
Claudio Jeker writes:
> Looking at the screenshot it seems there is a timing issue. The fsck -N
> tries to run before the disk was actually attached. I guess the iscsid
> startup script should wait to ensure the disks are ready.
> You could probably add a 'sleep 5' to rc_start() in
On 2021/02/22 13:48, Stuart Henderson wrote:
> Not much information on this but it's an unusual one so I thought I'd
> post in case it's of interest to anyone. (Re-typed from a screen photo,
> it's remote and used by non-technical people, this is all I have).
>
> panic: uao_fin_swhash_elt: can't
On Sun, Feb 21, 2021 at 04:45:19PM +, marfabastewart wrote:
[...]
> and this is the output of sendbug -P on an APU2
> with the patch compiled in, after plugging in
> the USB drive and rebooting. The USB drive is not
> detected on the APU2 on boot, but the lines
> from the patch are generated:
On 23/02/21(Tue) 07:53, Jonathan Matthew wrote:
> On Mon, Feb 22, 2021 at 01:48:01PM +, Stuart Henderson wrote:
> > Not much information on this but it's an unusual one so I thought I'd
> > post in case it's of interest to anyone. (Re-typed from a screen photo,
> > it's remote and used by
On 22/02/21(Mon) 13:48, Stuart Henderson wrote:
> Not much information on this but it's an unusual one so I thought I'd
> post in case it's of interest to anyone. (Re-typed from a screen photo,
> it's remote and used by non-technical people, this is all I have).
>
> panic: uao_fin_swhash_elt:
On Mon, Feb 22, 2021 at 09:27:58PM -0500, Ashton Fagg wrote:
> >Synopsis:Mouting iSCSI disk at boot time causes machine to enter single
> >user mode.
> >Category:Bug.
> >Environment:
> System : OpenBSD 6.9
> Details : OpenBSD 6.9-beta (GENERIC.MP) #346: Fri Feb 19
17 matches
Mail list logo
