[Crash-utility] timer: invalid list entry: 1

Fri Mar 1 11:44:02 UTC 2013

some more info:
I am debugging crash utility with gdb, and getting following stack trace.

crash> timer
TVEC_BASES[0]: c0a419c0
JIFFIES
4297762
EXPIRES  TIMER_LIST  FUNCTION
    128   c1621ea8   c007260c  <idle_worker_timeout>
  30208   c0b81f04   c04e4244  <inet_frag_secret_rebuild>
  30720   c0b7f264   c0461440  <flow_cache_new_hashrnd>
  30840   dba2be04   c0068ebc  <process_timeout>
  38228   dbae5e04   c0068ebc  <process_timeout>
11796480   c097cb64   c0010aa4  <sched_clock_poll>
4294937694   c0a6f118   c026f820  <rx_timeout_handler>
4294945658   c16238fc   c007412c  <delayed_work_timer_fn>
4294945667   d811be14   c0068ebc  <process_timeout>
4294945700   c16237cc   c007412c  <delayed_work_timer_fn>
4294945700   c16236e0   c007412c  <delayed_work_timer_fn>
4294946020   c0a1dcbc   c007412c  <delayed_work_timer_fn>
4294946029   dca8f884   c007412c  <delayed_work_timer_fn>
4294946504   c0b871c4   c007412c  <delayed_work_timer_fn>
4294950720   c0b81d6c   c007412c  <delayed_work_timer_fn>

Breakpoint 2, do_list (ld=0xff961c78) at tools.c:3507
3507                            error(INFO, "\ninvalid list entry: %lx\n", next);
(gdb) bt
#0  do_list (ld=0xff961c78) at tools.c:3507
#1  0x0811de03 in do_timer_list (vec_kvaddr=3699761524, size=256, vec=0x85c9f40, option=0x0, highest=0x0, tv=0xff962ec4) at kernel.c:6983
#2  0x0811c9d3 in dump_timer_data_tvec_bases_v2 () at kernel.c:6678
#3  0x0811afac in dump_timer_data () at kernel.c:6370
#4  0x0811af8a in cmd_timer () at kernel.c:6329
#5  0x080910a1 in exec_command () at main.c:818
#6  0x08090ec7 in main_loop () at main.c:766
#7  0x081bf35a in current_interp_command_loop ()
#8  0x081bfbcf in captured_command_loop ()
#9  0x081beddc in catch_errors ()
#10 0x081c0a9a in captured_main ()
#11 0x081beddc in catch_errors ()
#12 0x081c0adc in gdb_main ()
#13 0x081c0b29 in gdb_main_entry ()
#14 0x08121590 in gdb_main_loop (argc=2, argv=0xff964014) at gdb_interface.c:76
#15 0x08090c01 in main (argc=3, argv=0xff964014) at main.c:671

here exactly I hit invalid entry.

Regards,
Oza.

________________________________
 From: paawan oza <paawan1982 at yahoo.com>
To: Dave Anderson <anderson at redhat.com>; "Discussion list for crash utility usage, maintenance and development" <crash-utility at redhat.com> 
Sent: Friday, 1 March 2013 10:58 AM
Subject: Re: [Crash-utility]  timer: invalid list entry: 1

 I would give some more info.

It is dual core system.  (ARM)
both core are stuck at wfi (wait for interrupt)
and we observe that the timer counter has one much ahead than the comparators.
so we never get a local timer interrupt, and nobody is there to wake the cpu up.

so we observe the freeze.

Regards,
Oza.

________________________________
 From: Dave Anderson <anderson at redhat.com>
To: paawan oza <paawan1982 at yahoo.com>; "Discussion list for crash utility usage, maintenance and development" <crash-utility at redhat.com> 
Sent: Thursday, 28 February 2013 7:54 PM
Subject: Re: [Crash-utility]  timer: invalid list entry: 1

----- Original Message -----
> 
> 
> 
> Hi,
> 
> I am getting folowing: I am unable to get whether there is memory
> corruption or crash utility has problem displaying.
> 
> using crash utility version: 6.1.1
> kernel version : 3.4.5+
> 
> I am getting following.
> 
> crash> timer
> TVEC_BASES[0]: c0a419c0
> JIFFIES
> 4297762
> EXPIRES TIMER_LIST FUNCTION
> 128 c1621ea8 c007260c <idle_worker_timeout>
> 30208 c0b81f04 c04e4244 <inet_frag_secret_rebuild>
> 30720 c0b7f264 c0461440 <flow_cache_new_hashrnd>
> 30840 dba2be04 c0068ebc <process_timeout>
> 38228 dbae5e04 c0068ebc <process_timeout>
> 11796480 c097cb64 c0010aa4 <sched_clock_poll>
> 4294937694 c0a6f118 c026f820 <rx_timeout_handler>
> 4294945658 c16238fc c007412c
 <delayed_work_timer_fn>
> 4294945667 d811be14 c0068ebc <process_timeout>
> 4294945700 c16237cc c007412c <delayed_work_timer_fn>
> 4294945700 c16236e0 c007412c <delayed_work_timer_fn>
> 4294946020 c0a1dcbc c007412c <delayed_work_timer_fn>
> 4294946029 dca8f884 c007412c <delayed_work_timer_fn>
> 4294946504 c0b871c4 c007412c <delayed_work_timer_fn>
> 4294950720 c0b81d6c c007412c <delayed_work_timer_fn>
> timer: invalid list entry: 1
> timer: ignoring faulty timer list at index 44 of timer array
> timer: invalid list entry: 1
> timer: ignoring faulty timer list at index 44 of timer array
> TVEC_BASES[1]: dc85e000
> JIFFIES
> 4297762
> EXPIRES TIMER_LIST FUNCTION
> 384 c0a42ba8 c007260c <idle_worker_timeout>
> 4297862 dbec0dfc c007412c <delayed_work_timer_fn>
> 4297897 c162c6e0 c007412c
 <delayed_work_timer_fn>
> 4297962 dbec0ea0 c04a7cec <estimation_timer>
> 4297997 c162c7cc c007412c <delayed_work_timer_fn>
> 4300768 dcb36654 c007412c <delayed_work_timer_fn>
> 4309824 c0a20024 c0516718 <addrconf_verify>
> 4327762 dcaabf54 c0068ebc <process_timeout>
> 4327808 c162aea8 c007260c <idle_worker_timeout>
> 4357762 dbaa3e04 c0068ebc <process_timeout>
> 4357762 dbaa3e04 c0068ebc <process_timeout>
> 4357888 c0b83fa4 c04e4244 <inet_frag_secret_rebuild>
> 4357888 c0b84694 c04e4244 <inet_frag_secret_rebuild>
> 4357888 c0b83fa4 c04e4244 <inet_frag_secret_rebuild>
> 4357888 c0b84694 c04e4244 <inet_frag_secret_rebuild>
> 
> 
> 
> Regards,
> Oza.

It's impossible to answer without knowing the specifics.

It could be corruption, or perhaps the cpu 0 was
 manipulating
the timer chains when the kernel panicked, or perhaps there
is some off-the-wall condition that the crash utility has
never encountered.

Dave

Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20130301/a203dec8/attachment.htm>