Messages in this thread | | | Subject | Re: PROBLEM: 2.2.18 oops leaves umount hung in disk sleep | From | Trond Myklebust <> | Date | 22 Mar 2001 19:43:41 +0100 |
| |
>>>>> " " == Camm Maguire <camm@enhanced.com> writes:
> 2.2.18 oops leaves umount hung in disk sleep
This is normal behaviour for an Oops ;-)
> Unable to handle kernel NULL pointer dereference at > virtual address 00000000 current-> tss.cr3 = 02872000, %%cr3 = 02872000 > *pde = 00000000 Oops: 0000 CPU: 0
> intech9# ksymoops <oo.txt
> ksymoops 2.3.4 on i586 2.2.18-i586tsc. Options used -V > (default) -k /proc/ksyms (default) -l /proc/modules > (default) -o /lib/modules/2.2.18-i586tsc/ (default) -m > /boot/System.map-2.2.18-i586tsc (default)
> Warning: You did not tell me where to find symbol > information. I will assume that the log matches the > kernel and modules that are running right now and I'll use > the default options above for symbol resolution. If the > current kernel and/or modules do not match the log, you > can get more accurate output by telling me the kernel > version and where to find map, modules, ksyms etc. > ksymoops -h explains the options.
> Warning (compare_maps): ksyms_base symbol > module_list_R__ver_module_list not found in System.map. > Ignoring ksyms_base entry > Unable to handle kernel NULL pointer dereference at > virtual address 00000000 current->tss.cr3 = 02872000, > %%cr3 = 02872000 *pde = 00000000 Oops: 0000 CPU: 0
Do you have the full ksymoops decode available? The above is somewhat minimal.
Also please could you try to duplicate the problem with a standard autofs v3 daemon? I'm not sure that the v4 'automount' is quite as well tested as the v3 daemon (it still seems to be in beta).
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |