"Christos Zoulas" wrote:
> Log Message:
>
> Don't crash if we are on a hippie trail, head full of zombie
+1 for any Australian references in a commit message :)
Cheers,
Simon.
Andrew Doran writes:
> I also recommend disabling ACPI idle, at least until it can be made less
> aggressive by default. It causes a significant slowdown. It can be done
> with detaching all acpicpu devices using "drvctl -d" on each.
this disables cpufreq support, doesn't it? that seems like
On Fri, Jan 10, 2020 at 10:21:25PM +, Andrew Doran wrote:
> Hi Frank,
>
> On Fri, Jan 10, 2020 at 01:10:02PM +0100, Frank Kardel wrote:
>
> > Hi !
> >
> > With this state of January 2nd we ran some tests for robustness and timing
> > with our database setup:
> >
> > Machine:
> >
> >
On 2020/01/21 20:20, Patrick Welche wrote:
> On Tue, Jan 21, 2020 at 03:48:27PM +0900, Masanobu SAITOH wrote:
>> I suspect the location of your panic is after the following message
>> (because of ixgbe_allocate_msix()'s failure):
>>
>>> aprint_normal(" ETrackID %08x\n", ((uint32_t)high <<
On Tue, Jan 21, 2020 at 03:48:27PM +0900, Masanobu SAITOH wrote:
> I suspect the location of your panic is after the following message
> (because of ixgbe_allocate_msix()'s failure):
>
> > aprint_normal(" ETrackID %08x\n", ((uint32_t)high << 16) | low);
Exactly right:
ixg0 at pci8 dev 0
