lkml.org 
[lkml]   [2000]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: nbd problems under 2.3.48
[ Friday, March  3, 2000 ] Pavel Machek wrote:
> Try passing explicit size to mke2fs.

Thanks! I'll give that a shot :)

I had tried the NBD remotely the first time. On another machine, I
tried it on the console and caught an oops. The oops itself (which
happened upon invoking nbd-client) and the ksymoops output is attached.

Upon looking through the log of the original machine, it had an oops
caused by nbd-server, but not enough in the log output to ksymoops it
(strangely)

Mar 2 23:04:42 jmm kernel: nbd: registered device at major 43
Mar 2 23:05:04 jmm nbd_server[1875]: connect from 127.0.0.1, assigned file is /tmp/delme
Mar 2 23:05:04 jmm nbd_server[1875]: size of exported file/device is 104521728
Mar 2 23:05:04 jmm kernel: Unable to handle kernel NULL pointer dereference at
virtual address 00000010
Mar 2 23:05:04 jmm kernel: printing eip:
Mar 2 23:05:04 jmm kernel: d087f886
Mar 2 23:05:04 jmm kernel: *pde = 00000000
Mar 2 23:05:04 jmm kernel: Oops: 0000
Mar 2 23:05:04 jmm kernel: CPU: 0
Mar 2 23:05:04 jmm nbd_server[1875]: Read failed: Success

James
[root@jmm-nt linux]# nbd-client localhost 1024 /dev/nd0
Negotiation: ..size = 104857600
Unable to handle kernel NULL pointer dereference at virtual address 00000010
printing eip:
c8817886
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c8817886>]
EFLAGS: 00010217
eax: c8819700 ebx: c88196c0 ecx: c88196d8 edx: 00200000
esi: c4e4c000 edi: 00000000 ebp: c88196c0 esp: c4e4df14
ds: 0018 es: 0018 ss: 0018
Process nbd-client (pid: 3210, stackpage=c4e4d000)
Stack: c88196c0 c4e4c000 c88196e0 c8819700 c88196d8 c8817d81 c88196c0 c5179440
40106a2c ffffffe7 c4e4c000 c8819700 c4e4c000 c7dcb988 c7dcb988 c4e4df50
00000000 c01835f8 c7dcb000 c7d96a20 00000000 00000000 c014624e c4cec200
Call Trace: [<c88196c0>] [<c88196e0>] [<c8819700>] [<c88196d8>] [<c8817d81>] [<c88196c0>] [<c8819700>]
[<c01835f8>] [<c014624e>] [<c014d827>] [<c010c01c>]
Code: 0f b6 47 10 89 c2 c1 e2 04 01 c2 c1 e2 02 89 d0 05 c0 96 81
Segmentation fault
ksymoops 0.7c on i686 2.3.48. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.3.48/ (default)
-m /usr/src/linux/System.map (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.

Unable to handle kernel NULL pointer dereference at virtual address 00000010
c8817886
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c8817886>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010217
eax: c8819700 ebx: c88196c0 ecx: c88196d8 edx: 00200000
esi: c4e4c000 edi: 00000000 ebp: c88196c0 esp: c4e4df14
ds: 0018 es: 0018 ss: 0018
Process nbd-client (pid: 3210, stackpage=c4e4d000)
Stack: c88196c0 c4e4c000 c88196e0 c8819700 c88196d8 c8817d81 c88196c0 c5179440
40106a2c ffffffe7 c4e4c000 c8819700 c4e4c000 c7dcb988 c7dcb988 c4e4df50
00000000 c01835f8 c7dcb000 c7d96a20 00000000 00000000 c014624e c4cec200
Call Trace: [<c88196c0>] [<c88196e0>] [<c8819700>] [<c88196d8>] [<c8817d81>] [<c88196c0>] [<c8819700>]
[<c01835f8>] [<c014624e>] [<c014d827>] [<c010c01c>]
Code: 0f b6 47 10 89 c2 c1 e2 04 01 c2 c1 e2 02 89 d0 05 c0 96 81

>>EIP; c8817886 <[nbd]nbd_clear_que+1e/108> <=====
Trace; c88196c0 <[nbd]nbd_dev+0/21ff>
Trace; c88196e0 <[nbd]nbd_dev+20/21ff>
Trace; c8819700 <[nbd]nbd_dev+40/21ff>
Trace; c88196d8 <[nbd]nbd_dev+18/21ff>
Trace; c8817d81 <[nbd]nbd_ioctl+151/4f0>
Trace; c88196c0 <[nbd]nbd_dev+0/21ff>
Trace; c8819700 <[nbd]nbd_dev+40/21ff>
Trace; c01835f8 <tty_write+324/418>
Trace; c014624e <blkdev_ioctl+26/30>
Trace; c014d827 <sys_ioctl+26b/324>
Trace; c010c01c <system_call+34/38>
Code; c8817886 <[nbd]nbd_clear_que+1e/108>
00000000 <_EIP>:
Code; c8817886 <[nbd]nbd_clear_que+1e/108> <=====
0: 0f b6 47 10 movzbl 0x10(%edi),%eax <=====
Code; c881788a <[nbd]nbd_clear_que+22/108>
4: 89 c2 mov %eax,%edx
Code; c881788c <[nbd]nbd_clear_que+24/108>
6: c1 e2 04 shl $0x4,%edx
Code; c881788f <[nbd]nbd_clear_que+27/108>
9: 01 c2 add %eax,%edx
Code; c8817891 <[nbd]nbd_clear_que+29/108>
b: c1 e2 02 shl $0x2,%edx
Code; c8817894 <[nbd]nbd_clear_que+2c/108>
e: 89 d0 mov %edx,%eax
Code; c8817896 <[nbd]nbd_clear_que+2e/108>
10: 05 c0 96 81 00 add $0x8196c0,%eax


1 warning issued. Results may not be reliable.
\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.047 / U:0.656 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site