[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-hackers-public] Re: [Urgent] Re: Savannah down
From: |
Justin Baugh |
Subject: |
[Savannah-hackers-public] Re: [Urgent] Re: Savannah down |
Date: |
Sat, 12 Mar 2005 11:40:01 -0500 (EST) |
User-agent: |
SquirrelMail/1.4.4 |
> Please reboot the machine asap. It should be broad day light in the US
> now, please hurry!
>
> --
> Sylvain
>
> On Sat, Mar 12, 2005 at 10:07:23AM +0100, Sylvain Beucler wrote:
>> Hello,
>>
>> Savannah appears to be down. Could you reboot it and investigate?
>>
>> Thanks,
>
Sylvain,
I was in the process of doing this when I received your second mail.
Unfortunately all I am able to retrieve right at this moment is a partial
trace of a kernel panic:
[<c010c8e2>] smp_apic_timer_interrupt+0xce/0xd4
[<c0102b4c>] apic_timer_interrupt+0x1c/0x24
[<c02d05d6>] _spin_lock+0xa/0x10
[<c0188f54>] journal_dirty_data+0x64/0x1d8
[<c017b72e>] ext3_journal_dirty_data+0x12/0x38
[<c017b58c>] walk_page_buffers+0x54/0x78
[<c017b7f5>] ext3_ordered_commit_write+0x51/0xb4
[<c017b71c>] ext3_journal_dirty_data+0x0/0x38
[<c012bd7f>] generic_file_buffered_write+0x38b/0x5c8
[<c015c8e0>] inode_update_time+0x7c/0xac
[<c012c394>] __generic_file_aio_write_nolock+0x3d8/0x408
[<c012c401>] generic_file_aio_write_nolock+0x3d/0x88
[<c012c624>] generic_file_aio_write+0x64/0xb8
[<c01793af>] ext3_file_write+0x2b/0xbc
[<c0145e3d>] do_sync_write+0xb1/0xe0
[<c0126e8c>] autoremove_wake_function+0x0/0x40
[<c0145880>] generic_file_llseek+0x0/0xa8
[<c0145f0c>] vfs_write+0xa0/0xd0
[<c0145fe8>] sys_write+0x40/0x6c
[<c01020d7>] syscall_call+0x7/0xb
Code: d0 89 ec 5d c3 90 55 89 e5 57 bf 00 01 48 c0 56 be 00 01 48 c0 53 8b
45 0c
9c 8f 00 fa 8b 55 08 8b 42 04 89 fb 8b 40 10 c1 e0 02 <03> 98 20 50 48 c0
89 d8
e8 4e fd 1b 00 8b 55 08 8b 42 04 8b 50
<0>Kernel panic - not syncing: Fatal exception in interrupt
Savannah is back up now. Jim and I will investigate further.
-Justin