> On Apr 18, 2018, at 1:42 PM, John Baldwin wrote:
>>
>> Chenged made for it was
>>
>> Index: sys/x86/x86/nexus.c
>> ===
>> --- sys/x86/x86/nexus.c (revision 332663)
>> +++ sys/x86/x86/nexus.c (working copy)
>> @@ -698,7 +698,7 @@
JB> O, this is a different issue. Sorry. As a hack, try changing
JB> 'FIRST_MSI_INT' to 512 in sys/amd64/include/intr_machdep.h. The issue
JB> is that some systems now include more than 256 interrupt pins on I/O
JB> APICs, so IRQ 256 is already reserved for use by one of those
JB> interrupt
On Wednesday, April 18, 2018 01:56:49 PM Vitalij Satanivskij wrote:
> JB> > If you need any aditional information please tell me about.
> JB>
> JB> Can you perhaps turn off the stack trace on boot to not lose the panic
> messages
> JB> (remove KDB_TRACE from kernel config) and maybe modify the p
JB> > If you need any aditional information please tell me about.
JB>
JB> Can you perhaps turn off the stack trace on boot to not lose the panic
messages
JB> (remove KDB_TRACE from kernel config) and maybe modify the panic message to
JB> include the IRQ number passed to nexus_add_irq?
Hm looks
On Tuesday, April 17, 2018 10:15:53 PM Vitalij Satanivskij wrote:
> Dear John
>
> I'm try patch with no success
>
> http://hell.ukr.net/panic/recorder_patch165.webm
>
> Also I'm enable verbose boot and record boot process (hpet was disabled so
> crash in another driver atach)
> http://hell.ukr.
Dear John
I'm try patch with no success
http://hell.ukr.net/panic/recorder_patch165.webm
Also I'm enable verbose boot and record boot process (hpet was disabled so
crash in another driver atach)
http://hell.ukr.net/panic/recorder_patch_verbose.webm
root@test:/usr/src # svnlite diff
Index: sys/
On Monday, April 16, 2018 10:12:13 PM Vitalij Satanivskij wrote:
>
> igb0@pci0:1:0:0:class=0x02 card=0x152115d9 chip=0x15218086
> rev=0x01 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'I350 Gigabit Network Connection'
> class = network
> subclass =
Oh bios.
It's already lastest bios for now with agesa 1.0.0.5 in it.
It's dated 2/14/2018 So most likely new version will not appear soon
Stephen Hurd wrote:
SH> Yeah, this looks like some sort of general MSI issue, not igb specific.
SH> I'm not familiar with that part of the kernel, but maybe
Dear Stephen
I'm disable msix on igb both 1 and 0
and enable HPET in bios
get hpet_attach panic. http://hell.ukr.net/panic/recorder_hpet.webm
so i disable hpet again and get msi_alloc and so on
http://hell.ukr.net/panic/recorder_msi.webm
So for test I'm set hw.pci.enable_msi=0 and get panic
igb0@pci0:1:0:0:class=0x02 card=0x152115d9 chip=0x15218086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class = network
subclass = ethernet
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[5
Hi Vitalij,
On Mon, Apr 16, 2018 at 3:27 AM, Vitalij Satanivskij wrote:
> DUMP can be found here http://hell.ukr.net/panic/panic.jpg
> or even video record from screen http://hell.ukr.net/panic/recorder.webm
Looks like the panic message is printed directly after: "igb0: using 2
rx queues 2 tx qu
11 matches
Mail list logo