urndis on octeon. urndis0: IOERROR
Hi, i get this trying to use usb tethering w/android on edgerouter lite latest(or very close) snap GENERIC.MP: urndis0 at uhub1 port 1 configuration 1 interface 0 "SAMSUNG SAMSUNG_Android" rev 2.00/ff.ff addr 4 urndis0: using RNDISurndis0: IOERROR urndis0: unable to get query response : unable to get hardware address missing letoh32() somewhere in init path? full dmesg from where i tried to enable the urndis twice below. -Artturi Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2017 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.1-current (GENERIC.MP) #0: Tue Aug 1 05:17:56 UTC 2017 visa@octeon:/usr/src/sys/arch/octeon/compile/GENERIC.MP real mem = 536870912 (512MB) avail mem = 524009472 (499MB) mainbus0 at root cpu0 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu0: cache L1-I 32KB 4 way D 8KB 64 way, L2 128KB 8 way cpu1 at mainbus0: CN50xx CPU rev 0.1 500 MHz, Software FP emulation cpu1: cache L1-I 32KB 4 way D 8KB 64 way, L2 128KB 8 way clock0 at mainbus0: int 5 iobus0 at mainbus0 simplebus0 at iobus0: "soc" octciu0 at simplebus0 cn30xxsmi0 at simplebus0 com0 at simplebus0: ns16550a, 64 byte fifo com0: console dwctwo0 at iobus0 base 0x118006800 irq 56 usb0 at dwctwo0: USB revision 2.0 uhub0 at usb0 configuration 1 interface 0 "Octeon DWC2 root hub" rev 2.00/1.00 addr 1 octrng0 at iobus0 base 0x14000 irq 0 cn30xxgmx0 at iobus0 base 0x118000800 cnmac0 at cn30xxgmx0: RGMII, address dc:9f:db:80:0f:39 atphy0 at cnmac0 phy 7: AR8035 10/100/1000 PHY, rev. 2 cnmac1 at cn30xxgmx0: RGMII, address dc:9f:db:80:0f:3a atphy1 at cnmac1 phy 6: AR8035 10/100/1000 PHY, rev. 2 cnmac2 at cn30xxgmx0: RGMII, address dc:9f:db:80:0f:3b atphy2 at cnmac2 phy 5: AR8035 10/100/1000 PHY, rev. 2 /dev/ksyms: Symbol table not valid. uhub1 at uhub0 port 1 configuration 1 interface 0 "Terminus Technology USB 2.0 Hub [Safe]" rev 2.00/1.11 addr 2 umass0 at uhub1 port 2 configuration 1 interface 0 "Verbatim STORE N GO" rev 2.00/11.00 addr 3 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI0 0/direct removable serial.18a50302103744VCIXG1 sd0: 7620MB, 512 bytes/sector, 15605760 sectors vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets boot device: sd0 root on sd0a (80bf465f2582c4de.a) swap on sd0b dump on sd0b WARNING: No TOD clock, believing file system. WARNING: CHECK AND RESET THE DATE! cpu1 launched umodem0 at uhub1 port 1 configuration 2 interface 1 "SAMSUNG SAMSUNG_Android" rev 2.00/4.00 addr 4 umodem0: data interface 2, has no CM over data, has no break umodem0: status change notification available ucom0 at umodem0 ugen0 at uhub1 port 1 configuration 2 "SAMSUNG SAMSUNG_Android" rev 2.00/4.00 addr 4 ucom0 detached umodem0 detached ugen0 detached urndis0 at uhub1 port 1 configuration 1 interface 0 "SAMSUNG SAMSUNG_Android" rev 2.00/ff.ff addr 4 urndis0: using RNDISurndis0: IOERROR urndis0: unable to get query response : unable to get hardware address urndis0 detached umodem0 at uhub1 port 1 configuration 2 interface 1 "SAMSUNG SAMSUNG_Android" rev 2.00/4.00 addr 4 umodem0: data interface 2, has no CM over data, has no break umodem0: status change notification available ucom0 at umodem0 ugen0 at uhub1 port 1 configuration 2 "SAMSUNG SAMSUNG_Android" rev 2.00/4.00 addr 4 ucom0 detached umodem0 detached ugen0 detached urndis0 at uhub1 port 1 configuration 1 interface 0 "SAMSUNG SAMSUNG_Android" rev 2.00/ff.ff addr 4 urndis0: using RNDISurndis0: IOERROR urndis0: unable to get query response : unable to get hardware address urndis0 detached
Re: run(4) driver kernel panic OBSD 6.0 amd64 on boot
On Fri, Aug 04, 2017 at 10:26:37PM +0100, Stuart Henderson wrote: > On 2017/08/04 23:05, Denis wrote: > > OpenBSD 6.0-stable (CUSTOM.MP) #8: Fri Mar 31 15:01:38 > > r...@root.name:/usr/src/sys/arch/amd64/compile/CUSTOM.MP > > That is still 6.0: > It's also some wacky "CUSTOM.MP" configuration. > > On 04.08.2017 15:07, Stefan Sperling wrote: > > > Please try -current. I will not look into bug reports for 6.0. > > > There are already too many bug reports I need to handle. > > ... >
Re: run(4) driver kernel panic OBSD 6.0 amd64 on boot
On 2017/08/04 23:05, Denis wrote: > OpenBSD 6.0-stable (CUSTOM.MP) #8: Fri Mar 31 15:01:38 > r...@root.name:/usr/src/sys/arch/amd64/compile/CUSTOM.MP That is still 6.0: > On 04.08.2017 15:07, Stefan Sperling wrote: > > Please try -current. I will not look into bug reports for 6.0. > > There are already too many bug reports I need to handle. ...
Re: run(4) driver kernel panic OBSD 6.0 amd64 on boot
OpenBSD 6.0-stable (CUSTOM.MP) #8: Fri Mar 31 15:01:38 r...@root.name:/usr/src/sys/arch/amd64/compile/CUSTOM.MP real mem = 2121138176 (2022MB) avail mem = 2055188480 (1959MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.2 @ 0xf0800 (39 entries) bios0: vendor Phoenix Technologies, LTD version "6.00 PG" acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP MCFG APIC acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5) PEX5(S5) HUB0 (S5) UAR1(S5) UAR2(S5) USB0(S1) USB1(S1) USB2(S1) USB3(S1) USBE(S1) AC97(S5) AZA L(S5) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2167.17 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM 2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2166.82 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM 2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEX0) acpiprt2 at acpi0: bus 2 (PEX1) acpiprt3 at acpi0: bus -1 (PEX2) acpiprt4 at acpi0: bus -1 (PEX3) acpiprt5 at acpi0: bus -1 (PEX4) acpiprt6 at acpi0: bus -1 (PEX5) acpiprt7 at acpi0: bus 3 (HUB0) acpicpu0 at acpi0: C1(@1 halt!) acpicpu1 at acpi0: C1(@1 halt!) acpibtn0 at acpi0: PWRB "PNP0501" at acpi0 not configured "PNP0501" at acpi0 not configured "PNP0501" at acpi0 not configured "PNP0501" at acpi0 not configured cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130d2206000d22 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 2167 MHz: speeds: 2167, 1000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03 inteldrm0 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03 drm0 at inteldrm0 intagp0 at inteldrm0 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0: apic 2 int 16 inteldrm0: 1920x1200 wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi pci1 at ppb0 bus 1 bge0 at pci1 dev 0 function 0 "Broadcom BCM5787M" rev 0x02, BCM5754/5787 A2 (0xb 002): msi, address 00:02:b6:42:ea:c0 brgphy0 at bge0 phy 1: BCM5787 10/100/1000baseT PHY, rev. 0 ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi pci2 at ppb1 bus 2 bge1 at pci2 dev 0 function 0 "Broadcom BCM5787M" rev 0x02, BCM5754/5787 A2 (0xb 002): msi, address 00:02:b6:42:ea:c1 brgphy1 at bge1 phy 1: BCM5787 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 2 int 23 uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 2 int 19 uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 2 int 18 uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 2 int 16 ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2 pci3 at ppb2 bus 3 auich0 at pci0 dev 30 function 2 "Intel 82801GB AC97" rev 0x02: apic 2 int 17, I CH7 AC97 ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0) audio0 at auich0 pcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02 pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA, channel 0 c onfigured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: <> wd0: 1-sector PIO, LBA, 3967MB, 8125488 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 pciide0: channel 1 ignored (disabled) pciide1 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x02: DMA, channel 0
Re: "pkg_info -Q" very slow
On Fri, Aug 04, 2017 at 11:12:01AM -0400, Michael Reed wrote:
> $ sysctl -n kern.version
> OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> -
>
> It looks like PkgInfo.pm revision 1.45 (discussed briefly in this[3] thread)
> made "pkg_info -Q" very slow:
>
> PkgInfo.pm 1.44 [1]
> $ for i in 1 2 3; do time pkg_info -Q xfce > /dev/null; done
> 0m01.78s real 0m00.58s user 0m00.13s system
> 0m01.51s real 0m00.46s user 0m00.11s system
> 0m01.41s real 0m00.42s user 0m00.06s system
>
> PkgInfo.pm 1.45 [2]
> $ for i in 1 2 3; do time pkg_info -Q xfce > /dev/null; done
> 0m45.10s real 0m03.08s user 0m03.30s system
> 0m44.07s real 0m02.57s user 0m03.11s system
> 0m41.49s real 0m03.15s user 0m03.72s system
>
> I don't know enough perl to debug this fully, but I thought I would at least
> bring this issue to the developers attention, assuming it's not already
> known :)
Thanks for bringing it to light!
Here is some profiling information for anyone interested:
https://deftly.net/pkg_info_trace/
Attached is a diff that only calls find_pkg when other flags that need
it are included in the options.
Index: OpenBSD/PkgInfo.pm
===
RCS file: /cvs/src/usr.sbin/pkg_add/OpenBSD/PkgInfo.pm,v
retrieving revision 1.45
diff -u -p -r1.45 PkgInfo.pm
--- OpenBSD/PkgInfo.pm 3 Aug 2017 13:08:58 - 1.45
+++ OpenBSD/PkgInfo.pm 4 Aug 2017 17:10:57 -
@@ -406,18 +406,13 @@ sub print_info
}
$state->say("#1", $compose);
} elsif ($state->opt('I')) {
- if ($state->opt('Q')) {
- $state->say(
- is_installed($pkg) ? "#1 (installed)" : "#1", $pkg);
+ if ($state->opt('q')) {
+ $state->say("#1", $pkg);
} else {
- if ($state->opt('q')) {
- $state->say("#1", $pkg);
- } else {
- my $l = 20 - length($pkg);
- $l = 1 if $l <= 0;
- $state->say("#1#2#3", $pkg, " "x$l,
- get_comment($handle->info));
- }
+ my $l = 20 - length($pkg);
+ $l = 1 if $l <= 0;
+ $state->say("#1#2#3", $pkg, " "x$l,
+ get_comment($handle->info));
}
} else {
if ($state->opt('c')) {
@@ -606,10 +601,15 @@ sub parse_and_run
my $r = $state->repo->match_locations($partial);
for my $p (sort map {$_->name} @$r) {
- $self->find_pkg($state, $p,
- sub {
- $self->print_info($state, @_);
- });
+ if ($state->hasanyopt('cdfMqs')) {
+ $self->find_pkg($state, $p,
+ sub {
+ $self->print_info($state, @_);
+ });
+ } else {
+ $state->say(
+ is_installed($p) ? "#1 (installed)" : "#1",
$p);
+ }
}
return 0;
>
>
> [1]:
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/pkg_add/OpenBSD/PkgInfo.pm?rev=1.44&content-type=text/x-cvsweb-markup
> [2]:
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/pkg_add/OpenBSD/PkgInfo.pm?rev=1.45&content-type=text/x-cvsweb-markup
> [3]: https://marc.info/?l=openbsd-tech&m=150134645310914&w=2
>
--
PGP: 0x1F81112D62A9ADCE / 3586 3350 BFEA C101 DB1A 4AF0 1F81 112D 62A9 ADCE
Re: [RPI3] TP-Link TL-WN821N V4 kernel panic
On Fri, Aug 04, 2017 at 01:09:53PM -0300, R0me0 *** wrote: > To ensure, one more time I removed again all /usr/obj/* > > Certified that diff is correct. What was little different now, was the > panic ( RUN-RUN ) so why I am posting again, may it helps in something. > > I will perform AMD64-Current tests today and will back with results I can reproduce the RUN->RUN panic on amd64. This might take some time to fix properly. I have removed the panics in -current just now. It will still print a warning to dmesg if an invalid transition happens and if 'ifconfig urtwn0 debug' was run. This means we can still find the bugs. If you run with 'ifconfig urtwn0 debug' you will still be notified and can report such issues. But it won't take down the entire box anymore. > Thank you so much for your attention and efforts. Thanks for taking the time to send reports.
Re: [RPI3] TP-Link TL-WN821N V4 kernel panic
To ensure, one more time I removed again all /usr/obj/* Certified that diff is correct. What was little different now, was the panic ( RUN-RUN ) so why I am posting again, may it helps in something. I will perform AMD64-Current tests today and will back with results Thank you so much for your attention and efforts. Bests, # *cd /sys/arch/$(machine)/compile/GENERIC* # *make obj* # *make config* # *make && make install* # *reboot* # sh /etc/netstart urtwn0 panic: invalid transition RUN -> RUN Stopped at panic+0x158:TIDPIDUID PRFLAGS PFLAGS C PU COMMAND *412518 74742 0 0x14000 0x2000 usbtask db_enter() at panic+0x154 panic() at rtwn_newstate+0x6c4 rtwn_newstate() at urtwn_task+0x5c urtwn_task() at usb_task_thread+0xe8 usb_task_thread() at proc_trampoline+0xc 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> show panic invalid transition RUN -> RUN
Thinkpad x200 headphone jack does not mute speakers
(please let me know if you do not want to be CC'd, Alexandre) My thinkpad x200, which runs libreboot (not sure if that's important), uses the azalia(4) audio driver: azalia0 at pci0 dev 27 function 0 "Intel 82801I HD Audio" rev 0x03: msi azalia0: codecs: Conexant CX20561 audio0 at azalia0 Here's the issue: run "cat /dev/random > /dev/audio" noise is now playing through laptop speakers plug headphones into headphone jack noise is now playing through laptop speakers AND headphones Expected behavior: run "cat /dev/random > /dev/audio" noise is now playing through laptop speakers plug headphones into headphone jack noise is now playing through headphones; speakers are muted - My azalia0 seems to have jack sensing support, as the mixer control outputs.hp_sense correctly shows whether headphones are plugged in, but for some reason it lacks the "outputs.spkr_muters" mixer control. Maybe the spkr_muters mixer control is not showing up because of a hardware quirk? I don't really know. As a workaround I disable speaker volume at all times via mixerctl.conf: # effectively disable speakers inputs.dac-2:3=0 # make XF86* audio hotkeys not affect volume of dac-2:3 (AKA speakers) outputs.master.slaves=dac-0:1 - $ sysctl -n kern.version OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP (these are my default mixer settings---I commented out mixerctl.conf and rebooted before running this command) $ mixerctl -f /dev/mixer0 inputs.dac-0:1=126,126 inputs.dac-2:3=126,126 inputs.beep=85 record.adc-2:3_source=mic2 record.adc-2:3=126,126 record.adc-0:1_source=mic record.adc-0:1=126,126 outputs.hp_source=dac-0:1 outputs.hp_boost=off inputs.mic=126,126 outputs.mic_dir=input-vr80 outputs.spkr_source=dac-2:3 outputs.spkr_eapd=on inputs.mic2=126,126 outputs.hp_sense=unplugged outputs.mic_sense=unplugged outputs.master=126,126 outputs.master.mute=off outputs.master.slaves=dac-0:1,dac-2:3 record.volume=126,126 record.volume.mute=off record.volume.slaves=adc-2:3,adc-0:1 $ audioctl -f /dev/audioctl0 name=azalia0 mode= pause=0 active=0 nblks=2 blksz=960 rate=48000 encoding=s16le play.channels=2 play.bytes=0 play.errors=0 record.channels=2 record.bytes=0 record.errors=0 dmesg: OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8299085824 (7914MB) avail mem = 8041775104 (7669MB) warning: no entropy supplied by boot loader mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbfaa0020 (8 entries) bios0: vendor coreboot version "CBET4000 370b885" date 09/07/2016 bios0: LENOVO 745432U acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT MCFG TCPA APIC DMAR HPET acpi0: wakeup devices HDEF(S4) USB1(S4) USB2(S4) USB3(S4) EHC1(S4) USB4(S4) USB5(S4) USB6(S4) EHC2(S4) SLT1(S4) SLT2(S4) SLT3(S4) SLT6(S4) LANC(S3) LANR(S3) SLPB(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU P8700 @ 2.53GHz, 1600.27 MHz cpu0: FPU,VME,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,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU P8700 @ 2.53GHz, 1600.06 MHz cpu1: FPU,VME,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,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEGP) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 4 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpiprt8 at acpi0: bus 5 (PCIB) acpiec0 at acpi0 acpicpu0 at acpi0 C1: bogo buffer C2: bogo buffer C3: bogo buffer: C1(@1 halt!), PSS acpicpu1 at acpi0 C1: bogo buffer C2: bogo buffer C3: bogo buffer: C1(@1 halt!), PSS acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 99 degC acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model "42T4696" serial 8527 type LION oem "Panasonic" acpibat1 at acpi0: BAT1 no
Re: [RPI3] TP-Link TL-WN821N V4 kernel panic
sh /etc/netstart urtwn0
panic: invalid transition AUTH -> RUN
Stopped at panic+0x158:TIDPIDUID PRFLAGS
PFLAGS C
PU COMMAND
*352180 67191 0 0x14000 0x2000 usbtask
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc
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> show panic
invalid transition AUTH -> RUN
ddb> trace
db_enter() at panic+0x154
panic() at rtwn_newstate+0x6c4
rtwn_newstate() at urtwn_task+0x5c
urtwn_task() at usb_task_thread+0xe8
usb_task_thread() at proc_trampoline+0xc
# diff -u /root/ieee80211_proto-orig.c ieee80211_proto.c
--- /root/ieee80211_proto-orig.cFri Aug 4 10:45:32 2017
+++ ieee80211_proto.c Fri Aug 4 10:05:29 2017
@@ -1022,11 +1022,11 @@
switch (ostate) {
case IEEE80211_S_INIT:
case IEEE80211_S_SCAN:
- case IEEE80211_S_ASSOC:
panic("invalid transition %s -> %s",
ieee80211_state_name[ostate],
ieee80211_state_name[nstate]);
break;
+ case IEEE80211_S_ASSOC:
case IEEE80211_S_AUTH:
IEEE80211_SEND_MGMT(ic, ni,
IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
2017-08-03 16:13 GMT-03:00 Stefan Sperling :
> On Thu, Aug 03, 2017 at 03:20:13PM -0300, R0me0 *** wrote:
> > Yes, all on raspberry
> >
> > Stefan, I can setup VM and test amd64. Current or 6.1-stable?
> >
> > To ensure I didn't a mess follow the diff:
> >
> > diff -u ieee80211_proto-orig.c /usr/src/sys/net80211/ieee80211_proto.c
>
> This diff is incorrect, it deletes way too many lines.
>
> > --- ieee80211_proto-orig.c Thu Aug 3 13:38:26 2017
> > +++ /usr/src/sys/net80211/ieee80211_proto.c Thu Aug 3 13:10:45 2017
> > @@ -1023,10 +1023,6 @@
> >case IEEE80211_S_INIT:
> >case IEEE80211_S_SCAN:
> >case IEEE80211_S_ASSOC:
> > - panic("invalid transition %s -> %s",
> > - ieee80211_state_name[ostate],
> > - ieee80211_state_name[nstate]);
> > - break;
> >case IEEE80211_S_AUTH:
> >IEEE80211_SEND_MGMT(ic, ni,
> >IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
>
> Here is my diff again (move just the "IEEE80211_S_ASSOC" line down).
>
> Index: ieee80211_proto.c
> ===
> RCS file: /cvs/src/sys/net80211/ieee80211_proto.c,v
> retrieving revision 1.78
> diff -u -p -r1.78 ieee80211_proto.c
> --- ieee80211_proto.c 22 Jul 2017 16:54:46 - 1.78
> +++ ieee80211_proto.c 28 Jul 2017 09:05:55 -
> @@ -1022,11 +1022,11 @@ justcleanup:
> switch (ostate) {
> case IEEE80211_S_INIT:
> case IEEE80211_S_SCAN:
> - case IEEE80211_S_ASSOC:
> panic("invalid transition %s -> %s",
> ieee80211_state_name[ostate],
> ieee80211_state_name[nstate]);
> break;
> + case IEEE80211_S_ASSOC:
> case IEEE80211_S_AUTH:
> IEEE80211_SEND_MGMT(ic, ni,
> IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
>
>
"pkg_info -Q" very slow
$ sysctl -n kern.version OpenBSD 6.1-current (GENERIC.MP) #44: Thu Aug 3 12:12:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP - It looks like PkgInfo.pm revision 1.45 (discussed briefly in this[3] thread) made "pkg_info -Q" very slow: PkgInfo.pm 1.44 [1] $ for i in 1 2 3; do time pkg_info -Q xfce > /dev/null; done 0m01.78s real 0m00.58s user 0m00.13s system 0m01.51s real 0m00.46s user 0m00.11s system 0m01.41s real 0m00.42s user 0m00.06s system PkgInfo.pm 1.45 [2] $ for i in 1 2 3; do time pkg_info -Q xfce > /dev/null; done 0m45.10s real 0m03.08s user 0m03.30s system 0m44.07s real 0m02.57s user 0m03.11s system 0m41.49s real 0m03.15s user 0m03.72s system I don't know enough perl to debug this fully, but I thought I would at least bring this issue to the developers attention, assuming it's not already known :) [1]: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/pkg_add/OpenBSD/PkgInfo.pm?rev=1.44&content-type=text/x-cvsweb-markup [2]: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/pkg_add/OpenBSD/PkgInfo.pm?rev=1.45&content-type=text/x-cvsweb-markup [3]: https://marc.info/?l=openbsd-tech&m=150134645310914&w=2
Re: run(4) driver kernel panic OBSD 6.0 amd64 on boot
On Fri, Aug 04, 2017 at 02:57:46PM +0300, Denis wrote: > Trying to attach run(4) supported usb adapter to OpenBSD 6.0 amd 64 Please try -current. I will not look into bug reports for 6.0. There are already too many bug reports I need to handle. > During boot I see the message from kernel (not always, boot after boot): We need a full dmesg as well for bug reports please. > -- > panic: attempt to execute user address 0x0 in supervisor mode > Starting stack trace... > panic() at panic+0x10b > trap() at trap+0x7dd > --- trap (number 6) --- > param.c() at 0 > usb_task_thread() at usb_task_thread+0xb6 > end trace frame: 0x0, count: 253 > End of stack trace. > syncing disks... 9 8 done > sd detached > > --- > > > >
run(4) driver kernel panic OBSD 6.0 amd64 on boot
Trying to attach run(4) supported usb adapter to OpenBSD 6.0 amd 64 During boot I see the message from kernel (not always, boot after boot): -- panic: attempt to execute user address 0x0 in supervisor mode Starting stack trace... panic() at panic+0x10b trap() at trap+0x7dd --- trap (number 6) --- param.c() at 0 usb_task_thread() at usb_task_thread+0xb6 end trace frame: 0x0, count: 253 End of stack trace. syncing disks... 9 8 done sd detached ---
Re: apu2 gateway crashed upon reboot
On 4 August 2017 at 13:05, Jesper Wallin wrote:
>
> On Fri, Aug 04, 2017 at 10:47:31AM +0100, Stuart Henderson wrote:
> > To clarify: you ran syspatch, and after fetching the patches (but still
> > on the old kernel) you attempted to reboot, and it stopped responding
> > at that point - is that correct?
>
> Correct. I applied all patches and attempted to reboot into the new
> kernel.
>
> > Which kernel was it running previously?
>
> OpenBSD 6.1 (GENERIC.MP) #8: Tue Jun 27 08:50:26 CEST 2017
>
> > If it happens again, post the panic message - if you don't have
> > anything logging the serial at the time you can repeat it with "show
> > panic". Also the process listing ("ps" in DDB) - this occurred when
> > a process was exiting and it would be useful to know which one.
>
> Yeah, the plan was of course to run the ddb commands suggested on
> https://www.openbsd.org/ddb.html, but I was unable to after it froze.
>
> My bad for not starting with "show panic" though. Taking notes. :-)
>
> > Information about config of the machine might help too. Which PF
> > features are you using? Any source tracking? What daemons are you
> > using? (ftp-proxy? relayd? etc.)
>
> The machine acts as our gateway running the default daemons plus
> unbound, dhcpd, relayd and sshd. PF is using nat, rdr-to, normalization,
> queueing (both queue and prio) and keep/modulate state. I have added
> pf.conf.txt, relayd.conf.txt and ifconfig.txt to the directory
> previously linked.
>
Another thing to try would be this change that didn't make it to stable.
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf.c.diff?r1=1.1034&r2=1.1035
Re: apu2 gateway crashed upon reboot
On Fri, Aug 04, 2017 at 10:47:31AM +0100, Stuart Henderson wrote:
> To clarify: you ran syspatch, and after fetching the patches (but still
> on the old kernel) you attempted to reboot, and it stopped responding
> at that point - is that correct?
Correct. I applied all patches and attempted to reboot into the new
kernel.
> Which kernel was it running previously?
OpenBSD 6.1 (GENERIC.MP) #8: Tue Jun 27 08:50:26 CEST 2017
> If it happens again, post the panic message - if you don't have
> anything logging the serial at the time you can repeat it with "show
> panic". Also the process listing ("ps" in DDB) - this occurred when
> a process was exiting and it would be useful to know which one.
Yeah, the plan was of course to run the ddb commands suggested on
https://www.openbsd.org/ddb.html, but I was unable to after it froze.
My bad for not starting with "show panic" though. Taking notes. :-)
> Information about config of the machine might help too. Which PF
> features are you using? Any source tracking? What daemons are you
> using? (ftp-proxy? relayd? etc.)
The machine acts as our gateway running the default daemons plus
unbound, dhcpd, relayd and sshd. PF is using nat, rdr-to, normalization,
queueing (both queue and prio) and keep/modulate state. I have added
pf.conf.txt, relayd.conf.txt and ifconfig.txt to the directory
previously linked.
Re: apu2 gateway crashed upon reboot
On 2017/08/04 09:06, Jesper Wallin wrote:
> After applying the latest errata patches for 6.1 yesterday (logged
> on via ssh), I rebooted our apu2 acting as a gateway. The machine
> stopped responding (the ssh session hung) and this morning I logged
> on via serial console to learn it was stuck at the ddb{3} prompt.
To clarify: you ran syspatch, and after fetching the patches (but still
on the old kernel) you attempted to reboot, and it stopped responding
at that point - is that correct?
Which kernel was it running previously? If you're not sure, "zgrep OpenBSD
/var/log/messages*" might still have the kernel timestamp from when it booted.
Here's a list of kernels from syspatch to match up.
61-002_vmmfpu: OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT
2017
61-004_softraid_concat: OpenBSD 6.1 (GENERIC.MP) #1: Tue May 2 10:47:59 CEST
2017
61-005_pf_src_tracking: OpenBSD 6.1 (GENERIC.MP) #2: Tue May 2 12:58:57 CEST
2017
61-008_exec_subr: OpenBSD 6.1 (GENERIC.MP) #4: Sat May 6 09:33:37 CEST
2017
61-009_icmp_opts: OpenBSD 6.1 (GENERIC.MP) #5: Thu May 18 22:22:32 CEST
2017
61-012_wsmux: OpenBSD 6.1 (GENERIC.MP) #6: Mon May 22 20:34:30 CEST
2017
61-013_icmp6_linklocal: OpenBSD 6.1 (GENERIC.MP) #7: Mon Jun 12 20:41:01 CEST
2017
61-015_sigio: OpenBSD 6.1 (GENERIC.MP) #8: Tue Jun 27 08:50:26 CEST
2017
61-016_sendsyslog: OpenBSD 6.1 (GENERIC.MP) #9: Thu Aug 3 12:03:39 CEST
2017
61-017_fuse:OpenBSD 6.1 (GENERIC.MP) #10: Thu Aug 3 12:24:00 CEST
2017
61-018_recv:OpenBSD 6.1 (GENERIC.MP) #11: Thu Aug 3 12:36:28 CEST
2017
61-019_tcp_usrreq: OpenBSD 6.1 (GENERIC.MP) #12: Thu Aug 3 12:50:41 CEST
2017
61-020_sockaddr:OpenBSD 6.1 (GENERIC.MP) #13: Thu Aug 3 13:08:51 CEST
2017
61-021_ptrace: OpenBSD 6.1 (GENERIC.MP) #14: Thu Aug 3 13:27:01 CEST
2017
61-022_fcntl: OpenBSD 6.1 (GENERIC.MP) #15: Thu Aug 3 13:45:26 CEST
2017
61-023_wsdisplay: OpenBSD 6.1 (GENERIC.MP) #16: Thu Aug 3 14:04:03 CEST
2017
61-024_sosplice:OpenBSD 6.1 (GENERIC.MP) #17: Thu Aug 3 14:22:19 CEST
2017
61-025_ieee80211: OpenBSD 6.1 (GENERIC.MP) #18: Thu Aug 3 14:40:44 CEST
2017
If it happens again, post the panic message - if you don't have
anything logging the serial at the time you can repeat it with "show
panic". Also the process listing ("ps" in DDB) - this occurred when
a process was exiting and it would be useful to know which one.
Information about config of the machine might help too. Which PF
features are you using? Any source tracking? What daemons are you
using? (ftp-proxy? relayd? etc.)
Re: asus x205ta keyboard issue
On Thu, Aug 03, 2017 at 08:20:24PM -0400, Ted Unangst wrote: > michele.cu...@gmail.com wrote: > > >Synopsis: iic keyboard sometimes reapeat key press > > When the problem happens, on dmesg I see messages like this: > > > > dwiic1: timed out reading remaining 13 > > > > Any idea what's happening? > > keyboard controllers are surprisingly complex. or perhaps quirky is a better > word. it took 20 years to get the pckbd driver working. and now we get to > start all over with iic controllers. > > that's kind of a meta point, but the idea is until such machines become > common, there's probably going to be a few issues. Got it, thank you ;) Have a nice day, Michele
apu2 gateway crashed upon reboot
After applying the latest errata patches for 6.1 yesterday (logged
on via ssh), I rebooted our apu2 acting as a gateway. The machine
stopped responding (the ssh session hung) and this morning I logged
on via serial console to learn it was stuck at the ddb{3} prompt.
I ran a 'trace' and copied the output, as well as a 'mach ddbcpu 0'.
--8<--
ddb{3}> trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
pf_state_key_unref() at pf_state_key_unref+0xc6
pf_pkt_unlink_state_key() at pf_pkt_unlink_state_key+0x15
m_free() at m_free+0xc0
sbdrop() at sbdrop+0x80
sbflush() at sbflush+0x1f
sbrelease() at sbrelease+0x11
sorflush() at sorflush+0x158
sofree() at sofree+0xa7
soclose() at soclose+0x8d
soo_close() at soo_close+0x1c
fdrop() at fdrop+0x2c
closef() at closef+0xcb
fdfree() at fdfree+0x60
exit1() at exit1+0x2e3
sys_exit() at sys_exit+0x17
syscall() at syscall+0x27b
--- syscall (number 1) ---
end trace frame: 0x0, count: -19
0x1ef09408d58a:
ddb{3}> mach ddbcpu 0
Stopped at Debugger+0x9: leave
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1c
--- interrupt ---
__mp_lock() at __mp_lock+0x42
softintr_dispatch() at softintr_dispatch+0x43
Xsoftclock() at Xsoftclock+0x1f
--- interrupt ---
acpi_s3_vector_real() at 0x8
end() at 0x
-->8--
The 'mach ddbcpu 0' never finished and the machine stopped responding
altogether. Had to kill the power and reboot it.
The output from above and things like dmesg and such can be found at
https://ifconfig.se/panic/
I'm not sure if this is of any use but I thought I'd report it anyway.
Sorry if I'm wasting anyones time.
