Re: What you can also do to better observe the real problem on your computer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Patrick,

I never worked on a problem theoretically. So open an SSH connection to your computer for my intent. I gave you my public SSH key in a private email.

If you do not open me an SSH connection, I shall classify your problem as non reproducible. It will then be then up to you to correct the driver if you want to be satisfied. Anyhow, I never sign others work unless I can also prove it produces expected result.

Philippe

Le 09/01/2012 15:21, Patrick Boyadjian a écrit :
HI Philippe,

Something very wierd is going on here.  I have the modem in the original IRQ #19 slot (the slot my other hcf modem was in) and the lspci -vv output is as follows:

01:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
         Subsystem: Intel Corporation Digium X100P/X101P analogue PSTN FXO interface
         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 11
         Region 0: I/O ports at a000 [size=256]
         Region 1: Memory at f1004000 (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: hisax, netjet




IRQ 11?!?!?  why would it switch from IRQ 19???





cat /proc/interrupts shows:

[root@pb3000 ~]# cat /proc/interrupts
             CPU0       CPU1
    0:        121          0   IO-APIC-edge      timer
    1:          2          0   IO-APIC-edge      i8042
    7:          0          0   IO-APIC-edge      parport0
    8:          1          0   IO-APIC-edge      rtc0
    9:          0          0   IO-APIC-fasteoi   acpi
   12:          4          0   IO-APIC-edge      i8042
   14:        324          0   IO-APIC-edge      ata_piix
   15:          0          0   IO-APIC-edge      ata_piix
   16:         74          0   IO-APIC-fasteoi   uhci_hcd:usb5, i915
   18:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4
   19:     466267          0   IO-APIC-fasteoi   ata_piix, uhci_hcd:usb3
   21:        474          0   IO-APIC-fasteoi   p3p1
   23:       2845          0   IO-APIC-fasteoi   ehci_hcd:usb1, uhci_hcd:usb2, firewire_ohci
   40:        226          0   PCI-MSI-edge      snd_hda_intel
  NMI:          1          0   Non-maskable interrupts
  LOC:      27201      10536   Local timer interrupts
  SPU:          0          0   Spurious interrupts
  PMI:          1          0   Performance monitoring interrupts
  IWI:          0          0   IRQ work interrupts
  RES:       3140       6289   Rescheduling interrupts
  CAL:         30         34   Function call interrupts
  TLB:         53        110   TLB shootdowns
  TRM:          0          0   Thermal event interrupts
  THR:          0          0   Threshold APIC interrupts
  MCE:          0          0   Machine check exceptions
  MCP:          1          1   Machine check polls
  ERR:          0
  MIS:          0


Here is the dmesg of ./test now:

[  385.166575] 537: Loaded
[  386.787168] BUG: scheduling while atomic: kworker/1:2/46/0x10000200
[  386.787219] Modules linked in: 8021q garp Intel537 bridge stp llc it87 hwmon_vid nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ppdev joydev microcode snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq netjet isdnhdlc crc_ccitt mISDNipac snd_seq_device i2c_i801 serio_raw r8169 mii mISDN_core snd_pcm iTCO_wdt iTCO_vendor_support parport_pc parport snd_timer snd soundcore snd_page_alloc uinput usb_storage firewire_ohci firewire_core crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan]
[  386.787280] Pid: 46, comm: kworker/1:2 Not tainted 3.1.6-1.fc16.i686 #1
[  386.787283] Call Trace:
[  386.787294]  [<c090411b>] ? printk+0x2d/0x2f
[  386.787299]  [<c0903eb8>] __schedule_bug+0x5e/0x64
[  386.787305]  [<c090b4b6>] __schedule+0x876/0x8b0
[  386.787311]  [<c04e57bc>] ? __alloc_pages_nodemask+0xfc/0x6f0
[  386.787317]  [<c04090e8>] ? sched_clock+0x8/0x10
[  386.787323]  [<c0470b7b>] ? sched_clock_local+0xcb/0x1c0
[  386.787328]  [<c041009f>] ? p4_pmu_enable_event+0xcf/0x130
[  386.787334]  [<c090eae0>] ? do_debug+0x180/0x180
[  386.787339]  [<c04449ab>] __cond_resched+0x1b/0x30
[  386.787344]  [<c090b569>] _cond_resched+0x29/0x30
[  386.787350]  [<c0517a4d>] kmem_cache_alloc+0x11d/0x140
[  386.787355]  [<c0411a3c>] ? p4_pmu_disable_all+0x5c/0x70
[  386.787359]  [<c040b18f>] ? init_fpu+0x7f/0x120
[  386.787364]  [<c090eae0>] ? do_debug+0x180/0x180
[  386.787368]  [<c040b18f>] init_fpu+0x7f/0x120
[  386.787372]  [<c090eae0>] ? do_debug+0x180/0x180
[  386.787376]  [<c0404374>] math_state_restore+0x24/0x50
[  386.787381]  [<c090eaf0>] do_device_not_available+0x10/0x20
[  386.787385]  [<c090e0e7>] error_code+0x67/0x6c
[  386.787586]  [<fa001c11>] ? w7_ippsFFTInitAlloc_C_16sc+0x3d/0x1d6 [Intel537]
[  386.787699]  [<f9e84bd8>] ? Phase2InitAlloc+0xb8/0x100 [Intel537]
[  386.787801]  [<f9e56039>] ? OmpInitAlloc+0x19/0x90 [Intel537]
[  386.787899]  [<f9e5063d>] ? ModemInit+0x2ed/0x380 [Intel537]
[  386.787997]  [<f9e4f39d>] ? ModemTasks+0x12d/0x160 [Intel537]
[  386.788185]  [<f9e472a1>] ? ModemTask+0x11/0x20 [Intel537]
[  386.788355]  [<f9e43b02>] ? linux_MT_AcquireLock_mt_dsp+0x12/0x20 [Intel537]
[  386.788548]  [<f9e4585d>] ? InterruptDSP+0x1d/0x30 [Intel537]
[  386.788842]  [<fa09b676>] ? set_register+0x30/0x34 [Intel537]
[  386.789010]  [<fa0dc688>] ? dspdrv_PutCRAM+0x74/0x7c [Intel537]
[  386.789318]  [<f9e43e0a>] ? linux_RSAGetExclusive+0xea/0x100 [Intel537]
[  386.789544]  [<fa0e3b5d>] ? cp_dsp+0x3f/0xf2 [Intel537]
[  386.789865]  [<fa09d1d9>] ? BLK_shell+0x39/0xa4 [Intel537]
[  386.790117]  [<fa0e0b45>] ? SendPacketOut+0x23/0x5a [Intel537]
[  386.790353]  [<fa0e0b0a>] ? send_pkt_to_dsp+0xe/0x26 [Intel537]
[  386.790601]  [<fa0e275d>] ? ResetDspIdle+0x87/0xde [Intel537]
[  386.790826]  [<fa0dce1a>] ? mt_init+0x32/0xf0 [Intel537]
[  386.791116]  [<fa0b9bf6>] ? master_init+0x50/0x16a [Intel537]
[  386.791293]  [<f9e42892>] ? clm_bg+0x32/0x180 [Intel537]
[  386.791484]  [<f9e42a2d>] ? RTS_Task+0x4d/0x60 [Intel537]
[  386.791567]  [<c046567a>] ? process_one_work+0xfa/0x390
[  386.791574]  [<c04637b0>] ? do_work_for_cpu+0x20/0x20
[  386.791764]  [<f9e429e0>] ? clm_bg+0x180/0x180 [Intel537]
[  386.791797]  [<c0466371>] ? worker_thread+0x121/0x2d0
[  386.791828]  [<c0466250>] ? manage_workers+0x1f0/0x1f0
[  386.791884]  [<c046a1cd>] ? kthread+0x6d/0x80
[  386.791916]  [<c046a160>] ? kthread_worker_fn+0x140/0x140
[  386.791974]  [<c09148be>] ? kernel_thread_helper+0x6/0x10
[root@pb3000 ~]#


