Opened 13 years ago

Closed 8 weeks ago

#4756 closed bug (invalid)

Panic with r33489 (did not with alpha) on Acer Aspire One netbook

Reported by: olaf Owned by: nobody
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #8326
Platform: x86

Description (last modified by umccullough)

Using the hrev33489 nightly (for October 9th) causes a panic when the alpha did not. I think the October 7th and October 6th probably did too (I don't remember which one it was, but I used that image as well and panicked). This is on my Acer Aspire One (model AOA150-1786) using the ggc2hybrid raw image on a 8GB SanDisk Cruzer. I booted and installed the alpha with this same drive. Haiku starts to boot as normal and displays the Deskbar but (I think before the desktop icons are displayed) it panics.

If anymore information/testing is needed feel free to contact me. I will attach the panic message to this ticket as well as paste it below...

PANIC: transaction 728 aborted, inode 0x81024aa0 still around!

Welcome to Kernel Debugging Land...
Thread 12 "block notifier/writer" running on CPU 1
kdebug> bt
stack trace for thread 12 "block notifier/writer"
    kernel stack: 0x80198000 to 0x8019c000
frame               caller      <image>:function + offset
 0 8019b9cc (+  48) 80067628    <kernel_x86> invoke_command_trampoline(0x8019ba64) + 0x001c
 1 8019b9fc (+  12) 800e0cbb    <kernel_x86>:arch_debug_call_with_fault_handler + 0x001b
 2 8019ba08 (+  48) 80066408    <kernel_x86>:debug_call_with_fault_handler + 0x0054
 3 8019ba38 (+  64) 80067881    <kernel_x86>:invoke_debugger_command + 0x00b9
 4 8019ba78 (+  64) 800676ad    <kernel_x86> invoke_pipe_segment(debugger_command_pipe*: 0x82a54030, int32: 0, 0x0 "<NULL>") + 0x0079
 5 8019bab8 (+  64) 800679ec    <kernel_x86>:invoke_debugger_command_pipe + 0x009c
 6 8019baf8 (+  48) 800693e8    <kernel_x86> ExpressionParser<0x8019bba8>::_ParseCommandPipe(0x8019bba4) + 0x0234
 7 8019bb28 (+  64) 80068822    <kernel_x86> ExpressionParser<0x8019bba8>::EvaluateCommand(0x8012bca0 "bt", 0x8019bba4) + 0x02ba
 8 8019bb68 (+ 224) 8006a7fc    <kernel_x86>:evaluate_debug_command + 0x0080
 9 8019bc48 (+  64) 800653fa    <kernel_x86> kernel_debugger_loop(0x8019bd28 "transaction 728 aborted, inode 0x81024aa0 still around!
", int32: 1) + 0x0276
10 8019bc88 (+  48) 8006564e    <kernel_x86> kernel_debugger_internal(0x8019bd28 "transaction 728 aborted, inode 0x81024aa0 still around!
", int32: 1) + 0x0042
11 8019bcb8 (+  48) 800665bf    <kernel_x86>:kernel_debugger + 0x0023
12 8019bce8 (+ 192) 80066591    <kernel_x86>:panic + 0x0029
13 8019bda8 (+  48) 804c8d60    <bfs> InodeAllocator<0x000002d8>::_TransactionListener(int32: 2, int32: -2130556256, 0x800dd659) + 0x0030
14 8019bdd8 (+  96) 80030381    <kernel_x86> flush_pending_notifications(block_cache*: 0x80ebf348) + 0x01a1
15 8019be38 (+  64) 80030471    <kernel_x86> flush_pending_notifications() + 0x006d
16 8019be78 (+ 352) 8003276d    <kernel_x86> block_notifier_and_writer(NULL) + 0x0055
17 8019bfd8 (+  32) 8005954b    <kernel_x86> _create_kernel_thread_kentry() + 0x001b
18 8019bff8 (+2145796104) 800594e8    <kernel_x86> thread_kthread_exit() + 0x0000

Attachments (1)

panic.txt (2.2 KB ) - added by olaf 13 years ago.
Panic message and bt results

Download all attachments as: .zip

Change History (11)

by olaf, 13 years ago

Attachment: panic.txt added

Panic message and bt results

comment:1 by olaf, 13 years ago

FOR CLARITY: This is me booting hrev33489 from USB!

comment:2 by olaf, 13 years ago

btw my e-mail is olafcore@… if you have any questions about this or need me to run some tests

comment:3 by olaf, 13 years ago

olafcore/ @/ gmail/ .com/

comment:4 by umccullough, 13 years ago

Description: modified (diff)

comment:5 by umccullough, 13 years ago

hrev33489 gcc2hybrid nightly raw image works for my on my AOA150 1887 (1gb ram, 160gb HD)

I used a Patriot Mini 2gb stick and wrote the image with Win32DiskImager in windows.

comment:6 by olaf, 13 years ago

i tried with hrev33513 and it worked, the first time i had a couldn't mount boot drive error or something to that effect. the second time it booted fine. i'm not sure what's wrong, but i guess you can close this ticket?

comment:7 by axeld, 5 years ago

Blocking: 8326 added

(In #8326) Yep, seems to be the same issue as #4756; of course, it might be caused by a different issue, but that's impossible to tell from the available info.

comment:8 by axeld, 5 years ago

Owner: changed from axeld to nobody
Status: newassigned

comment:9 by bitigchi, 22 months ago

Is this still reproducible?

comment:10 by waddlesplash, 8 weeks ago

Resolution: invalid
Status: assignedclosed

No reply, closing.

Note: See TracTickets for help on using tickets.