ACPI kernel panic in first boot after new OpenBSD install

Hello all, I have just installed the OpenBSD on a ASUS tuf f15 gaming laptop, installation went very smooth. But I soon as I reboot the computer, it put me in ddb shell and there was a kernel panic related to acpi. I searched on internet, and tried to update my bios to the latest version

Re: reboot after kernel panic on 7.2

On 2023-03-05, mabi wrote: > Hello > > Is it possible to have OpenBSD 7.2 automatically reboot after a kernel panic > happens? > > I tried setting: > > ddb.panic=0 > > but it does not reboot automatically. > > As I am affected by the pfsync issue which leads

reboot after kernel panic on 7.2

Hello Is it possible to have OpenBSD 7.2 automatically reboot after a kernel panic happens? I tried setting: ddb.panic=0 but it does not reboot automatically. As I am affected by the pfsync issue which leads to a kernel panic on OpenBSD 7.2 so I would like the firewall to reboot as soon

Re: How do I report a kernel panic occuring on install media?

Thanks for the tip! So I’ll try another configuration with another install. But so far I haven’t found any documentation about how to power off the system - disabling acpi prevents system from shutting down. Cheers Le jeu. 14 avr. 2022 à 12:29, Stuart Henderson a écrit : > On 2022/04/14

Re: How do I report a kernel panic occuring on install media?

On 2022/04/14 12:21, rtw0 dtw0 wrote: > Hi, > > To disable acpi permanently: > # config -ef /bsd > ukc > disable acpi > ukc > quit This is a REALLY BAD IDEA. >From my earlier mail: https://marc.info/?l=openbsd-misc=164983204029245=2 | (Note: acpi drivers are used for various machine

Re: How do I report a kernel panic occuring on install media?

Hi, To disable acpi permanently: # config -ef /bsd ukc > disable acpi ukc > quit One thing I haven’t been able to do yet is get shutdown(8) to work with acpi disabled, as it ends up rebooting automatically and -p or -h options do not respond as they normally do. acpi(4) explains that acpi is

Re: How do I report a kernel panic occuring on install media?

On 4/13/22 3:01 AM, misc.99...@aleeas.com wrote: As far as I remember the CPU is only 32-bit capable. But outputs I gathered from Linux is telling me otherwise (given below). i don't know enough about this cpu, so i'm going to bow out now. i just thought it was a simple accident. sorry if i

Re: How do I report a kernel panic occuring on install media?

boot amd64 install70.img (sha256: > 6bc7f945c2709247d449892c33c0f1b9a31590528572c1e988fef4a7637210e6) on the > machine and this time it didn't even get to kernel panic stage. > > Using drive 0, partition 3. > Loading. > probing: pc0 mem[634K 2035M a20=on] > disk hd0

Re: How do I report a kernel panic occuring on install media?

y I'm facing a kernel panic. It shows on screen: > > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Atom(TM) CPU N2600 @ 1.60 GHz ("GenuineIntel" 686-class) 1.60 > GHz, 06-36-01 > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF

Re: How do I report a kernel panic occuring on install media?

On 4/12/22 9:39 PM, misc.99...@aleeas.com wrote: I'm trying to boot OpenBSD 7.0 i386 image (sha256: 2423307414df1800537063b3cafd9ae788b46711074b7f94d855c8a3de622f51) from a USB flash drive on HP Mini, Intel Atom N2600 1.60 GHz machine It sounds like you're trying to use the 32bit OpenBSD

Re: snapshot kernel panic related to radeondrm missing firmware

On Wed, Jan 13, 2021 at 04:10:46AM +0200, Mihai Popescu wrote: > I took the chance and installed from a recent snapshot - 12.01.2021. I got > a kernel panic at first boot after install, related to missing firmware for > radeondrm. > I disabled the radeondrm then the boot process wa

snapshot kernel panic related to radeondrm missing firmware

I took the chance and installed from a recent snapshot - 12.01.2021. I got a kernel panic at first boot after install, related to missing firmware for radeondrm. I disabled the radeondrm then the boot process was fine and I installed radeondrm firmware by hand. At the next boot everything was fine