here is the lsmod output:

[root@pb3000 ~]# lsmod
Module                  Size  Used by
8021q                  16205  0
garp                    5484  1 8021q
Intel537             4308822  0
bridge                 71710  0
stp                     1519  2 garp,bridge
llc                     4150  3 garp,bridge,stp
it87                   27326  0
hwmon_vid               2620  1 it87
nf_conntrack_ipv4       7530  5
nf_defrag_ipv4          1173  1 nf_conntrack_ipv4
xt_state                1022  5
nf_conntrack           64124  2 nf_conntrack_ipv4,xt_state
ppdev                   6899  0
joydev                  7780  0
microcode              11746  0
snd_hda_codec_realtek   247366  1
snd_hda_intel          23025  0
snd_hda_codec          84779  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               5396  1 snd_hda_codec
snd_seq                48285  0
netjet                 13686  0
isdnhdlc                4723  1 netjet
crc_ccitt               1281  1 isdnhdlc
mISDNipac              30298  1 netjet
snd_seq_device          5441  1 snd_seq
i2c_i801                8657  0
serio_raw               3582  0
r8169                  40635  0
mii                     4091  1 r8169
mISDN_core             74659  2 netjet,mISDNipac
snd_pcm                73885  2 snd_hda_intel,snd_hda_codec
iTCO_wdt               10396  0
iTCO_vendor_support     2203  1 iTCO_wdt
parport_pc             18014  0
parport                29655  2 ppdev,parport_pc
snd_timer              17660  2 snd_seq,snd_pcm
snd                    55194  8 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore               5892  1 snd
snd_page_alloc          6641  2 snd_hda_intel,snd_pcm
uinput                  5946  0
usb_storage            39367  0
firewire_ohci          26697  0
firewire_core          47693  1 firewire_ohci
crc_itu_t               1287  1 firewire_core
i915                  500426  1
drm_kms_helper         26252  1 i915
drm                   172493  2 i915,drm_kms_helper
i2c_algo_bit            4724  1 i915
i2c_core               23631  5 i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video                  10744  1 i915









