Messages in this thread | | | From | (Eric W. Biederman) | Subject | Re: 2.6.23-rc2-mm2 | Date | Fri, 10 Aug 2007 10:03:36 -0600 |
| |
Gabriel C <nix.or.die@googlemail.com> writes:
> ... > >> +sysctl-core-stop-using-the-unnecessary-ctl_table-typedef.patch >> +sysctl-factor-out-sysctl_data.patch >> +sysctl-error-on-bad-sysctl-tables.patch >> +sysctl-update-sysctl_check_table.patch >> +sysct-mqueue-remove-the-binary-sysctl-numbers.patch >> +sysctl-remove-binary-sysctl-support-where-it-clearly-doesnt-work.patch >> +sysctl-fix-neighbour-table-sysctls.patch >> +sysctl-ipv6-route-flushing-kill-binary-path.patch >> +sysctl-remove-broken-sunrpc-debug-binary-sysctls.patch >> +sysctl-x86_64-remove-unnecessary-binary-paths.patch >> +sysctl-remove-broken-cdrom-binary-sysctls.patch >> +sysctl-ipv4-remove-binary-sysctl-paths-where-they-are-broken.patch >> > +sysctl-remove-the-binary-interface-for-aio-nr-aio-max-nr-acpi_video_flags.patch >> >> sysctl cleanups >> > > ... > > > Getting all this on boot : > > ... > > [ 484.984331] sysctl table check failed: /dev/parport/default/timeslice > .7.3.-3.1 Missing strategy > [ 484.984515] sysctl table check failed: /dev/parport/default/spintime .7.3.-3.2 > Missing strategy > [ 485.001254] sysctl table check failed: /dev/parport/parport0/devices/Device ID > probe .7.3.1.6.1 Directory with extra1 > [ 485.001472] sysctl table check failed: /dev/parport/parport0/devices/Device ID > probe/timeslice .7.3.1.6.1.1 Missing strategy > [ 485.042786] sysctl table check failed: /dev/parport/parport0/devices/Device ID > probe .7.3.1.6.1 Directory with extra1 > [ 485.042962] sysctl table check failed: /dev/parport/parport0/devices/Device ID > probe/timeslice .7.3.1.6.1.1 Missing strategy > [ 485.083586] sysctl table check failed: /dev/parport/parport0/spintime .7.3.1.1 > Missing strategy > [ 485.083731] sysctl table check failed: /dev/parport/parport0/base-addr > .7.3.1.2 Missing strategy > [ 485.083878] sysctl table check failed: /dev/parport/parport0/irq .7.3.1.3 > Missing strategy > [ 485.084022] sysctl table check failed: /dev/parport/parport0/dma .7.3.1.4 > Missing strategy > [ 485.084166] sysctl table check failed: /dev/parport/parport0/modes .7.3.1.5 > Missing strategy > [ 485.084317] sysctl table check failed: /dev/parport/parport0/devices .7.3.1.6 > Directory with extra1 > [ 485.084470] sysctl table check failed: /dev/parport/parport0/devices/active > .7.3.1.6.-3 Missing strategy > [ 485.084653] sysctl table check failed: /dev/parport/parport0/autoprobe > .7.3.1.16 Missing strategy > [ 485.084806] sysctl table check failed: /dev/parport/parport0/autoprobe0 > .7.3.1.17 Missing strategy > [ 485.084954] sysctl table check failed: /dev/parport/parport0/autoprobe1 > .7.3.1.18 Missing strategy > [ 485.085103] sysctl table check failed: /dev/parport/parport0/autoprobe2 > .7.3.1.19 Missing strategy > [ 485.085253] sysctl table check failed: /dev/parport/parport0/autoprobe3 > .7.3.1.20 Missing strategy > [ 485.114655] sysctl table check failed: /dev/parport/parport0/devices/lp > .7.3.1.6.1 Directory with extra1 > [ 485.114856] sysctl table check failed: > /dev/parport/parport0/devices/lp/timeslice .7.3.1.6.1.1 Missing strategy
Hmm. Thanks it doesn't like I had the parport code enabled in my test kernel. With a little luck it looks like we can just nuke the binary sysctl interface here. And get the /proc/sys interface working again.
Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |