Opened 11 years ago

Closed 11 years ago

#2576 closed bug (fixed)

[Tar] PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call

Reported by: scottmc Owned by: axeld
Priority: blocker Milestone: R1/alpha1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

On a fresh vmware development image, hrev26837, I downloaded a tarball of a port I was going to try, and when I tried to use expander to open it got dropped into KDL.

PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call

Welcome to Kernel Debugging Land...

Thread 193 "tar" running on CPU 0

PANIC: could not read block 5656: bytesRead: -1, error: Interrupted system call



Welcome to Kernel Debugging Land...

Thread 193 "tar" running on CPU 0

kdebug> bt

stack trace for thread 193 "tar"

    kernel stack: 0x929a0000 to 0x929a4000

      user stack: 0x7efef000 to 0x7ffef000

frame            caller     <image>:function + offset

 0 929a35f4 (+  48) 800544ed   <kernel>:invoke_debugger_command + 0x00ed

 1 929a3624 (+  64) 800542e5   <kernel>:invoke_pipe_segment__FP21debugger_command_pipelPc + 0x0079

 2 929a3664 (+  64) 8005462d   <kernel>:invoke_debugger_command_pipe + 0x009d

 3 929a36a4 (+  48) 80055508   <kernel>:_ParseCommandPipe__16ExpressionParserRi + 0x0234

 4 929a36d4 (+  48) 80054ebe   <kernel>:EvaluateCommand__16ExpressionParserPCcRi + 0x01de

 5 929a3704 (+ 224) 800568d4   <kernel>:evaluate_debug_command + 0x0088

 6 929a37e4 (+  64) 80052962   <kernel>:kernel_debugger_loop__Fv + 0x01ae

 7 929a3824 (+  48) 800534fb   <kernel>:kernel_debugger + 0x0117

 8 929a3854 (+ 192) 800533d9   <kernel>:panic + 0x0029

 9 929a3914 (+  96) 80029c40   <kernel>:get_cached_block__FP11block_cachexPbb + 0x015c

10 929a3974 (+  80) 8002ca42   <kernel>:block_cache_get_etc + 0x004e

11 929a39c4 (+  48) 8002caf4   <kernel>:block_cache_get + 0x0020

12 929a39f4 (+  96) 80586d39   <bfs>:InternalSetTo__10CachedNodeP11Transactionx + 0x014d

13 929a3a54 (+  48) 805867c9   <bfs>:SetTo__10CachedNodexb + 0x00d1

14 929a3a84 (+  64) 80587ff3   <bfs>:_FindFreeDuplicateFragment__9BPlusTreeR11TransactionPC14bplustree_nodeR10CachedNodePxPP14bplustree_nodePUl + 0x008b

15 929a3ac4 (+ 176) 80588548   <bfs>:_InsertDuplicate__9BPlusTreeR11TransactionR10CachedNodePC14bplustree_nodeUsx + 0x0494

16 929a3b74 (+ 480) 80589400   <bfs>:Insert__9BPlusTreeR11TransactionPCUcUsx + 0x0460

17 929a3d54 (+  80) 8058df05   <bfs>:Update__5IndexR11TransactionPCclPCUcUsT4UsP5Inode + 0x0245

18 929a3da4 (+  96) 8058e245   <bfs>:UpdateSize__5IndexR11TransactionP5Inode + 0x00a1

19 929a3e04 (+  96) 8059e9bd   <bfs>:bfs_free_cookie__FP9fs_volumeP8fs_vnodePv + 0x020d

20 929a3e64 (+  48) 80089d44   <kernel>:file_free_fd__FP15file_descriptor + 0x0028

21 929a3e94 (+  48) 80079a4c   <kernel>:put_fd + 0x0038

22 929a3ec4 (+  64) 80079b36   <kernel>:close_fd_index + 0x0032

23 929a3f04 (+  32) 8007a631   <kernel>:common_close__Fib + 0x0031

24 929a3f24 (+  32) 8007af08   <kernel>:_user_close + 0x0018

25 929a3f44 (+ 100) 800b6d42   <kernel>:pre_syscall_debug_done + 0x0002 (nearest)

user iframe at 0x929a3fa8 (end = 0x929a4000)

 eax 0x85           ebx 0x2f0b18        ecx 0x7ffeee10   edx 0xffff0104

 esi 0xf62          edi 0x1802e400      ebp 0x7ffeee3c   esp 0x929a3fdc

 eip 0xffff0104  eflags 0x207      user esp 0x7ffeee10

 vector: 0x63, error code: 0x0

26 929a3fa8 (+   0) ffff0104

27 7ffeee3c (+  80) 00211f20   <_APP_>:extr_init + 0x0f58 (nearest)

28 7ffeee8c (+  48) 00212c16   <_APP_>:extract_archive + 0x0176

29 7ffeeebc (+ 144) 0021851d   <_APP_>:read_and + 0x01a1

30 7ffeef4c (+  48) 002238c8   <_APP_>:main + 0x0178

31 7ffeef7c (+  48) 00208df7   <_APP_>:_start + 0x005b

32 7ffeefac (+  48) 001008ea   4421:runtime_loader_seg0ro@0x00100000 + 0x8ea

33 7ffeefdc (+   0) 7ffeefec   4420:tar_main_stack@0x7efef000 + 0xffffec

Attachments (2)

serial.txt (70.1 KB) - added by scottmc 11 years ago.
Here's the serial debug output, note that I typed reboot, and was able to get dumped in kdl by trying to unzip same file again.
serial-sh.txt (68.2 KB) - added by scottmc 11 years ago.
Here's the second serial log file, this time failing in the terminal when running ./configure

Download all attachments as: .zip

Change History (5)

Changed 11 years ago by scottmc

Attachment: serial.txt added

Here's the serial debug output, note that I typed reboot, and was able to get dumped in kdl by trying to unzip same file again.

comment:1 Changed 11 years ago by scottmc

Ok, so it's not just Tar that triggers this. I gunzipped and tar -xf'd it on the command line and then tried running ./configure and got the same panic but in "sh" just a few lines into the configure. Attaching a second serial log file.

Changed 11 years ago by scottmc

Attachment: serial-sh.txt added

Here's the second serial log file, this time failing in the terminal when running ./configure

comment:2 Changed 11 years ago by axeld

Component: - GeneralSystem/Kernel
Milestone: R1R1/alpha1
Priority: normalblocker

This might be a problem with how the I/O scheduler handles the OperationCompleted() method.

comment:3 Changed 11 years ago by bonefish

Resolution: fixed
Status: newclosed

Fixed in hrev26850.

Note: See TracTickets for help on using tickets.