From: Christophe Lermytte <christophe.lermytte@thomson.net>
To: linux-kernel@vger.kernel.org
Subject: mutex_lock_slowpath warning using mxser tty driver (input/output error)
Date: Thu, 02 Apr 2009 18:26:05 +0200 [thread overview]
Message-ID: <1238689565.14822.99.camel@thom> (raw)
Hi all,
I have upgraded one of my automated test setups from 2.6.27 to 2.6.29. I
now have issues with using a Moxa multiport serial device, where I had
none before :-)
> MOXA Smartio/Industio family driver version 2.0.4
> mxser 0000:03:02.0: found MOXA C168H/PCI series board (BusNo=3,
DevNo=2)
> mxser 0000:03:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> mxser: max. baud rate = 921600 bps
When I cat /dev/setup3 (which is a symlink to /dev/ttyMI3), which is
connected to a device that outputs data (tried it with one @ 115200bps
and one @ 9600bps), I get the following kernel trace:
------------[ cut here ]------------
WARNING: at kernel/mutex.c:135 __mutex_lock_slowpath+0x50/0x211()
Hardware name: OptiPlex 755
Modules linked in: i915 drm i2c_algo_bit ipv6 8021q dummy fuse arc4 ecb
snd_hda_codec_analog snd_hda_intel snd_hda_codec rtl8187 mac80211 usbhid
i2c_i801 snd_pcm serio_raw eeprom_93cx6 iTCO_wdt i2c_core
iTCO_vendor_support cfg80211 snd_timer snd snd_page_alloc rtc_cmos
rtc_core intel_agp agpgart mxser ppdev thermal uhci_hcd sg rtc_lib
parport_pc processor parport button thermal_sys dcdbas
Pid: 0, comm: swapper Not tainted 2.6.29-autodistro-r4 #1
Call Trace:
[<c0127479>] warn_slowpath+0x74/0x8a
[<c016bb1a>] ? get_page_from_freelist+0xc1/0x3c6
[<c04e0093>] ? usb_hcd_submit_urb+0x88d/0x95b
[<c05d2d41>] ? _spin_lock+0x8/0xb
[<c0187063>] ? cache_alloc_refill+0x19f/0x499
[<c05d1b63>] __mutex_lock_slowpath+0x50/0x211
[<c05d1d36>] mutex_lock+0x12/0x15
[<c026d677>] echo_set_canon_col+0x14/0x37
[<c026e478>] n_tty_receive_buf+0x2f3/0xe0c
[<c05d2d41>] ? _spin_lock+0x8/0xb
[<c0187063>] ? cache_alloc_refill+0x19f/0x499
[<c05d2e5e>] ? _spin_lock_irqsave+0x28/0x2f
[<c012f01d>] ? lock_timer_base+0x1f/0x3e
[<c0118b2d>] ? default_spin_lock_flags+0x8/0xb
[<c0118b2d>] ? default_spin_lock_flags+0x8/0xb
[<c02710ed>] flush_to_ldisc+0xe9/0x159
[<c027119e>] tty_flip_buffer_push+0x41/0x51
[<f842e5f5>] mxser_receive_chars+0x237/0x246 [mxser]
[<f842fac5>] mxser_interrupt+0x18e/0x228 [mxser]
[<c015ac54>] handle_IRQ_event+0x2a/0x5a
[<c015c11a>] handle_fasteoi_irq+0x7b/0xb4
[<c015c09f>] ? handle_fasteoi_irq+0x0/0xb4
<IRQ> [<c0103527>] ? common_interrupt+0x27/0x2c
[<c0108131>] ? mwait_idle+0x4c/0x5b
[<c0101a5b>] ? cpu_idle+0x59/0x6d
[<c05ce807>] ? start_secondary+0x19f/0x1a4
---[ end trace 433a17e91cdf059a ]---
After I break the cat, subsequent cat's result in:
cat /dev/setup3
cat: /dev/setup3: Input/output error
I'm not a kernel expert, so if you have any pointers or ways to provide
more information, don't hesitate to ask.
Regards,
Christophe L.
next reply other threads:[~2009-04-02 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 16:26 Christophe Lermytte [this message]
2009-04-02 18:19 ` mutex_lock_slowpath warning using mxser tty driver (input/output error) Peter Zijlstra
2009-04-02 18:44 ` Alan Cox
2009-04-02 20:23 ` Jiri Slaby
2009-04-02 22:55 ` Alan Cox
2009-04-03 0:33 ` Johannes Weiner
2009-04-21 12:20 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2009-04-02 21:37 Christophe Lermytte
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=1238689565.14822.99.camel@thom \
--to=christophe.lermytte@thomson.net \
--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