Re: Kernel panic probably linked to inteldrm

Ok, after further investigations, my problem does not seems to be linked with inteldrm. The kernel panic seems to happen randomly with or without inteldrm enabled. Nevertheless, if I disable inteldrm, I can access ddb when the panic happen (I don't know why, BTW) and I get this. kernel

Kernel panic probably linked to inteldrm

Hi misc@, I have installed OpenBSD 6.7 on a new laptop and I experiment regular kernel panic. Unfortunately, I lack of information because ddb doesn't start when it happens. After some researches and tests, I've disabled inteldrm at kernel level and since I don't experience any kernel panic

video: kernel panic

Hello, any of the list members came across a kernel panic caused by running /usr/X11R6/bin/video ? $ video fatal protection fault in supervisor mode http://155.138.134.219/videokernelcrash.jpg OpenBSD 6.7-current (GENERIC.MP) #204: Thu May 21 11:44:48 MDT 2020 dera...@amd64.openbsd.org

Kernel panic during install 6.6

of rust and starting to learn something new, I'm pulling a PowerEdge SC1435 out of the closet, then promptly getting a kernel panic from both install66.fs and install66.iso.  Memory seems to check out, suspected cause is the Areca ARC-1200 RAID controller since that's where the boot process fails

Re: ppppoe octeon kernel panic .6.6

hi with the current version OpenBSD 6.6-current (GENERIC.MP) #48: Tue Dec 10 16:30:01 MST 2019 dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC.MP the pppoe interface works as expected. no kernel panic anymore thanks holger Am 22.10.19 um 21:12 schrieb Holger Glaess

Re: ppppoe octeon kernel panic .6.6

On Wed, Oct 23, 2019 at 08:21:50AM +0200, Holger Glaess wrote: > hi > > > here the traceback , i hope ;) Hi Holger & Tech, I have made my octeon router work again and I have a patch. But I'm not an openbsd developer, nor is this patch official in any way. It was a lot of debugging and

Re: ppppoe octeon kernel panic .6.6

uhub1 port 1 configuration 1 interface 0 "American Power Conversion Back-UPS CS 650 FW:817.v9.I USB FW:v9" rev 1.10/0.06 addr 2 uhidev0: iclass 3/0, 98 report ids upd0 at uhidev0 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: removable sd0: 3776MB, 512 bytes/sector

Re: ppppoe octeon kernel panic .6.6

0: 3776MB, 512 bytes/sector, 7733248 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on sd0a (b3a80208ecd8c82c.a) swap on sd0b dump on sd0b WARNING: / was not properly unmounted WARNING: No TOD clock, believing file system. WARNING: CHEC

ppppoe octeon kernel panic .6.6

0 scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: removable sd0: 3776MB, 512 bytes/sector, 7733248 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on sd0a (b3a80208ecd8c82c.a) swap on sd0b dump on sd0b WARNING: /

ppppoe octeon kernel panic .6.6

hi if i boot my edgerouter with connected dsl modem i get an kernel panic. reordering libraries: Trap cause = 2 Frame 0x98004efcb860 Trap PC 0x813cc38c RA 0x8109feac fault 0x0 0x813cc2d8 (1,98000f991b76,1,2)  ra 0x8109feac sp 0x98004efcb9b8, sz 0

Re: Strange kernel panic-like problem

On Thu, Feb 07, 2019 at 11:18:40PM -0600, Kyle wrote: > I recently upgraded a box running 6.2 to 6.4 via clean install. After a few > days of running normally it started locking up, usually within a minute or so > after booting up to the login prompt. ddb appears on the console. > > I

Strange kernel panic-like problem

I recently upgraded a box running 6.2 to 6.4 via clean install. After a few days of running normally it started locking up, usually within a minute or so after booting up to the login prompt. ddb appears on the console. I eventually thought to try booting bsd.sp, which has been running for

Re: Problem upgrading to today's snapshot on VirtualBox 6 installation (kernel panic)

