I know mamma told me I shouldn't be doing these funny things, but I
couldn't resist.. Anyway, here it goes:
#modprobe aha152x
aha152x: BIOS test: Blah, blah, blah... (loaded ok)
#cd /proc/scsci/aha152x
#rmmod aha152x
#ls -l
[Oops at this point.. I'm sending the ksymoops results only. Should I
send the oops itself also ?]
Using `System.map' to map addresses to symbols.
>>EIP: c0143edd <proc_readdir+7d/118>
Trace: c012f229 <sys_getdents+f5/18c>
Trace: c012f0b0 <filldir>
Trace: c0143edd <proc_readdir+7d/118>
Trace: c0107afc <system_call+34/38>
Code: c0143edd <proc_readdir+7d/118>
Code: c0143edd <proc_readdir+7d/118> 8b 53 24 movl 0x24(%ebx),%edx
Code: c0143ee0 <proc_readdir+80/118> 0f b7 12 movzwl (%edx),%edx
Code: c0143ee3 <proc_readdir+83/118> 52 pushl %edx
Code: c0143ee4 <proc_readdir+84/118> 56 pushl %esi
Code: c0143ee5 <proc_readdir+85/118> 6a 02 pushl $0x2
Code: c0143ee7 <proc_readdir+87/118> 68 86 aa 1a c0 pushl $0xc01aaa86
Code: c0143eec <proc_readdir+8c/118> 8b 4c 24 28 movl0x28(%esp,1),%ecx
Code: c0143ef0 <proc_readdir+90/118> 51 pushl %ecx
Well, wouldn't something like 'ls: .: No such file or directory'
be a bit nicer than an oops ? I guess (a REALLY, REALLY WILD GUESS, mind
you) the problem is on the /proc fs layer itself.. Am I right ?
Still on the subject, killing a process when you're under /proc/PID/ also
does some funny stuffs but no oops...
All the best,
Renato Moutinho Silva - rmsilva@ruralrj.com.br
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/