Well, this is some kind of summarized feedback on the real bumpy ride related to the 4.6 kernel series - hopefully helpful and some specific to 4.6.4-r1. - early 4.6 releases until 4.6.3-r1 won´t boot on x86 box, early panic - 4.6.3-r1 panics on x86 related to pppd when DSL is pulled on modem - 4.6.4 on amd64 box panics on shutdown to reboot - 4.6.4-r1 on amd64 box panics shortly after boot on login via ssh - fallback to 4.5 on all boxes restores normal operation - as far as noticed (some are headless), all panics were related to spinlock on the terminal No 4.6 revision has ran flawlessly on any box so far. If needed, I will give further details.
I confirm this. Kernel freezes after setting my net. 4.6.4-r1 freezes but 4.6.4 works normal for me.
(In reply to reagentoo from comment #1) > I confirm this. Kernel freezes after setting my net. 4.6.4-r1 freezes but > 4.6.4 works normal for me. *sigh* I'll pass it upstream.
getting your configs and some output from the kernel would be helpful. also if you try the latest grsec patch then either disable size overflow or boot with pax_size_overflow_report_only for now.
Created attachment 441154 [details] kernel-config-x86_64-4.6.4-hardened-r1 my kernel config
Created attachment 441158 [details] dmesg dmesg out with pax_size_overflow_report_only
*** Bug 588700 has been marked as a duplicate of this bug. ***
I'm not too sure, that my bug 588700 actually is a duplicate of this, since it occurred before 4.6 and involves a different error (not a size overflow but an inability to handle a kernel paging request).
Created attachment 441214 [details] Kernel Log after ssh login ssh login triggers the overflow
Created attachment 441216 [details] Testbox kernel config
(In reply to Markus Oehme from comment #7) > I'm not too sure, that my bug 588700 actually is a duplicate of this, since > it occurred before 4.6 and involves a different error (not a size overflow > but an inability to handle a kernel paging request). okay. can you test 4.6.4-r2 which I just put on the tree. @pipacs 4.6.4-r2 = grsecurity-3.1-4.6.4-201607192040
(In reply to Anthony Basile from comment #10) > okay. can you test 4.6.4-r2 which I just put on the tree. I'm now running 4.6.4-r2 and everything looks fine. *thumbs up*