ither, or whether the backed out commit made it into the snapshot > > (probably not). > > The new snapshot, "14/01/2019, 10:38:00", also does not work. Same > "ACPI: Reset initiated by ACPI" in the VirtualBox log. This time I > managed to capture a kernel panic

Re: Problem upgrading to today's snapshot on VirtualBox 6 installation (kernel panic)

> either, or whether the backed out commit made it into the snapshot > (probably not). The new snapshot, "14/01/2019, 10:38:00", also does not work. Same "ACPI: Reset initiated by ACPI" in the VirtualBox log. This time I managed to capture a kernel panic by hooking up a se

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

On Mon, Oct 22, 2018 at 08:59:46PM +0300, snikolov wrote: > On Mon, 2018-10-22 at 10:27 -0700, Mike Larkin wrote: > > On Mon, Oct 22, 2018 at 10:13:14AM -0700, Mike Larkin wrote: > > > On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > > > > This appears to be related to the LFENCE

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

On Mon, 2018-10-22 at 10:27 -0700, Mike Larkin wrote: > On Mon, Oct 22, 2018 at 10:13:14AM -0700, Mike Larkin wrote: > > On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > > > This appears to be related to the LFENCE serializing MSR change > > > > that > > > > went in > > > > during the

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

On Mon, Oct 22, 2018 at 10:13:14AM -0700, Mike Larkin wrote: > On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > > This appears to be related to the LFENCE serializing MSR change that > > > went in > > > during the last round of side channel analysis fixes: > > > > > >

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

On Mon, Oct 22, 2018 at 08:01:13PM +0300, snikolov wrote: > > This appears to be related to the LFENCE serializing MSR change that > > went in > > during the last round of side channel analysis fixes: > > > > 811c3037:   b9 29 10 01 > > c0  mov$0xc0011029,%ecx > >

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

de > > trap type 4 code 0 rip 811c303c cs 8 rflags 10202 cr2  0 cpl e > > rsp 81a06a20 > > gsbase 0x81872ff0  kgsbase 0x0 > > panic: trap type 4, code=0, pc=811c303c > > > > The operating system has halted. > > Please press any key to reboot. > >

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

> This appears to be related to the LFENCE serializing MSR change that > went in > during the last round of side channel analysis fixes: > > 811c3037:   b9 29 10 01 > c0  mov$0xc0011029,%ecx > 811c303c:   0f 32   rdmsr > > According to the

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

~~ > > Should I report this as a bug ? > > Best Regards, > Strahil Nikolov > > > On Sun, 2018-10-21 at 18:07 +0300, snikolov wrote: > > Hello All, > > > > During install of install64.iso I experience a kernel panic during > > boot of the

Re: amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

