|
From: Manuel Lauss on 1 Sep 2006 06:00 I need the following patch to make it build. __NR_execve is undeclared. --- a/arch/i386/kernel/sys_i386.c~ 2006-09-01 11:48:45.000000000 +0200 +++ b/arch/i386/kernel/sys_i386.c 2006-09-01 11:48:45.000000000 +0200 @@ -22,6 +22,7 @@ #include <asm/uaccess.h> #include <asm/ipc.h> +#include <asm/unistd.h> /* * sys_pipe() is the normal C calling standard for creating - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Grant Wilson on 1 Sep 2006 06:50 Andrew Morton wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/ [snip] > The CONFIG_BLOCK changes wrecked these. The CONFIG_BLOCK changes also seem to prevent the selection of any RAID or LVM drivers... Cheers, Grant - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Grant Coady on 1 Sep 2006 21:10 On Fri, 1 Sep 2006 01:58:18 -0700, Andrew Morton <akpm(a)osdl.org> wrote: > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/ .... >- See the `hot-fixes' directory for any important updates to this patchset. > Okay, I applied hotfixes and it crashed on boot, keyboard LEDs flashing: Repeating message, hand copied: atkbd.c: Spurious ACK in isa0060/serio0. Some program might be trying access hardware directly. Thing is, I've been getting this similar message once in dmesg for ages: <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.14.7a.gz>: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.15.7a.gz>: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.16.27a.gz>: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.16.28a.gz>: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.17.11a.gz>: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.18-rc3-mm2a.gz>: <no mention> <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.18-rc4a.gz>: atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/dmesg-2.6.18-rc5-git4b>: atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly. <http://bugsplatter.mine.nu/test/boxen/sempro/> for more info on hardware This is MSI KM4M-V <http://tinyurl.com/64cfd> AMD Sempron SktA 32-bit CPU, I don't see the error on Intel CPU boxen, nor on an AMD K6-2/500 CPU (2.6.15.6) Grant. -- VGER BF report: U 0.480374 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 1 Sep 2006 21:20 On Friday 01 September 2006 21:06, Grant Coady wrote: > On Fri, 1 Sep 2006 01:58:18 -0700, Andrew Morton <akpm(a)osdl.org> wrote: > > > > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/ > ... > >- See the `hot-fixes' directory for any important updates to this patchset. > > > Okay, I applied hotfixes and it crashed on boot, keyboard LEDs flashing: > > Repeating message, hand copied: > atkbd.c: Spurious ACK in isa0060/serio0. Some program might be trying access > hardware directly. > Please try booting with i8042.panicblink=0 to see the real oops (important data). We should probably disable blinking if X is not active... -- Dmitry -- VGER BF report: H 2.32592e-14 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 1 Sep 2006 21:40 On Friday 01 September 2006 21:12, Dmitry Torokhov wrote: > On Friday 01 September 2006 21:06, Grant Coady wrote: > > On Fri, 1 Sep 2006 01:58:18 -0700, Andrew Morton <akpm(a)osdl.org> wrote: > > > > > > > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/ > > ... > > >- See the `hot-fixes' directory for any important updates to this patchset. > > > > > Okay, I applied hotfixes and it crashed on boot, keyboard LEDs flashing: > > > > Repeating message, hand copied: > > atkbd.c: Spurious ACK in isa0060/serio0. Some program might be trying access > > hardware directly. > > > > Please try booting with i8042.panicblink=0 to see the real oops (important > data). ... or try the patch below. -- Dmitry Input: i8042 - disable keyboard port when panicking and blinking This should get rid of "spurious ACK" messages from atkbd driver during panic. Signed-off-by: Dmitry Torokhov <dtor(a)mail.ru> --- drivers/input/serio/i8042.c | 7 +++++++ 1 files changed, 7 insertions(+) Index: work/drivers/input/serio/i8042.c =================================================================== --- work.orig/drivers/input/serio/i8042.c +++ work/drivers/input/serio/i8042.c @@ -836,9 +836,16 @@ static long i8042_panic_blink(long count */ if (!i8042_blink_frequency) return 0; + if (count - last_blink < i8042_blink_frequency) return 0; + /* + * Disable keyboard port so ATKBD won't fill logs with + * "spurious ACK" messages + */ + i8042_ports[I8042_KBD_PORT_NO].exists = 0; + led ^= 0x01 | 0x04; while (i8042_read_status() & I8042_STR_IBF) DELAY; -- VGER BF report: H 0 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Next
|
Last
Pages: 1 2 3 4 5 6 Prev: Help in kernel error Next: kernel BUGs when removing largish files with the SLOB allocator |