Re: Ssh key stopped working
On Thu, May 15, 2014 at 03:09:42PM +0200, Eivind Evensen wrote: On Thu, May 15, 2014 at 01:53:22PM +0200, Eivind Evensen wrote: On Sat, May 10, 2014 at 10:44:47PM +, Stuart Henderson wrote: On 2014-05-08, Eivind Evensen eivi...@terraplane.org wrote: Hello. After upgrading an i386 I can no longer login via ssh using the key I normally use. The server says in authlog: There have been a couple of bugs in -current recently that have broken ssh in various situations, please could you try an up-to-date snapshot and post again if it still happens? Thanks for the reply. I still see it: May 15 13:44:49 rev sshd[27321]: error: buffer_get_bignum2_ret: bignum is too large [preauth] May 15 13:44:49 rev sshd[27321]: error: key_from_blob: can't read rsa key [preauth] May 15 13:44:49 rev sshd[27321]: error: userauth_pubkey: cannot decode key: ssh-rsa [preauth] May 15 13:44:54 rev sshd[27321]: Connection closed by 10.10.10.8 [preauth] OpenBSD 5.5-current (GENERIC) #105: Mon May 12 21:43:29 MDT 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC Another funny thing, trying to use ssh and the ssh-agent on an amd64 computer with the same key: .eval `ssh-agent -c` Agent pid 19739 .ssh-add -l The agent has no identities. .ssh-add Enter passphrase for /home/rumrunner/.ssh/id_rsa: Error reading response length from authentication socket. Could not add identity: /home/rumrunner/.ssh/id_rsa .ssh-add -l Could not open a connection to your authentication agent. But still: .ssh klump buffer_get_bignum2_ret: bignum is too large key_from_blob: can't read rsa key key_read: dump of key comes hereEnter passphrase for key '/home/rumrunner/.ssh/id_rsa': Last login: Fri May 9 17:37:27 2014 from elg it logs me in at this point No newline before the Enter passphrase... is how it was displayed. This is on: OpenBSD 5.5-current (GENERIC.MP) #126: Mon May 12 22:40:04 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP For the record, with sources upgraded and built from cvs from Sunday I still see this, with new keys too: .ssh-keygen -b 16384 Generating public/private rsa key pair. load: 1.43 cmd: ssh-keygen 18502 [running] 397.51u 0.00s 99% 0k Enter file in which to save the key (/home/rumrunner/.ssh/id_rsa): taskulf Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in taskulf. Your public key has been saved in taskulf.pub. The key fingerprint is: 16:61:8a:3a:3f:da:b3:96:39:31:f2:87:e0:f4:1e:0f rumrunner@ugle.hjerdalen.lokalnett The key's randomart image is: +--[ RSA 16384]---+ |o| | . o . | |. . .| | . . | | o S| | +oo . | | o =E* | | .oX=. | | .o+=. | +-+ .file taskulf* taskulf: ASCII text taskulf.pub: ASCII text, with very long lines .eval `ssh-agent -c` Agent pid 23633 .ps ax |grep ssh-ag 23633 ?? Ss 0:00.02 ssh-agent -c 21022 p3 S+ 0:00.00 grep ssh-ag .ssh-add taskulf Error reading response length from authentication socket. Could not add identity: taskulf .ps ax |grep ssh-ag (process is dead) -- Eivind
Re: Ssh key stopped working
On Thu, May 15, 2014 at 01:53:22PM +0200, Eivind Evensen wrote: On Sat, May 10, 2014 at 10:44:47PM +, Stuart Henderson wrote: On 2014-05-08, Eivind Evensen eivi...@terraplane.org wrote: Hello. After upgrading an i386 I can no longer login via ssh using the key I normally use. The server says in authlog: There have been a couple of bugs in -current recently that have broken ssh in various situations, please could you try an up-to-date snapshot and post again if it still happens? Thanks for the reply. I still see it: May 15 13:44:49 rev sshd[27321]: error: buffer_get_bignum2_ret: bignum is too large [preauth] May 15 13:44:49 rev sshd[27321]: error: key_from_blob: can't read rsa key [preauth] May 15 13:44:49 rev sshd[27321]: error: userauth_pubkey: cannot decode key: ssh-rsa [preauth] May 15 13:44:54 rev sshd[27321]: Connection closed by 10.10.10.8 [preauth] OpenBSD 5.5-current (GENERIC) #105: Mon May 12 21:43:29 MDT 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC Another funny thing, trying to use ssh and the ssh-agent on an amd64 computer with the same key: .eval `ssh-agent -c` Agent pid 19739 .ssh-add -l The agent has no identities. .ssh-add Enter passphrase for /home/rumrunner/.ssh/id_rsa: Error reading response length from authentication socket. Could not add identity: /home/rumrunner/.ssh/id_rsa .ssh-add -l Could not open a connection to your authentication agent. But still: .ssh klump buffer_get_bignum2_ret: bignum is too large key_from_blob: can't read rsa key key_read: dump of key comes hereEnter passphrase for key '/home/rumrunner/.ssh/id_rsa': Last login: Fri May 9 17:37:27 2014 from elg it logs me in at this point No newline before the Enter passphrase... is how it was displayed. This is on: OpenBSD 5.5-current (GENERIC.MP) #126: Mon May 12 22:40:04 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP -- Eivind
Re: Ssh key stopped working
On Sat, May 10, 2014 at 10:44:47PM +, Stuart Henderson wrote: On 2014-05-08, Eivind Evensen eivi...@terraplane.org wrote: Hello. After upgrading an i386 I can no longer login via ssh using the key I normally use. The server says in authlog: There have been a couple of bugs in -current recently that have broken ssh in various situations, please could you try an up-to-date snapshot and post again if it still happens? Thanks for the reply. I still see it: May 15 13:44:49 rev sshd[27321]: error: buffer_get_bignum2_ret: bignum is too large [preauth] May 15 13:44:49 rev sshd[27321]: error: key_from_blob: can't read rsa key [preauth] May 15 13:44:49 rev sshd[27321]: error: userauth_pubkey: cannot decode key: ssh-rsa [preauth] May 15 13:44:54 rev sshd[27321]: Connection closed by 10.10.10.8 [preauth] OpenBSD 5.5-current (GENERIC) #105: Mon May 12 21:43:29 MDT 2014 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC -- Eivind
Ssh key stopped working
Hello. After upgrading an i386 I can no longer login via ssh using the key I normally use. The server says in authlog: May 8 08:44:13 rev sshd[18843]: error: buffer_get_bignum2_ret: bignum is too large [preauth] May 8 08:44:13 rev sshd[18843]: error: key_from_blob: can't read rsa key [preauth] May 8 08:44:13 rev sshd[18843]: error: userauth_pubkey: cannot decode key: ssh-rsa [preauth] The only thing not being quite common is the key, which has more bits than the default. If I remember correctly I generated it with ssh-keygen -b 16384. Any ideas what to do about this? Eivind OpenBSD 5.5-current (GENERIC) #70: Thu May 1 12:10:13 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) M processor 1400MHz (GenuineIntel 686-class) 1.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,PERF real mem = 233205760 (222MB) avail mem = 216981504 (206MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/18/04, BIOS32 rev. 0 @ 0xfd740, SMBIOS rev. 2.31 @ 0xdf010 (28 entries) bios0: vendor Hewlett-Packard version F.10 date 08/18/2004 bios0: Hewlett-Packard hp pavilion ze4900 (PJ943EA#ABN) acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP BOOT SSDT acpi0: wakeup devices BAT0(S3) LAN_(S5) PS2K(S3) PSM1(S3) PSM2(S3) USB0(S3) USB1(S3) USB7(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PCIB) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1 acpitz0 at acpi0: critical temperature is 95 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model JM-6 serial 185 type LION oem Hewlett-Packard acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpivideo0 at acpi0: GFX0 bios0: ROM list: 0xc/0xcc00! 0xcd000/0x1000 0xdf000/0x1000! 0xe/0x4000! cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82855GM Host rev 0x02 Intel 82855GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82855GM Config rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82855GM Video rev 0x02 intagp0 at vga1 agp0 at intagp0: aperture at 0xe800, size 0x800 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82855GM Video rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x03: irq 10 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x03: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x03: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x03: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x83 pci1 at ppb0 bus 2 rl0 at pci1 dev 0 function 0 Realtek 8139 rev 0x10: irq 10, address 00:c0:9f:50:32:6a rlphy0 at rl0 phy 0: RTL internal PHY cbb0 at pci1 dev 5 function 0 TI PCI1410 CardBus rev 0x02: irq 11, CardBus support disabled cardslot0 at cbb0 slot 0 flags 0 pcmcia0 at cardslot0 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x03 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: FUJITSU MHT2060AT wd0: 16-sector PIO, LBA, 57231MB, 117210240 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: PHILIPS, CDRW/DVD CDD5263, UH89 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x03: irq 5 iic0 at ichiic0 spdmem0 at iic0 addr 0x51: 256MB DDR SDRAM non-parity PC2700CL2.5 auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x03: irq 5, ICH4 AC97 ac97: codec id 0x43585430 (Conexant CXT48) ac97: codec features reserved, headphone, 18 bit DAC, 18 bit ADC, No 3D Stereo audio0 at auich0 Intel 82801DB Modem rev 0x03 at pci0 dev 31 function 6 not configured usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pms0: Synaptics touchpad, firmware 5.9 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using
Re: Updating ports via anoncvs hangs
On Thu, May 23, 2013 at 07:43:56AM +1000, John Tate wrote: When I go to update ports by anoncvs it just hangs, it's been like this for hours. Something doesn't seem right. elijah:usr # cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs get -rOPENBSD_5_3 -P ports Did you check what ^T tells? -- Eivind
Re: vnd and softraid panic
On Thu, Jan 31, 2013 at 12:20:14AM +1100, Joel Sing wrote: On Wed, 30 Jan 2013, Eivind Evensen wrote: On Wed, Jan 23, 2013 at 02:33:16AM +1100, Joel Sing wrote: On Thu, 3 Jan 2013, Eivind Evensen wrote: On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... FWIW this should now be rectified in -current. I tried a snapshot downloaded on 21.th (OpenBSD 5.2-current (GENERIC) #17: Fri Jan 18 19:42:57 MST 2013) which produced the same results. I waited a few days in case the snapshot was too old and built from sources from yesterday, still giving the same results. I don't need such a setup so it's not a big deal, but here's output and dmesg in case it may be helpful: Thanks for the report. For some reason I thought you had tried using softraid crypto on a vnd and overlooked the fact that you were trying to use RAID 5 (and now RAID 1). To clarify, RAID 0, CONCAT and CRYPTO should all now work on top of a vnd - RAID 1, RAID 4 and RAID 5 will still break in the manner given below (panic related to active workunits). These disciplines require the same changes that I've made to the other three, however they're a little more complex and time consuming. I'll try to get to them fixed soon. I see, thanks for the explanation. Eivind.
Re: vnd and softraid panic
On Wed, Jan 23, 2013 at 02:33:16AM +1100, Joel Sing wrote: On Thu, 3 Jan 2013, Eivind Evensen wrote: On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... FWIW this should now be rectified in -current. I tried a snapshot downloaded on 21.th (OpenBSD 5.2-current (GENERIC) #17: Fri Jan 18 19:42:57 MST 2013) which produced the same results. I waited a few days in case the snapshot was too old and built from sources from yesterday, still giving the same results. I don't need such a setup so it's not a big deal, but here's output and dmesg in case it may be helpful: root:skoeske dd if=/dev/zero of=disk1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.875 secs (36462177 bytes/sec) root:skoeske r disk1=disk2 dd if=/dev/zero of=disk2 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.219 secs (32567739 bytes/sec) root:skoeske r disk2=disk3 dd if=/dev/zero of=disk3 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.569 secs (29378164 bytes/sec) root:skoeske vnconfig vnd0 disk1 root:skoeske vnconfig vnd1 disk2 root:skoeske vnconfig vnd2 disk3 root:skoeske fdisk -iy vnd0 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd1 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd2 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd0 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd1 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd2 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske bioctl -c 1 -l /dev/vnd0a,/dev/vnd1a,/dev/vnd2a softraid0 sd0 at scsibus1 targ 1 lun 0: OPENBSD, SR RAID 1, 005 SCSI2 0/direct fixed sd0: 99MB, 512 bytes/sector, 204144 sectors softraid0: SR RAID 1 volume attached as sd0 panic: softraid0: sr_wu_init got active wu Stopped at Debugger+0x4: popl%ebp RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger(d08fcddc,f2087de8,d08d0da4,f2087de8,d0a7e540) at Debugger+0x4 panic(d08d0da4,d0f8c014,f2087dfc,d036ccf3,d0fedab8) at panic+0x5d sr_wu_init(d1055000,d0fedab8,f2087e3c,d1055a30,d1057f00) at sr_wu_init+0x73 sr_wu_put(d1055000,d0fedab8,f2087e3c,f2087e3c,d02030dd) at sr_wu_put+0x2f scsi_io_put(d1055a30,d0fedab8,8000,d0fedab8,d0fedab8) at scsi_io_put+0x19 scsi_xs_put(f2027000,f2027000,f2087e8c,d041de18,d1055000) at scsi_xs_put+0x37 sr_raid1_intr(d1065000,f1fabdc4,f17dc000,200,52000) at sr_raid1_intr+0x107 vndstrategy(d1065000,0,0,50,d1065000) at vndstrategy+0x70 spec_strategy(f2087f48,0,f2087f6c,d03f2c28,d1053d90) at spec_strategy+0x3d VOP_STRATEGY(d1065000,0,0,0,d0fedaf8) at VOP_STRATEGY+0x2c sr_startwu_callback(d1055000,d0fedab8,d02008bf,d1053d80,d03f2c50) at sr_startwu _callback+0x39 workq_thread(d1053d80) at workq_thread+0x36 Bad frame pointer: 0xd0bc8ed8 ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND *23369 0 0 0 70x100200srdis 19292 1571 6315 1000 30x80 ttyin less 1571 6315 6315 1000 30x88 pause sh 6315 30722 6315 1000 30x80 wait man 30722 11048 30722 1000 30x88 pause ksh 11048 2130 2130 1000 30x80 selectsshd 2130 1703 2130 0 30x80 poll sshd 2513 1 2513 0 20x80ksh 20983 1 20983 0 30x80 ttyin getty 22576 1 22576 0 30x80 ttyin getty 19748 1 19748 0 30x80 ttyin getty 21880 1 21880 0 30x80 ttyin getty 5243 1 5243 0 30x80 ttyin getty 32690 1 32690 0 30x80 selectcron 24485 1 24485 99 30x80 poll sndiod 99 1 99 0 30x80 selectinetd 22458 15830 15830 95 30x80 kqreadsmtpd 17649 15830 15830 95 30x80 kqreadsmtpd 17949 15830 15830 95 30x80 kqreadsmtpd 3934
Re: vnd and softraid panic
On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: On Mon, 31 Dec 2012, Eivind Evensen wrote: Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. ... ddb trace Debugger(d08fa43c,f2017e08,d08ce53b,f2017e08,0) at Debugger+0x4 panic(d08ce53b,d0f8a014,f2017e3c,d105fa30,d105ce00) at panic+0x5d sr_wu_put(d105f000,d0ff12b8,f2017e3c,f2017e3c,d02030dd) at sr_wu_put+0x104 scsi_io_put(d105fa30,d0ff12b8,8000,d1068000,d1068000) at scsi_io_put+0x19 scsi_xs_put(f1f4d000,d1068000,f2017e8c,d0418d98,f1f4d000) at scsi_xs_put+0x37 sr_raidp_intr(d1068000,f1e8601c,f11ec000,200,52000) at sr_raidp_intr+0x15b vndstrategy(d1068000,0,0,50,d1068000) at vndstrategy+0x70 spec_strategy(f2017f48,0,f2017f6c,d03ee028,d1053f50) at spec_strategy+0x3d VOP_STRATEGY(d1068000,0,0,0,d0ff12f8) at VOP_STRATEGY+0x2c sr_startwu_callback(d105f000,d0ff12b8,d02008bf,d1053f40,d03ee050) at sr_startwu _callback+0x39 workq_thread(d1053f40) at workq_thread+0x36 Bad frame pointer: 0xd0bc6ed8 Thanks - it is a known issue, which I hope to be able to finish addressing during the next hackathon. Nice to know. If it helps, I can test patches. Regards, Eivind
vnd and softraid panic
Hello. Trying to play around a bit with softraid using vnd reliably results in a panic when assembling the raid volume. I think the first time I tried this was around 4.9 so it's not something new. While the combination of vnd and softraid may not be useful for any real purpose, I noticed this while hoping to be able to fail a disk in a somewhat simpler to retry manner than the nailgun approach I read about here recently... I don't know if it's important, but also after the trace and ps listed below, boot reboot won't reboot the first time, but I can enter ddb again by sending a serial break and then get the machine to reboot by reexecuting the boot reboot command. Regards, Eivind root:skoeske dd if=/dev/zero of=disk1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.852 secs (27215650 bytes/sec) root:skoeske r disk1=disk2 dd if=/dev/zero of=disk2 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.569 secs (40802861 bytes/sec) root:skoeske r disk2=disk3 dd if=/dev/zero of=disk3 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.750 secs (27957919 bytes/sec) root:skoeske vnconfig vnd0 disk1 root:skoeske vnconfig vnd1 disk2 root:skoeske vnconfig vnd2 disk3 root:skoeske fdisk -iy vnd0 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd1 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske fdisk -iy vnd2 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd0 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd1 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske printf a\n\n\n\nRAID\nw\nq\n\n | disklabel -E vnd2 Label editor (enter '?' for help at any prompt) partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] No label changes. root:skoeske bioctl -c 5 -l /dev/vnd0a,/dev/vnd1a,/dev/vnd2a softraid0 sd0 at scsibus1 targ 1 lun 0: OPENBSD, SR RAID 5, 005 SCSI2 0/direct fixed sd0: 199MB, 512 bytes/sector, 408064 sectors softraid0: SR RAID 5 volume attached as sd0 panic: softraid0: sr_wu_put got active wu Stopped at Debugger+0x4: popl%ebp RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger(d08fa43c,f2017e08,d08ce53b,f2017e08,0) at Debugger+0x4 panic(d08ce53b,d0f8a014,f2017e3c,d105fa30,d105ce00) at panic+0x5d sr_wu_put(d105f000,d0ff12b8,f2017e3c,f2017e3c,d02030dd) at sr_wu_put+0x104 scsi_io_put(d105fa30,d0ff12b8,8000,d1068000,d1068000) at scsi_io_put+0x19 scsi_xs_put(f1f4d000,d1068000,f2017e8c,d0418d98,f1f4d000) at scsi_xs_put+0x37 sr_raidp_intr(d1068000,f1e8601c,f11ec000,200,52000) at sr_raidp_intr+0x15b vndstrategy(d1068000,0,0,50,d1068000) at vndstrategy+0x70 spec_strategy(f2017f48,0,f2017f6c,d03ee028,d1053f50) at spec_strategy+0x3d VOP_STRATEGY(d1068000,0,0,0,d0ff12f8) at VOP_STRATEGY+0x2c sr_startwu_callback(d105f000,d0ff12b8,d02008bf,d1053f40,d03ee050) at sr_startwu _callback+0x39 workq_thread(d1053f40) at workq_thread+0x36 Bad frame pointer: 0xd0bc6ed8 ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND * 4458 0 0 0 70x100200srdis 9614 9263 31326 1000 30x80 ttyin less 9263 31326 31326 1000 30x88 pause sh 31326 8662 31326 1000 30x80 wait man 8662 24219 8662 1000 30x88 pause ksh 24219 7388 7388 1000 30x80 selectsshd 7388 1358 7388 0 30x80 poll sshd 8332 1 8332 0 20x80ksh 21947 1 21947 0 30x80 ttyin getty 28840 1 28840 0 30x80 ttyin getty 32669 1 32669 0 30x80 ttyin getty 25686 1 25686 0 30x80 ttyin getty 19769 1 19769 0 30x80 ttyin getty 10627 1 10627 0 30x80 selectcron 14888 1 14888 99 30x80 poll sndiod 5483 1 5483 0 30x80 selectinetd 27714 10979 10979 95 30x80 kqreadsmtpd 9877 10979 10979 95 30x80 kqreadsmtpd 31352 10979 10979 95 30x80 kqreadsmtpd 17499 10979 10979 95 30x80 kqreadsmtpd 25024 10979 10979 95 30x80 kqreadsmtpd 28736 10979 10979 95 30x80 kqreadsmtpd 22163 10979 10979 95 30x80 kqread
umct(4) man page
The umct(4) man page states: BUGS This driver is not known to work currently. If someone does discover that it is working, please report this. I see that this message was added in 2002 according to cvs ann, but in case it's of interest, the device from the dmesg below works mostly. The only thing I've noticed doesn't work is sending a break with ~# in cu. At least I haven't been able to get the machine into ddb using it. OpenBSD 5.2-beta (GENERIC.MP) #36: Thu Jun 21 23:35:24 CEST 2012 rumrunner@ugle.hjerdalen.lokalnett:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3870363648 (3691MB) avail mem = 3744972800 (3571MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeafd0 (50 entries) bios0: vendor American Megatrends Inc. version 216 date 08/26/2011 bios0: ASUSTeK Computer Inc. K53U acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT SLIC acpi0: wakeup devices SBAZ(S4) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD E-450 APU with Radeon(tm) HD Graphics, 1646.73 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD E-450 APU with Radeon(tm) HD Graphics, 1646.50 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative ioapic0 at mainbus0: apid 3 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (PE20) acpiprt2 at acpi0: bus 4 (PE21) acpiprt3 at acpi0: bus -1 (PE22) acpiprt4 at acpi0: bus -1 (PE23) acpiprt5 at acpi0: bus -1 (BR15) acpiprt6 at acpi0: bus -1 (PCE6) acpiprt7 at acpi0: bus -1 (PCE7) acpiprt8 at acpi0: bus -1 (PCE8) acpiprt9 at acpi0: bus 1 (PCE4) acpiec0 at acpi0 acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS acpitz0 at acpi0: critical temperature is 99 degC acpibat0 at acpi0: BAT1 model PA3533U serial 41167 type Li-Ion oem TOSHIBA acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: LID_ acpivideo0 at acpi0: VGA_ acpivideo1 at acpi0: VGA_ cpu0: 1646 MHz: speeds: 1650 1320 825 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD AMD64 14h Host rev 0x00 vga1 at pci0 dev 1 function 0 ATI Radeon HD 6320 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 3 int 18 drm0 at radeondrm0 azalia0 at pci0 dev 1 function 1 ATI Radeon HD 6310 HD Audio rev 0x00: msi azalia0: no supported codecs ppb0 at pci0 dev 4 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci1 at ppb0 bus 1 ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x40: apic 3 int 19, AHCI 1.2 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, ST9500325AS, 0003 SCSI3 0/direct fixed naa.5000c500464e37ee sd0: 476940MB, 512 bytes/sector, 976773168 sectors cd0 at scsibus0 targ 1 lun 0: HL-DT-ST, DVDRAM GT34N, AS00 ATAPI 5/cdrom removable ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 3 int 18, version 1.0, legacy support ehci0 at pci0 dev 18 function 2 ATI SB700 USB2 rev 0x00: apic 3 int 17 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 19 function 0 ATI SB700 USB rev 0x00: apic 3 int 18, version 1.0, legacy support ehci1 at pci0 dev 19 function 2 ATI SB700 USB2 rev 0x00: apic 3 int 17 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 ATI EHCI root hub rev 2.00/1.00 addr 1 piixpm0 at pci0 dev 20 function 0 ATI SBx00 SMBus rev 0x42: polling iic0 at piixpm0 spdmem0 at iic0 addr 0x51: 4GB DDR3 SDRAM PC3-10600 SO-DIMM pciide0 at pci0 dev 20 function 1 ATI SB700 IDE rev 0x40: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility azalia1 at pci0 dev 20 function 2 ATI SBx00 HD Audio rev 0x40: apic 3 int 16 azalia1: codecs: Realtek ALC269 audio0 at azalia1 pcib0 at pci0 dev 20 function 3 ATI SB700 ISA rev 0x40 ppb1 at pci0 dev 20
Re: after downgrade OpenBSD dmesg display wrong information
On Thu, Apr 19, 2012 at 12:22:11AM -0400, Hugo Villeneuve wrote: On Tue, Apr 17, 2012 at 10:34:22AM +0200, Otto Moerbeek wrote: Some machines keep previous dmessages in mem. Scroll down to see the most recent dmesg, or check /var/run/dmesg.boot A cold boot wipes the dmesg buffer. -Otto Did something change in -current? /etc/rc just does dmesg /var/run/dmesg.boot. It will also have the previous boot data on computer that don't reset memory. It annoyed me enough that I added this to rc.local on those computer: I like having those old messages available. On junk that doesn't have serial ports it's the simplest way of getting to for example ddb output after a reboot. ed -s /var/run/dmesg.boot EOF /dev/null 21 ?^OpenBSD [0-9]? 1,-d wq EOF -- Eivind
