On 05/11/2012 08:02 PM, Greg KH wrote:
On Fri, May 11, 2012 at 06:19:39PM +0200, Oncaphillis wrote:
On 05/11/2012 04:51 PM, Greg KH wrote:
On Fri, May 11, 2012 at 10:24:52AM -0400, Alan Stern wrote:
On Fri, 11 May 2012, Oncaphillis wrote:
hallo,
I'm developing a hardware application based on theEZ-USB SX2 Chip
>from Cypress using libusb-1.0.8 and I see kernel crashes like:
<snip>
May 03 19:11:59 [kernel] Pid: 3998, comm: Engine25DeviceP Tainted:
P 2.6.38.2+ #1 To be filled by O.E.M. To be fil
Is it possible for you to reproduce this using a 3.3.y or 3.4-rc
kernel?
And for you to try this on a machine without a closed source kernel
module, and a valid BIOS?
Sorry I was horrible unclear. The original Error line came from an
2.6.38+ kernel, but we see the same error on 3.3.4. The Poison
messages are form an untained 3.3.4 kernel.
No, it looks like the error message you showed came from a 2.6.38.2
kernel, plus unknown modifications.
What do you mean with valid BIOS ? Anything you see in the debug messages ?
Look at the "To be filled by O.E.M. To be fil" line above. That shows
you are running on some strange hardware, right?
I actually don't know how strange it is. Its and Advaantech industrial
PC. I'm currently debugging it remotely, so I don't want to risk to
brick it.
Can you show the full error you get on 3.3.4 please?
The real crash realy happens very seldom. I was happy that I could
identify the SLUG Poisoning stuff. We also see sporadic losses of bytes
transfered from the peripheral.
Have you tested 3.4-rc6 or later?
No -- not yet
Would it be helpfull to give you the SLUP/Poisining output for a 3.4-rc6
Anything else what could be helpfull ?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
