Bug 10474 - 2.15-core76-beta1 crash after activation of QoS
Summary: 2.15-core76-beta1 crash after activation of QoS
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Minor Usability
Assignee: Michael Tremer
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-06 18:36 UTC by Jochen Rossbach
Modified: 2014-05-10 17:05 UTC (History)
4 users (show)

See Also:

Attachments
Picture 1 of QoS crash (2.18 MB, image/jpeg)
2014-02-10 16:59 UTC, Gamoholic 		Details
Picture 2 of QoS crash (2.21 MB, image/jpeg)
2014-02-10 17:00 UTC, Gamoholic 		Details
Picture 3 of QoS crash (1.84 MB, image/jpeg)
2014-02-10 17:00 UTC, Gamoholic 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jochen Rossbach 2014-02-06 18:36:30 UTC 
After entering my up and downlink values,I pushed the preset button and the system crashed entered into a reboot loop.

A similiar behavior i registered, after I executed the online update with activated QoS.

Unfortunately, I cant provide at the moment logfiles or screen dumps, as my Aten CN6000 KVM over IP reacts to slow.

My Hardwareprofile is e22d753754cc5fd46bee38a0be7f181762f4823f.
Comment 1 Stefan Schantl 2014-02-08 15:59:31 UTC 
Hello Jochen,

I can confirm that QOS is still working without problems on IPFire 2.15 Beta1. 

Please post some additional informations to your installation. Do you use a fresh installed system or do you have upgraded an existing one?

If you have performed an upgrade, do you have used QOS before?

Thanks in advance,

-Stefan
Comment 2 Gamoholic 2014-02-10 14:19:02 UTC 
After upgrading my system to 2.15 beta1 it went into a reboot loop. I had QoS enabled. After installing 2.15 beta1 from scratch it works just fine, even with QoS enabled.

2919c1425eda362bfe841f8dfd23544dd56d22ee
Comment 3 Gamoholic 2014-02-10 15:52:15 UTC 
Update:

All is NOT well with QoS! After setting up several things such as Squid, OpenVPN, and QoS I rebooted my router. It went into another reboot loop. I had configured QoS, but it was not on. I got several screenshots of the crashes which I can attach upon request. The most useful crash said something about "Kernel panic - not syncing: Fatal exception in interrupt".

The new profile ID for this box is 1303ebea732085327bca86b3b22995f1d1ae1c10
Comment 4 Michael Tremer 2014-02-10 16:45:16 UTC 
Could you please try to provide screenshots of the panic messages?

I believe that this is a hardware issue that may possibly be triggered by QoS.
Comment 5 Gamoholic 2014-02-10 16:59:42 UTC 
Created attachment 180 [details]
Picture 1 of QoS crash
Comment 6 Gamoholic 2014-02-10 17:00:22 UTC 
Created attachment 181 [details]
Picture 2 of QoS crash
Comment 7 Gamoholic 2014-02-10 17:00:46 UTC 
Created attachment 182 [details]
Picture 3 of QoS crash