Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Martin Pieuchot
Hello Denis,

On 25/01/18(Thu) 17:16, Denis wrote:
> Finally catch kernel panic in the middle of run adapter work.

Could you please set ddb.panic to 1?

It's hard to figure out what's wrong in your reports because as soon as
your machine tries to reboot it panics, panics and panics again.  So we
can't tell what is the first (real) problem.

And please stop cross posting.  bugs@ is enough for such problems :)

Thanks,
Martin

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Denis Lapshin-2
Hello Martin,

Thank you for your attention to the problem with run driver.

Here is DDB output.
.
.. dmesg
starting network
panic: attempt to execute user address 0x0 in supervisor mode
Stopped at     db_enter+0x5    popq    %rbp
TID    PID    UID    PRFLAGS    PFLAGS    CPU    COMMAND
*374840    4608    0    0x14000    0x20    1    usbtask
db_enter() at db_enter+0x5
panic() at panic+0x128
trap() at trap+0x6ac
--- trap (number 6) ---
(null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
usb_task_thread(0) at usb_task_thread+0xd8
end trace frame: 0x0, count: 10

ddb{1} trace
db_enter() at db_enter+0x5
panic() at panic+0x128
trap() at trap+0x6ac
--- trap (number 6) ---
(null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
usb_task_thread(0) at usb_task_thread+0xd8
end trace frame: 0x0, count: -5

Denis


On 1/25/2018 5:34 PM, Martin Pieuchot wrote:

> Hello Denis,
>
> On 25/01/18(Thu) 17:16, Denis wrote:
>> Finally catch kernel panic in the middle of run adapter work.
> Could you please set ddb.panic to 1?
>
> It's hard to figure out what's wrong in your reports because as soon as
> your machine tries to reboot it panics, panics and panics again.  So we
> can't tell what is the first (real) problem.
>
> And please stop cross posting.  bugs@ is enough for such problems :)
>
> Thanks,
> Martin
>

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Denis Lapshin-2
In reply to this post by Martin Pieuchot
Catch the second one kernel panic.

The output is the same, but on another kernel.  Hope this helps.

... dmesg
starting network
panic: attempt to execute user address 0x0 in supervisor mode
Stopped at     db_enter+0x5    popq    %rbp
TID    PID    UID    PRFLAGS    PFLAGS    CPU    COMMAND
*123456    1234    0    0x14000    0x200    3    usbtask
...

Denis

On 1/25/2018 5:34 PM, Martin Pieuchot wrote:

> Hello Denis,
>
> On 25/01/18(Thu) 17:16, Denis wrote:
>> Finally catch kernel panic in the middle of run adapter work.
> Could you please set ddb.panic to 1?
>
> It's hard to figure out what's wrong in your reports because as soon as
> your machine tries to reboot it panics, panics and panics again.  So we
> can't tell what is the first (real) problem.
>
> And please stop cross posting.  bugs@ is enough for such problems :)
>
> Thanks,
> Martin
>

--
mailto: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Martin Pieuchot
In reply to this post by Denis Lapshin-2
Hello Denis,

On 27/01/18(Sat) 12:38, Denis wrote:
> Hello Martin,
>
> Thank you for your attention to the problem with run driver.
>
> Here is DDB output.

Sorry but can you give more context?  How does this happen, why do
you need to do?  What is the output of 'ps', what is your dmesg?  What
is your hostname.runX ?

See https://www.openbsd.org/report.html for more informations about how
to report a problem.

