Larry, Currently I'm struggling trying to reproduce the panic again.. Unfortunately it is working without problems now.. When it happened to you, was the RTL8187SE associated to any AP ? was there network traffic flowing ? Do you have done some other test ? do you have had more panics ? Any more information about that panic is really welcome.. Jumping back to your older mail, about your note on compile warning of rtl8187 driver, I have verified that In rtl8187 reference sources I have, the register is really accessed as 8 bit wide, while in the rtl8187se reference code (staging linux driver indeed) it is accessed in 16 bit way. I don't have a big endian system me too to test if uniforming to 16bit brokes thing, but: Despite I suspect the two ASIC have the same MAC and the same AFE, and that one of the two reference code is wrong, I can't know which one, so I'm thinking about keeping the common register struct as it is, and avoiding modify the rtl8187 driver about this, while eventually I will stick to the 16 bit access on the rtl8187se using a raw cast.. Better ideas are welcome :) Thanks Andrea Thank you Andrea On Wed, Jan 15, 2014 at 5:11 PM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote: > Andrea, > > Just a head's up, but I had a kernel panic overnight. This kernel (3.13-rc7 > from wireless testing) has been stable - the only thing new is the > RTL8187SE. I have no diagnostic information other than the blinking console > lights. If/when I get more info, I'll let you know. > > Larry > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
