Hi,
continuing on my series of problems with the current next build, I currently have the following problems: - unbound (well, you already know about the problem of the name resolution) - segfaulting hwclock on /usr/local/bin/settime and during startup (S60setclock) and shutdown (K47setclock) - grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /sbin/hwclock - "error: no symbol table. (...) Press any key to continue..." before the kernel is loaded, right after grub. - even when no key is pressed, the boot continues
Sorry that I bother you only with problems this time, but I want to make sure that this "normal" for the current next, before I rebase and re-sent the apache patches.
Best regards, Wolfgang PS.: I also can have a look at some of these issues, just not today and I wanted to make sure that these issues are not only because of VirtualBox.
Hi,
On Mon, 2017-06-26 at 20:43 +0200, Wolfgang Apolinarski wrote:
Hi,
continuing on my series of problems with the current next build, I currently have the following problems:
Yes, we are still in the middle of getting in stable. Hence it is called next.
I have just packaged the core update and the nightly builds will hopefully run through. And then the big testing starts.
- unbound (well, you already know about the problem of the name resolution)
That should be fixed.
- segfaulting hwclock on /usr/local/bin/settime and during startup
(S60setclock) and shutdown (K47setclock) - grsec: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /sbin/hwclock
I still haven't looked into this.
- "error: no symbol table. (...) Press any key to continue..." before the
kernel is loaded, right after grub. - even when no key is pressed, the boot continues
This is the first time I hear about this. Could you please open a ticket and collect all information about this problem that you have?
The system is booting up fine on my virtual machines that I used for testing.
Sorry that I bother you only with problems this time, but I want to make sure that this "normal" for the current next, before I rebase and re-sent the apache patches.
No that's fine. That's what this list is for :)
Best regards, Wolfgang PS.: I also can have a look at some of these issues, just not today and I wanted to make sure that these issues are not only because of VirtualBox.