On Fri, 26 Feb 2016, Radosław Warowny wrote:
> > I agree, but where was a crash? I don't have any context here, was
> > there a kernel oops somewhere? I thought the hub just reset itself. I
> > have a hub like that here, it resets itself a few times a day, but
> > there's no kernel crash becaus
> I agree, but where was a crash? I don't have any context here, was
> there a kernel oops somewhere? I thought the hub just reset itself. I
> have a hub like that here, it resets itself a few times a day, but
> there's no kernel crash because of it.
Yes, there were kernel oopses, you can find
On Tue, Feb 23, 2016 at 07:40:15PM +0100, Radosław Warowny wrote:
> > In the future, please include the information in the email, so that
> > people don't have to dig it out from a web site.
>
> Thanks for suggestion
>
> > Use a better cable, nothing we can do about broken hardware, sorry :)
>
>
> In the future, please include the information in the email, so that
> people don't have to dig it out from a web site.
Thanks for suggestion
> Use a better cable, nothing we can do about broken hardware, sorry :)
Maybe we can do something Linux to survive without crashing
all the system. It se
On Thu, Feb 11, 2016 at 10:44:10PM +0100, Radosław Warowny wrote:
> Hi,
>
> I reported the following bug report:
> https://bugzilla.kernel.org/show_bug.cgi?id=112311
In the future, please include the information in the email, so that
people don't have to dig it out from a web site.
> Maybe some
