On Wed, Oct 26, 2011 at 1:07 PM, Bjorn Helgaas <email address hidden> wrote:
> It looks like this report is for a valid problem, but died on the vine.
> Robert, did you ever resolve this? There's a similar report from Nick
> Bray here: https://lkml.org/lkml/2011/10/26/191 with screenshots that
> show a very similar backtrace. In Nick's case, booting with "maxcpus=1"
> is a workaround.
The system that I was testing with wasn't a primary machine, so I
deferred taking action on it.
I can get is setup again to see if this is still occurring, so I will
need to make sure that I'm not booting in 3.0.3 in order to get
upgraded.
On Wed, Oct 26, 2011 at 1:07 PM, Bjorn Helgaas <email address hidden> wrote: /lkml.org/ lkml/2011/ 10/26/191 with screenshots that
> It looks like this report is for a valid problem, but died on the vine.
> Robert, did you ever resolve this? There's a similar report from Nick
> Bray here: https:/
> show a very similar backtrace. In Nick's case, booting with "maxcpus=1"
> is a workaround.
The system that I was testing with wasn't a primary machine, so I
deferred taking action on it.
I can get is setup again to see if this is still occurring, so I will
need to make sure that I'm not booting in 3.0.3 in order to get
upgraded.