Messages in this thread | | | Date | Wed, 6 Feb 2008 00:24:20 -0800 | From | Andrew Morton <> | Subject | Re: OOPS in sysctl.c |
| |
On Tue, 5 Feb 2008 12:24:56 +0100 Holger Schurig <hs4233@mail.mn-solutions.de> wrote:
> > I have an embedded target (PXA255 based) where I have a nice > > running kernel 2.6.15. Today I'm trying to get 2.6.24 running > > on it. >
Backtrace: [<c0038bbc>] (sysctl_head_next+0x0/0x64) from [<c00a4b80>] (proc_sys_readdir+0x360/0x394) r4:00000000 [<c00a4820>] (proc_sys_readdir+0x0/0x394) from [<c007c860>] (vfs_readdir+0x70/0x98) [<c007c7f0>] (vfs_readdir+0x0/0x98) from [<c007cdf0>] (sys_getdents64+0x6c/0xc0) [<c007cd84>] (sys_getdents64+0x0/0xc0) from [<c0023e60>] (ret_fast_syscall+0x0/0x2c)
> Whatever the problem is, sysfs works now flawlessly even after > a suspend/resume with v2.6.24-7284-g9ef9dc6.
erp. We'd really like to know what we did to fix it, and then get that fix back into 2.6.24.x.
| |