kernel panic from scsi_get_target_luns
Hi, I don't see this reported, but I may have overlooked it. From this morning's snapshot, I'm getting a panic on reboot. This is happening on at least one of my machines, possibly two, but I don't have serial access to the other to confirm. ddb{0}> bt scsi_detach_link(8011a500,1,1e6a129e516adcd4,fd80083cef00,8 011a500,1) at scsi_detach_link+0xe3 scsi_probe_link(8011bc00,1,0,0,b281d1a92a58951a,1) at scsi_probe_link+0 x2b7 scsi_get_target_luns(8011bc00,1,8270e670,8011bc00,13798 05388fbe9b,1) at scsi_get_target_luns+0x2d scsi_probe_bus(8011bc00,8011bc00,fea2dc0ea45d96c1,8011b b80,8270e840,822a4cb8) at scsi_probe_bus+0x6e config_attach(8011bb80,822c01e8,8270e840,81c96b a0,9df33f3d46cb6508,8011e784) at config_attach+0x1f4 atapiscsi_attach(8011e000,8011bb80,8270e940,801 1e000,9dd95a5d27b314b4,8011e000) at atapiscsi_attach+0x117 config_attach(8011e000,822c0488,8270e940,810cf9 e0,9df33f3d46eb5d58,8011e770) at config_attach+0x1f4 wdcattach(8011e710,8011e710,8398a67612b1279e,80,8011ec6 0,1) at wdcattach+0x257 piixsata_chip_map(8011e000,8270ea90,b751a862a747d11d,80 024700,8270ea90,822a23d8) at piixsata_chip_map+0x462 config_attach(80024700,822c1250,8270ea90,81e805 a0,9df33f3d460e5aff,8000fa00) at config_attach+0x1f4 pci_probe_device(80024700,8000fa00,0,0,abdb1641964ffad4,0) at pci_probe _device+0x4e0 pci_enumerate_bus(80024700,0,0,80024700,886d2be239337f03,80 02e180) at pci_enumerate_bus+0x139 config_attach(8002e180,822c09c8,8270ec98,819182 70,9df33f3d4677d363,80024900) at config_attach+0x1f4 acpipci_attach_bus(8002e180,80024900,87d17a04b6b95c72,0,800 2e180,822a7570) at acpipci_attach_bus+0x1ac acpipci_attach_busses(8002e180,8002e180,106e0abcc9e5aafb,ff ff8270edb8,8002e180,0) at acpipci_attach_busses+0x5d mainbus_attach(0,8002e180,0,0,9b96c8f0b3a50dc0,0) at mainbus_attach+0x1 c3 config_attach(0,822c04f8,0,0,9df33f3d4661302c,0) at config_attach+0x1f4 cpu_configure(d37ec72fac7fe040,0,0,8002f000,81876103,82 70ef00) at cpu_configure+0x33 main(0,0,0,0,0,1) at main+0x3a3 end trace frame: 0x0, count: -19 Thanks!
Re: Kernel panic with i386 on latest snapshot
On Tue, 15 Dec 2020 at 15:03, Mark Kettenis wrote: > > > Thanks. This is committed now. However, there may be other case > where we use uvm_km_valloc() early on that will trip over the kernel > lock assertion that mpi@ added in uvm_km_pgremove(). Ideally we > should get rid of all the uvm_km_free() calls in the kernel. > Thank you and mpi@ for the fix. I wasn't able to test your diff, since my machine doesn't have the src checked out, so thank you to bluhm and Hrvoje for testing it out.
Kernel panic with i386 on latest snapshot
Hi All, On my i386 Toshiba netbook machine, I am getting a kernel panic with the latest i386 snapshot. I hope this information helps someone with the issue. > show panic kernel diagnostic assertion "_kernel_lock_held()" failed: "/usr/src/sys/uvm/uvm_km.c", line 246 > bt db_enter(d0bc6fab,d0c2da31,d0c3a6bb,d0e36b7c,d0e36b7c) at db_enter+0x4 panic(d0bc6fab, d0c2da31, d0c3a6bb, d0c51f06, f6) at panic+0xd3 _assert(d0c2da31,d0c51f06,f6,d0c3a6bb,d0e71330) at _assert+0x19 uvm_km_pgremove(d0e578ec,2552c000,2553000) at uvm_km_pgremove+0x119 uvm_umap_kill_entry(d0e36b7c,d0e71330) at uvm_unmap_kill_entry+0x92 uvm_unmap(d0e36b7c,f552c000,f553) at uvm_unmap+0x53 uvm_km_free(d0e36b7c,f552c000,4000,4000) at uvm_km_free+0x25 cpu_ucode_setup(f092c000,f080,efff9000,8d565328,1107000) at cpu_ucode_setup+0xeb cpu_startup(8d565328,1107000,1116000,110a000,0) at cpu_startup+0x14a main(0,0,0,0) at main+0x6b I've had no panics on amd64. Thanks!
Re: Kernel panic in latest snapshot
On Wed, 2 Dec 2020 at 14:36, Martin Pieuchot wrote: > > On 02/12/20(Wed) 14:22, jungle Boogie wrote: > > Hi All, > > > > Getting this kernel panic on my machine with the latest amd64 snapshot > > (13:13 timestamp) > > > > ddb{1}> bt > > spllower(821b8cb4) at spllower+0x21 > > single_thread_check_locked(80002030,0) at > > single_thread_check_locked+0x > > f4 > > userret(80002030) at userret+0x187 > > syscall(ff800032ec6ec0) at syscall+0x30e > > Xsyscall() at Xsyscall +0x128 > > end of kernel > > end of trace frame: 0xc3aee8, count: -5 > > > > Hope this helps someone! > > Thanks for the report, I just reverted the diff. I committed a wrong > version. > > Next snapshot should be alright. Wow, thanks for the quick fix! I realize my report probably could have included more info. Sorry about that. In fact, according to "show panic": "The kernel did not panic", so I used the wrong terminology. Best!
Kernel panic in latest snapshot
Hi All, Getting this kernel panic on my machine with the latest amd64 snapshot (13:13 timestamp) ddb{1}> bt spllower(821b8cb4) at spllower+0x21 single_thread_check_locked(80002030,0) at single_thread_check_locked+0x f4 userret(80002030) at userret+0x187 syscall(ff800032ec6ec0) at syscall+0x30e Xsyscall() at Xsyscall +0x128 end of kernel end of trace frame: 0xc3aee8, count: -5 Hope this helps someone! thanks, j.b.
Re: OpenBSD.calendar patch
On 6/28/20 11:15 PM, Jason McIntyre wrote: On Sat, Jun 27, 2020 at 11:56:49AM -0700, jungle boogie wrote: Hi Friends, Here's a small patch to the OpenBSD.calendar. I didn't want to spend too much time on this until I find out if it would be accepted. morning. i think if such a file is worth having, it's worth updating. having said that, i'm counting myself out from looking after this one - hopefully someone else will pick it up. Understood. And thanks for replying to my email. Anyone else care to take this on? jmc
Re: OpenBSD.calendar patch
1: ARM hackathon, Coimbra, Portugal, 8 developers, 2011 +Nov 05 p2k19: Ports hackathon, Bucharest, Romania, 18 developers, 2019 Nov 11 want.html added to OpenBSD/www, 1998 Nov 12 p2k11: Ports hackathon, Budapest, Hungary, 15 developers, 2011 Nov 14 c2k12: Coimbra hackathon, Coimbra, Portugal, 10 developers, 2012 @@ -112,6 +124,7 @@ Nov 20 h2k8: Hardware hackathon, Coimbra, Portugal, 18 Nov 21 h2k9: Hardware hackathon, Coimbra, Portugal, 15 developers, 2009 Nov 22 h2k7: Hardware hackathon, Coimbra, Portugal, 11 developers, 2007 Nov 25 h2k6: Hardware driver hackathon, Coimbra, Portugal, 14 developers, 2006 +Nov 25 e2k19: Elk Lakes Cabin hackathon, Elk Lakes Cabin, BC, 13 developers, 2019 Nov 27 Unified buffer & VM cache enters OpenBSD, 2001 Nov 30 OpenBSD gets RAID support w/ a dpt(4) addition, 1999 Dec 01 OpenBSD 3.0 released, including PF, triple set, 2001 On 6/27/20 11:56 AM, jungle boogie wrote: Hi Friends, Here's a small patch to the OpenBSD.calendar. I didn't want to spend too much time on this until I find out if it would be accepted. Here's my changes:
OpenBSD.calendar patch
Hi Friends, Here's a small patch to the OpenBSD.calendar. I didn't want to spend too much time on this until I find out if it would be accepted. Here's my changes: --- /usr/share/calendar/calendar.openbsdFri Jun 26 21:01:56 2020 +++ calendar.openbsdSat Jun 27 01:37:40 2020 @@ -10,15 +10,19 @@ Jan 06 IPF gets integrated into the OpenBSD kernel, 1996 Jan 06 NRL IPv6 addition to OpenBSD, 1999 Jan 09 n2k10: Network hackathon, Melbourne, Australia, 17 developers, 2010 +Jan 12 u2k20: Uckermark hackathon, Urckermark, Germany, 14 developers, 2020 Jan 13 n2k13: Network hackathon, Dunedin, New Zealand, 17 developers, 2013 +Jan 17 a2k19: Antipodean hackathon, Wellington, New Zealand, 18 developers, 2019 Jan 18 n2k14: Mini-hackathon, Dunedin, New Zealand, 15 developers, 2014 Jan 20 Bind 9 goes into the tree, 2003 +Jan 20 a2k20: Antipodean hackathon, Hobart, Tasmania, 17 developers, 2020 Jan 26 Anoncvs service inaugurated, 1996 Jan 26 n2k9: Network hackathon, Basel, Switzerland, 19 developers, 2009 Jan 27 OpenBSD/amd64 port is added, from NetBSD, 2004 Jan 29 "second anoncvs server is 100 miles from the first", 1996 Jan 31 OpenBSD/cats port is added, from NetBSD, 2004 Feb 03 Describe the ports mechanism [in OpenBSD], 1997 +Feb 05 a2k18: Dunedin, New Zeland, 19 developers, 2018 Feb 13 Unpatented fast block cipher for new password hashing, 1997 Feb 14 GNU RCS expired from source tree, replaced with OpenRCS, 2007 Feb 19 IPsec package by John Ioannidis and Angelos D. Keromytis, 1997 @@ -27,6 +31,7 @@ Feb 28 Cryptographic services framework in OpenBSD, 2000 Mar 09 Support for the VAX architecture removed, 2016 Mar 10 OpenBSD/WWW translation started -- German, Spanish, Dutch, 2000 +Mar 28 t2k19: Taipei mini hackathon, Taipei, Taiwan, 16 developers, 2019 Apr 01 OpenBSD/hppa64 port is added, 2005 Apr 01 k2k11: Kernel hackathon, Hafnarfjordur, Iceland, 15 developers, 2011 Apr 10 f2k7: First filesystem hackathon, Vienna, Austria, 14 developers, 2007 @@ -40,10 +45,12 @@ Apr 27 i386/PAE work integrated, 2006 May 01 OpenBSD 3.3 released, exploiting W^X, 2003 May 05 n2k8: Network hackathon, Ito, Japan, 18 developers, 2008 +May 07 g2k19: General hackathon, Ottawa, Canada, 43 developers, 2019 May 08 c2k3 General hackathon, Calgary, Alberta, 51 developers, 2003 May 09 First commit to OpenBSD stable branch, OPENBSD_2_7, 2000 May 09 OpenBSD/aviion port is added, 2006 May 19 OpenBSD 2.3 released, including "ports" system, 1998 +May 19 OpenBSD 6.7 released, 48th release, 2020 May 21 c2k5: General hackathon, Calgary, Alberta, 60 developers, 2005 May 21 c2k6: General hackathon, Calgary, Alberta, 47 developers, 2006 May 24 OpenBSD gets a trunk(4), 2005 @@ -57,6 +64,7 @@ Jun 04 c99: First hackathon (IPsec), Calgary, Alberta, 10 developers, 1999 Jun 04 c2k2: General hackathon, Calgary, Alberta, 42 developers, 2002 Jun 06 c2k8: General hackathon, Edmonton, Alberta, 55 developers, 2008 +Jun 21 WireGuard imported into kernel, 2020 Jun 14 r2k6: First network hackathon, Hamburg, Germany, 6 developers, 2006 Jun 15 OpenBSD 2.7 released, including OpenSSH, 2000 Jun 15 c2k: First general hackathon, Calgary, Alberta, 18 developers, 2000 @@ -70,6 +78,7 @@ Jul 02 c2k11: General hackathon, Edmonton, Alberta, Canada, 36 developers, 2011 Jul 07 g2k12: General hackathon, Budapest, Hungary, 41 developers, 2012 Jul 08 g2k14: General hackathon, Ljubljana, Slovenia, 49 developers, 2014 +Jul 08 g2k18: General hackathon, Ljubljana, Slovenia, 39 developers, 2018 Jul 11 OpenBSD goes wireless w/ if_wi addition, 1999 Jul 23 OpenBSD goes multimedia with Brooktree 848 support, 1998 Jul 24 Non-executable stack on most architectures, 2002 @@ -83,6 +92,7 @@ Aug 28 k2k6: IPsec hackathon, Schloss Kransberg, Germany, 14 developers, 2006 Sep 01 Support for the sparc (32bit) architecture removed, 2016 Sep 03 Support for the zaurus architecture removed, 2016 +Sep 06 n2k18: Network hackathon, Usti nad Labem, Czech Republic, 11 developers, 2018 Sep 16 s2k11: General hackathon, Ljubljana, Slovenia, 25 developers, 2011 Sep 17 n2k12: Network hackathon, Starnberg, Germany, 23 developers, 2012 Sep 19 j2k10: Mini-hackathon, Sakae Mura, Nagano, Japan, 19 developers, 2010 @@ -103,7 +113,9 @@ Oct 30 OpenBSD 3.4 released, implementing W^X on i386 and AES in VIA C3, 2003 Nov 01 OpenBSD 3.2 released, ftp mirrors preload for the first time, 2002 Nov 01 v2k5: First ports hackathon, Venice, Italy, 12 developers, 2005 +Nov 03 l2k18: Libressl hackathon, Edmonton, Canada, 5 developers, 2018 Nov 05 a2k11: ARM hackathon, Coimbra, Portugal, 8 developers, 2011 +Nov 05 p2k19: Ports hackathon, Bucharest, Romania, 18 developers, 2019 Nov 11 want.html added to OpenBSD/www, 1998 Nov 12 p2k11: Ports hackathon, Budapest, Hungary, 15 developers, 2011 Nov 14 c2k12: Coimbra hackathon, Coimbra, Portugal, 10 developers, 2012 @@ -112,6 +124,7 @@ Nov 21 h2k9: Hardware hackathon, Coimbra, Portugal, 15 developers, 2009 Nov 22 h2k7
Re: dwxe: resetting interface on watchdog timeout
On Wed 17 Apr 2019 9:44 AM, Sebastien Marie wrote: Hi, With a pine64, I am experimenting regulary dwxe watchdog timeout. Usually it is a sign that something doesn't work in the driver itself. Good to know this isn't just affecting my three devices. Let's hope this patch gets some feedback and makes its way into the build.
Re: www/64.html - OpenSSH version 7.8 or 7.9?
Thus said Darren Tucker on Fri, 19 Oct 2018 14:23:48 +1100 On 18 October 2018 at 07:20, Markus Lude wrote: Hello, www/64.html mentions OpenSSH version 7.8. With snapshot from october 11th on amd64 the version of ssh is 7.9: it's 7.9, which was officially released a couple of hours ago. The website will be updated shortly. I see the release notes are alive: https://www.openssh.com/txt/release-7.9 Might want to change the link on https://www.openssh.com leading to the release, still showing 7.8.
smtp core dump
Hi All, I'm only playing around with smtp(1), so my use case may be wrong. I'm getting a coredump with it on OpenBSD snapshot from today (8 Sept). My string to cause the core dump: smtp -C -vv -F jungleboog...@gmail.com -s smtp://user:p...@imap.gmail.com:587 jungleboog...@gmail.com hello trying host 74.125.195.108 port 587... 0x12f009456800: INIT -> BANNER 0x12f009456800: <<< 220 smtp.gmail.com ESMTP r23-v6sm25386962pfj.5 - gsmtp 0x12f009456800: BANNER -> EHLO mta: 0x12f009456800: >>> EHLO puffer.in.mydomain.net 0x12f009456800: <<< 250-smtp.gmail.com at your service, [70.173.220.152] 0x12f009456800: <<< 250-SIZE 35882577 0x12f009456800: <<< 250-8BITMIME 0x12f009456800: <<< 250-STARTTLS 0x12f009456800: <<< 250-ENHANCEDSTATUSCODES 0x12f009456800: <<< 250-PIPELINING 0x12f009456800: <<< 250-CHUNKING 0x12f009456800: <<< 250 SMTPUTF8 0x12f009456800: EHLO -> STARTTLS mta: 0x12f009456800: >>> STARTTLS 0x12f009456800: <<< 220 2.0.0 Ready to start TLS validating server certificate... 0x12f009456800: STARTTLS -> EHLO mta: 0x12f009456800: >>> EHLO puffer.in.mydomain.net 0x12f009456800: <<< 250-smtp.gmail.com at your service, [70.173.220.152] 0x12f009456800: <<< 250-SIZE 35882577 0x12f009456800: <<< 250-8BITMIME 0x12f009456800: <<< 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH 0x12f009456800: <<< 250-ENHANCEDSTATUSCODES 0x12f009456800: <<< 250-PIPELINING 0x12f009456800: <<< 250-CHUNKING 0x12f009456800: <<< 250 SMTPUTF8 0x12f009456800: EHLO -> STARTTLS 0x12f009456800: STARTTLS -> AUTH 0x12f009456800: AUTH -> AUTH_PLAIN mta: 0x12f009456800: >>> AUTH PLAIN user:pass 0x12f009456800: <<< 501 5.5.2 Cannot Decode response r23-v6sm25386962pfj.5 - gsmtp rejected by server: 501 5.5.2 Cannot Decode response r23-v6sm25386962pfj.5 - gsmtp 0x12f009456800: AUTH_PLAIN -> QUIT mta: 0x12f009456800: >>> QUIT 0x12f009456800: <<< 221 2.0.0 closing connection r23-v6sm25386962pfj.5 - gsmtp connection closed... trying host 74.125.195.109 port 587... 0x12f009456c00: INIT -> BANNER 0x12f009456c00: <<< 220 smtp.gmail.com ESMTP z63-v6sm14785681pgd.69 - gsmtp 0x12f009456c00: BANNER -> EHLO mta: 0x12f009456c00: >>> EHLO puffer.in.mydomain.net 0x12f009456c00: <<< 250-smtp.gmail.com at your service, [70.173.220.152] 0x12f009456c00: <<< 250-SIZE 35882577 0x12f009456c00: <<< 250-8BITMIME 0x12f009456c00: <<< 250-STARTTLS 0x12f009456c00: <<< 250-ENHANCEDSTATUSCODES 0x12f009456c00: <<< 250-PIPELINING 0x12f009456c00: <<< 250-CHUNKING 0x12f009456c00: <<< 250 SMTPUTF8 0x12f009456c00: EHLO -> STARTTLS mta: 0x12f009456c00: >>> STARTTLS 0x12f009456c00: <<< 220 2.0.0 Ready to start TLS Bus error (core dumped) The backtrace is pretty uneventful, there's no debugging: gdb) bt #0 SSL_set_fd (s=0x12f06818ff00, fd=5) at /usr/src/lib/libssl/ssl_lib.c:580 #1 0x12edb7d035b6 in ?? () from /usr/bin/smtp #2 0x12edb7d04e18 in ?? () from /usr/bin/smtp #3 0x12edb7d0318d in ?? () from /usr/bin/smtp #4 0x12effd9aeb6d in event_base_loop (base=0x12f068189800, flags=0) at /usr/src/lib/libevent/event.c:350 #5 0x12edb7d063ef in ?? () from /usr/bin/smtp #6 0x12edb7d061f7 in ?? () from /usr/bin/smtp #7 0x12edb7d00c56 in ?? () from /usr/bin/smtp #8 0x in ?? () So what's going on with this?
fsck - abort trap on openBSD current
Hi All, Getting some unexpected inconsistencies reported during boot up on my openBSD -current amd64 machine: https://i.imgur.com/ZxnXrx8.jpg How can I fsck /var if fsck abort traps? Wait for next build? Thanks!
Re: panic: unveil_nipledge_lookup: unexpected pledge bits: 8589934592 after update to recent -current
Reported it here: https://marc.info/?l=openbsd-bugs&m=153324017411435&w=2 Should I have posted to tech@ instead? I can confirm the next snapshot fixed the panic.
Octeon - kernel panic at login
Hi All, I logged into my erl octeon device to upgrade it. When I logged in via serial, I received a panic. login: root panic: init died (signal 0, exit 10) Stopped at 0x8135036c: jr ra 0x81350370: nop TIDPIDUID PRFLAGS PFLAGS CPU COMMAND *344602 1 0 0x2 0x20000K init 0x81350368 (1202c41c2c6691bc,900107000208,208,98000fff7d98) ra 0x813ac5f8 sp 0x98000fff7dd0, sz 0 0x813ac3b8 (1202c41c2c6691bc,900107000208,208,98000fff7d98) ra 0x0 sp 0x98000fff7dd0, sz 0 User-level: pid 1 https://www.openbsd.org/ddb.html describes the minimum info required in bug reports. Insufficient info makes it difficult to find and fix bugs. ddb{0}> bt 0x81350368 (1202c41c2c6691bc,900107000208,208,98000fff7d98) ra 0x813ac5f8 sp 0x98000fff7dd0, sz 0 0x813ac3b8 (1202c41c2c6691bc,900107000208,208,98000fff7d98) ra 0x0 sp 0x98000fff7dd0, sz 0 User-level: pid 1 Last snapshot was from Tue Jun 26 03:54:54 UTC 2018 Thanks!
Re: libxshmfence.so.0.0 issues with latest snapshot?
On 26 June 2018 at 11:46, James Turner wrote: > > I ran into the same issue. You can either wait for a new snapshot, or > build X yourself following step 5 in release(8). > Thanks for the reply! I'll await the next snapshot. > -- > James Turner -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
libxshmfence.so.0.0 issues with latest snapshot?
Hi All, Prior to updating to the latest snapshot (#56), I updated my packages, then updated to #56. Now X won't start and I have a library error: ls.so: X: can't load library libxshmfence.so.0.0 At the time of updating packages, there wasn't a new snapshot available so I felt it was safe to proceed. What are my options at this point? Is this something others are also experiencing? --- inum: 883510009027723 sip: jungleboo...@sip2sip.info