All of lore.kernel.org
 help / color / mirror / Atom feed
* [Xenomai-core] BUG while modprobing nucleus - no SMI workaround
@ 2007-11-29 17:57 Giammarco Zacheo
  2007-12-09 16:04 ` Jan Kiszka
  2007-12-09 16:11 ` Jan Kiszka
  0 siblings, 2 replies; 6+ messages in thread
From: Giammarco Zacheo @ 2007-11-29 17:57 UTC (permalink / raw)
  To: xenomai

Just installed kernel 2.6.23.9 with Xenomai 2.4-rc7 on my quad-core
machine, and I got this on the console:

BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/4776
caller is flat_send_IPI_allbutself+0x17/0x32

Call Trace:
 [<ffffffff80319796>] debug_smp_processor_id+0xde/0xec
 [<ffffffff80219fb5>] flat_send_IPI_allbutself+0x17/0x32
 [<ffffffff8021651a>] ipipe_critical_enter+0x84/0xaf
 [<ffffffff80253239>] ipipe_register_domain+0x65/0x225
 [<ffffffff8025387e>] rthal_init+0x164/0x1fd
 [<ffffffff803da4e7>] rthal_domain_entry+0x0/0x3d
 [<ffffffff88103059>] :xeno_nucleus:__xeno_sys_init+0x3e/0x1d4
 [<ffffffff8024bfb2>] sys_init_module+0x1565/0x16c5
 [<ffffffff8020b482>] system_call+0x92/0x97

BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/4776
caller is flat_send_IPI_allbutself+0x17/0x32

Call Trace:
 [<ffffffff80319796>] debug_smp_processor_id+0xde/0xec
 [<ffffffff80219fb5>] flat_send_IPI_allbutself+0x17/0x32
 [<ffffffff802ac2d4>] create_proc_entry+0x73/0x8a
 [<ffffffff8021651a>] ipipe_critical_enter+0x84/0xaf
 [<ffffffff802532e6>] ipipe_register_domain+0x112/0x225
 [<ffffffff8025387e>] rthal_init+0x164/0x1fd
 [<ffffffff803da4e7>] rthal_domain_entry+0x0/0x3d
 [<ffffffff88103059>] :xeno_nucleus:__xeno_sys_init+0x3e/0x1d4
 [<ffffffff8024bfb2>] sys_init_module+0x1565/0x16c5
 [<ffffffff8020b482>] system_call+0x92/0x97

I-pipe: Domain Xenomai registered.
Xenomai: hal/x86_64 started.
Xenomai: real-time nucleus v2.4-rc7 (Bells Of Lal) loaded.
Xenomai: SMI-enabled chipset found
Xenomai: SMI workaround failed!
Xenomai: starting native API services.
Xenomai: starting RTDM services.

if you need my .config file, let me know

Giammarco


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Xenomai-core] BUG while modprobing nucleus - no SMI workaround
  2007-11-29 17:57 [Xenomai-core] BUG while modprobing nucleus - no SMI workaround Giammarco Zacheo
@ 2007-12-09 16:04 ` Jan Kiszka
  2007-12-10 11:24   ` Giammarco Zacheo
  2007-12-09 16:11 ` Jan Kiszka
  1 sibling, 1 reply; 6+ messages in thread
From: Jan Kiszka @ 2007-12-09 16:04 UTC (permalink / raw)
  To: Giammarco Zacheo; +Cc: xenomai

Giammarco Zacheo wrote:
> Just installed kernel 2.6.23.9 with Xenomai 2.4-rc7 on my quad-core
> machine, and I got this on the console:
> 
> BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/4776
> caller is flat_send_IPI_allbutself+0x17/0x32
> 
> Call Trace:
>  [<ffffffff80319796>] debug_smp_processor_id+0xde/0xec
>  [<ffffffff80219fb5>] flat_send_IPI_allbutself+0x17/0x32
>  [<ffffffff8021651a>] ipipe_critical_enter+0x84/0xaf
>  [<ffffffff80253239>] ipipe_register_domain+0x65/0x225
>  [<ffffffff8025387e>] rthal_init+0x164/0x1fd
>  [<ffffffff803da4e7>] rthal_domain_entry+0x0/0x3d
>  [<ffffffff88103059>] :xeno_nucleus:__xeno_sys_init+0x3e/0x1d4
>  [<ffffffff8024bfb2>] sys_init_module+0x1565/0x16c5
>  [<ffffffff8020b482>] system_call+0x92/0x97

Looks like a harmless false positive. Does this patch help?

Index: linux-2.6.23.8-xeno_64/lib/smp_processor_id.c
===================================================================
--- linux-2.6.23.8-xeno_64.orig/lib/smp_processor_id.c
+++ linux-2.6.23.8-xeno_64/lib/smp_processor_id.c
@@ -19,7 +19,7 @@ unsigned int debug_smp_processor_id(void
 	if (likely(preempt_count))
 		goto out;

-	if (irqs_disabled())
+	if (irqs_disabled() || irqs_disabled_hw())
 		goto out;

 	/*

Jan


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Xenomai-core] BUG while modprobing nucleus - no SMI workaround
  2007-11-29 17:57 [Xenomai-core] BUG while modprobing nucleus - no SMI workaround Giammarco Zacheo
  2007-12-09 16:04 ` Jan Kiszka