Philippe, I am not very familiar with stack traces and all the things you mention , so can you please keep things in laymans terms and explicitly give commands I should be typing in?

I do observe the PC hanging and locking up when I do make install and make uninstall commands...not sure if that helps.

Is there anyway to start things from scratch?  If so what are my steps?

Patrick


On Sun, Jan 08, 2012 at 09:24:06AM +0100, Philippe Vouters wrote:
Patrick,

The keyword to remain when the problem becomes complex is
simplification. Although there is an IRQ conflict between the sound
driver and 536EP driver on my computer, if I do not activate the
sound while testing the 536EP driver, I now incur no observable
problem with both the small test program and efax. I may test wvdial
but this should inevitably lead me to a NO CARRIER behavior as I no
longer subscribe to a phone line having switched to VoIP.

As the problem involves a driver, in a first approach, perform an
lsmod than you output to a text file for eventual later control.
Then rmmod all the drivers running on your computer which are
unneeded for the problem. At first glance, you should only keep a
video, mouse, and keyboard driver all used by the X server, likely
as well an IP stack related drivers and of course the 537 driver.

For the software, you only need the test program in a first
approach. Attempt to reproduce the problem with all the Intel's
driver code you downloaded from my Web site (with the "_bh" string
back in coredrv/locks.c) and the C source driver's code I last
mailed you. If you execute the test code several times quickly do
you still incur the problem ? Do you observe a computer freeze like
I did during my testing. Is the Call trace identical or different
than the efax Call trace you sent me. If different, check more
closely your PC hardware.

If you no longer generate any Call trace with the test program,
recheck with the efax command I suggest on my Web site and that I
mailed you. If efax reacts normally when no phone call dialing in,
then still in the very same simple drivers environment, test a real
wvdial. Is it reacting as expected ? When it dials your Internet
provider phone number, take up the phone receiver and listen to the
noise wvdial produces. Is the sound you hear expected from a modem
software ?

When and if all tests succeed without any obvious symptom proving a
badly executing software, you may then complexify step by step . For
this, you reinject using modprobe one driver at a time you rmmod and
perform again the exact same wvdial test. Also check each time using
cat /proc/interrupts which driver occupies which IRQ. Once you get
wvdial no longer correclty behaving, you perfectly know which driver
causes the interference with the 537 driver on your computer. With
this knowledge, you may act accordingly to get rid from the
interference.

If none of the drivers you modprobe'd cause a problem, then you'll
have to check your natural software environment. First, reboot your
computer to start it up normally. Once your computer is operaitonal,
output dmesg to a file and study it carefully. Then recheck the
wvdial command after having started a tail -f /var/log/messages in
another terminal.

If you notice again a call trace involving the Intel 537 driver and
you do not incur a freeze, then perform from root an lsof that you
direct to a file that you study in detail.

The question to answer : which software running on your computer
uses which /dev/xxxx device. Pay special attention to any software
using /dev/modem or /dev/537. Another item to look at: which
software uses a /dev device which IRQ is at the same level than for
the 537 modem.

If after reboot, the wvdial command works normally with no call
trace and you did make strictly no change, either to software or to
hardware, you may likely once again incur a problem later, but when
it will occur this will be without me as your problem is purely
hardware.

Philippe
--
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/


--
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux