Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Wed, 20 Feb 2008 23:04:40 +0300 Oleg Nesterov <[EMAIL PROTECTED]> wrote: > Yes, please look at http://marc.info/?t=12030984056 > > Btw. The bug in tty_io.c _can_ explain this trace, but it would be nice > to ensure we don't have other problems. Could you try this > > http://marc.info/?l=linux-kernel=120352655031911 > > patch? Fun. With that debugging patch applied, the oops on boot no longer happens... No, I have no idea why... -- All Rights Reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Wed, 20 Feb 2008 14:34:17 -0500 Rik van Riel <[EMAIL PROTECTED]> wrote: > On Sun, 17 Feb 2008 09:40:33 +0530 > Kamalesh Babulal <[EMAIL PROTECTED]> wrote: > > > [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b > > [ 25.514926] IP: [] proc_flush_task+0x5b/0x223 > > I wonder if this one is related. Also with 2.6.25-rc2-mm1 on x86_64: Probably - am testing some locking patches now -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On 02/20, Rik van Riel wrote: > > On Sun, 17 Feb 2008 09:40:33 +0530 > Kamalesh Babulal <[EMAIL PROTECTED]> wrote: > > > [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b > > [ 25.514926] IP: [] proc_flush_task+0x5b/0x223 > > I wonder if this one is related. Also with 2.6.25-rc2-mm1 on x86_64: > > BUG: unable to handle kernel paging request at 00200200 > IP: [] free_pid+0x35/0x90 > ... > Call Trace: > [] ? release_task+0x1be/0x346 > [] ? do_wait+0x6c2/0xa0e > [] ? trace_hardirqs_on_caller+0xf2/0x115 > [] ? default_wake_function+0x0/0xe > [] ? trace_hardirqs_on_caller+0xf2/0x115 > [] ? sys_wait4+0x8a/0xa1 > [] ? system_call_after_swapgs+0x7b/0x80 Yes, please look at http://marc.info/?t=12030984056 Btw. The bug in tty_io.c _can_ explain this trace, but it would be nice to ensure we don't have other problems. Could you try this http://marc.info/?l=linux-kernel=120352655031911 patch? (I can't understand why this happens at the boot time, and it is not reproducable on my side). Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote: > [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b > [ 25.514926] IP: [] proc_flush_task+0x5b/0x223 I wonder if this one is related. Also with 2.6.25-rc2-mm1 on x86_64: BUG: unable to handle kernel paging request at 00200200 IP: [] free_pid+0x35/0x90 PGD 43c00c067 PUD 43e5f1067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /sys/devices/pnp0/00:0b/id CPU 7 Modules linked in: dm_multipath qla2xxx bnx2 iTCO_wdt iTCO_vendor_support serio_raw rtc_cmos pcspkr watchdog_core scsi_transport_fc watchdog_dev i5000_edac edac_core button dcdbas joydev sg sr_mod cdrom usb_storage ata_piix libata dm_snapshot dm_zero dm_mirror dm_mod shpchp megaraid_sas sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode] Pid: 1992, comm: S05kudzu Not tainted 2.6.25-rc2-mm1 #4 RIP: 0010:[] [] free_pid+0x35/0x90 RSP: 0018:81043c895e58 EFLAGS: 00010046 RAX: RBX: 81043dd31440 RCX: 81043e5ffb08 RDX: 00200200 RSI: 0046 RDI: RBP: 81043b9703c0 R08: R09: 0001 R10: 81043d1a R11: R12: 81043e5ffac0 R13: R14: R15: 008cd530 FS: 7f68f99786f0() GS:81043e7100c0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 00200200 CR3: 000436c1f000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process S05kudzu (pid: 1992, threadinfo 81043c894000, task 81043b9acb40) Stack: 81043dd31440 81043b9703c0 81043c84ae40 81035a6d 81043b9703c0 07cd 810362b7 81043c895f18 81051316 7fff01989514 Call Trace: [] ? release_task+0x1be/0x346 [] ? do_wait+0x6c2/0xa0e [] ? trace_hardirqs_on_caller+0xf2/0x115 [] ? default_wake_function+0x0/0xe [] ? trace_hardirqs_on_caller+0xf2/0x115 [] ? sys_wait4+0x8a/0xa1 [] ? system_call_after_swapgs+0x7b/0x80 -- All Rights Reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote: [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b [ 25.514926] IP: [c04a8fac] proc_flush_task+0x5b/0x223 I wonder if this one is related. Also with 2.6.25-rc2-mm1 on x86_64: BUG: unable to handle kernel paging request at 00200200 IP: [81043d3c] free_pid+0x35/0x90 PGD 43c00c067 PUD 43e5f1067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /sys/devices/pnp0/00:0b/id CPU 7 Modules linked in: dm_multipath qla2xxx bnx2 iTCO_wdt iTCO_vendor_support serio_raw rtc_cmos pcspkr watchdog_core scsi_transport_fc watchdog_dev i5000_edac edac_core button dcdbas joydev sg sr_mod cdrom usb_storage ata_piix libata dm_snapshot dm_zero dm_mirror dm_mod shpchp megaraid_sas sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode] Pid: 1992, comm: S05kudzu Not tainted 2.6.25-rc2-mm1 #4 RIP: 0010:[81043d3c] [81043d3c] free_pid+0x35/0x90 RSP: 0018:81043c895e58 EFLAGS: 00010046 RAX: RBX: 81043dd31440 RCX: 81043e5ffb08 RDX: 00200200 RSI: 0046 RDI: RBP: 81043b9703c0 R08: R09: 0001 R10: 81043d1a R11: R12: 81043e5ffac0 R13: R14: R15: 008cd530 FS: 7f68f99786f0() GS:81043e7100c0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 00200200 CR3: 000436c1f000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process S05kudzu (pid: 1992, threadinfo 81043c894000, task 81043b9acb40) Stack: 81043dd31440 81043b9703c0 81043c84ae40 81035a6d 81043b9703c0 07cd 810362b7 81043c895f18 81051316 7fff01989514 Call Trace: [81035a6d] ? release_task+0x1be/0x346 [810362b7] ? do_wait+0x6c2/0xa0e [81051316] ? trace_hardirqs_on_caller+0xf2/0x115 [8102ac72] ? default_wake_function+0x0/0xe [81051316] ? trace_hardirqs_on_caller+0xf2/0x115 [8103668d] ? sys_wait4+0x8a/0xa1 [8100be3b] ? system_call_after_swapgs+0x7b/0x80 -- All Rights Reversed -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On 02/20, Rik van Riel wrote: On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote: [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b [ 25.514926] IP: [c04a8fac] proc_flush_task+0x5b/0x223 I wonder if this one is related. Also with 2.6.25-rc2-mm1 on x86_64: BUG: unable to handle kernel paging request at 00200200 IP: [81043d3c] free_pid+0x35/0x90 ... Call Trace: [81035a6d] ? release_task+0x1be/0x346 [810362b7] ? do_wait+0x6c2/0xa0e [81051316] ? trace_hardirqs_on_caller+0xf2/0x115 [8102ac72] ? default_wake_function+0x0/0xe [81051316] ? trace_hardirqs_on_caller+0xf2/0x115 [8103668d] ? sys_wait4+0x8a/0xa1 [8100be3b] ? system_call_after_swapgs+0x7b/0x80 Yes, please look at http://marc.info/?t=12030984056 Btw. The bug in tty_io.c _can_ explain this trace, but it would be nice to ensure we don't have other problems. Could you try this http://marc.info/?l=linux-kernelm=120352655031911 patch? (I can't understand why this happens at the boot time, and it is not reproducable on my side). Oleg. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Wed, 20 Feb 2008 14:34:17 -0500 Rik van Riel [EMAIL PROTECTED] wrote: On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote: [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b [ 25.514926] IP: [c04a8fac] proc_flush_task+0x5b/0x223 I wonder if this one is related. Also with 2.6.25-rc2-mm1 on x86_64: Probably - am testing some locking patches now -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Wed, 20 Feb 2008 23:04:40 +0300 Oleg Nesterov [EMAIL PROTECTED] wrote: Yes, please look at http://marc.info/?t=12030984056 Btw. The bug in tty_io.c _can_ explain this trace, but it would be nice to ensure we don't have other problems. Could you try this http://marc.info/?l=linux-kernelm=120352655031911 patch? Fun. With that debugging patch applied, the oops on boot no longer happens... No, I have no idea why... -- All Rights Reversed -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On 02/17, Kamalesh Babulal wrote: > > There has been discussion on the patch for this panic on > http://lkml.org/lkml/2008/2/16/99 This looks similar... > [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b > [ 25.514926] IP: [] proc_flush_task+0x5b/0x223 > [ 25.516934] Oops: [#1] SMP > [ 25.517918] last sysfs file: /sys/block/hdc/removable > [ 25.517918] Modules linked in: dm_mirror dm_mod video output sbs sbshc > battery ac parport_pc lp parport floppy sg serio_raw ide_cd_mod cdrom > scb2_flash mtd chipreg button i2c_piix4 i2c_core pcspkr tg3 mptspi mptscsih > mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd > [ 25.517918] > [ 25.517918] Pid: 1, comm: init Not tainted (2.6.25-rc2-mm1-autotest #1) > [ 25.517918] EIP: 0060:[] EFLAGS: 00010282 CPU: 2 > [ 25.517918] EIP is at proc_flush_task+0x5b/0x223 > [ 25.517918] EAX: 9d74e35b EBX: f7881ef0 ECX: f7a5ed84 EDX: a56b6b6b > [ 25.517918] ESI: f74f76f8 EDI: a56b6b6b EBP: f7881f08 ESP: f7881ec0 > [ 25.517918] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 > [ 25.517918] Process init (pid: 1, ti=f7881000 task=f788adf0 > task.ti=f7881000) > [ 25.517918] Stack: f7a5ed84 0001 f7a5ed58 f7a5ed58 a56b6b6b > f7852750 f7a5ed68 > [ 25.517918]35881ef4 3130 f788b4a4 f788adf0 0012d6c5 0003 > f7881ee3 0003 > [ 25.517918]f7a72df0 f7a72df0 f7881f1c c042676d 0003 01f5 > f7a72df0 f7881f78 > [ 25.517918] Call Trace: > [ 25.517918] [] release_task+0x19/0x2d5 > [ 25.517918] [] do_wait+0x5f2/0x8fc > [ 25.517918] [] default_wake_function+0x0/0xd > [ 25.517918] [] sys_wait4+0x78/0x8e > [ 25.517918] [] sys_waitpid+0x13/0x15 > [ 25.517918] [] sysenter_past_esp+0x5f/0x99 > [ 25.517918] === > [ 25.517918] Code: 1c 89 4d d4 89 4d c4 89 55 b8 e9 b5 01 00 00 31 ff 83 7d > c4 00 74 06 8b 45 d4 8b 78 1c 8b 55 b8 8b 4d b8 8b 12 89 55 cc 8b 41 04 <8b> > 40 20 52 68 33 cd 6f c0 6a 0d 89 45 d0 8d 45 db 50 89 45 f0 Kamalesh, could you send me the output of "objdump -d fs/proc/base.o" ? and just in case, fs/proc/base.s (make fs/proc/base.s). Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On 02/17, Kamalesh Babulal wrote: There has been discussion on the patch for this panic on http://lkml.org/lkml/2008/2/16/99 This looks similar... [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b [ 25.514926] IP: [c04a8fac] proc_flush_task+0x5b/0x223 [ 25.516934] Oops: [#1] SMP [ 25.517918] last sysfs file: /sys/block/hdc/removable [ 25.517918] Modules linked in: dm_mirror dm_mod video output sbs sbshc battery ac parport_pc lp parport floppy sg serio_raw ide_cd_mod cdrom scb2_flash mtd chipreg button i2c_piix4 i2c_core pcspkr tg3 mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd [ 25.517918] [ 25.517918] Pid: 1, comm: init Not tainted (2.6.25-rc2-mm1-autotest #1) [ 25.517918] EIP: 0060:[c04a8fac] EFLAGS: 00010282 CPU: 2 [ 25.517918] EIP is at proc_flush_task+0x5b/0x223 [ 25.517918] EAX: 9d74e35b EBX: f7881ef0 ECX: f7a5ed84 EDX: a56b6b6b [ 25.517918] ESI: f74f76f8 EDI: a56b6b6b EBP: f7881f08 ESP: f7881ec0 [ 25.517918] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 25.517918] Process init (pid: 1, ti=f7881000 task=f788adf0 task.ti=f7881000) [ 25.517918] Stack: f7a5ed84 0001 f7a5ed58 f7a5ed58 a56b6b6b f7852750 f7a5ed68 [ 25.517918]35881ef4 3130 f788b4a4 f788adf0 0012d6c5 0003 f7881ee3 0003 [ 25.517918]f7a72df0 f7a72df0 f7881f1c c042676d 0003 01f5 f7a72df0 f7881f78 [ 25.517918] Call Trace: [ 25.517918] [c042676d] release_task+0x19/0x2d5 [ 25.517918] [c042701b] do_wait+0x5f2/0x8fc [ 25.517918] [c041d9e7] default_wake_function+0x0/0xd [ 25.517918] [c042739d] sys_wait4+0x78/0x8e [ 25.517918] [c04273c6] sys_waitpid+0x13/0x15 [ 25.517918] [c04039ba] sysenter_past_esp+0x5f/0x99 [ 25.517918] === [ 25.517918] Code: 1c 89 4d d4 89 4d c4 89 55 b8 e9 b5 01 00 00 31 ff 83 7d c4 00 74 06 8b 45 d4 8b 78 1c 8b 55 b8 8b 4d b8 8b 12 89 55 cc 8b 41 04 8b 40 20 52 68 33 cd 6f c0 6a 0d 89 45 d0 8d 45 db 50 89 45 f0 Kamalesh, could you send me the output of objdump -d fs/proc/base.o ? and just in case, fs/proc/base.s (make fs/proc/base.s). Oleg. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
Andrew Morton wrote: > On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote: > >> Hi Andrew, >> >> The signals-do_signal_stop-use-signal_group_exit.patch is causing the >> kernel panic, while booting in to the 2.6.25-rc2-mm1 kernel on x86. >> >> There has been discussion on the patch for this panic on >> http://lkml.org/lkml/2008/2/16/99 >> >> [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b >> [ 25.514926] IP: [] proc_flush_task+0x5b/0x223 >> [ 25.516934] Oops: [#1] SMP >> [ 25.517918] last sysfs file: /sys/block/hdc/removable >> [ 25.517918] Modules linked in: dm_mirror dm_mod video output sbs sbshc >> battery ac parport_pc lp parport floppy sg serio_raw ide_cd_mod cdrom >> scb2_flash mtd chipreg button i2c_piix4 i2c_core pcspkr tg3 mptspi mptscsih >> mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd >> uhci_hcd >> [ 25.517918] >> [ 25.517918] Pid: 1, comm: init Not tainted (2.6.25-rc2-mm1-autotest #1) >> [ 25.517918] EIP: 0060:[] EFLAGS: 00010282 CPU: 2 >> [ 25.517918] EIP is at proc_flush_task+0x5b/0x223 >> [ 25.517918] EAX: 9d74e35b EBX: f7881ef0 ECX: f7a5ed84 EDX: a56b6b6b >> [ 25.517918] ESI: f74f76f8 EDI: a56b6b6b EBP: f7881f08 ESP: f7881ec0 >> [ 25.517918] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 >> [ 25.517918] Process init (pid: 1, ti=f7881000 task=f788adf0 >> task.ti=f7881000) >> [ 25.517918] Stack: f7a5ed84 0001 f7a5ed58 f7a5ed58 a56b6b6b >> f7852750 f7a5ed68 >> [ 25.517918]35881ef4 3130 f788b4a4 f788adf0 0012d6c5 0003 >> f7881ee3 0003 >> [ 25.517918]f7a72df0 f7a72df0 f7881f1c c042676d 0003 01f5 >> f7a72df0 f7881f78 >> [ 25.517918] Call Trace: >> [ 25.517918] [] release_task+0x19/0x2d5 >> [ 25.517918] [] do_wait+0x5f2/0x8fc >> [ 25.517918] [] default_wake_function+0x0/0xd >> [ 25.517918] [] sys_wait4+0x78/0x8e >> [ 25.517918] [] sys_waitpid+0x13/0x15 >> [ 25.517918] [] sysenter_past_esp+0x5f/0x99 >> [ 25.517918] === >> [ 25.517918] Code: 1c 89 4d d4 89 4d c4 89 55 b8 e9 b5 01 00 00 31 ff 83 >> 7d c4 00 74 06 8b 45 d4 8b 78 1c 8b 55 b8 8b 4d b8 8b 12 89 55 cc 8b 41 04 >> <8b> 40 20 52 68 33 cd 6f c0 6a 0d 89 45 d0 8d 45 db 50 89 45 f0 >> [ 25.517918] EIP: [] proc_flush_task+0x5b/0x223 SS:ESP >> 0068:f7881ec0 >> [ 25.517939] ---[ end trace d0df919a64605019 ]--- >> [ 25.518925] Kernel panic - not syncing: Attempted to kill init! >> > > hm, are you sure that signals-do_signal_stop-use-signal_group_exit.patch > causes this oops? sorry signals-do_signal_stop-use-signal_group_exit.patch is not causing the problem, not sure of what is causing this panic :-( -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote: > Hi Andrew, > > The signals-do_signal_stop-use-signal_group_exit.patch is causing the > kernel panic, while booting in to the 2.6.25-rc2-mm1 kernel on x86. > > There has been discussion on the patch for this panic on > http://lkml.org/lkml/2008/2/16/99 > > [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b > [ 25.514926] IP: [] proc_flush_task+0x5b/0x223 > [ 25.516934] Oops: [#1] SMP > [ 25.517918] last sysfs file: /sys/block/hdc/removable > [ 25.517918] Modules linked in: dm_mirror dm_mod video output sbs sbshc > battery ac parport_pc lp parport floppy sg serio_raw ide_cd_mod cdrom > scb2_flash mtd chipreg button i2c_piix4 i2c_core pcspkr tg3 mptspi mptscsih > mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd > [ 25.517918] > [ 25.517918] Pid: 1, comm: init Not tainted (2.6.25-rc2-mm1-autotest #1) > [ 25.517918] EIP: 0060:[] EFLAGS: 00010282 CPU: 2 > [ 25.517918] EIP is at proc_flush_task+0x5b/0x223 > [ 25.517918] EAX: 9d74e35b EBX: f7881ef0 ECX: f7a5ed84 EDX: a56b6b6b > [ 25.517918] ESI: f74f76f8 EDI: a56b6b6b EBP: f7881f08 ESP: f7881ec0 > [ 25.517918] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 > [ 25.517918] Process init (pid: 1, ti=f7881000 task=f788adf0 > task.ti=f7881000) > [ 25.517918] Stack: f7a5ed84 0001 f7a5ed58 f7a5ed58 a56b6b6b > f7852750 f7a5ed68 > [ 25.517918]35881ef4 3130 f788b4a4 f788adf0 0012d6c5 0003 > f7881ee3 0003 > [ 25.517918]f7a72df0 f7a72df0 f7881f1c c042676d 0003 01f5 > f7a72df0 f7881f78 > [ 25.517918] Call Trace: > [ 25.517918] [] release_task+0x19/0x2d5 > [ 25.517918] [] do_wait+0x5f2/0x8fc > [ 25.517918] [] default_wake_function+0x0/0xd > [ 25.517918] [] sys_wait4+0x78/0x8e > [ 25.517918] [] sys_waitpid+0x13/0x15 > [ 25.517918] [] sysenter_past_esp+0x5f/0x99 > [ 25.517918] === > [ 25.517918] Code: 1c 89 4d d4 89 4d c4 89 55 b8 e9 b5 01 00 00 31 ff 83 7d > c4 00 74 06 8b 45 d4 8b 78 1c 8b 55 b8 8b 4d b8 8b 12 89 55 cc 8b 41 04 <8b> > 40 20 52 68 33 cd 6f c0 6a 0d 89 45 d0 8d 45 db 50 89 45 f0 > [ 25.517918] EIP: [] proc_flush_task+0x5b/0x223 SS:ESP > 0068:f7881ec0 > [ 25.517939] ---[ end trace d0df919a64605019 ]--- > [ 25.518925] Kernel panic - not syncing: Attempted to kill init! > hm, are you sure that signals-do_signal_stop-use-signal_group_exit.patch causes this oops? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote: Hi Andrew, The signals-do_signal_stop-use-signal_group_exit.patch is causing the kernel panic, while booting in to the 2.6.25-rc2-mm1 kernel on x86. There has been discussion on the patch for this panic on http://lkml.org/lkml/2008/2/16/99 [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b [ 25.514926] IP: [c04a8fac] proc_flush_task+0x5b/0x223 [ 25.516934] Oops: [#1] SMP [ 25.517918] last sysfs file: /sys/block/hdc/removable [ 25.517918] Modules linked in: dm_mirror dm_mod video output sbs sbshc battery ac parport_pc lp parport floppy sg serio_raw ide_cd_mod cdrom scb2_flash mtd chipreg button i2c_piix4 i2c_core pcspkr tg3 mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd [ 25.517918] [ 25.517918] Pid: 1, comm: init Not tainted (2.6.25-rc2-mm1-autotest #1) [ 25.517918] EIP: 0060:[c04a8fac] EFLAGS: 00010282 CPU: 2 [ 25.517918] EIP is at proc_flush_task+0x5b/0x223 [ 25.517918] EAX: 9d74e35b EBX: f7881ef0 ECX: f7a5ed84 EDX: a56b6b6b [ 25.517918] ESI: f74f76f8 EDI: a56b6b6b EBP: f7881f08 ESP: f7881ec0 [ 25.517918] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 25.517918] Process init (pid: 1, ti=f7881000 task=f788adf0 task.ti=f7881000) [ 25.517918] Stack: f7a5ed84 0001 f7a5ed58 f7a5ed58 a56b6b6b f7852750 f7a5ed68 [ 25.517918]35881ef4 3130 f788b4a4 f788adf0 0012d6c5 0003 f7881ee3 0003 [ 25.517918]f7a72df0 f7a72df0 f7881f1c c042676d 0003 01f5 f7a72df0 f7881f78 [ 25.517918] Call Trace: [ 25.517918] [c042676d] release_task+0x19/0x2d5 [ 25.517918] [c042701b] do_wait+0x5f2/0x8fc [ 25.517918] [c041d9e7] default_wake_function+0x0/0xd [ 25.517918] [c042739d] sys_wait4+0x78/0x8e [ 25.517918] [c04273c6] sys_waitpid+0x13/0x15 [ 25.517918] [c04039ba] sysenter_past_esp+0x5f/0x99 [ 25.517918] === [ 25.517918] Code: 1c 89 4d d4 89 4d c4 89 55 b8 e9 b5 01 00 00 31 ff 83 7d c4 00 74 06 8b 45 d4 8b 78 1c 8b 55 b8 8b 4d b8 8b 12 89 55 cc 8b 41 04 8b 40 20 52 68 33 cd 6f c0 6a 0d 89 45 d0 8d 45 db 50 89 45 f0 [ 25.517918] EIP: [c04a8fac] proc_flush_task+0x5b/0x223 SS:ESP 0068:f7881ec0 [ 25.517939] ---[ end trace d0df919a64605019 ]--- [ 25.518925] Kernel panic - not syncing: Attempted to kill init! hm, are you sure that signals-do_signal_stop-use-signal_group_exit.patch causes this oops? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG] 2.6.25-rc2-mm1 - Kernel panic while bootup caused by signal_group_exit()
Andrew Morton wrote: On Sun, 17 Feb 2008 09:40:33 +0530 Kamalesh Babulal [EMAIL PROTECTED] wrote: Hi Andrew, The signals-do_signal_stop-use-signal_group_exit.patch is causing the kernel panic, while booting in to the 2.6.25-rc2-mm1 kernel on x86. There has been discussion on the patch for this panic on http://lkml.org/lkml/2008/2/16/99 [ 25.512919] BUG: unable to handle kernel paging request at 9d74e37b [ 25.514926] IP: [c04a8fac] proc_flush_task+0x5b/0x223 [ 25.516934] Oops: [#1] SMP [ 25.517918] last sysfs file: /sys/block/hdc/removable [ 25.517918] Modules linked in: dm_mirror dm_mod video output sbs sbshc battery ac parport_pc lp parport floppy sg serio_raw ide_cd_mod cdrom scb2_flash mtd chipreg button i2c_piix4 i2c_core pcspkr tg3 mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd [ 25.517918] [ 25.517918] Pid: 1, comm: init Not tainted (2.6.25-rc2-mm1-autotest #1) [ 25.517918] EIP: 0060:[c04a8fac] EFLAGS: 00010282 CPU: 2 [ 25.517918] EIP is at proc_flush_task+0x5b/0x223 [ 25.517918] EAX: 9d74e35b EBX: f7881ef0 ECX: f7a5ed84 EDX: a56b6b6b [ 25.517918] ESI: f74f76f8 EDI: a56b6b6b EBP: f7881f08 ESP: f7881ec0 [ 25.517918] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 25.517918] Process init (pid: 1, ti=f7881000 task=f788adf0 task.ti=f7881000) [ 25.517918] Stack: f7a5ed84 0001 f7a5ed58 f7a5ed58 a56b6b6b f7852750 f7a5ed68 [ 25.517918]35881ef4 3130 f788b4a4 f788adf0 0012d6c5 0003 f7881ee3 0003 [ 25.517918]f7a72df0 f7a72df0 f7881f1c c042676d 0003 01f5 f7a72df0 f7881f78 [ 25.517918] Call Trace: [ 25.517918] [c042676d] release_task+0x19/0x2d5 [ 25.517918] [c042701b] do_wait+0x5f2/0x8fc [ 25.517918] [c041d9e7] default_wake_function+0x0/0xd [ 25.517918] [c042739d] sys_wait4+0x78/0x8e [ 25.517918] [c04273c6] sys_waitpid+0x13/0x15 [ 25.517918] [c04039ba] sysenter_past_esp+0x5f/0x99 [ 25.517918] === [ 25.517918] Code: 1c 89 4d d4 89 4d c4 89 55 b8 e9 b5 01 00 00 31 ff 83 7d c4 00 74 06 8b 45 d4 8b 78 1c 8b 55 b8 8b 4d b8 8b 12 89 55 cc 8b 41 04 8b 40 20 52 68 33 cd 6f c0 6a 0d 89 45 d0 8d 45 db 50 89 45 f0 [ 25.517918] EIP: [c04a8fac] proc_flush_task+0x5b/0x223 SS:ESP 0068:f7881ec0 [ 25.517939] ---[ end trace d0df919a64605019 ]--- [ 25.518925] Kernel panic - not syncing: Attempted to kill init! hm, are you sure that signals-do_signal_stop-use-signal_group_exit.patch causes this oops? sorry signals-do_signal_stop-use-signal_group_exit.patch is not causing the problem, not sure of what is causing this panic :-( -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
