netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Markus Feldmann <feldmann_markus@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: Messages are printed on screen
Date: Fri, 02 Oct 2009 11:56:36 +0100	[thread overview]
Message-ID: <1254480996.23350.73.camel@localhost> (raw)
In-Reply-To: <ha4igd$ghh$1@ger.gmane.org>

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

On Fri, 2009-10-02 at 11:52 +0200, Markus Feldmann wrote:
> Hi All,
> 
> i am setting up my Server, with Linux Debian lenny. Therefore i am using 
>   Kernel 2.6.31.1.

The current kernel version for 'lenny' is 2.6.26 (with stable updates
and other fixes).

2.6.31 is known to have a large number of regressions outstanding, which
is why it is not in Debian yet.

> I configured this Kernel with <make defconfig> and 
> <make menuconfig>. My motherboard has 5 PCI slots and 1 AGP slot. All 
> slots are in use. All devices are mapped to the following IRQ-Line:
> 
> Mass Storage Device (PCI Slot1)	IRQ-Line 11
> Ethernet (PCI Slot 2) 		IRQ-Line 4
> Ethernet (PCI Slot 3) 		IRQ-Line 5
> Ethernet (PCI Slot 4) 		IRQ-Line 7
> Ethernet (PCI Slot 5) 		IRQ-Line 11
> Onboard USB-Controller		IRQ-Line 5
> Onboard USB-Controller		IRQ-Line 4
> Onboard USB-Controller		IRQ-Line 11
> Onboard IDE			IRQ-Line 14
> AGP VGA				IRQ-Line 11
> 
> As you see some of my IRQ-Lines are multiply in use, so my Server is 
> working hard at his limit.

IRQ sharing is normal on PCs without MSI support, but to see where
that's happening you need to look at /proc/interrupts and not the BIOS
setup program or wherever you got the above information from.

This does not result in 'working hard at his limit'.

> The result is sometimes freezing of my 
> Server, especially if there is much processing on these devices. I 
> remember that with Kernel 2.6.18 my system didn't does freezing.

This is simply a bug, not a result of IRQ sharing or 'working hard'.

> So i am trying to reduce the amount of this processing. I still get 
> messages about dropped network packets on my Terminal, although i set up 
> my <rsyslog> to save this only to </var/log>. Here is my 
> </etc/rsyslog.conf>

You forgot to paste it.

> How can i disable the output of messages (about dropped packets from my 
> firewall) to my terminal ?

Edit the value of kernel.printk in /etc/sysctl.conf.

> How can i stabilize my IRQ-System with the kernel 2.6.31.1 ?

I would expect the standard kernel version for 'lenny' or the 2.6.30
kernel from 'sid' to be more stable.

> What debug features should i disable ?

No idea, you didn't even specify what you enabled...

Ben.

-- 
Ben Hutchings
Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp

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

  parent reply	other threads:[~2009-10-02 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  9:52 Messages are printed on screen Markus Feldmann
2009-10-02 10:56 ` Markus Feldmann
2009-10-02 10:56 ` Ben Hutchings [this message]
2009-10-02 12:01   ` Markus Feldmann
2009-10-02 20:49     ` Ben Hutchings

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=1254480996.23350.73.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=feldmann_markus@gmx.de \
    --cc=netdev@vger.kernel.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 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).