@ 2007-12-09 16:11 ` Jan Kiszka
  2007-12-09 16:26   ` Gilles Chanteperdrix
  1 sibling, 1 reply; 6+ messages in thread
From: Jan Kiszka @ 2007-12-09 16:11 UTC (permalink / raw)
  To: Giammarco Zacheo; +Cc: xenomai

Giammarco Zacheo wrote:
> Just installed kernel 2.6.23.9 with Xenomai 2.4-rc7 on my quad-core
> machine, and I got this on the console:
> 
...
> 
> I-pipe: Domain Xenomai registered.
> Xenomai: hal/x86_64 started.
> Xenomai: real-time nucleus v2.4-rc7 (Bells Of Lal) loaded.
> Xenomai: SMI-enabled chipset found
> Xenomai: SMI workaround failed!

And that's a different story, likely. Can you post your lspci -nn?

Jan



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Xenomai-core] BUG while modprobing nucleus - no SMI workaround
  2007-12-09 16:11 ` Jan Kiszka
@ 2007-12-09 16:26   ` Gilles Chanteperdrix
       [not found]     ` <b054e88e0712100258l4a52db06m1efd4b0cc2c4e4be@domain.hid>
  0 siblings, 1 reply; 6+ messages in thread
From: Gilles Chanteperdrix @ 2007-12-09 16:26 UTC (permalink / raw)
  To: Jan Kiszka; +Cc: xenomai

Jan Kiszka wrote:
 > Giammarco Zacheo wrote:
 > > Just installed kernel 2.6.23.9 with Xenomai 2.4-rc7 on my quad-core
 > > machine, and I got this on the console:
 > > 
 > ...
 > > 
 > > I-pipe: Domain Xenomai registered.
 > > Xenomai: hal/x86_64 started.
 > > Xenomai: real-time nucleus v2.4-rc7 (Bells Of Lal) loaded.
 > > Xenomai: SMI-enabled chipset found
 > > Xenomai: SMI workaround failed!
 > 
 > And that's a different story, likely. Can you post your lspci -nn?

"SMI workaround failed" does not mean that the chipset is not supported,
it means that the chipset is supported but that masking/settting the SMI
bits failed, probably because the BIOS locked the SMI bits.

-- 


					    Gilles Chanteperdrix.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Xenomai-core] BUG while modprobing nucleus - no SMI workaround
  2007-12-09 16:04 ` Jan Kiszka
