On 2024/01/27 10:36, Radek wrote:
> but it doesn't work for another APC UPS hardware
> uhidev0 at uhub0 port 3 configuration 1 interface 0 "American Power
> Conversion Smart-UPS 2200 FW:UPS 09.3 / ID=18" rev 2.00/1.06 addr 2
...
> > > On 2024-01-19 13:21, Stuart Henderson wrote:
> > > >
On Sat, Jan 27, 2024 at 08:01:09AM +0100, Hrvoje Popovski wrote:
> On 26.1.2024. 21:56, Marcus Glocker wrote:
> > On Fri, Jan 26, 2024 at 11:41:49AM +0100, Hrvoje Popovski wrote:
> >
> >> I've manage to reproduce TSO em problem on anoter setup, unfortunatly
> >> production.
> >>
> >> Setup is
On 2024/01/28 00:20, stephane Tranchemer wrote:
> Got it !
>
> I had a hunch so I modified all the tty0X the same way as tty00 to see if
> someone answers:
>
> tty00 "/usr/libexec/getty std.115200" vt220on secure
>
> and I got a tty at next reboot.
> However I find myself on tty04, so it
On 27.1.2024. 21:01, Marcus Glocker wrote:
> On Sat, Jan 27, 2024 at 08:01:09AM +0100, Hrvoje Popovski wrote:
>
>> On 26.1.2024. 21:56, Marcus Glocker wrote:
>>> On Fri, Jan 26, 2024 at 11:41:49AM +0100, Hrvoje Popovski wrote:
>>>
I've manage to reproduce TSO em problem on anoter setup,
Got it !
I had a hunch so I modified all the tty0X the same way as tty00 to see
if someone answers:
tty00 "/usr/libexec/getty std.115200" vt220on secure
and I got a tty at next reboot.
However I find myself on tty04, so it would mean that com4 goes invariably to
tty04 even if this
This should be fixed with
https://cvsweb.openbsd.org/src/lib/libssl/tls13_legacy.c#rev1.43
which you should be able to backport to 7.4 without issues if you don't
want to use current.
The short version is that it is an unfortunate interaction between nginx
fiddling with internal state of the
> Date: Sat, 27 Jan 2024 18:49:02 +
> From: Mikolaj Kucharski
>
> Mark,
>
> On Sat, Jan 27, 2024 at 03:05:10PM +0100, Mark Kettenis wrote:
> > > Date: Sat, 27 Jan 2024 22:47:05 +0900
> > > From: stephane Tranchemer
> > >
> > > Hello Jonathan,
> > >
> > > made a kernel with the patch and
Mark,
On Sat, Jan 27, 2024 at 03:05:10PM +0100, Mark Kettenis wrote:
> > Date: Sat, 27 Jan 2024 22:47:05 +0900
> > From: stephane Tranchemer
> >
> > Hello Jonathan,
> >
> > made a kernel with the patch and here is what I get on dmesg:
> >
> > puc0 at pci0 dev 26 function 0 "Intel C3000 UART"
> Date: Sat, 27 Jan 2024 22:47:05 +0900
> From: stephane Tranchemer
>
> Hello Jonathan,
>
> made a kernel with the patch and here is what I get on dmesg:
>
> puc0 at pci0 dev 26 function 0 "Intel C3000 UART" rev 0x11: ports: 16 com
> com4 at puc0 port 0 apic 2 int 16: ns16550a, 16 byte fifo
>
On Sat, Jan 27, 2024 at 07:54:43PM +0900, stran...@free.fr wrote:
> >Synopsis:Console is lost at boot when com0 is on a UART PCI
> >Category:system amd64
> >Environment:
> System : OpenBSD 7.4
> Details : OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023
>
Hello Jonathan,
made a kernel with the patch and here is what I get on dmesg:
puc0 at pci0 dev 26 function 0 "Intel C3000 UART" rev 0x11: ports: 16 com
com4 at puc0 port 0 apic 2 int 16: ns16550a, 16 byte fifo
so now it seems to get the com port, however when I type "set tty com4"
on the boot
I said works with
stty com4 115200
mach comaddr 0xe060
set tty com4
but not entirely...
I indeed get the output of the kernel loading and the system is up, but I don't
get a login prompt at the end.
Here is a sample of the last lines I get throught console:
[...]
clearing /tmp
On Sat, Jan 27, 2024, at 8:21 AM, stephane Tranchemer wrote:
> I said works with
>
> stty com4 115200
> mach comaddr 0xe060
> set tty com4
>
> but not entirely...
> I indeed get the output of the kernel loading and the system is up, but
> I don't get a login prompt at the end.
>
> Here is a
Works !
I actually had to do
stty com4 115200
mach comaddr 0xe060
set tty com4
Le 27/01/2024 à 23:05, Mark Kettenis a écrit :
Date: Sat, 27 Jan 2024 22:47:05 +0900
From: stephane Tranchemer
Hello Jonathan,
made a kernel with the patch and here is what I get on dmesg:
puc0 at pci0 dev 26
but it doesn't work for another APC UPS hardware
OpenBSD 7.4-current (GENERIC.MP) #1623: Tue Jan 23 22:30:16 MST 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4259917824 (4062MB)
avail mem = 4110110720 (3919MB)
random: good seed from bootblocks
>Synopsis:Console is lost at boot when com0 is on a UART PCI
>Category:system amd64
>Environment:
System : OpenBSD 7.4
Details : OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023
> Date: Sat, 27 Jan 2024 19:54:43 +0900 (JST)
> From: stran...@free.fr
>
> >Synopsis:Console is lost at boot when com0 is on a UART PCI
> >Category:system amd64
> >Environment:
> System : OpenBSD 7.4
> Details : OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023
>
Hello Brian,
Thanks for confirming, I changed in /etc/ttys the line
tty00 "/usr/libexec/getty std.9600" unknown off
to
tty00 "/usr/libexec/getty std.115200" vt220 on secure
but get no change.
Le 27/01/2024 à 23:56, Brian Conway a écrit :
On Sat, Jan 27, 2024, at 8:21 AM, stephane
Thanks so much for this very clear explanation, I didn’t know that one.
I have a question regarding the patch I successfully applied on the kernel,
could such modification be accepted as a syspatch in the actual 7.4 release or
should it be expected in CURRENT and planned for the next to come
On Sun, Jan 28, 2024 at 10:46:43AM +0900, Tranchemer Stéphane wrote:
> Thanks so much for this very clear explanation, I didn’t know that one.
>
> I have a question regarding the patch I successfully applied on the kernel,
> could such modification be accepted as a syspatch in the actual 7.4
20 matches
Mail list logo
