friday 13 bug?

friday 13 bug?

[zohn_ming wu]

Kernel 2.4.23 on redhat 8.0Please cc any response from
linux kernel list.  TIA.

On or about 7:50am Friday 13 2004 my postgresql server
breaks down.  I can ssh and use "top" and "ps" but
postgresql stops accepting connection.  A small perl
script that logs system load average also hangs.  I
cannot "kill -9" any hang processes including
postgreqsql postmaster process.

I then check dmesg and found error message that I copy
and paste at the bottom.

I finally issued reboot but reboot also didn't work
and I had to push the reset button.

AMD XP 2500+ with 1.5GB Memory.  Postgresql data lives
on a software raid 1 device.

Kernel 2.4.23 on redhat 8.0

Postgresql 7.4

The last time server was rebooted was about 60 days
ago when I upgraded the kernel

Can someone suggest anything to help me avoid this
type of breakdown?  I tried to post the message
yesterday but postgresql list wasn't responding at all
to subscription request.

------------

swap_free: Bad swap file entry 00000004
kernel BUG at buffer.c:539!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c0138e8e>]    Not tainted
EFLAGS: 00010282
eax: cfd10a40   ebx: 00000002   ecx: e75f6ac0   edx:
c02c548c
esi: e75f6ac0   edi: 00000001   ebp: e75f6ac0   esp:
f74efe60
ds: 0018   es: 0018   ss: 0018
Process postmaster (pid: 457, stackpage=f74ef000)
Stack: 00000002 c01397ab e75f6ac0 00000002 e75f6ac0
00001000 c013a326 e75f6ac0
       00001000 00000000 00420000 00000000 c2166b40
f7822980 c013aaef f7822980
       c2166b40 00000000 00001000 c2166b40 f7822980
00001000 f7822a34 c016064c
Call Trace:    [<c01397ab>] [<c013a326>] [<c013aaef>]
[<c016064c>] [<c0160310>]
  [<c012af71>] [<c012b4f6>] [<c015d8a9>] [<c0137753>]
[<c010733f>]
                                                      
                                                      
    
Code: 0f 0b 1b 02 17 e0 23 c0 8b 02 85 c0 75 07 89 0a
89 49 24 8b
linux-kernel@vger.kernel.orglinux-kernel@vger.kernel.orglinux-kernel@vger.kernel.org

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

Re: [HACKERS] friday 13 bug?

[Joshua D. Drake]

Hello,

I personally ran into the exact same thing with another customer.
They are running RedHat 8.0 with (2.4.20 at the time). We had to upgrade 
them to 2.4.23 and reboot. Worked like a charm. This was about two months 
ago. I swear it was almost the exact same error.

Sincerely,

Joshua D. Drake


On Sat, 14 Feb 2004, zohn_ming wu wrote:

> Kernel 2.4.23 on redhat 8.0Please cc any response from
> linux kernel list.  TIA.
> 
> On or about 7:50am Friday 13 2004 my postgresql server
> breaks down.  I can ssh and use "top" and "ps" but
> postgresql stops accepting connection.  A small perl
> script that logs system load average also hangs.  I
> cannot "kill -9" any hang processes including
> postgreqsql postmaster process.
> 
> I then check dmesg and found error message that I copy
> and paste at the bottom.
> 
> I finally issued reboot but reboot also didn't work
> and I had to push the reset button.
> 
> AMD XP 2500+ with 1.5GB Memory.  Postgresql data lives
> on a software raid 1 device.
> 
> Kernel 2.4.23 on redhat 8.0
> 
> Postgresql 7.4
> 
> The last time server was rebooted was about 60 days
> ago when I upgraded the kernel
> 
> Can someone suggest anything to help me avoid this
> type of breakdown?  I tried to post the message
> yesterday but postgresql list wasn't responding at all
> to subscription request.
> 
> ------------
> 
> swap_free: Bad swap file entry 00000004
> kernel BUG at buffer.c:539!
> invalid operand: 0000
> CPU:    0
> EIP:    0010:[<c0138e8e>]    Not tainted
> EFLAGS: 00010282
> eax: cfd10a40   ebx: 00000002   ecx: e75f6ac0   edx:
> c02c548c
> esi: e75f6ac0   edi: 00000001   ebp: e75f6ac0   esp:
> f74efe60
> ds: 0018   es: 0018   ss: 0018
> Process postmaster (pid: 457, stackpage=f74ef000)
> Stack: 00000002 c01397ab e75f6ac0 00000002 e75f6ac0
> 00001000 c013a326 e75f6ac0
>        00001000 00000000 00420000 00000000 c2166b40
> f7822980 c013aaef f7822980
>        c2166b40 00000000 00001000 c2166b40 f7822980
> 00001000 f7822a34 c016064c
> Call Trace:    [<c01397ab>] [<c013a326>] [<c013aaef>]
> [<c016064c>] [<c0160310>]
>   [<c012af71>] [<c012b4f6>] [<c015d8a9>] [<c0137753>]
> [<c010733f>]
>                                                       
>                                                       
>     
> Code: 0f 0b 1b 02 17 e0 23 c0 8b 02 85 c0 75 07 89 0a
> 89 49 24 8b
> linux-kernel@vger.kernel.orglinux-kernel@vger.kernel.orglinux-kernel@vger.kernel.org
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online.
> http://taxes.yahoo.com/filing.html
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faqs/FAQ.html
> 

-- 
Co-Founder
Command Prompt, Inc.
The wheel's spinning but the hamster's dead

Re: [HACKERS] friday 13 bug?

[Manfred Spraul]

zohn_ming wu wrote:

>swap_free: Bad swap file entry 00000004
>
Do you use ECC memory, is ECC enabled in the BIOS [and does it work - 
some vendors lie about ECC support]?

I would bet that it's a soft memory error: 00000000 means not used. One 
bit differs, and the kernel complains about the invalid value. I think 
the following oops is a side effect of the bad swap entry.
Do you have timestaps in the system log? Is the swap error just before 
the BUG in buffer.c?

--
    Manfred