On Sat, Nov 10, 2012 at 08:37:58PM -0500, Alan Stern wrote:
> On Sat, 10 Nov 2012 starlight.201...@binnacle.cx wrote:
>
> > Hello,
> >
> > I'm wondering how long it will be before this
> > patch appears in a 3.6.x release. Any idea?
>
> Probably a week or two. It's up to Greg KH.
As it's real
Just started a copies of /dev/urandom
to the new drive mirror pairs (in preparation
for crypt'ing them). This will take four
days so I can't touch the system for a
week now. No hurry on a 3.6 patch if
you were contemplating one. Maybe 3.7
will be out by then anyway.
>At 08:37 PM 11/10/2012 -05
At 08:37 PM 11/10/2012 -0500, Alan Stern wrote:
>Does the patch fix the problem?
Morning and coffee motivated an attempt
to build a kernel and try the patch.
However it fails to apply for 3.6.6
--even caffine is not enough to inspire
me to consider a -rc for production.
Any chance for a 3.6 patc
At 08:37 PM 11/10/2012 -0500, Alan Stern wrote:
>Does the patch fix the problem?
Will let you and the list know. Want
to wait for a full kernel release.
The drives go active if the power to
the docks is toggled after they spin
up--going with that for now.
Will finish configuring the array
and o
On Sat, 10 Nov 2012 starlight.201...@binnacle.cx wrote:
> Hello,
>
> I'm wondering how long it will be before this
> patch appears in a 3.6.x release. Any idea?
Probably a week or two. It's up to Greg KH.
> Any opinion on whether a 3.4.x or 3.2.x kernel
> would be better than 3.6.x for a prod
Hello,
I'm wondering how long it will be before this
patch appears in a 3.6.x release. Any idea?
Any opinion on whether a 3.4.x or 3.2.x kernel
would be better than 3.6.x for a production
network backup system (i.e. super critical)?
Or is 3.6 best? Running 3.1.8 at present.
Seeing the timeout
This patch (as1631) fixes a bug that shows up when a config change
fails for a device under an xHCI controller. The controller needs to
be told to disable the endpoints that have been enabled for the new
config. The existing code does this, but before storing the
information about which endpoints
