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 installer for a 64bit cpu. In that case, you would want the AMD64 installer.
Re: How do I report a kernel panic occuring on install media?
On 2022-04-13, 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. Before I could
> install, unfortunately 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,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,NXE,LAHF,PERF,ITSC,SENSOR,ARAT,MELTDOWN
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64 max=64. C-substates=0.2.2.0.2.0.3, IBE
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins, remapped
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt0 at acpi0: bus 3 (PCI1)
> acpiprt0 at acpi0: bus 1 (RP01)
> acpiprt0 at acpi0: bus 2 (RP02)
> acpiec0 at acpi0
> Could not convert 1 to 0
>
> panic: aml_die aml_convert:2095
>
> The operating system has halted.
> Please press any key to reboot.
>
> Almost any key or key combination I press gets the machine to reboot.
This is expected from the install kernel, it doesn't have DDB.
> It runs Windows 7 and Debian just fine. In fact I rebooted on to the media
> from a Debian install which is running without any hardware complaints. But
> OpenBSD seems to have this issue.
OpenBSD has its own written-from-scratch ACPI implementation and can
sometimes run into problems interpreting machine ACPI tables that are
already handled by other implementations.
What's needed is a dump of the ACPI tables, which you could get from
another OS, but it would be helpful to try and get it booted into
OpenBSD as this could give more information.
Try boot -c at the boot loader prompt and disabling individual acpi
device drivers and see if you can get it booted like that. The i386
install kernel has these:
$ grep ^acpi RAMDISK_CD
acpi0 at bios?
acpihpet* at acpi?
acpicmos* at acpi?
acpiec* at acpi?
acpimadt0 at acpi?
acpiprt*at acpi?
So after "boot -c", I would first try "disable acpiec" and "quit" and
see if that boots. If not then try disabling others (acpiprt is probably
ok as you would likely have seen the error earlier).
If none work you can try "disable acpi" but information about *which*
driver hit the problem is likely to be helpful.
If you can get it installed then try to get it booted - you'll need
to disable the driver again to boot the standard kernel, and as this
has additional acpi drivers, potentially you may need to disable some
others - here's the list in case you do run into it:
$ grep ^acpi GENERIC
acpi0 at bios?
acpitimer* at acpi?
acpihpet* at acpi?
acpiac* at acpi?
acpibat*at acpi?
acpibtn*at acpi?
acpicpu*at acpi?
acpicmos* at acpi?
acpidock* at acpi?
acpiec* at acpi?
acpimadt0 at acpi?
acpimcfg* at acpi?
acpiprt*at acpi?
acpisbs*at acpi?
acpitz* at acpi?
acpiasus* at acpi?
acpisony* at acpi?
acpithinkpad* at acpi?
acpitoshiba*at acpi?
acpivideo* at acpi?
acpivout* at acpivideo?
acpipwrres* at acpi?
If you can get it booted then run sendbug to generate a report (usually
easiest as "sendbug -P > somefile" and move it to a machine which
already has email configured; scp or copy via USB storage etc).
Send that in to b...@openbsd.org along with details of which driver/s
you disabled, and the kernel output you included in your mail above.
(Note: acpi drivers are used for various machine functions including
in some cases temperature control, so it's not advisable to run with
them disabled long term, but should be fine for a short test - the
N2600 is low power too which helps).
--
Please keep replies on the mailing list.
Re: How do I report a kernel panic occuring on install media?
On 2022-04-13, misc.99...@aleeas.com wrote: > > It sounds like you're trying to use the 32bit OpenBSD installer for a >> 64bit cpu. In that case, you would want the AMD64 installer. Even if that is the case, it's not very likely to change the ACPI parsing. > As far as I remember the CPU is only 32-bit capable. But outputs I gathered > from Linux is telling me otherwise (given below). CPU spec sheet says it could support it, but maybe it's disabled by BIOS. IIRc 64-bit mode on some of the Atoms does not work brilliantly anyway. > To give it a shot, I just tried to 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+ hd1+* >>> OpenBSD/amd64 BOOT 3.53 > boot> > cannot open hd0a:/etc/random.seed: No such file or directory > booting hd0a /7.0/amd64/bsd.rd: 3830471+1598464+3907256+0+704512 > [109+288+28]=0x995530 > entry point at 0x81001000 > > Then it stops. Pressing Ctrl+Alt+Del or any key doesn't do anything. Only way > is to press the power button to force shutdown. The two main causes of this: - booting on serial console without "set tty com0" in the boot loader - trying to run amd64 on a machine that only supports 32-bit
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 sent you on a wild goose chase.
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 also responsible for powering off the machine. /dev/apm might be an alternative for power management. Anyone with a clue for shutting down the system with acpi disabled? Cheers Andy Le mer. 13 avr. 2022 à 22:25, a écrit : > Thanks. Your email gave me hope. > I thought it would never be possible to run OpenBSD on the hardware. > > > This is expected from the install kernel, it doesn't have DDB. > > This is important information. I think it would've been nice to see > something about it on man pages, documentation, download page or > somewhere noticable. I have a feeling there is something but I totally > missed it. > > > Try boot -c at the boot loader prompt ... I would first try "disable > > acpiec" and "quit" and see if that boots. > > This worked. Gave me a "UKC" prompt. > > boot> boot -c > ... > UKC> disable acpiec > 257 acpiec* disabled > UKC> quit > ... > > Then it booted like usual to install-upgrade screen. > > > ...What's needed is a dump of the ACPI tables, which you could get > > from another OS, but it would be helpful to try and get it booted into > > OpenBSD as this could give more information. > > I don't know how to have a OpenBSD dual booting install so I tried once > and then cancelled and then realized my whole HD was formatted!!! Even > though I cancelled!! > > I tried installing to a flash drive and it didn't get detected (probably > due to disabling acpiec). Then tried to install on the install media > itself. It seemed to work. > > Wifi wouldn't turn on, so had to connect ethernet cable. Installed file > sets from a mirror (I entered http, [enter], ftp.jaist.ac.jp, enter ... > -x*, -game*, -comp* - in case someone else gets to this thread in > future) since the install media doesn't have the file sets anymore and > has been already formatted for the installation. > > It was getting hot when installing file sets. So I pointed a table fan > at it just in case. :) > > After installing I rebooted and tried disabling acpiec first and it > worked like before. I quickly got a dmesg and dmesg.boot. > > Then I tried booting again and again disabling one by one of these each > time to see what happens: > > acpi0: boots > acpitimer: boots into ddb prompt > acpihpet: boots into ddb prompt > acpiac: boots into ddb prompt > acpibat: boots into ddb prompt > acpibtn: boots into ddb prompt > acpicpu: boots into ddb prompt > acpicmos: boots into ddb prompt > acpidock: boots into ddb prompt > acpiec: boots > acpimadt0: boots into ddb prompt > acpimcfg: boots into ddb prompt > acpiprt: boots into ddb prompt > acpisbs: boots into ddb prompt > acpitz: boots into ddb prompt > acpiasus: boots into ddb prompt > acpisony: boots into ddb prompt > acpithinkpad: boots into ddb prompt > acpitoshiba: boots into ddb prompt > acpivideo: boots into ddb prompt > acpivout: boots into ddb prompt > acpipwrres: boots into ddb prompt > > For some reason ssh access is not working even though port 22 is open. > I'll try to get the outputs and post it to @bugs. My email is > also having trouble so don't know how soon I can post it. > > > CPU spec sheet says it could support it, but maybe it's disabled by > > BIOS. IIRc 64-bit mode on some of the Atoms does not work > > brilliantly anyway. > > Will check later. >
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&m=164983204029245&w=2 | (Note: acpi drivers are used for various machine functions including | in some cases temperature control, so it's not advisable to run with | them disabled long term, but should be fine for a short test - the | N2600 is low power too which helps).
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 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&m=164983204029245&w=2 > > | (Note: acpi drivers are used for various machine functions including > | in some cases temperature control, so it's not advisable to run with > | them disabled long term, but should be fine for a short test - the > | N2600 is low power too which helps). > >
