Hi, On Mon, Mar 26, 2007 at 09:16:27PM -0800, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc5/2.6.21-rc5-mm2/ > > > - This is the same as 2.6.12-rc5-mm1, except the staircase deadline CPU > scheduler has been added.
OOPS (hand-pasted), happens on roughly 85% of bootups, didn't seem to occur during my several previous 2.6.21-rc4-mm1 bootups: ----- ... Setting up ICE socket directory /tmp/.ICE-unix...done. BUG: unable to handle kernel NULL pointer dereference at virtual address 00000024 !!!!! ======> last sysfs file: block/loop7/removable <======= Process init trace: show_trace_log_lvl+0x1a show_stack_log_lvl+0x9d show_registers+0x1c0 die+0xe5 do_page_fault+0x432 error_code+0x71 sysfs_drop_dentry+0x30 sysfs_hash_and_remove+0x8e sysfs_remove_file+0xd device_remove_file+0x1c device_del+0x1ed device_unregister+0x26 device_destroy+0x8a vcs_remove_sysfs+0x1a con_close+0x4c release_dev+0x1f0 tty_release+0xa __fput+0xb8 fput+0x31 filp_close+0x54 put_files_struct+0x7c do_exit+0x1e3 sys_exit_group+0x0 sys_exit_group+0xf syscall_call+0x7 EIP: __iget+0x6 Fixing recursive fault but reboot is needed! ----- Any hints? Possibly existing bug surfaced due to RSDL scheduling timing differences? I did NOT test -mm1 to check this. P3/700 UP i815 IDE ext3, Debian unstable. Further .config available on request. Note that something killed my /bin/run-parts (Debian) and S10portmap files (and possibly some others are corrupted??), so it might be something fishy (but this fishiness could also have uncovered this OOPS, so...). Restoring those files didn't change the status quo. CC'd relevant maintainers/recent submitters. Andreas Mohr - 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/
