Re: [HACKERS] Kernel Tainted

2016-10-05 Thread reiner peterke 

> On Oct 5, 2016, at 9:43 PM, Tomas Vondra  wrote:
> 
> On 10/05/2016 08:41 PM, reiner peterke wrote:
>> Hi,
>> 
>> We are helping a client test an application On Power8 using Postgres
>> 9.5.4 which has been compiled specifically for the Power.
>> 
>> This is running on sles12sp1  the current kernel is 3.12.49-11
>> 
>> We are getting these kernel warning associated with the postmaster
>> process.  The application is handling around 15000TPS  It appears that
>> one of these messages is generated for each each transaction which fills
>> up the warn.log quite quickly.
>> 
>> I’m trying to understand what is causing the Tainted kernel messages.
>> the warning is at 'WARNING: at ../net/core/dst.c:287’.
>> I’ve found one link that indicates that this is ip6 related.
>> https://brunomgalmeida.wordpress.com/2015/07/23/disable-ipv6-postgres-and-pgbouncer/
>> Is this accurate?  And if these action resolve the error, is it more of
>> a bandaid then an actual fix?
>> 
> 
> As Andres already pointed out, this is most likely a kernel issue, not a 
> PostgreSQL one. The "tainted" has nothing to do with the cause, it's just a 
> way to inform users whether it's a clean kernel build, or if it includes code 
> not available in vanilla kernels etc. The "X" means there are some 
> SuSe-specific modules loaded, IIRC.
> 
> And yes, it seems IPv6 related, at least judging by the stack trace:
> 
> 0xc16f7d80 (unreliable)
> sk_dst_check+0x174/0x180
> ip6_sk_dst_lookup_flow+0x4c/0x2a0
> udpv6_sendmsg+0x688/0xb20
> inet_sendmsg+0x9c/0x120
> sock_sendmsg+0xec/0x140
> SyS_sendto+0x108/0x150
> SyS_send+0x50/0x70
> SyS_socketcall+0x2a0/0x440
> syscall_exit+0x0/0x7c
> 
> You should probably talk to SuSe or whoever supports that system.
> 
> regards
> 
> -- 
> Tomas Vondra  http://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
> 
> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
Thanks for the clear information.
I think there are a few kernel upgrade we can apply first, then see if that 
fixes the problem.

Reiner

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Kernel Tainted

2016-10-05 Thread Tomas Vondra 

On 10/05/2016 08:41 PM, reiner peterke wrote:

Hi,

We are helping a client test an application On Power8 using Postgres
9.5.4 which has been compiled specifically for the Power.

This is running on sles12sp1  the current kernel is 3.12.49-11

We are getting these kernel warning associated with the postmaster
process.  The application is handling around 15000TPS  It appears that
one of these messages is generated for each each transaction which fills
up the warn.log quite quickly.

I’m trying to understand what is causing the Tainted kernel messages.
the warning is at 'WARNING: at ../net/core/dst.c:287’.
I’ve found one link that indicates that this is ip6 related.
 
https://brunomgalmeida.wordpress.com/2015/07/23/disable-ipv6-postgres-and-pgbouncer/
Is this accurate?  And if these action resolve the error, is it more of
a bandaid then an actual fix?



As Andres already pointed out, this is most likely a kernel issue, not a 
PostgreSQL one. The "tainted" has nothing to do with the cause, it's 
just a way to inform users whether it's a clean kernel build, or if it 
includes code not available in vanilla kernels etc. The "X" means there 
are some SuSe-specific modules loaded, IIRC.


And yes, it seems IPv6 related, at least judging by the stack trace:

0xc16f7d80 (unreliable)
sk_dst_check+0x174/0x180
ip6_sk_dst_lookup_flow+0x4c/0x2a0
udpv6_sendmsg+0x688/0xb20
inet_sendmsg+0x9c/0x120
sock_sendmsg+0xec/0x140
SyS_sendto+0x108/0x150
SyS_send+0x50/0x70
SyS_socketcall+0x2a0/0x440
syscall_exit+0x0/0x7c

You should probably talk to SuSe or whoever supports that system.

regards

--
Tomas Vondra  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Kernel Tainted

2016-10-05 Thread Andres Freund 
Hi,

On 2016-10-05 20:41:54 +0200, reiner peterke wrote:
> We are getting these kernel warning associated with the postmaster process.  
> The application is handling around 15000TPS  It appears that one of these 
> messages is generated for each each transaction which fills up the warn.log 
> quite quickly.
> 
> I’m trying to understand what is causing the Tainted kernel
> messages. the warning is at 'WARNING: at ../net/core/dst.c:287’.

Which makes this a kernel, not a postgres issue.

Greetings,

Andres Freund


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Kernel Tainted

2016-10-05 Thread reiner peterke 
Hi,

We are helping a client test an application On Power8 using Postgres 9.5.4 
which has been compiled specifically for the Power.

This is running on sles12sp1  the current kernel is 3.12.49-11

We are getting these kernel warning associated with the postmaster process.  
The application is handling around 15000TPS  It appears that one of these 
messages is generated for each each transaction which fills up the warn.log 
quite quickly.

I’m trying to understand what is causing the Tainted kernel messages. the 
warning is at 'WARNING: at ../net/core/dst.c:287’.  
I’ve found one link that indicates that this is ip6 related.  
https://brunomgalmeida.wordpress.com/2015/07/23/disable-ipv6-postgres-and-pgbouncer/
 

Is this accurate?  And if these action resolve the error, is it more of a 
bandaid then an actual fix?

