> > > > > > I glanced at the bugs and I can only see the trace dump. I am > > > > > > pretty sure there is an issue before the dump - fw assert of > > > > > > something like that. Can it be possible to get the full log? > > > > > > > > > > > > > > > > Can you ask people to try the attached patch? > > > > > This will let us know where the fw is brought down. > > > > > > > > Yes, I'll build kernel with that patch and request for test and dmesg. > > > > > > debug=0x400 is enough or do you want also some other flags? > > > > > 0x400 should be enough, but 0x403 would be better :-) > > > There is some feedback from user with micocode errors here > https://bugzilla.redhat.com/show_bug.cgi?id=866013 > Ok, this is what I suspected. SYSASSERT before the WARNING.... So we have 2 issues here - the SYSASSERT and the reset. BTW - do we have any insight on the NIC used - although I am pretty sure it doesn't matter much. > Emmanuel, perhaps you could CC to those bug report I provided links earlier, > so I'll not need to mail you, when someone will add additional info to those > reports ? > I will check :-) > Thanks > Stanislaw --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- 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
