linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Mark Symonds <mark@symonds.net>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 hard lock, 100% reproducible.
Date: Sun, 07 Dec 2003 12:34:39 +0100	[thread overview]
Message-ID: <1070796878.23878.57.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <049e01c3bca9$0eae8880$7a01a8c0@gandalf>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

On Sun, 2003-12-07 at 11:01, Mark Symonds wrote:

> puggy:/usr/src/linux/2.4.23# ksymoops -m ./System.map -A c02363dd
> ksymoops 2.4.9 on i686 2.4.23.  Options used
>      -V (default)
>      -k /proc/ksyms (default)
>      -l /proc/modules (default)
>      -o /lib/modules/2.4.23/ (default)
>      -m ./System.map (specified)
> 
> Error (regular_file): read_ksyms stat /proc/ksyms failed
> ksymoops: No such file or directory
> No modules in ksyms, skipping objects
> No ksyms, skipping lsmod
> 
> 
> Adhoc c02363dd <tcp_print_conntrack+2d/60>

Hmm, it looks like it's this line in tcp_print_conntrack()

return sprintf(buffer, "%s ", tcp_conntrack_names[state]);

But it would be good if you could recompile and use addr2line (or gdb)
to get the exact line (offsets and memory-addresses depends on compiler
used and other stuff).

I took a quick look at the code but didn't see anything obvious.

-- 
/Martin

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-07 11:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07  6:50 2.4.23 hard lock, 100% reproducible Alex Davis
2003-12-07  6:55 ` William Lee Irwin III
     [not found]   ` <046a01c3bca1$267ba5e0$7a01a8c0@gandalf>
2003-12-07  9:07     ` William Lee Irwin III
2003-12-07  9:16       ` Keith Owens
2003-12-07  9:36         ` William Lee Irwin III
2003-12-08 16:34           ` Oliver Teuber
2003-12-07 10:01         ` Mark Symonds
2003-12-07 11:34           ` Martin Josefsson [this message]
2003-12-07 14:40           ` Marcelo Tosatti
2003-12-07 23:18             ` Mark Symonds
2003-12-08  4:53               ` William Lee Irwin III
2003-12-08  7:12               ` Tim Timmerman
2003-12-08 11:06                 ` Marcelo Tosatti
2003-12-09  6:29                   ` Tim Timmerman
2003-12-08 10:17               ` Marcelo Tosatti
2003-12-08 15:54                 ` Stephan von Krawczynski
2003-12-08 16:15                   ` Marcelo Tosatti
2003-12-08 16:31                     ` Jeff Garzik
2003-12-08 16:55                     ` Stephan von Krawczynski
2003-12-08 19:56                 ` Mark Symonds
2003-12-07  7:33 ` Mark Symonds
2003-12-07 16:24   ` Alex Davis
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08 17:06 Xose Vazquez Perez
2003-12-07  2:36 Mark Symonds
2003-12-07  3:30 ` Philippe Troin
2003-12-07  4:34   ` Mark Symonds
2003-12-07 18:32     ` Chris Frey
2003-12-07 18:49       ` James Bourne
2003-12-07 19:21         ` David Rees
2003-12-07 20:19           ` James Bourne

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=1070796878.23878.57.camel@tux.rsn.bth.se \
    --to=gandalf@wlug.westbo.se \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@symonds.net \
    /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).