~ Should I report this as a bug ? Best Regards, Strahil Nikolov On Sun, 2018-10-21 at 18:07 +0300, snikolov wrote: > Hello All, > > During install of install64.iso I experience a kernel panic during > boot of the CD (pc=811c3

amd64.iso KVM guest kernel panic pc=ffffffff811c303c (Opteron_G3 to Opteron_G5)

Hello All, During install of install64.iso I experience a kernel panic during boot of the CD (pc=811c303c). install64.iso sha256sum is 81833b79e23dc0f961ac5fb34484bca66386deb3181ddb8236870fa4f488cdd2 which matches https://cdn.openbsd.org/pub/OpenBSD/6.4/amd64/SHA256 I have tested

Re: kernel panic while reproducing video with mpv

Hi Visa, On Sun, Jun 24, 2018 at 05:54:15PM +, Visa Hankala wrote: > On Sun, Jun 24, 2018 at 12:37:45PM +0200, Walter Alejandro Iglesias wrote: > > panic: mtx 0x81c86470: locking against myself > > Stopped at db_enter+0x12: popq%r11 > > TIDPIDUID PRFLAGS

Re: kernel panic while reproducing video with mpv

On Sun, Jun 24, 2018 at 12:37:45PM +0200, Walter Alejandro Iglesias wrote: > panic: mtx 0x81c86470: locking against myself > Stopped at db_enter+0x12: popq%r11 > TIDPIDUID PRFLAGS PFLAGS CPU COMMAND > 104021 96401 1000 0x3 0x4002 mpv >

kernel panic while reproducing video with mpv

Hello, I had a kernel panic while reproducing a video with mpv. It's my first kernel panic with OpenBSD, so I didn't know how to use ddb(4). Since I'm running my http and smtp server in this machine I cannot entertain myself too much reproducing the panic to get more info. That's why I don't

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

> Hi, > > could you please try this diff from kettenis@ > https://marc.info/?l=openbsd-tech=152650279308779=2 > Hi Hrvoje, misc@, I'm sorry, but I don't access to the hardware (Dell PowerEdge R440) anymore. I've returned it to the supplier already as this was leased only for testing. Sorry,

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

On 2.5.2018. 11:28, Jan Vlach wrote: > R440 WAS( Re: Dell PowerEdge R430/R440 support) > Reply-To: > In-Reply-To: <20180425150215.gh20...@diehard.n-r-g.com> > > Hello misc@ > > > the Dell PowerEdge R440 server arrived for testing and it panics on boot > to installed system. Installer works

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

On Thu, May 03, 2018 at 02:02:48PM +0200, Jan Vlach wrote: > > kettenis@ may know more, I think he knows about this issue already. It's > > just > > a missing piece of the standard we didn't implement yet. An AML dump may > > be useful, yes. > > > > -ml > > > > Hello Mike, > > just have

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

> kettenis@ may know more, I think he knows about this issue already. It's just > a missing piece of the standard we didn't implement yet. An AML dump may > be useful, yes. > > -ml > Hello Mike, just have installed FreeBSD11.1 on the PowerEdge R440 to get acpidump & debug info. I've followed

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

> Last time I checked, we don't support LoadTable. > > -ml > Thank you Mike for your reply. I have no clue about ACPI. Is this a new way how vendors extend ACPI? Is there generally a way to switch it to some "legacy" mode or is this endgame? Is there some info I could get from the system

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

On 2.5.2018. 19:06, Mike Larkin wrote: > On Wed, May 02, 2018 at 06:51:51PM +0200, Jan Vlach wrote: >>> Last time I checked, we don't support LoadTable. >>> >>> -ml >>> >> >> Thank you Mike for your reply. I have no clue about ACPI. Is this a new >> way how vendors extend ACPI? Is there generally

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

On Wed, May 02, 2018 at 06:51:51PM +0200, Jan Vlach wrote: > > Last time I checked, we don't support LoadTable. > > > > -ml > > > > Thank you Mike for your reply. I have no clue about ACPI. Is this a new > way how vendors extend ACPI? Is there generally a way to switch it to > some "legacy"

Re: 6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

On Wed, May 02, 2018 at 11:28:47AM +0200, Jan Vlach wrote: > R440 WAS( Re: Dell PowerEdge R430/R440 support) > Reply-To: > In-Reply-To: <20180425150215.gh20...@diehard.n-r-g.com> > > Hello misc@ > > > the Dell PowerEdge R440 server arrived for testing and it panics on boot > to installed

6.3-current kernel panic: aml_die aml_parse:4194 on PowerEdge

R440 WAS( Re: Dell PowerEdge R430/R440 support) Reply-To: In-Reply-To: <20180425150215.gh20...@diehard.n-r-g.com> Hello misc@ the Dell PowerEdge R440 server arrived for testing and it panics on boot to installed system. Installer works fine, it's the reboot into installed system that fails.

aesni/crypto related kernel panic on 6.3

to reproduce the problem to find out what it is related to and managed to even make both firewalls kernel panic at the same time. When this happens the hardware is frozen and won't take any input and won't even reboot automatically. I need to power it off and on again. As I was logged into the serial

Re: OpenBSD 6.3 kernel panic

On Sun, Apr 15, 2018 at 1:02 AM, Mike Larkin wrote: > On Sat, Apr 14, 2018 at 11:32:00PM -0500, Juan Morado wrote: > > Here's the text as best I can see it. > > > > uvm_fault (0xc1afca80, 0x808ca000, 0, 1) -> e > > kernel: page fault trap, code=0 > > Stopped

Re: OpenBSD 6.3 kernel panic

Technically, you can debug your real machine kernel using serial (aka com) port, but I do not think you need to do that. When your kernel panics, it takes your to ddb, right? You got "uvm_fault page fault trap": it means kernel tries to access some invalid memory address. It happens in

Re: OpenBSD 6.3 kernel panic

Rupert, that's a great article, thanks for sharing. I don't see how that helps when my OpenBSD host machine would crash (not the QEMU guest) when I so much as touch the track pad. On Sun, Apr 15, 2018 at 2:05 AM, Rupert Gallagher wrote: >

Re: OpenBSD 6.3 kernel panic

http://bijanebrahimi.github.io/blog/remote-debugging-the-running-openbsd-kernel.html On Sun, Apr 15, 2018 at 08:02, Mike Larkin wrote: > PS, this bug report leaves a lot to be desired... -ml

Re: OpenBSD 6.3 kernel panic

gt; Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, > > minfree > > > > > files from the crash dump. If there is any interest in looking at > > these, > > > > > please advise the best way to share them. > > > > > > > > > > -

Re: OpenBSD 6.3 kernel panic

bounds, > minfree > > > > files from the crash dump. If there is any interest in looking at > these, > > > > please advise the best way to share them. > > > > > > > > - JM > > > > > > > > --- > > > > > > Where's

Re: OpenBSD 6.3 kernel panic

sd.0, bounds, minfree > > > files from the crash dump. If there is any interest in looking at these, > > > please advise the best way to share them. > > > > > > - JM > > > > > > --- > > > > Where's the panic string? > > > > H

Re: OpenBSD 6.3 kernel panic

> > Maybe kernel panic isn't the correct terminology? ddb is invoked anytime I > touch the track pad while booting. You are right: it is kernel panic. Accroding to ddb(4): "ddb is invoked upon a kernel panic when the sysctl(8) ddb.panic is set to 1." I am not sure, bu

Re: OpenBSD 6.3 kernel panic

t if the track pad is touched > so I > > was able to get a dump from ddb. > > > > Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, minfree > > files from the crash dump. If there is any interest in looking at these, > > please advise the best way to share

Re: OpenBSD 6.3 kernel panic

On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote: > Hi all, > > I searched the mail archives briefly but couldn't find a related issue. > Apologies if this is a duplicate. > > Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing > whenever I touch the track pad. >

OpenBSD 6.3 kernel panic

Hi all, I searched the mail archives briefly but couldn't find a related issue. Apologies if this is a duplicate. Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing whenever I touch the track pad. Touching the track pad after X starts generally causes the machine to just

Re: kernel panic with cmp

Hardware was bad, now it's ok. W dniu 17.02.2018 o 08:23, Krzysztof Strzeszewski pisze: > Hi, > > I have kernel panic in OpenBSD 6.1 end 6.2 on the same machine. Command > "cmp" is in my script , it starts every minute. When I don't use "cmp" > command with

kernel panic with cmp

Hi, I have kernel panic in OpenBSD 6.1 end 6.2 on the same machine. Command "cmp" is in my script , it starts every minute. When I don't use "cmp" command with my script, is ok. This kernel panic is after the last path of February 2, 2018. Kernel is default f

Re: Kernel panic with openbsd 6.2

le > > On Fri, Jan 19, 2018 at 21:50, Mik J <mikyde...@yahoo.fr> wrote: > >> Hello, I had many kernel panic these past days. This is a 6.2 openbsd VM >> running on esxi 5.5

Re: Kernel panic with openbsd 6.2

esxi 5.5.0 dates back to 2013. obsd runs better on qemu nowadays. To avoid the mess with x86/amd64, perhaps qemu-sparc with obsd-sparc will serve you better. Sent from ProtonMail Mobile On Fri, Jan 19, 2018 at 21:50, Mik J <mikyde...@yahoo.fr> wrote: > Hello, I had many kernel panic t

Re: Kernel panic with openbsd 6.2

On Thu, January 25, 2018 4:29 am, Maxim Bourmistrov wrote: > As Stuart mentioned, em(4) on top of e1000 proven to be more stable. > Even under higher load. > Vmx starting to misbehave under high load, resulting for ex. with unstable > CARP setup. > > //mxb > >> 25 jan. 2018 kl. 02:40 skrev trondd

Re: Kernel panic with openbsd 6.2

8 Ã
11:48:00 UTC+1, Stuart Henderson >>> <s...@spacehopper.org> a écrit : >>> On 2018-01-19, Mik J <mikyde...@yahoo.fr> wrote: >>>> I had many kernel panic these past days. This is a 6.2 openbsd VM >>> running o= >>>> n esxi 5.5 >&g

Re: Kernel panic with openbsd 6.2

Stuart Henderson >> <s...@spacehopper.org> a écrit : >> On 2018-01-19, Mik J <mikyde...@yahoo.fr> wrote: >> > I had many kernel panic these past days. This is a 6.2 openbsd VM >> running o= >> > n esxi 5.5 >> > >> > # grep "&quo

Re: Kernel panic with openbsd 6.2

m: "Mik J" <mikyde...@yahoo.fr> >> To: Misc <misc@openbsd.org> >> Subject: Kernel panic with openbsd 6.2 >> >> Hello, >> >> I had many kernel panic these past days. This is a 6.2 openbsd VM running on >> esxi 5.5 >> >> I took s

Re: Kernel panic with openbsd 6.2

Could it be related to: https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/ ? > Sent: Friday, January 19, 2018 at 9:50 PM > From: "Mik J" <mikyde...@yahoo.fr> > To: Misc <misc@openbsd.org> > Subj

Re: Kernel panic with openbsd 6.2

22 janvier 2018 à 10:35:47 UTC+1, Stuart Henderson <s...@spacehopper.org> a écrit : On 2018/01/22 00:22, Mik J wrote: > Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson > <s...@spacehopper.org> a écrit : > On 2018-01-19, Mik J <mikyde...@yahoo.fr> w

Re: Kernel panic with openbsd 6.2

On 2018/01/22 00:22, Mik J wrote: > Le dimanche 21 janvier 2018 à 11:48:00 UTC+1, Stuart Henderson > <s...@spacehopper.org> a écrit : > On 2018-01-19, Mik J <mikyde...@yahoo.fr> wrote: > > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= &g

Re: Kernel panic with openbsd 6.2

à 11:48:00 UTC+1, Stuart Henderson <s...@spacehopper.org> a écrit : On 2018-01-19, Mik J <mikyde...@yahoo.fr> wrote: > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > n esxi 5.5 > > # grep "" /tmp/if_vmx.dis I've reported a lo

Re: Kernel panic with openbsd 6.2

On 2018-01-19, Mik J <mikyde...@yahoo.fr> wrote: > I had many kernel panic these past days. This is a 6.2 openbsd VM running o= > n esxi 5.5 > > # grep "" /tmp/if_vmx.dis I've reported a lot of vmxnet3_getbuf panics, nobody seems interested. I suggest switch

Re: Apollo Lake kernel panic

I cannot check it right now, but I am pretty sure I have disabled the C states and as well CSM. Also I have upgrade the firmware to the latest. At the beginning I also had some troubles. The system was crashing at different times. Now it is stable. I am running 6.2 -current not Release. Às

Re: Apollo Lake kernel panic

I copied the bsd.mp kernel from a working machine. Here is the dmesg. I also disabled C states in BIOS and was able cleanly to halt machine OpenBSD 6.2 (GENERIC) #132: Tue Oct 3 21:18:21 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 16799846400

Re: Apollo Lake kernel panic

I was able to boot machine which crashed with bsd.sp kernel. Please see message below. That kernel is non-patched kernel as I was running normally bsd.mp kernel. Also I forgot to say in my previous message that I didn't mess with C states (BIOS option). I was also using legacy (not pure UEFI boot)

Re: Apollo Lake kernel panic

first one died but NewEgg sent me the second one. I don't know where to begin. With the default ACPI configuration options 1. Suspend to RAM enabled 2. ACPI HPET Table enabled one can't clearly shut down 6.2 stable. This is what I got www.devio.us/~ppunosevac/kernel-panic-1.jpg The system wa

Re: kernel panic i386

On Sat, Oct 14, 2017 at 6:57 AM, Krzysztof Strzeszewski wrote: > This is very interested "the kernel did non panic". panic() is an explicit call in the kernel, made when some sanity or consistency check fails. Dereferencing a bogus pointer results in a failed page fault trap

Re: kernel panic i386

0.2017 o 11:58, Philip Guenther pisze: On Fri, Oct 13, 2017 at 12:21 PM, Krzysztof Strzeszewski <krz...@krzy.ch <mailto:krz...@krzy.ch>> wrote: When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. It's unfortunate that no one has submitted to dm...@openbsd.org <mai

Re: kernel panic i386

On Fri, Oct 13, 2017 at 12:21 PM, Krzysztof Strzeszewski <krz...@krzy.ch> wrote: > When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. > It's unfortunate that no one has submitted to dm...@openbsd.org the dmesg from that hardware since February 2016. Please consider do

Re: kernel panic i386

I changed only name kernel :) W dniu 14.10.2017 o 01:13, Mike Larkin pisze: On Fri, Oct 13, 2017 at 09:21:37PM +0200, Krzysztof Strzeszewski wrote: Hi, When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. Try 6.1 stock kernel and see if that works. Then at least we know if we

