mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: tglx@linutronix.de
Cc: "Ingo Molnar" <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, "Esben Nielsen" <simlo@phys.au.dk>,
	"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: 2.6.15-rt17
Date: Tue, 21 Feb 2006 22:15:46 +0100	[thread overview]
Message-ID: <6bffcb0e0602211315n4ea36c06q@mail.gmail.com> (raw)
In-Reply-To: <1140554250.2480.1042.camel@localhost.localdomain>

Hi,

On 21/02/06, Thomas Gleixner <tglx@linutronix.de> wrote:
> The stack maximum messages are harmless. They just report a new
> watermark high quite verbose. You can turn them off by disabling
> DEBUG_STACKOVERFLOW.

Sorry, I forgot about this.

>
> skge eth0: Link is up at 100 Mbps, full duplex, flow control tx and rx
> WARNING: softirq-tasklet/8 changed soft IRQ-flags.
>  [<c0103b33>] dump_stack+0x1b/0x1f (20)
>  [<c0134035>] illegal_API_call+0x41/0x46 (20)
>  [<c0134084>] local_irq_disable+0x1d/0x1f (8)
>  [<f8839bf3>] skge_extirq+0x117/0x138 [skge] (32)
>  [<c0120a73>] __tasklet_action+0xb8/0xfd (28)
>  [<c0120afc>] tasklet_action+0x44/0x4e (28)
>  [<c0120ce8>] ksoftirqd+0x10f/0x19e (32)
>  [<c012dfa6>] kthread+0x7b/0xa9 (36)
>  [<c01010dd>] kernel_thread_helper+0x5/0xb (1037991964)
>
> This one is interesting. It brought my attention to that piece of code
> which is a long standing problem on one of my boxen anyway. Patch
> attached.
>
>         tglx
>

Thanks, problem solved.

Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

  reply	other threads:[~2006-02-21 21:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 15:55 2.6.15-rt17 Ingo Molnar
2006-02-21 16:11 ` 2.6.15-rt17 K.R. Foley
2006-02-21 16:21 ` 2.6.15-rt17 K.R. Foley
2006-02-22  7:51   ` 2.6.15-rt17 Ingo Molnar
2006-02-21 17:16 ` 2.6.15-rt17 Michal Piotrowski
2006-02-21 18:53   ` 2.6.15-rt17 Michal Piotrowski
2006-02-21 20:37     ` 2.6.15-rt17 Thomas Gleixner
2006-02-21 21:15       ` Michal Piotrowski [this message]
2006-02-22 12:22   ` 2.6.15-rt17 Steven Rostedt
2006-02-22 13:47     ` 2.6.15-rt17 Michal Piotrowski
2006-02-24  6:38     ` 2.6.15-rt17 Ingo Molnar
2006-02-24  7:09       ` 2.6.15-rt17 Steven Rostedt
2006-02-21 17:23 ` 2.6.15-rt17 Timothy R. Chavez
2006-02-21 18:24 ` 2.6.15-rt17 Daniel Walker
2006-02-21 18:46   ` 2.6.15-rt17 Thomas Gleixner
2006-02-22 16:50 ` 2.6.15-rt17 Esben Nielsen
2006-02-22 23:17   ` 2.6.15-rt17 Thomas Gleixner
2006-02-25 17:11     ` 2.6.15-rt17 Esben Nielsen
2006-02-25 17:32       ` 2.6.15-rt17 Steven Rostedt
2006-02-25 21:29         ` 2.6.15-rt17 Esben Nielsen
2006-02-25 22:25           ` 2.6.15-rt17 Esben Nielsen
2006-02-26 15:14           ` 2.6.15-rt17 Steven Rostedt
2006-02-26 22:38             ` 2.6.15-rt17 Esben Nielsen
2006-02-27  7:15               ` 2.6.15-rt17 Steven Rostedt
2006-02-23 13:49 ` 2.6.15-rt17 Bill Huey
2006-02-23 13:53   ` 2.6.15-rt17 Ingo Molnar
2006-02-23 14:05     ` 2.6.15-rt17 Bill Huey
2006-02-28 19:21 2.6.15-rt17 Karsten Wiese
2006-02-28 19:43 ` 2.6.15-rt17 Ingo Molnar

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=6bffcb0e0602211315n4ea36c06q@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=simlo@phys.au.dk \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome