Might be a DRM issue.
Have you tried to remotely connect (eg with ssh) in order to see what's happening?
Have you looked at journalctl output?
try run "journalct --since 2016-06-20>/tmp/bug18751.txt" as root and attach (*not* paste) the resulting /tmp/bug18751.txt file to this bug report

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud, tmb
Source RPM: firefox-45.2.0-1.mga5, kernel-(desktop,server)-4.4.13-1.mga5-1-1.mga5 => kernel-4.4.13-1.mga5-1-1.mga5, firefox-45.2.0-1.mga5

Created attachment 8038 [details]
firefox freezes the system

(In reply to Thierry Vignaud from comment #1)
> Might be a DRM issue.
> Have you tried to remotely connect (eg with ssh) in order to see what's
> happening?
> Have you looked at journalctl output?
> try run "journalct --since 2016-06-20>/tmp/bug18751.txt" as root and attach
> (*not* paste) the resulting /tmp/bug18751.txt file to this bug report

sorry bugzilla refuses to attach the file bug18751.txt since it is 1200kB in size
I'edit a new file:
journalctl --since 2016-06-21 > bug18751.txt
since the crash occured today june 21st at about 13:00; I had to reboot by pressing the reset button at precisely 13:07:08, as you'll see on the log, and I have rebooted on kernel-4.1.15-server which never caused any trouble at this day

Thomas, it looks like there's issues with disk controller IRQ:
"irq 16: nobody cared (try booting with the "irqpoll" option)"

this irq seems shared between pata & usb controllers on that machine

Assignee: bugsquad => tmb

Created attachment 8039 [details]
irqpoll added in grub/menulst as boot option

(In reply to Thierry Vignaud from comment #4)
> Thomas, it looks like there's issues with disk controller IRQ:
> "irq 16: nobody cared (try booting with the "irqpoll" option)"
> 
> this irq seems shared between pata & usb controllers on that machine

here the return of the command journalctl --since 2016-06-21 > bug18751_irqpoll.txt

after rebooting on kernel-4.4.13 with boot option irqpoll added in grub/menulst

if it may help you...

Did it worked better for you?

(In reply to Thierry Vignaud from comment #7)
> Did it worked better for you?

I can't say for the moment; boot is always so slow, especially after logging in
but firefox's crash happens only frequently, but not all the time, fortunately!
now everything seems OK

(In reply to Thierry Vignaud from comment #7)
> Did it worked better for you?

No, today morning I had a freeze with firefox; I think it's an emergency to go to kernel-4.4.15

(In reply to Thierry Vignaud from comment #7)
> Did it worked better for you?

in fact I have noticed that the firefox freezes coincide always with mdam raid volumes desynchronizing; in these cases, I have to reboot using the worse method, say to press the reset button, and once rebooted, wait resync process be achieved, which needs a long time; during resync process using my machine is almost impossible; raid volumes desync happens much more frequently with the actual kernel 4.4.13 than under the former one 4.1.15

Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Hi Peter,

Thank you for having taken the needed time to report this issue and for having provided requested information!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

(In reply to Marja Van Waes from comment #12)
> Hi Peter,
> 
> Thank you for having taken the needed time to report this issue and for
> having provided requested information!
> 
> Did this bug get fixed? If so, please change its status to RESOLVED - FIXED
> 
> If it didn't, then we regret that we weren't able to fix it in Mageia 5.
> Mageia 5 has officially reached its End of Life on December 31st, 2017
> https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
> It only continued to get important security updates since then, because we
> are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the
> Mageia 5 => 6 upgrade issues.
> 
> If you haven't seen that this bug got fixed, then please check whether this
> bug still exists in Mageia 6. If it does, then please change the Version
> (near the top, at the left) to "6". If you know it exists in Cauldron, then
> change Version to Cauldron. If you see it in both Cauldron and Mageia 6,
> then please set Version to Cauldron and add MGA6TOO on the Whiteboard.
> 
> Thanks,
> Marja

bug fixed for both mageia5 & 6

Per comment 13 setting to FIXED

Status: NEW => RESOLVED
CC: (none) => fri
Resolution: (none) => FIXED