Any comments are appreciated.

A sample of the error is below.

Reiner

2016-10-05T15:08:50.219292+02:00 PPDLMREB04 kernel: [ cut here 
]
2016-10-05T15:08:50.219335+02:00 PPDLMREB04 kernel: WARNING: at 
../net/core/dst.c:287
2016-10-05T15:08:50.219341+02:00 PPDLMREB04 kernel: Modules linked in: 
af_packet xfs libcrc32c ibmveth(X) rtc_generic btrfs xor raid6_pq 
dm_service_time sr_mod sd_mod cdrom crc_t10dif ibmvfc(X) scsi_transport_fc 
ibmvscsi(X) scsi_transport_srp scsi_tgt dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua scsi_dh dm_mod sg scsi_mod autofs4
2016-10-05T15:08:50.219346+02:00 PPDLMREB04 kernel: Supported: Yes, External
2016-10-05T15:08:50.219350+02:00 PPDLMREB04 kernel: CPU: 28 PID: 113041 Comm: 
postmaster Tainted: G   X 3.12.49-11-default #1
2016-10-05T15:08:50.219355+02:00 PPDLMREB04 kernel: task: c003c31100d0 ti: 
c003c1f08000 task.ti: c003c1f08000
2016-10-05T15:08:50.219362+02:00 PPDLMREB04 kernel: NIP: c05c0bb0 LR: 
c0594bc4 CTR: c06a0ae0
2016-10-05T15:08:50.219415+02:00 PPDLMREB04 kernel: REGS: c003c1f0b630 
TRAP: 0700   Tainted: G   X  (3.12.49-11-default)
2016-10-05T15:08:50.219424+02:00 PPDLMREB04 kernel: MSR: 80029033 
  CR: 24022288  XER: 0016
2016-10-05T15:08:50.219430+02:00 PPDLMREB04 kernel: CFAR: c0594bc0 
SOFTE: 1 
2016-10-05T15:08:50.219438+02:00 PPDLMREB04 kernel: GPR00: c0594bc4 
c003c1f0b8b0 c0e8ff00 c003c35a1980 
2016-10-05T15:08:50.219444+02:00 PPDLMREB04 kernel: GPR04: 0002 
 0001  
2016-10-05T15:08:50.219448+02:00 PPDLMREB04 kernel: GPR08:  
0001  c0710810 
2016-10-05T15:08:50.219452+02:00 PPDLMREB04 kernel: GPR12: c06a0ae0 
c7b2fc00 7fff 003c 
2016-10-05T15:08:50.219457+02:00 PPDLMREB04 kernel: GPR16:  
10735620   
2016-10-05T15:08:50.219462+02:00 PPDLMREB04 kernel: GPR20: c003c1746d80 
0001  03a8 
2016-10-05T15:08:50.219466+02:00 PPDLMREB04 kernel: GPR24: c003c1f0b9f0 
  03a8 
2016-10-05T15:08:50.219470+02:00 PPDLMREB04 kernel: GPR28: 0002 
c003c1746a00  c003c35a1980 
2016-10-05T15:08:50.219475+02:00 PPDLMREB04 kernel: NIP [c05c0bb0] 
dst_release+0x50/0xa0
2016-10-05T15:08:50.219479+02:00 PPDLMREB04 kernel: LR [c0594bc4] 
sk_dst_check+0x174/0x180
2016-10-05T15:08:50.219484+02:00 PPDLMREB04 kernel: Call Trace:
2016-10-05T15:08:50.219489+02:00 PPDLMREB04 kernel: [c003c1f0b8b0] 
[c16f7d80] 0xc16f7d80 (unreliable)
2016-10-05T15:08:50.219495+02:00 PPDLMREB04 kernel: [c003c1f0b8e0] 
[c0594bc4] sk_dst_check+0x174/0x180
2016-10-05T15:08:50.219501+02:00 PPDLMREB04 kernel: [c003c1f0b920] 
[c068d4cc] ip6_sk_dst_lookup_flow+0x4c/0x2a0
2016-10-05T15:08:50.219506+02:00 PPDLMREB04 kernel: [c003c1f0b970] 
[c06b16b8] udpv6_sendmsg+0x688/0xb20
2016-10-05T15:08:50.219511+02:00 PPDLMREB04 kernel: [c003c1f0baf0] 
[c064b30c] inet_sendmsg+0x9c/0x120
2016-10-05T15:08:50.219515+02:00 PPDLMREB04 kernel: [c003c1f0bb40] 
[c058eabc] sock_sendmsg+0xec/0x140
2016-10-05T15:08:50.219519+02:00 PPDLMREB04 kernel: [c003c1f0bc60] 
[c05921a8] SyS_sendto+0x108/0x150
2016-10-05T15:08:50.219524+02:00 PPDLMREB04 kernel: [c003c1f0bd80] 
[c0592240] SyS_send+0x50/0x70
2016-10-05T15:08:50.219530+02:00 PPDLMREB04 kernel: [c003c1f0bdc0] 
[c05933f0] SyS_socketcall+0x2a0/0x440
2016-10-05T15:08:50.219534+02:00 PPDLMREB04 kernel: [c003c1f0be30] 
[c000a17c] syscall_exit+0x0/0x7c
2016-10-05T15:08:50.219541+02:00 PPDLMREB04 kernel: Instruction dump:
2016-10-05T15:08:50.219547+02:00 PPDLMREB04 kernel: 6000 2fbf 419e0038 
395f0080 7c2004ac 7d205028 3129 7d20512d