mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Arno Schuring <aelschuring@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i386 WARNING: at kernel/softirq.c:143 _local_bh_enable_ip+0x2f/0x7e
Date: Sun, 29 Aug 2010 15:58:24 +0200	[thread overview]
Message-ID: <201008291558.24588.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <4C781A3A.4010707@hotmail.com>

On piątek, 27 sierpnia 2010 o 22:04:10 Arno Schuring wrote:
> Hello list,
> 
> [ if this is the wrong place, please redirect. Kerneloops and bugzilla
> seem down atm, only other reference I found is this thread from
> February: http://lkml.org/lkml/2010/2/25/454 ]
> 
> 
> Testing current -git on my old desktop machine yields the following
> warning:
> 
> [   12.437090] WARNING: at kernel/softirq.c:143
> _local_bh_enable_ip+0x2f/0x7e()
> [   12.437094] Hardware name:
> [   12.437097] Modules linked in: xfs exportfs w83627hf_wdt w83627hf
> hwmon_vid dm_crypt dm_mod usbhid 8250_pnp 8250 hid processor pcspkr
> i2c_sis96x serial_core evdev usb_storage rtc_cmos button rtc_core
> rtc_lib ext4 jbd2 crc16 ohci_hcd ehci_hcd usbcore thermal thermal_sys
> floppy nls_base sr_mod cdrom [last unloaded: scsi_wait_scan]
> [   12.437148] Pid: 0, comm: swapper Not tainted 2.6.36-rc2+ #18
> [   12.437152] Call Trace:
> [   12.437167]  [<c1024fc1>] ? warn_slowpath_common+0x6a/0x7b
> [   12.437172]  [<c102975a>] ? _local_bh_enable_ip+0x2f/0x7e
> [   12.437178]  [<c1024fdf>] ? warn_slowpath_null+0xd/0x10
> [   12.437183]  [<c102975a>] ? _local_bh_enable_ip+0x2f/0x7e
> [   12.437191]  [<c125c782>] ? netpoll_rx+0x71/0x77
> [   12.437195]  [<c125c796>] ? netif_rx+0xe/0xf7
> [   12.437204]  [<c12207c3>] ? sis900_interrupt+0x1c7/0x4ab
> [   12.437212]  [<c10580e7>] ? handle_IRQ_event+0x54/0x102
> [   12.437218]  [<c1059985>] ? handle_fasteoi_irq+0x8c/0xdf
> [   12.437223]  [<c10598f9>] ? handle_fasteoi_irq+0x0/0xdf
> [   12.437226]  <IRQ>  [<c1003a3c>] ? do_IRQ+0x2b/0x7f
> [   12.437237]  [<c1002ca9>] ? common_interrupt+0x29/0x30
> [   12.437246]  [<c1007eba>] ? default_idle+0x39/0x4c
> [   12.437250]  [<c1001b00>] ? cpu_idle+0x35/0xad
> [   12.437258]  [<c14346c0>] ? start_kernel+0x274/0x277
> [   12.437262] ---[ end trace d2278ae4badf238c ]---
> 
> 
> Kernel version is current git (well, yesterday's):
> aschuring@neminis:~/work/linux-GIT$ git describe HEAD
> v2.6.36-rc2-237-gd4348c6
> 

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=17321
for your bug report, please add your address to the CC list in there, thanks!


-- 
Maciej Rutecki
http://www.maciek.unixy.pl

      reply	other threads:[~2010-08-29 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 20:04 Arno Schuring
2010-08-29 13:58 ` Maciej Rutecki [this message]

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=201008291558.24588.maciej.rutecki@gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=aelschuring@hotmail.com \
    --cc=linux-kernel@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

Powered by JetHome