Hi,
I've got a random crash while mouse-pasting text in the console:
uvm_fault(0xff021d131a00, 0x730d491b, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at rasops32_putchar+0xf2: movzbl 0x3(%r12),%r8d
ddb> trace
rasops32_putchar(80125148,31,0,ffab6b3a,7,31) at rasops32_putchar+
On 2022/08/08 07:59, Hendrik Meyburgh wrote:
> Hi.
>
> I started a sysupgrade to snapshot last night and left it unattended. I
> assume it rebooted after it downloaded the software and now it is in this
> state. I am not sure if this is before or after the install of the snapshot.
>
jpegs show
>Synopsis: kernel crash on shutdown
>Category: kernel amd64
>Environment:
System : OpenBSD 7.2
Details : OpenBSD 7.2 (GENERIC.MP) #4: Mon Dec 12 06:06:42 MST 2022
r...@syspatch-72-amd64.openbsd.org:/usr/src/sys/arch/amd6
Hi,
while switching networks a kernel crash appeared:
ddb{0}> show panic
kernel diagnostic assertion "p->p_wchan == NULL" failed: file
"/usr/src/sys/kern/kern_sched.c", line 328
Steps were:
ifconfig iwm0 down
route -n flush
sh /etc/netstart axen0
Crash happen
Hi there,
I've been hitting a kernel crash on both OpenBSD 5.6 and 5.7.
See below for the dmesg + a picture[0] of the crash. There was no ddb prompt
so there is little information there.
For the details on the OpenBSD 5.6 crash (managed to drop into ddb there)
see http://marc.in
rd.co/Hv3PTed.jpg
# 5
https://pasteboard.co/Hv3QfEe.jpg
# 6
https://pasteboard.co/Hv3QDNR.jpg
--
Eivind Eide
"ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD"
- Oceania Association of Autonomous Astronauts
>Synopsis: Kernel crash
>Category: Kern
# INPUT
Mounting ramdisk kernel.
# OUTPUT
...
mode = 0100644, inum = 173, fs = /mnt/vnd0a
panic: ffs_valloc: dup alloc
Stopped at db_enter+0x10: popq%rbp
TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
* 69200 60093 0 0x3 00K install
db_enter() at d
Dear OpenBSD-Team,
I have a kernel crash in OpenBSD 6.5 with all 6 patches applied.
My system:
+--+ ++ ++ +---+
| Cisco-Router |--em1--| OpenBSD-Bridge |--em0--| D-Link |- -| Other
Just ran into this issue, but unfortunately I can't reproduce.
Steps I took were: I rebooted the vm (openbsd-current from couple of
weeks old) via ssh and after disconnect I immediately connected via vmctl
console 1. The crash happened almost as soon as I hit enter.
martijn@
uvm_fault(0x8
Hi,
after the recent OpenBSD 7.0 updateI tried again
to install it into the Toshiba R50 laptop.
But for my dismay still have the same issue :
After a sucessfull installaiton I get something like this:
ehci0 at pci0 dev 29 function "Intel 8 Series USB" rev 0x04
usb1 at ehci0: USB revis
Hi,
I was building ports and at the same time started chromium and the
kernel panic-ed.
This has happened a few times in the last week. It started happening
at some point towards the end of May. It is not easy to reproduce locally.
I followed ddb.html and taken some pictures[0] of the crash.
Hi,
this is a kernel build on Sat. 2016-01-09 from source plus
Subject:rework em(4) tx ring handling
From: David Gwynne
Date: 2016-01-08 5:18:50
panic is at the end, unfortunatly it ran with bad ddb settings.
entry point at 0x1000160 [7205c766, 3404, 24448b12,
Yes, this is known and here is the work in progress to fix it.
There are one or two problem cases still in softraid and wdc.
Index: arch/alpha/alpha/machdep.c
===
RCS file: /cvs/src/sys/arch/alpha/alpha/machdep.c,v
retrieving revisio
erial attached
later.
https://imgur.com/a/D2S7u
The old picture got moved:
https://imgur.com/a/tjd9C
Am 25.01.2018 18:07 schrieb j...@posteo.de:
Hi,
while switching networks a kernel crash appeared:
ddb{0}> show panic
kernel diagnostic assertion "p->p_wchan == NULL" failed: fi
n:
why are you not including a dmesg?
On 2018-01-26 09:47, j...@posteo.de wrote:
Hi,
it happened again. Steps:
Suspending laptop while connected to wifi via iwm0.
Wake up laptop without reconnecting to any wifi.
Plugged in the axen driven usb network card and netstarting axen0.
Crash while doi
On Wed, Jul 18, 2018 at 08:39:17PM +0200, Eivind Eide wrote:
> Over several snapshots after 6.3 I get reliable system crash after a
> few minutes uptime on this old i386 machine of mine.
It would be helpful to know when this started. Does it happen with
6.3? Since 6.3 we have commited i386 Meltd
2018-07-18 23:04 GMT+02:00 Alexander Bluhm :
> On Wed, Jul 18, 2018 at 08:39:17PM +0200, Eivind Eide wrote:
>> Over several snapshots after 6.3 I get reliable system crash after a
>> few minutes uptime on this old i386 machine of mine.
>
> It would be helpful to know when this started. Does it hap
For bluhm and bugs@ readers, Eivind narrowed it down to between these:
OpenBSD 6.3-current (GENERIC) #567: Sun Apr 22 08:12:07 MDT 2018
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
OpenBSD 6.3-current (GENERIC) #568: Tue Apr 24 23:16:33 MDT 2018
dera...@i386.openbsd.org
On Fri, Jul 20, 2018 at 05:22:20PM +0100, Stuart Henderson wrote:
> For bluhm and bugs@ readers, Eivind narrowed it down to between these:
>
> OpenBSD 6.3-current (GENERIC) #567: Sun Apr 22 08:12:07 MDT 2018
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>
> OpenBSD 6.3-cur
2018-07-20 21:29 GMT+02:00 Alexander Bluhm :
>
> There were no i386 specific commits in this time frame, especially
> no Meltdown fixes.
>
> There was an "update ttm and radeondrm(4) to Linux 4.4.129" commit
> and I know that it was tested before in snapshots. So it might be
> related to that. I
On Sat, Jul 21, 2018 at 09:30:36PM +0200, Eivind Eide wrote:
> There are no crash with drm disabled. I'm attaching the dmesg to this
> mail. So the update to radeondrm are the cause.
So we know that "ATI Radeon Mobility M7" is broken with the new drm
code. Unfortunately I have no experience with
> Date: Mon, 23 Jul 2018 11:09:28 +0200
> From: Alexander Bluhm
>
> On Sat, Jul 21, 2018 at 09:30:36PM +0200, Eivind Eide wrote:
> > There are no crash with drm disabled. I'm attaching the dmesg to this
> > mail. So the update to radeondrm are the cause.
>
> So we know that "ATI Radeon Mobility
On Mon, Jul 23, 2018 at 11:09:28AM +0200, Alexander Bluhm wrote:
> On Sat, Jul 21, 2018 at 09:30:36PM +0200, Eivind Eide wrote:
> > There are no crash with drm disabled. I'm attaching the dmesg to this
> > mail. So the update to radeondrm are the cause.
>
> So we know that "ATI Radeon Mobility M7"
2018-07-23 11:27 GMT+02:00 Mark Kettenis :
>
> Interested, but the posted traceback doesn't contain any useful clues
> to even start looking. For some reason, immediately after the
> uvm_fault() another kernel fault happens while entering ddb. So the
> traceback we need to see where the fault hap
Synopsis: Once a day, my APU1D4 used to crash
Category: kernel
Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.
Le Mon, 04 May 2020 10:11:02 +,
Rupert Gallagher a écrit :
> > dmesg, bsd.rd version, hw info? Missing
>
> HW info, boot dmesg and bsd.rd are irrelevant in this case. The hw
> works very well with obsd, and the crash occurred when *I* was
> mounting a disk image.
Maybe it's a CPU related
> dmesg, bsd.rd version, hw info? Missing
HW info, boot dmesg and bsd.rd are irrelevant in this case. The hw works very
well with obsd, and the crash occurred when *I* was mounting a disk image.
> Steps to repro? Missing
I assume bug@ knows how to mount a disk image.
> The page <[https://www.o
On 2020/05/04 22:57, Rupert Gallagher wrote:
> > So you don't think there could be something odd in the bsd.rd so you would
> > write
> "download bsd.rd #234234 from ftp.unsynchedmirror.com or my copy here"
> Perhaps this was fixed in 6.5 and you are running something older?
>
> Why bothering a
On 2020/05/04 23:03, Rupert Gallagher wrote:
> > Maybe it's a CPU related bug, who knows.
> Maybe you are using powerpc or arch64 and your bug isn't reproducible on
> amd64.
>
> No, the CPU is an amd64. It is was something else, I would have mentioned it.
You aren't going to get accurate replies
> So you don't think there could be something odd in the bsd.rd so you would
> write
"download bsd.rd #234234 from ftp.unsynchedmirror.com or my copy here"
Perhaps this was fixed in 6.5 and you are running something older?
Why bothering about Mars when you have your feet wet on Earth?
bsd.rd, as
> Maybe it's a CPU related bug, who knows.
Maybe you are using powerpc or arch64 and your bug isn't reproducible on amd64.
No, the CPU is an amd64. It is was something else, I would have mentioned it.
> There is a page explaining how to report bug properly
> https://www.openbsd.org/report.html
>> bsd.rd, as well as everything else not in the OP, is irrelevant. I was not
>> running bsd.rd and I was not mounting its disk image, so stop asking for it.
> If you already know that it's irrelevant, then maybe don't bother asking for
> help on a mailing list which specifically asks you to pro
How about clearing your head from all those irrelevant questions of yours, and
focus instead on the info you already have in the OP?
It is a shame for obsd's kernel to crash when mounting a disk image, so focus
on the actual kernel crash to figure out a way to prevent this problem
upert Gallagher wrote:
> How about clearing your head from all those irrelevant questions of yours,
> and focus instead on the info you already have in the OP?
>
> It is a shame for obsd's kernel to crash when mounting a disk image, so focus
> on the actual kernel crash to figure
Hello bugs@,
I'm maybe feeding the troll, so to say, but wanted to give it a chance.
After all, it might be correct, right?
So, what do we have? A partial traceback, a partial input, and a partial
OS version. Subject: line indicates it's v6.6-stable, which, according
to [1], is 6.6 plus errata pa
On Tuesday, May 5, 2020, Lucas wrote:
> Hello bugs@,
>
> I'm maybe feeding the troll, so to say, but wanted to give it a chance.
> After all, it might be correct, right?
Check the mailing list archives for his name, he's a recurrent troll
>
> So, what do we have? A partial traceback, a partia
On 2019/07/30 11:15, Illya Meyer wrote:
> Dear OpenBSD-Team,
>
> I have a kernel crash in OpenBSD 6.5 with all 6 patches applied.
I think this is the same crash reported in
https://marc.info/?l=openbsd-bugs&m=155857827825633&w=2
I'm not sure what happened with that ..
On 30.7.2019. 13:34, illya.me...@wiesan.de wrote:
> Am 30.07.19 um 13:17 schrieb Hrvoje Popovski:
>> 2) - download install.iso, burn it on cd or usb disk
>> 3) - boot from cd or usb
>
> That's not so easy, I haven't a monitor at this machine.
> I try the „manual update process“ via ssh and if I cr
On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> I was building ports and at the same time started chromium and the
> kernel panic-ed.
>
> This has happened a few times in the last week. It started happening at
> some point towards the end of May. It is not easy to reproduce locally.
Thank y
On Mon, Jun 13, 2016 at 08:42:35AM -0700, Philip Guenther wrote:
> On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> > I was building ports and at the same time started chromium and the
> > kernel panic-ed.
> >
> > This has happened a few times in the last week. It started happening at
> > some
elow is all the stuff sendbug(1) outputs (not immediately after crash):
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-beta (compile) #0: Fri Jun 10 13:12:32 CEST 2016
matej@puffy:/home/matej/openbsd/compile
Architecture: OpenBSD.amd64
Machine : amd64
>Description:
u
On Wed, 15 Jun 2016, Matej Nanut wrote:
> Hello, I just got the same thing trigger yesterday. It happened twice
> about a week ago, but after a rebuild from CVS it didn't happen again,
> so I thought I had just messed something up.
>
> This time, it happend immediately after pressing the fullscree
On Mon, Jun 13, 2016 at 08:42:35AM -0700, Philip Guenther wrote:
> On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> > I was building ports and at the same time started chromium and the
> > kernel panic-ed.
> >
> > This has happened a few times in the last week. It started happening at
> > some
On 05/07/16(Tue) 12:28, Dimitris Papastamos wrote:
> On Mon, Jun 13, 2016 at 08:42:35AM -0700, Philip Guenther wrote:
> > On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> > > I was building ports and at the same time started chromium and the
> > > kernel panic-ed.
> > >
> > > This has happened a
On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> Without more information it's hard to find what could be the reason
> for this crash. Being able to reproduce the crash easily is the key
> to debugging. Can you do that?
while :; do (chrome &); sleep 8; pkill chrome; done
It ta
On 05/07/16(Tue) 19:01, Dimitris Papastamos wrote:
> On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> > Without more information it's hard to find what could be the reason
> > for this crash. Being able to reproduce the crash easily is the key
> > to debugging. Can you do that?
On Tue, Jul 05, 2016 at 07:01:11PM +0100, Dimitris Papastamos wrote:
> On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> > Without more information it's hard to find what could be the reason
> > for this crash. Being able to reproduce the crash easily is the key
> > to debugging.
On Wed, 6 Jul 2016, Tobias Ulmer wrote:
> On Tue, Jul 05, 2016 at 07:01:11PM +0100, Dimitris Papastamos wrote:
> > On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> > > Without more information it's hard to find what could be the reason
> > > for this crash. Being able to reproduc
On Wed, Jul 06, 2016 at 03:17:43PM +0200, Martin Pieuchot wrote:
> Thanks! So could you try the second step? After applying the diff below
> set splassert to 4 before starting your loop (sysctl kern.splassert=4).
>
> The machine should no longer panic but dump multiple traces until a NULL
> poin
On Wed, Jul 06, 2016 at 09:56:10AM -0700, Philip Guenther wrote:
> On Wed, 6 Jul 2016, Tobias Ulmer wrote:
> > On Tue, Jul 05, 2016 at 07:01:11PM +0100, Dimitris Papastamos wrote:
> > > On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> > > > Without more information it's hard to fi
Dimitris Papastamos wrote:
> On Mon, Jun 13, 2016 at 08:42:35AM -0700, Philip Guenther wrote:
> > On Sun, 12 Jun 2016, Dimitris Papastamos wrote:
> > > I was building ports and at the same time started chromium and the
> > > kernel panic-ed.
> > >
> > > This has happened a few times in the last w
On 2016/07/05 19:01, Dimitris Papastamos wrote:
> On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote:
> > Without more information it's hard to find what could be the reason
> > for this crash. Being able to reproduce the crash easily is the key
> > to debugging. Can you do that?
>
Hello Pascal,
On 09/04/20(Thu) 16:10, Pascal Cabaud wrote:
> > Synopsis: Once a day, my APU1D4 used to crash
> > Category: kernel
> > Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT
> 2019
>
>
On 10/04/20(Fri) 12:18, Pascal Cabaud wrote:
> Hello Martin,
>
> Thanks for searching bits in this bug report. Are the APU really popular
> to run OpenBSD or is there a problem with them: AFAICS, i've found many
> reports in archives...
The problem is unlikely to be related to the hardware.
> Le
On 2024/02/23 10:44, open...@huttu.net wrote:
> >Description:
> Trying to power off the system, the kernel crashes. I was trying to
> debug why 4/8 cores are offline.
I can answer the second bit - i7-1165G7 has 4 cores not 8 - the others
are smt (hyperthreading) pseudo-cores which are disab
On Fri, Feb 23, 2024 at 11:40:15AM +, Stuart Henderson wrote:
> On 2024/02/23 10:44, open...@huttu.net wrote:
> > >Description:
> > Trying to power off the system, the kernel crashes. I was trying to
> > debug why 4/8 cores are offline.
>
> I can answer the second bit - i7-1165G7 has 4 co
On 05/09/16(Mon) 16:39, Jens Sauer wrote:
> Hello OpenBSD Community,
>
> today i played a little bit with cisco routers and IPv6.
> It seems like a plain OpenBSD 6.0 install crashes while
> i reduced the IPv6 (cisco) RA parameters to a really short ammount.
> This behaviour was for me reproducible
; Could you try a -current snapshot? A lot of cleanup happened in this
> area and I'd like to know if you can still reproduce this crash.
>
> Thanks,
> Martin
Hello Martin,
hello OpenBSD Community,
I have tested it again with OpenBSD 6.0 current #2250 and could reproducible
get t
On 06/09/16(Tue) 13:54, Jens Sauer wrote:
> Hello Martin,
> hello OpenBSD Community,
>
> I have tested it again with OpenBSD 6.0 current #2250 and could reproducible
> get the same result (Kernel Crash). Seems like the ping isn't involved
> because the kernel crash happen
Sorry again,
i revisited the pcap 'complete_scenario.pcap' and it seems like after changing
to "short RA's" the openbsd multicast address get's a NS but did not respond
via NA. Would be pleased if some 'IPv6 gurus' could check it from previous post
(attachement). Maybe the reason for paket loss
Hi OpenBSD Community,
i have tested the current snapshot again and could confirm that the previous
crash doesn't occur anymore. The Ipv6 stack works like expected. Any paket loss
'heals' after a short time when the RA runs in 'normal' conditions again.
Great job!
Regards
J.Sauer
>Synopsis: pf.conf "set timeout interval 1" causes kernel crash
>Category: kernel amd64
>Environment:
System: OpenBSD 6.6
Details : OpenBSD 6.6-beta (GENERIC.MP) #235: Tue Aug 20
00:09:44 MDT 2019
dera...@amd64.openbs
Hello,
thanks for the report. I was able to trigger it. I'll take a look at it.
regards
sashan
On Tue, Aug 20, 2019 at 11:03:02AM -0300, Kor son of Rynar wrote:
> >Synopsis: pf.conf "set timeout interval 1" causes kernel crash
> >Category: kernel amd64
>
Hello,
> >How-To-Repeat:
> # echo "set timeout interval 1" >> /etc/pf.conf
> # pfctl -f /etc/pf.conf
>
>
>
> >Fix:
> Not known.
I've used same steps to reproduce the panic. This is what I could
see in resulting crash:
The system died at line 1441 in pf_free_state():
1415 void
Hi sashan,
On Tue, Aug 20, 2019 at 9:42 PM Alexandr Nedvedicky <
alexandr.nedvedi...@oracle.com> wrote:
> Hello,
>
>
>
> > >How-To-Repeat:
> > # echo "set timeout interval 1" >> /etc/pf.conf
> > # pfctl -f /etc/pf.conf
> >
> >
> >
> > >Fix:
> > Not known.
>
> I've used same steps to r
On Wed, Aug 21, 2019 at 02:36:36AM +0200, Alexandr Nedvedicky wrote:
> I've used same steps to reproduce the panic. This is what I could
> see in resulting crash:
I have poked at this in a VMM guest booting GENERIC with the following
in rc.local(8) to trigger it as early as possible on reboot:
The crash likely involves the laptop's CardBus/PCI bus not functioning
correctly. It happens in both OpenBSD 5.8, 5.9 and 6.0 with the generic 'bsd'
kernel.
However, 'bsd.rd' seems to work. I have not looked into what options make the
ramdisk kernel work on here. Boot log of course is provide
Hello,
I was testing the most recent ARMv7 snapshot on my Cubieboard2 and got the
crash documented in the attached file. Please let me know if I can be of any
help.
Thanks,
Peter
openbsd_cb2_bugreport
Description: Binary data
signature.asc
Description: Message signed with OpenPGP using GPG
Hi bugs@,
whenever i connect my turned-off Sansa Clip Zip to my openbsd desktop
machine,
the kernel hangs and throws me into dbb. It's 100% reproducible. The
output
was generated from the latest amd64-current-snapshot (23.02., dmesg
below),
connecting the player immediately after boot.
I replac
And what is weird that the CardBus implementation is hooked up the exact same
way in the bsd.rd kernel. Maybe there is too much devices set in the kernel?
Sounds like a stupid theory but that could be the case. On NetBSD, the bus
could not be detected without enabling fixups, but even if NetBSD
On Sat, Mar 19, 2016 at 11:36:14AM +0100, Peter Oruba wrote:
> Hello,
>
> I was testing the most recent ARMv7 snapshot on my Cubieboard2 and got the
> crash documented in the attached file. Please let me know if I can be of any
> help.
>
> Thanks,
> Peter
>
Hi,
unfortunately that issue is kn
Hello,
On 24/02/14(Mon) 13:01, n.reu...@hxgn.net wrote:
> Hi bugs@,
>
> whenever i connect my turned-off Sansa Clip Zip to my openbsd desktop
> machine,
> the kernel hangs and throws me into dbb. It's 100% reproducible. The
> output
> was generated from the latest amd64-current-snapshot (23.02.
.
The kernel crash appeared when disconnecting the USB NIC.
https://ctrlv.cz/5uyw
On Thu, Sep 13, 2018 at 08:44:05AM -0400, Xavier Guerin wrote:
> >Synopsis:Kernel crash in IWM driver after resume from sleep
> >Category:kernel
> >Environment:
> System : OpenBSD 6.4
> Details : OpenBSD 6.4-beta (GENERIC.MP) #292: Mon Se
On Thu, 2018-09-13 at 19:52 +0200, Stefan Sperling wrote:
> On Thu, Sep 13, 2018 at 08:44:05AM -0400, Xavier Guerin wrote:
> > > Synopsis: Kernel crash in IWM driver after resume from sleep
> > > Category: kernel
> > > Environment:
> >
> >
On Thu, 2018-09-13 at 19:52 +0200, Stefan Sperling wrote:
> On Thu, Sep 13, 2018 at 08:44:05AM -0400, Xavier Guerin wrote:
> > > Synopsis: Kernel crash in IWM driver after resume from sleep
> > > Category: kernel
> > > Environment:
> >
> >
> On Sep 14, 2018, at 11:16 AM, Xavier Guerin wrote:
>
> On Thu, 2018-09-13 at 19:52 +0200, Stefan Sperling wrote:
>> On Thu, Sep 13, 2018 at 08:44:05AM -0400, Xavier Guerin wrote:
>>>> Synopsis: Kernel crash in IWM driver after resume from sleep
>>>
On Mon, Sep 17, 2018 at 10:23:14AM -0400, "Xavier R. Guérin" wrote:
> > On Sep 14, 2018, at 11:16 AM, Xavier Guerin wrote:
> > I'm running the patched kernel since yesterday and the issue has not
> > shown up yet even after a whole bunch of sleep/resume cycles of various
> > duration.
> >
> > I'l
Hi,
iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 8260" rev 0x3a, msi
iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:e1:45:79
this patch seems to have caused increased error rates (IERRS in systat)
OpenBSD 6.4-beta (GENERIC.MP) #312: Fri Sep 21 14:12:02 MDT 2018
fo
On Sat, Sep 22, 2018 at 04:25:03PM +0200, Gregor Best wrote:
>
> Hi,
>
> iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 8260" rev 0x3a,
> msi
> iwm0: hw rev 0x200, fw ver 16.242414.0, address e4:a4:71:e1:45:79
>
> this patch seems to have caused increased error rates (IERRS in s
where I enabled
> USB3 passthrough of a USB ethernet dongle, I think a RTL8153 gigabit USB
> NIC.
>
> The kernel crash appeared when disconnecting the USB NIC.
>
> https://ctrlv.cz/5uyw
OpenBSD 6.4 has been released in 18 october 2018, lot of commits
happened meanwhile.
Can you try o
I guess that the kernel can't read the HDD connected to the SATA port.
fsck can't find any sector when I run it using bsd.rd.
U-Boot 2016.05 (Jun 23 2016 - 01:28:15 -0600) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Olimex A20-OLinuXino-LIME2
I2C: ready
DRAM: 1 GiB
MMC: SUNXI S
> Date: Wed, 17 Aug 2016 01:19:46 +0200
> From: Juan Francisco Cantero Hurtado
>
> I guess that the kernel can't read the HDD connected to the SATA port.
> fsck can't find any sector when I run it using bsd.rd.
Not sure what's going on here. But I made a critical fix on the 15th.
The timestamp
On Wed, Aug 17, 2016 at 11:33:19AM +0200, Mark Kettenis wrote:
> > Date: Wed, 17 Aug 2016 01:19:46 +0200
> > From: Juan Francisco Cantero Hurtado
> >
> > I guess that the kernel can't read the HDD connected to the SATA port.
> > fsck can't find any sector when I run it using bsd.rd.
>
> Not sure
On Wed, Aug 17, 2016 at 10:23:24PM +0200, Juan Francisco Cantero Hurtado wrote:
> On Wed, Aug 17, 2016 at 11:33:19AM +0200, Mark Kettenis wrote:
> > > Date: Wed, 17 Aug 2016 01:19:46 +0200
> > > From: Juan Francisco Cantero Hurtado
> > >
> > > I guess that the kernel can't read the HDD connected
>Synopsis: kernel crash on 29-July snapshot: WARNING: SPL NOT LOWERED ON
>SYSCALL 28 19 EXIT 48549400 7
>Category: kernel
>Environment:
System : OpenBSD 6.1
Details : OpenBSD 6.1-current (GENERIC.MP) #20: Sat Jul 29 14:21:
Hi,
I've just upgraded via bsd.rd to the 31st of July snapshot and the
crash is still 100% reproductible, please see below.
Syscall 28 is sendmsg so I'm pretty sure that the crash happens the
very first time unbound tries to send a DNS request via the PPPoE
interface. I'm using very similar PF &
On 01/08/17(Tue) 10:41, Andrei-Marius Radu wrote:
> Hi,
>
> I've just upgraded via bsd.rd to the 31st of July snapshot and the
> crash is still 100% reproductible, please see below.
Thanks for the report, diff below should fix it. Do you confirm?
Index: net/if_spppsubr.c
===
On 2017/08/01 11:44, Martin Pieuchot wrote:
> On 01/08/17(Tue) 10:41, Andrei-Marius Radu wrote:
> > Hi,
> >
> > I've just upgraded via bsd.rd to the 31st of July snapshot and the
> > crash is still 100% reproductible, please see below.
>
> Thanks for the report, diff below should fix it. Do you
On Tue, Aug 1, 2017, at 11:44, Martin Pieuchot wrote:
> On 01/08/17(Tue) 10:41, Andrei-Marius Radu wrote:
> > Hi,
> >
> > I've just upgraded via bsd.rd to the 31st of July snapshot and the
> > crash is still 100% reproductible, please see below.
>
> Thanks for the report, diff below should fix it
90 matches
Mail list logo