> .. dmesg
> starting network
> panic: attempt to execute user address 0x0 in supervisor mode
> Stopped at     db_enter+0x5    popq    %rbp
> TID    PID    UID    PRFLAGS    PFLAGS    CPU    COMMAND
> *374840    4608    0    0x14000    0x20    1    usbtask
> db_enter() at db_enter+0x5
> panic() at panic+0x128
> trap() at trap+0x6ac
> --- trap (number 6) ---
> (null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
> usb_task_thread(0) at usb_task_thread+0xd8
> end trace frame: 0x0, count: 10
>
> ddb{1} trace
> db_enter() at db_enter+0x5
> panic() at panic+0x128
> trap() at trap+0x6ac
> --- trap (number 6) ---
> (null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
> usb_task_thread(0) at usb_task_thread+0xd8
> end trace frame: 0x0, count: -5
>
> Denis
>
>
> On 1/25/2018 5:34 PM, Martin Pieuchot wrote:
> > Hello Denis,
> >
> > On 25/01/18(Thu) 17:16, Denis wrote:
> >> Finally catch kernel panic in the middle of run adapter work.
> > Could you please set ddb.panic to 1?
> >
> > It's hard to figure out what's wrong in your reports because as soon as
> > your machine tries to reboot it panics, panics and panics again.  So we
> > can't tell what is the first (real) problem.
> >
> > And please stop cross posting.  bugs@ is enough for such problems :)
> >
> > Thanks,
> > Martin
> >
>

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Martin Pieuchot
In reply to this post by Denis Lapshin-2
On 28/01/18(Sun) 19:38, Denis wrote:
> Catch the second one kernel panic.
>
> The output is the same, but on another kernel.  Hope this helps.

Sadly it doesn't.  It only creates frustration from both sides.  Please
see https://www.openbsd.org/report.html .

Reply | Threaded
Open this post in threaded view
|

Re: Kernel Panic on 6.2 amd64 when run0 RT3070 based device is attached during boot

Denis Lapshin-2
In reply to this post by Martin Pieuchot
Hello Martin,

Please let me know if need more information about machine and test
conditions.

$cat /etc/hostname.run0

dhcp lladdr xa:xb:xc:xx:xy:xz bssid ya:yb:yc:yx:yy:yz nwid <BSSID> wpa
wpakey <KEY> wpaprotos wpa2

I've copied the explanation from my previous post.

"From time to time I receive Kernel Panic on OpenBSD 6.2 amd64 when run0
driver for RT3070 based device is attached to the Lenovo X220 laptop
during boot.
It appears just after file system is mounted. Next boot I receive that
file system was not properly unmounted.
But after FS checking is completed the same run0 device usually works as
expected.  

The same thing when I connected RT3070 device to the fully booted
OpenBSD6.2 amd64. Three times out of ten I got kernel panic issue.

I have tested two RT3070 adapters on other systems. Both works smoothly.
But on 6.2 amd64 each of them produces panic issue with the same
probability."

Here is DDB output.
.
.. dmesg
starting network
panic: attempt to execute user address 0x0 in supervisor mode
Stopped at     db_enter+0x5    popq    %rbp
TID    PID    UID    PRFLAGS    PFLAGS    CPU    COMMAND
*374840    4608    0    0x14000    0x20    1    usbtask
db_enter() at db_enter+0x5
panic() at panic+0x128
trap() at trap+0x6ac
--- trap (number 6) ---
(null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
usb_task_thread(0) at usb_task_thread+0xd8
end trace frame: 0x0, count: 10

ddb{1} trace
db_enter() at db_enter+0x5
panic() at panic+0x128
trap() at trap+0x6ac
--- trap (number 6) ---
(null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
usb_task_thread(0) at usb_task_thread+0xd8
end trace frame: 0x0, count: -5

dmesg was copied from my previous messages too.

OpenBSD 6.2 (GENERIC.MP) #1: Thu Jan 18 11:09:28 UTC 2018
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8451125248 (8059MB)
avail mem = 8192278528 (7812MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
bios0: vendor LENOVO version "8DET72WW (1.42 )" date 02/18/2016
bios0: LENOVO 5491C51
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF!
TCPA SSDT SSDT DMAR UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4)
EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2791.33 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2791332320 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.93 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.93 MHz
cpu2:
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2790.93 MHz
cpu3:
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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus 5 (EXP4)
acpiprt5 at acpi0: bus 13 (EXP5)
acpiprt6 at acpi0: bus 14 (EXP7)
acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2
acpitz0 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0020" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "45N1172" serial 14231 type LION oem "SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"IBM0079" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpidock0 at acpi0: GDCK docked (15)
acpivideo0 at acpi0: VID_
acpivout at acpivideo0 not configured
acpivideo1 at acpi0: VID_
cpu0: Enhanced SpeedStep 2791 MHz: speeds: 2801, 2800, 2600, 2400, 2200,
2000, 1800, 1600, 1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address
f0:de:f1:d1:9d:19
ehci0 at pci0 dev 26 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 6 Series HD Audio" rev 0x04: msi
azalia0: codecs: Conexant CX20590, Intel/0x2805, using Conexant CX20590
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 6 Series PCIE" rev 0xb4: msi
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 1 "Intel 6 Series PCIE" rev 0xb4: msi
pci2 at ppb1 bus 3
athn0 at pci2 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2 int 17
athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 70:xx:xx:xx:xx:xx
ppb2 at pci0 dev 28 function 3 "Intel 6 Series PCIE" rev 0xb4: msi
pci3 at ppb2 bus 5
ppb3 at pci0 dev 28 function 4 "Intel 6 Series PCIE" rev 0xb4: msi
pci4 at ppb3 bus 13
sdhc0 at pci4 dev 0 function 0 "Ricoh 5U822 SD/MMC" rev 0x07: apic 2 int 16
sdhc0: SDHC 3.0, 50 MHz base clock
sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma
ppb4 at pci0 dev 28 function 6 "Intel 6 Series PCIE" rev 0xb4: msi
pci5 at ppb4 bus 14
xhci0 at pci5 dev 0 function 0 "NEC xHCI" rev 0x04: msi
usb1 at xhci0: USB revision 3.0
uhub1 at usb1 configuration 1 interface 0 "NEC xHCI root hub" rev
3.00/1.00 addr 1
ehci1 at pci0 dev 29 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel QM67 LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 6 Series AHCI" rev 0x04: msi,
AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, ST750LX003, 0002> SCSI3 0/direct fixed
sd0: 698940MB, 512 bytes/sector, 1356773168 sectors
ichiic0 at pci0 dev 31 function 3 "Intel 6 Series SMBus" rev 0x04: apic
2 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
spdmem1 at iic0 addr 0x51: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x940300
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
aps0 at isa0 port 0x1600/31
vmm0 at mainbus0: VMX/EPT
uhub3 at uhub0 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.00 addr 2
uhub4 at uhub3 port 1 configuration 1 interface 0 "Standard
Microsystems" rev 2.00/0.00 addr 3
run0 at uhub4 port 2 configuration 1 interface 0 "Ralink 3070" rev
2.00/1.01 addr 4
run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address
40:a5:ef:01:af:13
uhub5 at uhub2 port 1 configuration 1 interface 0 "Intel Rate Matching
Hub" rev 2.00/0.00 addr 2
ugen0 at uhub5 port 6 "OMNIKEY" rev 2.00/2.03 addr 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
softraid0: sd1 was not shutdown properly
sd1 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed
...


On 1/28/2018 7:46 PM, Martin Pieuchot wrote:

> Hello Denis,
>
> On 27/01/18(Sat) 12:38, Denis wrote:
>> Hello Martin,
>>
>> Thank you for your attention to the problem with run driver.
>>
>> Here is DDB output.
> Sorry but can you give more context?  How does this happen, why do
> you need to do?  What is the output of 'ps', what is your dmesg?  What
> is your hostname.runX ?
>
> See https://www.openbsd.org/report.html for more informations about how
> to report a problem.
>
>> .. dmesg
>> starting network
>> panic: attempt to execute user address 0x0 in supervisor mode
>> Stopped at     db_enter+0x5    popq    %rbp
>> TID    PID    UID    PRFLAGS    PFLAGS    CPU    COMMAND
>> *374840    4608    0    0x14000    0x20    1    usbtask
>> db_enter() at db_enter+0x5
>> panic() at panic+0x128
>> trap() at trap+0x6ac
>> --- trap (number 6) ---
>> (null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
>> usb_task_thread(0) at usb_task_thread+0xd8
>> end trace frame: 0x0, count: 10
>>
>> ddb{1} trace
>> db_enter() at db_enter+0x5
>> panic() at panic+0x128
>> trap() at trap+0x6ac
>> --- trap (number 6) ---
>> (null) (0,0,ffff80000025c508,5,ffffffff814c8e8d,ffff800032dc1180) at 0
>> usb_task_thread(0) at usb_task_thread+0xd8
>> end trace frame: 0x0, count: -5
>>
>> Denis
>>
>>
>> On 1/25/2018 5:34 PM, Martin Pieuchot wrote:
>>> Hello Denis,
>>>
>>> On 25/01/18(Thu) 17:16, Denis wrote:
>>>> Finally catch kernel panic in the middle of run adapter work.
>>> Could you please set ddb.panic to 1?
>>>
>>> It's hard to figure out what's wrong in your reports because as soon as
>>> your machine tries to reboot it panics, panics and panics again.  So we
>>> can't tell what is the first (real) problem.
>>>
>>> And please stop cross posting.  bugs@ is enough for such problems :)
>>>
>>> Thanks,
>>> Martin
>>>

--
mailto: [hidden email]