Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
Hi Andy,

OK, I booted a t2.micro instance from my AMI (Original OmniOS CE r151022
HVM).  Updated pkg and then updated to r151022as.

Then shut the instance down, changed the type to m4.large, then started
the instance.  A panic/reboot loop ensued.  Stopped the instance.

Changed the instance back to t2.micro and booted.  Applied the hotfix
and rebooted.  Rebooted fine.

Stopped the instance, changed instance type to m4.large, and started the
instance.  The instance started and I could log in just fine.

To be sure, I stopped and restarted the instance a few times. It always
came back up ok.

So, the patch looks good to me.  If you can think of any more tests you
would like me to run, I'll give them a go for you.

Thank you for the speedy fix.

regards

Al


On 09/04/18 18:05, Al Slater wrote:
> Hi Andy,
> 
> Wow, that was fast.  I will test this when I have fed the family.
> 
> I have my own AMI, so I can spin a server as a T2 instance, apply the
> fix and then restart after changing to an M4.
> 
> regards
> 
> Al
> 
> On 09/04/18 16:04, Andy Fiddaman wrote:
>>
>> Al,
>>
>> I've prepared a hot-fix containing this driver update if you'd like to
>> test. I tried to test it myself on AWS but can't provision any type of
>> machine from that unofficial CE r151022 AMI in London. Just snapshot the
>> EBS volume first in case of problems.
>>
>> To install:
>>
>>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
>>
>> which will create a new boot-environment, and reboot.
>>
>> Assuming it looks ok, this update will be part of next Monday's release.
>>
>> Regards,
>>
>> Andy
>>
>> On Mon, 9 Apr 2018, Al Slater wrote:
>>
>> ; Hi,
>> ;
>> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
>> ; r151022 since the initial CE release?
>> ;
>> ; I have an instance in AWS that they required me to stop and start again
>> ; due to host patching.  When I started it again the instance went into a
>> ; panic/reboot loop.  The stack dump looked similar to the one in the
>> ; error report.
>> ;
>> ; I managed to get the instance started by changing the instance type from
>> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
>> ; > 4 in london region.  I don't know how long until the t2 hosts are 
>> updated.
>> ;
>> ; regards
>> ;
>> ;
>>
> 
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
Hi Andy,

Wow, that was fast.  I will test this when I have fed the family.

I have my own AMI, so I can spin a server as a T2 instance, apply the
fix and then restart after changing to an M4.

regards

Al

On 09/04/18 16:04, Andy Fiddaman wrote:
> 
> Al,
> 
> I've prepared a hot-fix containing this driver update if you'd like to
> test. I tried to test it myself on AWS but can't provision any type of
> machine from that unofficial CE r151022 AMI in London. Just snapshot the
> EBS volume first in case of problems.
> 
> To install:
> 
>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
> 
> which will create a new boot-environment, and reboot.
> 
> Assuming it looks ok, this update will be part of next Monday's release.
> 
> Regards,
> 
> Andy
> 
> On Mon, 9 Apr 2018, Al Slater wrote:
> 
> ; Hi,
> ;
> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
> ; r151022 since the initial CE release?
> ;
> ; I have an instance in AWS that they required me to stop and start again
> ; due to host patching.  When I started it again the instance went into a
> ; panic/reboot loop.  The stack dump looked similar to the one in the
> ; error report.
> ;
> ; I managed to get the instance started by changing the instance type from
> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
> ; > 4 in london region.  I don't know how long until the t2 hosts are updated.
> ;
> ; regards
> ;
> ;
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Andy Fiddaman

Al,

I've prepared a hot-fix containing this driver update if you'd like to
test. I tried to test it myself on AWS but can't provision any type of
machine from that unofficial CE r151022 AMI in London. Just snapshot the
EBS volume first in case of problems.

To install:

  pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p

which will create a new boot-environment, and reboot.

Assuming it looks ok, this update will be part of next Monday's release.

Regards,

Andy

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi,
;
; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; r151022 since the initial CE release?
;
; I have an instance in AWS that they required me to stop and start again
; due to host patching.  When I started it again the instance went into a
; panic/reboot loop.  The stack dump looked similar to the one in the
; error report.
;
; I managed to get the instance started by changing the instance type from
; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
; > 4 in london region.  I don't know how long until the t2 hosts are updated.
;
; regards
;
;
-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Andy Fiddaman

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi,
;
; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; r151022 since the initial CE release?

Hi Al,

No, that one was not selected for back-porting. I'll get it added to the list
for the next weekly release.

Regards,

Andy

-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
On 09/04/2018 08:49, Al Slater wrote:
> Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
> r151022 since the initial CE release?
> 
> I have an instance in AWS that they required me to stop and start again
> due to host patching.  When I started it again the instance went into a
> panic/reboot loop.  The stack dump looked similar to the one in the
> error report.
> 
> I managed to get the instance started by changing the instance type from
> m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
>> 4 in london region.  I don't know how long until the t2 hosts are updated.

Repeatable on any m4 instance type I tried.

Technical Director
SCL

Phone : +44 (0)1273 07
Fax   : +44 (0)1273 01
email : al.sla...@scluk.com

Stanton Consultancy Ltd

Park Gate, 161 Preston Road, Brighton, East Sussex, BN1 6AU

Registered in England Company number: 1957652 VAT number: GB 760 2433 55
panic[cpu0]/thread=ff000f4e6c40: BAD TRAP: type=e (#pf Page fault)
rp=ff000f4e69b0 addr=40 occurred in module "xnf" due to a NULL
pointer dereference

sched: #pf Page fault

Bad kernel fault at addr=0x40

pid=0, pc=0xf79b6e67, sp=0xff000f4e6aa0, eflags=0x10206

cr0: 8005003b cr4:
1406b8


cr2: 40cr3: c40cr8: c
rdi:  286 rsi:6 rdx:c
rcx: ff03d5dbf064  r8:0  r9:0
rax:  150 rbx:3 rbp: ff000f4e6af0
r10:0 r11: fb800983 r12: ff03d5d9
r13:0 r14:   15 r15:9
fsb:0 gsb: fbc397e0  ds:   4b
 es:   4b  fs:0  gs:  1c3
trp:e err:0 rip: f79b6e67
 cs:   30 rfl:10206 rsp: ff000f4e6aa0
 ss:   38

Warning - stack not written to the dump buffer
ff000f4e6890 unix:die+df ()
ff000f4e69a0 unix:trap+e18 ()
ff000f4e69b0 unix:cmntrap+e6 ()
ff000f4e6af0 xnf:xnf_tx_clean_ring+c7 ()
ff000f4e6b60 xnf:tx_slots_get+95 ()
ff000f4e6ba0 xnf:xnf_intr+15b ()
ff000f4e6bf0 unix:av_dispatch_softvect+78 ()
ff000f4e6c20 unix:dispatch_softint+39 ()
ff000f635460 unix:switch_sp_and_call+13 ()
ff000f6354a0 unix:dosoftint+44 ()
ff000f635500 unix:do_interrupt+ba ()
ff000f635510 unix:cmnint+ba ()
f7c6aec0 sha2:SHA256TransformBlocks+109f ()


-- 
Al Slater

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


[OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
Hi,

Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
r151022 since the initial CE release?

I have an instance in AWS that they required me to stop and start again
due to host patching.  When I started it again the instance went into a
panic/reboot loop.  The stack dump looked similar to the one in the
error report.

I managed to get the instance started by changing the instance type from
m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
> 4 in london region.  I don't know how long until the t2 hosts are updated.

regards

-- 
Al Slater

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss