linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: senthilkumaar2021 <senthilkumaar2021@gmail.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel panic
Date: Tue, 18 May 2010 07:05:36 +0200	[thread overview]
Message-ID: <1274159136.2567.24.camel@edumazet-laptop> (raw)
In-Reply-To: <4BF21DAD.6050609@gmail.com>

Le mardi 18 mai 2010 à 10:25 +0530, senthilkumaar2021 a écrit :
> Hi
> 
> Thanks for the reply
> 
> Initially i was using kernel 2.6.28.5 and kernel panic occurred in that 
> version too
> 
> tproxy is not supported in linux 2.6.32
> 
> http://wiki.squid-cache.org/Features/Tproxy4
> 
> kindly guide me how to proceed

Please submit full panic log, and kernel version

AFAIK tproxy is now in Linux kernel tree.




  reply	other threads:[~2010-05-18  5:05 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  4:23 kernel panic senthilkumaar2021
2010-05-18  4:47 ` Justin P. Mattock
2010-05-18  4:55   ` senthilkumaar2021
2010-05-18  5:05     ` Eric Dumazet [this message]
2010-05-18  5:08     ` Justin P. Mattock
  -- strict thread matches above, loose matches on Subject: below --
2013-09-17  2:59 Kernel panic zhang xintao
2012-12-02 17:30 Stefan Beller
2012-12-02 17:51 ` Stefan Beller
2012-12-02 19:13   ` rh
     [not found] <201201191202.q0JC243u029201@curly.dor.state.ma.us>
2012-01-19 15:26 ` Ron Murray
2011-10-24 11:19 kernel panic nick bray
2011-10-25 20:55 ` Bjorn Helgaas
2011-10-26 10:00   ` Len Brown
2011-10-26 14:53     ` Bjorn Helgaas
     [not found]       ` <4EA82832.2070201@ntlworld.com>
2011-10-26 16:18         ` Bjorn Helgaas
     [not found]           ` <4EA83F5D.20001@ntlworld.com>
2011-10-26 18:10             ` Bjorn Helgaas
2011-10-28  2:13               ` Thomas Renninger
2011-10-31 12:24                 ` Thomas Renninger
     [not found] <9a5eeacd0804210350v79db27f0of73a29c55e2b7311@mail.gmail.com>
2008-04-21 10:56 ` Kernel panic Matthias Andersson
2008-04-21 11:07   ` Bart Van Assche
2006-08-24 18:01 kernel panic febo
2006-02-24 10:15 Rogel Miguez
     [not found] <4GLD8-5Wa-27@gated-at.bofh.it>
2005-08-29 23:50 ` Robert Hancock
2005-08-29  6:43 manomugdha biswas
2004-04-12 10:39 osmaker@hu
2004-04-12 10:43 ` osmaker@hu
2004-04-12 12:26 ` Zwane Mwaikambo
     [not found] <S263478AbTLEJ0s/20031205092648Z+878@vger.kernel.org>
2003-12-05  9:34 ` Kernel panic neel vanan
2003-12-05 14:19   ` William Lee Irwin III
2003-12-06  5:47     ` William Lee Irwin III
2003-03-26 20:22 Kernel Panic David van Hoose
2003-03-26 11:28 ` dan carpenter
2002-04-06  4:16 Kernel panic Daniel Mundy
2002-04-06 18:05 ` Alan Cox
2002-03-05 22:31 Hanno Böck
2002-03-06  1:40 ` Lionel Bouton
2002-03-06  1:50   ` Andre Hedrick
2002-02-19 18:27 kernel panic chiranjeevi vaka
2002-02-19 18:50 ` Justin Carlson
2002-02-21 17:17 ` Fernando Korndorfer
2002-01-02 19:34 nntp
2001-12-15 18:47 mempool design Benjamin LaHaise
2001-12-15 22:18 ` Ingo Molnar
2001-12-17 15:04   ` Andrea Arcangeli
2001-12-17 15:38     ` Victor Yodaiken
2001-12-17 17:33       ` kernel panic Geoffrey
2000-11-17 17:44 Kernel Panic Dave Seff
2000-11-18 19:29 ` Chmouel Boudjnah

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=1274159136.2567.24.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=senthilkumaar2021@gmail.com \
    /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).