Messages in this thread | | | Subject | Re: PROBLEM: 2.2.18 oops leaves umount hung in disk sleep | From | Trond Myklebust <> | Date | 22 Mar 2001 23:09:13 +0100 |
| |
>>>>> " " == Camm Maguire <camm@enhanced.com> writes:
> I'd be happy to generate one if I could. I've got the system > map. The defaults reported by ksymoops are all correct. Don't > know why it didn't give me more info. Normally, the info is > reported by klogd anyway, but not here. I've sent you all I > currently have. If you can suggest how I can get more, would > be glad to do so.
Unless you happen to have a dump from 'dmesg', there's probably not much you can do to recover the rest of the Oops...
We need at least the line 'EIP:' if we're to find out where the fault occurred. Are you certain that it can't be found in the syslog?
> I thought I was running v3. Can't seem to find anything now > which indicates the protocol version in use, but was under the > impression that v4 was only an option in 2.4.x, no?
Mar 21 01:14:49 intech9 automount[305]: using kernel protocol version 3 on reawaken
Sorry, the above message fooled me.
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/
| |