Re: kernel panic i386

On Fri, Oct 13, 2017 at 09:21:37PM +0200, Krzysztof Strzeszewski wrote: > Hi, > When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. > Try 6.1 stock kernel and see if that works. Then at least we know if we introduced a regression. Nobody knows (or cares) what NROOT

kernel panic i386

Hi, When I upgrade 6.1 to 6.2 in my futro s400 i have kernel panic. http://wklej.org/hash/e590382de31/ boot> booting hd0a:/bsd: 8154312+2282500+166852+0+1097728 [680614+82+489520+501323]=0xcc233c entry point at 0x2000d4 [ using 1671

Re: simple-mtpfs kernel panic

Hi, I tested this patch. From what I've seen, it works perfectly. After suspend / resume, I did not notice any problem. Thanks for the resolution of this bug. On Tue, Oct 3, 2017 at 11:27 AM, Martin Pieuchot wrote: > On 01/10/17(Sun) 20:35, Olivier Antoine wrote: >> Hi, >>

Re: simple-mtpfs kernel panic

On 01/10/17(Sun) 20:35, Olivier Antoine wrote: > Hi, > > Looks like this bug: > > I can also reproduce this with: > > $ while true ; do adb shell ls / ; adb kill-server ; done > > The code which is triggered in /sys/dev/usb/ehci.c: > >

Re: simple-mtpfs kernel panic

Hi, Looks like this bug: I can also reproduce this with: $ while true ; do adb shell ls / ; adb kill-server ; done The code which is triggered in /sys/dev/usb/ehci.c: ehci_device_clear_toggle(struct usbd_pipe *pipe) { struct

simple-mtpfs kernel panic

Hi misc@, during transferring some files from my laptop to my Android mobile mounted using simple-mtpfs, the machine rebooted and /var/crash now contains the following files: $ ls -h /var/crash/ bounds bsd.0 bsd.0.core minfree I read crash(8) but cannot get any meaningful

Re: 6.1-stable: kernel panic on pf_state_key_unref()

Le 07/09/2017 à 05:59, Maxim Bourmistrov a écrit : Hey, Got kernel panic on 6.1-stable during ’rcctl restart relayd’. Sorry for PNG below. Hi, It has been fixed with this diff : http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf.c.diff?r1=1.1034=1.1035

Re: Kernel panic on Dell R210 with OpenBSD 6.0 (relayd related ?)

On Tue, May 02, 2017 at 05:03:20PM +, Stuart Henderson wrote: > Probably the best thing to do at this point is to write a mail to bugs@: > > 1. describe what the machine is doing in detail. carp? ipsec? pfsync? > what sort of relays? include config (sanitized if necessary, but do that >

kernel panic: ehci_device_clear_toggle

/ddb.html, as the keyboard stops working after the kernel panic (probably because it's a usb keyboard). So, here's the output I can give you: # panic: ehci_device_clear_toggle: queue active Stopped at Debugger+0x7: leave TID PID UID PRFLAGS PFLAGS CPU COMMAND *359035 78367

Re: Kernel panic on Dell R210 with OpenBSD 6.0 (relayd related ?)

>> anchor "relayd/*" >> pass >> > > I upgraded the system to 6.1 release last week, the kernel panic is still here > (with the same logs). Probably the best thing to do at this poi

Re: Kernel panic on Dell R210 with OpenBSD 6.0 (relayd related ?)

On Tue, May 02, 2017 at 03:44:43PM +0200, Andre Ruppert wrote: > Hi, > > Im running 6.0 amd64 on a pair of R210 with relayd, but these are R210 (II). > > No kernel panics at all, and these systems are working in a live > environment... > > Regards > Andre Hi, Yes, i have also several OpenBSD

Re: Kernel panic on Dell R210 with OpenBSD 6.0 (relayd related ?)

: It also kernel panics with just this pf rules : # cat pf_minimal.conf set limit { states 10 } set skip on lo anchor "relayd/*" pass I upgraded the system to 6.1 release last week, the kernel panic is still here (with the same logs). smime.p7s Description: S/MIME Cryptographic Signature

Re: Kernel panic on Dell R210 with OpenBSD 6.0 (relayd related ?)

> pass > I upgraded the system to 6.1 release last week, the kernel panic is still here (with the same logs). -- Mathieu

Re: kernel panic question

On 04/04/17 20:40, Stuart Henderson wrote: >>> I have a case of OpenBSD-5.9 (i386) kernel panic. > Upgrade. I suspect that this kernel panic could be caused by hardware problems so upgrade will not be a cure. I sent the problem report to b...@openbsd.org (http://marc.info/?l=

Re: kernel panic question

for poor formatting. On 4 April 2017 19:16:13 Alexei Malinin <alexei.mali...@mail.ru> wrote: On 04/04/17 20:40, Stuart Henderson wrote: I have a case of OpenBSD-5.9 (i386) kernel panic. Upgrade. I suspect that this kernel panic could be caused by hardware problems so u

Re: kernel panic question

>> I have a case of OpenBSD-5.9 (i386) kernel panic. Upgrade.

Re: Kernel panic during boot on Dell Inspiron 15-5558

On 2017-04-02, Niko Pavlinek wrote: > On 2. 04. 2017 14:08, Stuart Henderson wrote: >> >> Please try a -current snapshot and report back. If you get it now (before >> the kernel version moves to 6.1-current) you'll be able to safely update >> to the proper 6.1 release

Re: kernel panic question

Is it a soekris? If so http://wiki.soekris.info/Installing_OpenBSD. If not https://www.openbsd.org/report.html Sent from my iPhone > On Apr 3, 2017, at 8:34 AM, Alexei Malinin <alexei.mali...@mail.ru> wrote: > > Hello. > > I have a case of OpenBSD-5.9 (i386) k

kernel panic question

Hello. I have a case of OpenBSD-5.9 (i386) kernel panic. I'd like to be pointed out to possible causes of the problem. Please tell me what info should I include to send useful kernel panic report. Now I have this: uvm_fault(0xd0ba6660, 0xdaf25000, 0, 1) -> e kernel: page fault trap, cod

Re: Kernel panic during boot on Dell Inspiron 15-5558

On 2. 04. 2017 14:08, Stuart Henderson wrote: > > Please try a -current snapshot and report back. If you get it now (before > the kernel version moves to 6.1-current) you'll be able to safely update > to the proper 6.1 release when it's out. > > ACPI is really required for modern PC hardware, it

  1   2   3   4   5   6   >