[asterisk-bugs] [JIRA] (DAHLIN-311) Kernel panic when loading X100P module wcfxo with Intel Server Board

Fernando Luiz Chaves Xavier Matos (JIRA) noreply at issues.asterisk.org
Wed Dec 19 18:24:45 CST 2012


    [ https://issues.asterisk.org/jira/browse/DAHLIN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200888#comment-200888 ] 

Fernando Luiz Chaves Xavier Matos commented on DAHLIN-311:
----------------------------------------------------------

I always used 2.6.1 since X100P purchase with 3.x kernels in Arch Linux and others. 
It works with any other computer, but not with this.
Currently, putting the X100P on another computer using Arch Linux with 3.6, it works.

output of "lspci -d d161:* -vvv"
02:08.0 Ethernet controller: Digium, Inc. Wildcard AEX800 8-port analog card (PCI-Express) (rev 11)
	Subsystem: Digium, Inc. Wildcard AEX800 8-port analog card (PCI-Express)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (16000ns min, 32000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at 4000 [size=256]
	Region 1: Memory at c1920000 (32-bit, non-prefetchable) [size=1K]
	Expansion ROM at c1900000 [disabled] [size=128K]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: wctdm24xxp
	Kernel modules: wctdm24xxp

Surely, this is not X100P but this:

05:00.0 Communication controller: Motorola Wildcard X100P
	Subsystem: Efar Microsystems Device 0001
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (250ns min, 32000ns max)
	Interrupt: pin A routed to IRQ 255
	Region 0: I/O ports at 2000 [size=256]
	Region 1: Memory at c2300000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: wcfxo


                
> Kernel panic when loading X100P module wcfxo with Intel Server Board
> --------------------------------------------------------------------
>
>                 Key: DAHLIN-311
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-311
>             Project: DAHDI-Linux
>          Issue Type: Bug
>      Security Level: None
>          Components: wcfxo
>    Affects Versions: 2.6.1
>         Environment: Hardware:
> Intel S1200BTLR
> Intel Xeon 1270v2
> 16GB DDR3 ECC
> 1 X100P
> 1 AEX800 with 8 FXS.
> Software tested:
> Centos 6.3 64-bit with kernel 2.6.32-279 and kernel-ml 3.6.10 (from elrepo.org)
> Ubuntu 12.10 32-bit (got the same issue).
>            Reporter: Fernando Luiz Chaves Xavier Matos
>            Assignee: Russ Meyerriecks
>            Severity: Critical
>
> When loading the X100P module "wcfxo" the kernel crashes.
> Notes:
> - On an ordinary computer (Asus M4A88T-M with Phenom II X4) everything works fine.
> - Tested with another X100P and got the same problem.
> - Running "modprobe wcfxo" without the X100P attached, the modules loads normally, being listed in "lsmod".
> Kernel dump:
> {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
> NOTICE-wcfxo: WCFXO/0: Unknown DAA chip revision: REVB=0
> Failed to initailize DAA, giving up...
> dahdi: disable_span: span 2
> {1}[Hardware Error]: APEI generic hardware error status
> {1}[Hardware Error]: severity: 1, fatal
> {1}[Hardware Error]: section: 0, severity: 1, fatal
> {1}[Hardware Error]: flags: 0x01
> {1}[Hardware Error]: primary
> {1}[Hardware Error]: section_type: PCIe error
> [Firmware Warn]: error section length is too small
> {1}[Hardware Error]: section: 1, severity: 1, fatal
> {1}[Hardware Error]: flags: 0x01
> {1}[Hardware Error]: primary
> {1}[Hardware Error]: section_type: PCIe error
> [Firmware Warn]: error section length is too small
> Kernel panic - not syncing: Fatal hardware error!
> panic occurred, switching back to text console
> ------------[ cut here ]------------
> WARNING: at arch/x86/kernel/smp.c:123 native_smp_send_reschedule+0x5c/0x60()
> Hardware name: S1200BTL
> Modules linked in: wcfxo(O+) sunrpc dahdi_echocan_mg2(O) wctdm24xxp(O) dahdi_voicebus(O) dahdi(O) crc_ccitt ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nfd
> Pid: 428, comm: udevd Tainted: G           O 3.6.10-1.el6.elrepo.x86_64 #1
> Call Trace:
>  [<ffffffff81055a2f>] warn_slowpath_common+0x7f/0xc0
>  [<ffffffff81055a8a>] warn_slowpath_null+0x1a/0x20
>  [<ffffffff8103896c>] native_smp_send_reschedule+0x5c/0x60
>  [<ffffffff810909b6>] trigger_load_balance+0x1c6/0x240
>  [<ffffffff81088e5f>] scheduler_tick+0x10f/0x140
>  [<ffffffff81065f2e>] update_process_times+0x6e/0x90
>  [<ffffffff810ae7fe>] tick_sched_timer+0x6e/0xe0
>  [<ffffffff8107e543>] __run_hrtimer+0x83/0x1d0
>  [<ffffffff810ae790>] ? tick_nohz_handler+0x100/0x100
>  [<ffffffff8107e916>] hrtimer_interrupt+0xf6/0x240
>  [<ffffffff815a2f79>] smp_apic_timer_interrupt+0x69/0x99
>  [<ffffffff815a1f4a>] apic_timer_interrupt+0x6a/0x70
>  [<ffffffff81089e13>] ? finish_task_switch+0x53/0xe0
>  [<ffffffff81597d5d>] __schedule+0x3ed/0x710
>  [<ffffffff8108d980>] ? try_to_wake_up+0x2b0/0x2b0
>  [<ffffffff815983a9>] schedule+0x29/0x70
>  [<ffffffff815970e5>] schedule_hrtimeout_range_clock+0xc5/0x160
>  [<ffffffff8107df40>] ? update_rmtp+0x80/0x80
>  [<ffffffff8107f0f4>] ? hrtimer_start_range_ns+0x14/0x20
>  [<ffffffff81597193>] schedule_hrtimeout_range+0x13/0x20
>  [<ffffffff8118c9b9>] poll_schedule_timeout+0x49/0x70
>  [<ffffffff8118cf55>] do_poll+0x255/0x2c0
>  [<ffffffff8118d9af>] do_sys_poll+0x1bf/0x240
>  [<ffffffff8118cba0>] ? __pollwait+0xf0/0xf0
>  [<ffffffff8118cba0>] ? __pollwait+0xf0/0xf0
>  [<ffffffff8118cba0>] ? __pollwait+0xf0/0xf0
>  [<ffffffff8118cba0>] ? __pollwait+0xf0/0xf0
>  [<ffffffff8118cba0>] ? __pollwait+0xf0/0xf0
>  [<ffffffff811498d9>] ? handle_mm_fault+0x259/0x370
>  [<ffffffff8117935a>] ? do_sync_write+0xaa/0xf0
>  [<ffffffff814a895e>] ? sys_recvfrom+0xee/0x170
>  [<ffffffff8101b969>] ? read_tsc+0x9/0x20
>  [<ffffffff810a718c>] ? ktime_get_ts+0x4c/0xf0
>  [<ffffffff8118c955>] ? poll_select_set_timeout+0x95/0xb0
>  [<ffffffff8118daa1>] sys_poll+0x71/0x100
>  [<ffffffff815a14a9>] system_call_fastpath+0x16/0x1b
> ---[ end trace 7406a3ac861eea2c ]---
> Rebooting in 30 seconds..

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list