From: James S. <mi...@st...> - 2001-04-06 04:50:09
|
Hi just after these appear i get a panic Remounting root filesystem read-only. Power down. i will look into it later i got other stuff todo (gdb) i line *268704827 Line 389 of "generic.c" starts at address 0x10041c3b <proc_kill_inodes+15> and ends at 0x10041c47 <proc_kill_inodes+27>. #0 panic (fmt=0x1011fc60 "Kernel mode fault at addr 0x%lx, ip 0x%lx") at panic.c:54 #1 0x100a8ab7 in segv (address=1515870874, ip=268704827, is_write=0, is_user=0) at trap_kern.c:54 #2 0x100a932e in segv_handler (sig=11, sc=0x50fcbc50, usermode=0) at trap_user.c:295 #3 0x100a9426 in sig_handler (sig=11) at trap_user.c:340 #4 <signal handler called> #5 0x888189 in ?? () #6 0x100420fd in remove_proc_entry (name=0x10119604 "max_dgram_qlen", parent=0x500bfc2c) at generic.c:573 #7 0x1000f1d3 in unregister_proc_table (table=0x1013c7cc, root=0x500bfc2c) at sysctl.c:671 #8 0x1000f1af in unregister_proc_table (table=0x1013c824, root=0x500f7b84) at sysctl.c:659 #9 0x1000f1af in unregister_proc_table (table=0x1013c87c, root=0x5006bdec) at sysctl.c:659 #10 0x1000f04b in unregister_sysctl_table (header=0x5006c294) at sysctl.c:585 #11 0x1009b26a in unix_sysctl_unregister () at sysctl_net_unix.c:43 #12 0x100f2cb7 in af_unix_exit () at af_unix.c:1882 #13 0x100ab5f5 in do_exitcalls () at process_kern.c:807 #14 0x100a6b9d in machine_power_off () at reboot.c:34 #15 0x100145c3 in sys_reboot (magic1=-18751827, magic2=672274793, cmd=1126301404, arg=0xbf7ffed8) at sys.c:309 #16 0x100a79f0 in execute_syscall (regs={regs = {4276215469, 672274793, 1126301404, 3212836568, 4276215469, 3212836204, 4294967258, 43, 43, 0, 0, 88, 1074514449, 35, 518, 3212836188, 43}}) at syscall_kern.c:348 #17 0x100a7afa in syscall_handler (unused=0x0) at syscall_user.c:73 thanks James -- --------------------------------------------- Check Out: http://stev.org E-Mail: mi...@st... 8:00pm up 10 days, 3:55, 5 users, load average: 2.83, 1.64, 1.65 |
From: James S. <mi...@st...> - 2001-04-26 16:07:55
|
Hi this seems to happen to me every time i try to shutdown / reboot uml heres a stack trace #0 panic (fmt=0x1011fe20 "Kernel mode fault at addr 0x%lx, ip 0x%lx") at panic.c:54 #1 0x100a8cbe in segv (address=1515870882, ip=268705419, is_write=0, is_user=0) at trap_kern.c:54 #2 0x100a95de in segv_handler (sig=11, sc=0x516afc50, usermode=0) at trap_user.c:303 #3 0x100a969b in sig_handler (sig=11) at trap_user.c:342 #4 <signal handler called> #5 0x888189 in ?? () #6 0x1004234d in remove_proc_entry (name=0x10119824 "max_dgram_qlen", parent=0x500bfc2c) at generic.c:573 #7 0x1000f223 in unregister_proc_table (table=0x1013c7ec, root=0x500bfc2c) at sysctl.c:671 #8 0x1000f1ff in unregister_proc_table (table=0x1013c844, root=0x500f7b84) at sysctl.c:659 #9 0x1000f1ff in unregister_proc_table (table=0x1013c89c, root=0x5006bdec) at sysctl.c:659 #10 0x1000f09b in unregister_sysctl_table (header=0x5006c294) at sysctl.c:585 #11 0x1009b67a in unix_sysctl_unregister () at sysctl_net_unix.c:43 #12 0x100f2f13 in af_unix_exit () at af_unix.c:1882 #13 0x100ab935 in do_exitcalls () at process_kern.c:788 #14 0x100a6d7d in machine_restart (__unused=0x0) at reboot.c:26 #15 0x100145df in sys_reboot (magic1=-18751827, magic2=672274793, cmd=19088743, arg=0xbf7ffed5) at sys.c:288 #16 0x100a7c20 in execute_syscall (regs={regs = {4276215469, 672274793, 19088743, 3212836565, 4276215469, 3212836188, 4294967258, 43, 43, 0, 0, 88, 1074514449, 35, 518, 3212836172, 43}}) at syscall_kern.c:348 #17 0x100a7d28 in syscall_handler (unused=0x0) at syscall_user.c:73 -- --------------------------------------------- Check Out: http://stev.org E-Mail: mi...@st... 5:10pm up 2 days, 3:58, 5 users, load average: 2.04, 2.48, 2.85 |
From: Jeff D. <jd...@ka...> - 2001-04-26 17:07:57
|
lis...@os... said: > The bad news is.... > Kernel panic: Kernel mode fault at addr 0x5a5a5aa2, ip 0x10045718 mi...@st... said: > heres a stack trace > #0 panic (fmt=0x1011fe20 "Kernel mode fault at addr 0x%lx, ip 0x%lx") > at panic.c:54 Can you guys turn on DEBUG in mm/slab.c and see if that catches anything? Jeff |
From: James S. <mi...@st...> - 2001-04-26 18:16:18
|
Hi it was already on and it did not catch anything On Thu, 26 Apr 2001, Jeff Dike wrote: > lis...@os... said: > > The bad news is.... > > Kernel panic: Kernel mode fault at addr 0x5a5a5aa2, ip 0x10045718 > > mi...@st... said: > > heres a stack trace > > #0 panic (fmt=0x1011fe20 "Kernel mode fault at addr 0x%lx, ip 0x%lx") > > at panic.c:54 > > Can you guys turn on DEBUG in mm/slab.c and see if that catches anything? > > Jeff > > -- --------------------------------------------- Check Out: http://stev.org E-Mail: mi...@st... 7:20pm up 2 days, 6:08, 5 users, load average: 1.76, 1.49, 1.51 |
From: <lis...@os...> - 2001-04-26 22:41:27
|
Jeff Dike writes: > lis...@os... said: > > The bad news is.... > > Kernel panic: Kernel mode fault at addr 0x5a5a5aa2, ip 0x10045718 > > mi...@st... said: > > heres a stack trace > > #0 panic (fmt=0x1011fe20 "Kernel mode fault at addr 0x%lx, ip 0x%lx") > > at panic.c:54 > > Can you guys turn on DEBUG in mm/slab.c and see if that catches anything? Like this? #define DEBUG 1 #define STATS 0 #define FORCED_DEBUG 1 I always have it on. |
From: James S. <mi...@st...> - 2001-04-26 23:17:28
|
yes its like that it was already on and i did not enable it > > Like this? > > #define DEBUG 1 > #define STATS 0 > #define FORCED_DEBUG 1 > > > I always have it on. > -- --------------------------------------------- Check Out: http://stev.org E-Mail: mi...@st... 12:20am up 2 days, 11:08, 6 users, load average: 0.00, 0.14, 0.13 |
From: Andrew M. <an...@uo...> - 2001-04-27 16:52:39
|
James Stevenson wrote: > > Hi > > this seems to happen to me every time i try to shutdown / reboot > uml > It's happening because the /proc filesystem is being shut down *before* the nfs /proc entries are unregistered. UML is the only architecture which implements exitcalls for non-modules. Seems logical that they should be run in reverse order, and this indeed fixes the problem. --- linux-2.4.3-ac14/arch/um/kernel/process_kern.c Wed Apr 25 23:43:58 2001 +++ um/arch/um/kernel/process_kern.c Fri Apr 27 09:42:55 2001 @@ -783,11 +783,9 @@ { exitcall_t *call; - call = &__exitcall_begin; - do { + call = &__exitcall_end; + while (--call >= &__exitcall_begin) (*call)(); - call++; - } while (call < &__exitcall_end); } void *round_up(unsigned long addr) BTW: is there a known-to-be-good version or gdb? I'm seeing some strange happenings with the gdb-5.0rh-3 rpm from this rather mixed-up redhat 7.0.93 system. * sending SIGUSR1 to the tracing thread causes "error stat'ing /dev/pts/p6: No such file or directory to come out on the uml console. * A number of gdb operations cause the message "Couldn't read floating-point and SSE registers: Invalid argument." to come out in the gdb xterm. * detaching from the tracing thread and attaching to a new one seems to not work. Both gdb and uml hang up. |
From: Henrik N. <hn...@ma...> - 2001-04-27 17:16:39
|
Andrew Morton wrote: > James Stevenson wrote: > > > > Hi > > > > this seems to happen to me every time i try to shutdown / reboot > > uml > > > > It's happening because the /proc filesystem is being > shut down *before* the nfs /proc entries are unregistered. > > UML is the only architecture which implements exitcalls > for non-modules. Seems logical that they should be run > in reverse order, and this indeed fixes the problem. Confirmed to fix the same shutdown issue here.. thanks for finding the cause. but calling all exitcalls in reverse order is not a real fix to the problem I think. As far as I know exitcalls are not really ordered, they just gets called in the order they happened to get linked in.. Or have I misunderstood the exitcall mechanism? -- Henrik Nordstrom |
From: <lis...@os...> - 2001-04-27 23:02:33
|
Andrew Morton writes: > James Stevenson wrote: > > > > Hi > > > > this seems to happen to me every time i try to shutdown / reboot > > uml > > > > It's happening because the /proc filesystem is being > shut down *before* the nfs /proc entries are unregistered. Not here; I am not using nfs, though I plan to. |
From: <lis...@os...> - 2001-04-28 15:08:09
|
Andrew Morton writes: > James Stevenson wrote: > > > > Hi > > > > this seems to happen to me every time i try to shutdown / reboot > > uml > > > > It's happening because the /proc filesystem is being > shut down *before* the nfs /proc entries are unregistered. > > UML is the only architecture which implements exitcalls > for non-modules. Seems logical that they should be run > in reverse order, and this indeed fixes the problem. > > > --- linux-2.4.3-ac14/arch/um/kernel/process_kern.c Wed Apr 25 23:43:58 2001 > +++ um/arch/um/kernel/process_kern.c Fri Apr 27 09:42:55 2001 Could I point out this advice? NOTES FOR PATCH SENDERS There are several things you should bear in mind if you are going to be sending out patches. Create your patch systematically. A good method is the command diff -Naur old new <snip> If the recipient is supposed to use the -pN option, do not send output that looks like this: diff -Naur v2.0.29/prog/README prog/README --- v2.0.29/prog/README Mon Mar 10 15:13:12 1997 +++ prog/README Mon Mar 17 14:58:22 1997 because the two file names have different numbers of slashes, and different versions of patch interpret the file names differently. To avoid confusion, send output that looks like this instead: diff -Naur v2.0.29/prog/README v2.0.30/prog/README --- v2.0.29/prog/README Mon Mar 10 15:13:12 1997 +++ v2.0.30/prog/README Mon Mar 17 14:58:22 1997 It's to be found in "man patch" and I recommend all who plan to create patches read it. |