@ 2007-12-10 11:24   ` Giammarco Zacheo
  0 siblings, 0 replies; 6+ messages in thread
From: Giammarco Zacheo @ 2007-12-10 11:24 UTC (permalink / raw)
  To: Jan Kiszka; +Cc: xenomai

Yes, it does.

Thanks a lot


On Dec 9, 2007 5:04 PM, Jan Kiszka <jan.kiszka@domain.hid> wrote:
> Giammarco Zacheo wrote:
> > Just installed kernel 2.6.23.9 with Xenomai 2.4-rc7 on my quad-core
> > machine, and I got this on the console:
> >
> > BUG: using smp_processor_id() in preemptible [00000001] code: modprobe/4776
> > caller is flat_send_IPI_allbutself+0x17/0x32
> >
> > Call Trace:
> >  [<ffffffff80319796>] debug_smp_processor_id+0xde/0xec
> >  [<ffffffff80219fb5>] flat_send_IPI_allbutself+0x17/0x32
> >  [<ffffffff8021651a>] ipipe_critical_enter+0x84/0xaf
> >  [<ffffffff80253239>] ipipe_register_domain+0x65/0x225
> >  [<ffffffff8025387e>] rthal_init+0x164/0x1fd
> >  [<ffffffff803da4e7>] rthal_domain_entry+0x0/0x3d
> >  [<ffffffff88103059>] :xeno_nucleus:__xeno_sys_init+0x3e/0x1d4
> >  [<ffffffff8024bfb2>] sys_init_module+0x1565/0x16c5
> >  [<ffffffff8020b482>] system_call+0x92/0x97
>
> Looks like a harmless false positive. Does this patch help?
>
> Index: linux-2.6.23.8-xeno_64/lib/smp_processor_id.c
> ===================================================================
> --- linux-2.6.23.8-xeno_64.orig/lib/smp_processor_id.c
> +++ linux-2.6.23.8-xeno_64/lib/smp_processor_id.c
> @@ -19,7 +19,7 @@ unsigned int debug_smp_processor_id(void
>         if (likely(preempt_count))
>                 goto out;
>
> -       if (irqs_disabled())
> +       if (irqs_disabled() || irqs_disabled_hw())
>                 goto out;
>
>         /*
>
> Jan
>


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Xenomai-core] BUG while modprobing nucleus - no SMI workaround
       [not found]     ` <b054e88e0712100258l4a52db06m1efd4b0cc2c4e4be@domain.hid>
@ 2007-12-10 11:25       ` Giammarco Zacheo
  0 siblings, 0 replies; 6+ messages in thread
From: Giammarco Zacheo @ 2007-12-10 11:25 UTC (permalink / raw)
  To: xenomai

The smictrl utility gives this output:

# ./smictrl -s 0

SMI-enabled chipset found:
PCI_VENDOR_ID_INTEL:PCI_DEVICE_ID_INTEL_ICH7_0 (8086:27b8)
SMI_EN register:       0002202b
new value:             00000003

Seems like someone's locking those bits.

Anyway, lspci -nn gives this:

00:00.0 Host bridge [0600]: Intel Corporation 82975X Memory Controller
Hub [8086:277c]
00:01.0 PCI bridge [0604]: Intel Corporation 82975X PCI Express Root
Port [8086:277d]
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family)
High Definition Audio Controller [8086:27d8] (rev 01)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI
Express Port 1 [8086:27d0] (rev 01)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7
Family) PCI Express Port 5 [8086:27e0] (rev 01)
00:1c.5 PCI bridge [0604]: Intel Corporation 82801GR/GH/GHM (ICH7
Family) PCI Express Port 6 [8086:27e2] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI Controller #1 [8086:27c8] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI Controller #2 [8086:27c9] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI Controller #3 [8086:27ca] (rev 01)
00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB UHCI Controller #4 [8086:27cb] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family)
USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family)
LPC Interface Bridge [8086:27b8] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family)
IDE Controller [8086:27df] (rev 01)
00:1f.2 RAID bus controller [0104]: Intel Corporation 82801GR/GH (ICH7
Family) SATA RAID Controller [8086:27c3] (rev 01)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV515GL
[FireGL V3350] [1002:7153]
01:00.1 Display controller [0380]: ATI Technologies Inc RV515GL
[FireGL V3350] (Secondary) [1002:7173]
3f:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme
BCM5755 Gigabit Ethernet PCI Express [14e4:167b] (rev 02)


> "SMI workaround failed" does not mean that the chipset is not supported,
> it means that the chipset is supported but that masking/settting the SMI
> bits failed, probably because the BIOS locked the SMI bits.
>
> --
>                                             Gilles Chanteperdrix.
>


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-12-10 11:25 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-29 17:57 [Xenomai-core] BUG while modprobing nucleus - no SMI workaround Giammarco Zacheo
2007-12-09 16:04 ` Jan Kiszka
2007-12-10 11:24   ` Giammarco Zacheo
2007-12-09 16:11 ` Jan Kiszka
2007-12-09 16:26   ` Gilles Chanteperdrix
     [not found]     ` <b054e88e0712100258l4a52db06m1efd4b0cc2c4e4be@domain.hid>
2007-12-10 11:25       ` Giammarco Zacheo

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.