On Wed, Dec 23, 2015 at 7:10 PM, Kevin O'Connor <kevin@koconnor.net> wrote:

On Wed, Dec 23, 2015 at 07:02:37PM +0100, Tobias Diedrich wrote:
> Wcall16 with invalid stack: eax=dfbf3e62 edx=0 func=0x000f9563 esp=dfbf3e50
>
> .text._farcall16 0x9563 : { *(.text._farcall16) }
>

Can you include the full log? It looks like the code tried to call a
16bit function while in a "thread", and I need to figure out which
thread did that.

From the esp address it looks like it'sin the USB probe for the MSC device (full log attached):

/dfc02000\ Start thread func=dfc135f1

|dfc02000| set_address 0xdfc0a200

|dfc02000| config_usb: 0xdfc0a0d0

|dfc02000| device rev=0210 cls=00 sub=00 proto=00 size=64

|dfc02000| Searching bootorder for: /pci@i0cf8/usb@12,2/storage@5/*@0/*@0,0

|dfc02000| Searching bootorder for: /pci@i0cf8/usb@12,2/usb-*@5

|dfc02000| USB MSC vendor='WD' product='Elements 10B8' rev='1012' type=0 removable=0

Wcall16 with invalid stack: eax=dfc02e66 edx=0 func=0x000f91f0 esp=dfc02e54 ret=0x000f0604