2.5.56 panics PostgreSQL

2.5.56 panics PostgreSQL

[David Ford]

[-- Attachment #1.1: Type: text/plain, Size: 1330 bytes --]

Yesterday I put 2.5.56 on my SQL server and PostgreSQL started panicking 
repeatedly and frequently complaining about missing commit logs.  2.5.56 
also issued a single NMI .. dazed and confused but continuing warning 
shortly after startup.

Rebooting back into 2.4 and the world was well again.  Attached is my 
.config in bz2 form.

David

-- 
I may have the information you need and I may choose only HTML.  It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion.  If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites.  I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access.  This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away.  Don't be a cluebert, buy one from K-mart today.

When it absolutely, positively, has to be destroyed overnight.
                           AIR FORCE


[-- Attachment #1.2: config.bz2 --]
[-- Type: application/octet-stream, Size: 1826 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 252 bytes --]

Re: 2.5.56 panics PostgreSQL

[Andrew Morton]

On Sun January 12 2003 10:47, David Ford wrote:
>
> Yesterday I put 2.5.56 on my SQL server and PostgreSQL started panicking 
> repeatedly and frequently complaining about missing commit logs.

Which filesystems were in use?

Re: 2.5.56 panics PostgreSQL

[David Ford]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Reiserfs.  Postgres is the only program that had problems, but it's also
the one that does 99% of all the activity on the system.

David

Andrew Morton wrote:

>On Sun January 12 2003 10:47, David Ford wrote:
>  
>
>>Yesterday I put 2.5.56 on my SQL server and PostgreSQL started panicking 
>>repeatedly and frequently complaining about missing commit logs.
>>    
>>
>
>Which filesystems were in use?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+IceU74cGT/9uvgsRAjVyAKChsd6nugAaDKYipYoiEOnaZD0qMgCgkZTb
bx8trXNJtflndfjwrcroJSI=
=+Rqc
-----END PGP SIGNATURE-----

Re: 2.5.56 panics PostgreSQL

[Chris Mason]

On Sun, 2003-01-12 at 14:52, David Ford wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Reiserfs.  Postgres is the only program that had problems, but it's also
> the one that does 99% of all the activity on the system.

Do you still have any of the oopsen?

-chris

Re: 2.5.56 panics PostgreSQL

[David Ford]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I can in short order.  Let me grab my notebook and get a kernel w/ 
serial console going.

David

Chris Mason wrote:

>On Sun, 2003-01-12 at 14:52, David Ford wrote:
>  
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Reiserfs.  Postgres is the only program that had problems, but it's also
>>the one that does 99% of all the activity on the system.
>>    
>>
>
>Do you still have any of the oopsen?
>
>-chris
>
>  
>

- -- 
I may have the information you need and I may choose only HTML.  It's up to you. Disclaimer: I am not responsible for any email that you send me nor am I bound to any obligation to deal with any received email in any given fashion.  If you send me spam or a virus, I may in whole or part send you 50,000 return copies of it. I may also publically announce any and all emails and post them to message boards, news sites, and even parody sites.  I may also mark them up, cut and paste, print, and staple them to telephone poles for the enjoyment of people without internet access.  This is not a confidential medium and your assumption that your email can or will be handled confidentially is akin to baring your backside, burying your head in the ground, and thinking nobody can see you butt nekkid and in plain view for miles away.  Don't be a cluebert, buy one from K-mart today.

When it absolutely, positively, has to be destroyed overnight.
                           AIR FORCE

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+Ihdc74cGT/9uvgsRAiTaAJ42qZ/WZyueTYpaDK6/e0WOIXJ82ACcCMDT
gmvHVssrIRcwwC8OXOGgIgQ=
=K5/f
-----END PGP SIGNATURE-----

Re: 2.5.56 panics PostgreSQL

[David Ford]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just for clarification, the kernel isn't OOPSing, PostgreSQL is the one 
having fits and shutting down/starting up left and right.

The NMI is the only kernel indication that something is odd.  Which 
never happens under 2.4.

David

Chris Mason wrote:

>On Sun, 2003-01-12 at 14:52, David Ford wrote:
>  
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Reiserfs.  Postgres is the only program that had problems, but it's also
>>the one that does 99% of all the activity on the system.
>>    
>>
>
>Do you still have any of the oopsen?
>
>-chris
>
>  
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+Ihg974cGT/9uvgsRAqaRAKCD3JLmwwOEpoDBebPyDs2QWGZSGgCff7yN
+g3+aIX6Y8DHkcj3ZFPpivI=
=86PN
-----END PGP SIGNATURE-----