From: "Marcin Mirosław" <marcin@mejor.pl>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0
Date: Fri, 20 Jan 2012 19:59:02 +0100 [thread overview]
Message-ID: <c9933477d3435d4acdd00d7208d1c89f@mejor.pl> (raw)
In-Reply-To: <alpine.LNX.2.01.1201201812130.29700@frira.zrqbmnf.qr>
W dniu 2012-01-20 18:14, Jan Engelhardt napisał(a):
> You have a crappy module (indicated by the "C") loaded, and since
> it's
> zram, I don't know what effects that could have w.r.t. memory
> corruption.
> Is this reproducible without zram?
Hi Jan,
without zram/zcache oops still appears, new log:
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.235485] BUG:
unable to handle kernel paging request at ffffffffa01d80e
0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.237586] IP:
[<ffffffff812a9451>] xt_find_target+0xa1/0x120
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.238616] PGD
1328067 PUD 132e063 PMD 1e29a063 PTE 0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.240035] Oops:
0000 [#1] SMP
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.241398] CPU 0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.241737] Modules
linked in: sit tunnel4 xt_TCPMSS ipt_REJECT xt_multipo
rt xt_set xt_TARPIT ip_set_hash_ip ip_set_hash_net sha1_generic
compat_xtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_rt xt_st
ate xt_NOTRACK ip_set iptable_raw ip6table_mangle iptable_mangle
iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_
ipv4 ip6table_filter ip6_tables iptable_filter ip_tables xfs exportfs
dm_mod ipv6 8139too evdev sr_mod cdrom 8139cp [last unl
oaded: xt_SYSRQ]
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436]
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] Pid:
4895, comm: iptables Not tainted 3.1.8-hardened #6 Xen HV
M domU
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RIP:
0010:[<ffffffff812a9451>] [<ffffffff812a9451>] xt_find_t
arget+0xa1/0x120
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RSP:
0018:ffff880017f53c18 EFLAGS: 00010282
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RAX:
ffffffffa01d80e0 RBX: ffff880017e59382 RCX: ffff880017e59
380
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RDX:
0000000000000000 RSI: ffff880017e59388 RDI: ffff88001dcdf
e96
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RBP:
ffff880017f53c68 R08: 0000000000000010 R09: ffff880017e59
758
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] R10:
0000000000000000 R11: 0000000000000010 R12: ffff88001dcdf
e80
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] R13:
ffff88001ea75910 R14: 0000000000000001 R15: 00000000fffff
ffe
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] FS:
000002c51ebe1700(0000) GS:ffff88001fc00000(0000) knlGS:00
00000000000000
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] CS:
0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] CR2:
ffffffffa01d80e0 CR3: 0000000001320000 CR4: 0000000000000
6b0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] DR0:
0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] DR3:
0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] Process
iptables (pid: 4895, threadinfo ffff88001ebf6270, task ffff88001ebf5e80)
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] Stack:
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436]
ffff880017f53c28 02a7b27e0ae1476c 00000000000000e0 ffff88001ea758e0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436]
ffff880017e59260 0000000000000002 ffff880017e59382 0000000000000001
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
0000000000000001 ffff88001d68c600 ffff880017f53c98 ffffffff812aa379
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] Call
Trace:
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812aa379>] xt_request_find_target+0x29/0x80
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffffa0140389>] translate_table+0x389/0x660 [ip_tables]
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffffa0141e05>] do_ipt_set_ctl+0x1f5/0x2a0 [ip_tables]
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812a8336>] nf_sockopt+0x66/0xc0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812a83cc>] nf_setsockopt+0x1c/0x30
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812b9d34>] ip_setsockopt+0x94/0xb0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812d6fe5>] raw_setsockopt+0x25/0x50
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff8126e35c>] sock_common_setsockopt+0x1c/0x30
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff8126d237>] sys_setsockopt+0x87/0xf0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff81311e7b>] system_call_fastpath+0x18/0x1d
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] Code: 4d
8b 24 24 4d 39 e5 74 71 49 8d 7c 24 10 48 89 de e8 d4 5c f2 ff 85 c0 75
e6 45 38 74 24 2d 75 d9 49 8b 44 24 58 48 85 c0 74 1e
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] RIP
[<ffffffff812a9451>] xt_find_target+0xa1/0x120
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] RSP
<ffff880017f53c18>
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] CR2:
ffffffffa01d80e0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] ---[ end
trace cfa32e0ddddcd297 ]---
next prev parent reply other threads:[~2012-01-20 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 16:48 [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0 Marcin Mirosław
2012-01-20 17:14 ` Jan Engelhardt
2012-01-20 18:59 ` Marcin Mirosław [this message]
2012-08-23 13:23 ` Jan Engelhardt
2012-09-18 11:20 ` Marcin Mirosław
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9933477d3435d4acdd00d7208d1c89f@mejor.pl \
--to=marcin@mejor.pl \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).