All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Hung Lin <hlin@nextone.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Kernel oops when putting the console option in /boot/grub/menu.lst
Date: Thu, 10 May 2007 18:44:18 +0200	[thread overview]
Message-ID: <46434BE2.5090605@trash.net> (raw)
In-Reply-To: <D0B3C45E7FCE4C488BEF410B2EF666A17F8D04@moe.nextone.local>

Hung Lin wrote:
> Hi,
> 
> I'm using ipset-2.2.9 with kernel 2.6.11.4-21.13 (SuSE 9.3 kernel) and
> iptables-1.3.1-3 (SuSE 9.3 iptables) and everything is fine.  But after
> I added a console option to /boot/grub/menu.lst, the kenrel will hang
> sometimes and show kernel oops message on the monitor.  After research,
> I found it is `iptables -m hashlimit` command to cause this problem.
> Therefore, I did some tests:
> 
> I used a loop to insert and delete hashlimit rules to iptables, here's
> the result:
> 
> 1. with ipset patch and without console option in grub menu, no problem
> 
> 2. withotu ipset patch and with console option in grub menu, no problem
> 
> 3. with ipset patch and with console option in grub menu, kernel crashs
> after hundreds of iterations.
> 
> 
> It looks like console option in the grub menu has something conflict
> with ipset kernel patch.  But I don't understand.
> 
> Please give me your advices.  Thanks in advance.


Please send the oops.

  reply	other threads:[~2007-05-10 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 15:41 Kernel oops when putting the console option in /boot/grub/menu.lst Hung Lin
2007-05-10 16:44 ` Patrick McHardy [this message]
2007-05-10 17:06   ` Hung Lin
2007-05-11 16:37     ` Patrick McHardy
2007-05-11 17:15     ` Carl-Daniel Hailfinger
2007-05-15 10:58 ` Amin Azez

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=46434BE2.5090605@trash.net \
    --to=kaber@trash.net \
    --cc=hlin@nextone.com \
    --cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.