SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-20-2008, 08:45 AM
| ||||
| ||||
 slackware current + kernel 2.6.12.2 problem hi all, I just want to know if anybody have the same problem than me. Here it is. When i compile the kernel 2.6.12.2 with the CONFIG_SECCOMP ("enable seccomp to safely compute untrusted bytecode") option, the system hang when it run the rc.hotplug script. I am a little confused because without CONFIG_SECCOMP, the system run perfectly, but this is not the recommended choice for this option. thanks. -- Seb      |
|
02-20-2008, 08:45 AM
| |||
| |||
| Re: slackware current + kernel 2.6.12.2 problem On Wed, 13 Jul 2005 18:49:05 +0200, Sébastien BALLET <invalid@invalid.com> wrote: >I just want to know if anybody have the same problem than me. Here it is. >When i compile the kernel 2.6.12.2 with the CONFIG_SECCOMP ("enable seccomp >to safely compute untrusted bytecode") option, the system hang when it run >the rc.hotplug script. There's more to it than that, 'cos I not seen the problem, but me no use udev either, so lots of things I don't see, is it possible there are some hints in the logs on reboot? > >I am a little confused because without CONFIG_SECCOMP, the system run >perfectly, but this is not the recommended choice for this option. But if it not work for you, leave it off, we do fine with the feature in 2,4? Another debug method is to make rc.hotplug non-exec, enable options manually until it lock up  Slow but gets you to failure point.Right now 'hang' not enough info, what hang? where hang? --Grant. |
|
02-20-2008, 08:46 AM
| ||||
| ||||
| Re: slackware current + kernel 2.6.12.2 problem "Grant Coady" <grant_lkml@dodo.com.au> a écrit dans le message de news: 3qsad11kjnk70ape4th6rmmck24s3bqhan@4ax.com... > On Wed, 13 Jul 2005 18:49:05 +0200, Sébastien BALLET <invalid@invalid.com> > wrote: > >>I just want to know if anybody have the same problem than me. Here it is. >>When i compile the kernel 2.6.12.2 with the CONFIG_SECCOMP ("enable >>seccomp >>to safely compute untrusted bytecode") option, the system hang when it run >>the rc.hotplug script. > There's more to it than that, 'cos I not seen the problem, but me > no use udev either, so lots of things I don't see, is it possible > there are some hints in the logs on reboot? nothing interresting in the log after reboot. >> >>I am a little confused because without CONFIG_SECCOMP, the system run >>perfectly, but this is not the recommended choice for this option. > But if it not work for you, leave it off, we do fine with the feature > in 2,4? > CONFIG_SECCOMP is a new option since 2.6.12 > Another debug method is to make rc.hotplug non-exec, enable options > manually until it lock up when i "chmod -x rc.hotplug" and reboot, the problem disappear but come back when i "chmod +x /etc/rc.d/rc.hotplug ; ./etc/rc.d/rc.hotplug start". > Slow but gets you to failure point. Right now 'hang' not enough info, what > hang? full hang: no keyboard response. > where hang? unable to know where it hang exactly. After some investigation, the problem seems to be very strange because it come only after 2.6.12.2 compilation/installation/reboot. if i reboot twice, the problem disappear and seems to never come back (Tried with 5 reboot). |
Linear Mode
