Bug 153432 - klogd: xfrm_lookup: IPv4 route is stale (obsolete=4294967295, loops=0)
Summary: klogd: xfrm_lookup: IPv4 route is stale (obsolete=4294967295, loops=0)
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 3
Hardware: i686 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-24 17:21 UTC by Per Jessen
Modified: 2006-03-11 10:26 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Per Jessen 2006-02-24 17:21:09 UTC 
I have hundreds if not thousands of lines like this in /var/log/messages: 

Feb 24 18:07:04 io klogd: xfrm_lookup: IPv4 route is stale (obsolete=4294967295, loops=0)
Feb 24 18:07:04 io klogd:  [<c028bf35>] xfrm_lookup+0x412/0x492
Feb 24 18:07:04 io klogd:  [<f8d0a9ce>] ipv6_dev_get_saddr+0x500/0x588 [ipv6]
Feb 24 18:07:04 io klogd:  [<f8d065b8>] ip6_dst_lookup+0x1eb/0x255 [ipv6]
Feb 24 18:07:04 io klogd:  [<f8d235f6>] ip6_datagram_connect+0x2e5/0x41a [ipv6]
Feb 24 18:07:04 io klogd:  [<c023da59>] release_sock+0x10/0x9b
Feb 24 18:07:04 io klogd:  [<c027ea18>] inet_dgram_connect+0x45/0x4e
Feb 24 18:07:04 io klogd:  [<c023cf0b>] sys_connect+0x76/0x98
Feb 24 18:07:04 io klogd:  [<c015b43d>] fd_install+0x24/0x50
Feb 24 18:07:04 io klogd:  [<c0159085>] cache_alloc_debugcheck_after+0xc1/0xf9
Feb 24 18:07:04 io klogd:  [<c015978d>] __kmalloc+0xb5/0xbe
Feb 24 18:07:04 io klogd:  [<c0140627>] audit_socketcall+0x37/0x79
Feb 24 18:07:04 io klogd:  [<c023d048>] sys_socketcall+0x8c/0x19e
Feb 24 18:07:04 io klogd:  [<c0103c09>] syscall_call+0x7/0xb

They seem to produced during periods of network activity.  The box has a vanilla 10.1 beta3 install and doesn't do any IPV6.
Comment 1 Michael Gross 2006-02-24 18:12:09 UTC 
At first, disable the firewall completely and test if the messages still occur (if it is enabled).
Comment 2 Michael Gross 2006-02-24 18:24:19 UTC 
Per: Try again with Beta5, people told me this issue was known and fixed. Reopen if you still have trouble with B5.
Comment 3 Per Jessen 2006-02-24 19:18:29 UTC 
OK, will wait for B5 to appear.  FYI, firewall was not enabled.  This is happening on a workstation on our local network.
Comment 4 Per Jessen 2006-03-11 10:26:37 UTC 
OK, have now tried Beta6 and the messages do seem to have disappeared.