linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 49821] New: Random Call traces when using tape device.
Date: Wed, 31 Oct 2012 19:23:17 +0000 (UTC)	[thread overview]
Message-ID: <bug-49821-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=49821

           Summary: Random Call traces when using tape device.
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 3.2.29
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
        AssignedTo: linux-scsi@vger.kernel.org
        ReportedBy: ilovequake@tlen.pl
        Regression: No


Created an attachment (id=85361)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=85361)
dmesg, lsmod, lspci, irqs

Hello,

Sorry if I posted in bad section.
When i'm using my tape device to save the data i'm getting this message:
[ 8914.751464] Call Trace:
[ 8914.751469]  [<c1485e23>] ? printk+0x1d/0x1f
[ 8914.751472]  [<c109c419>] __report_bad_irq+0x29/0xd0
[ 8914.751475]  [<c12b3625>] ? add_interrupt_randomness+0x125/0x150
[ 8914.751477]  [<c109c6d5>] note_interrupt+0x175/0x1c0
[ 8914.751478]  [<c125b04c>] ? intel_idle+0xdc/0x130
[ 8914.751480]  [<c109a5aa>] handle_irq_event_percpu+0xaa/0x1d0
[ 8914.751482]  [<c109a702>] handle_irq_event+0x32/0x60
[ 8914.751484]  [<c109cee0>] ? unmask_irq+0x30/0x30
[ 8914.751486]  [<c109cf2b>] handle_fasteoi_irq+0x4b/0xd0
[ 8914.751487]  <IRQ>  [<c148f7b2>] ? do_IRQ+0x42/0xc0
[ 8914.751490]  [<c148f6f0>] ? common_interrupt+0x30/0x38
[ 8914.751493]  [<c10400e0>] ? task_times+0x60/0xa0
[ 8914.751494]  [<c125b04c>] ? intel_idle+0xdc/0x130
[ 8914.751497]  [<c139e0a6>] ? cpuidle_idle_call+0xb6/0x210
[ 8914.751498]  [<c1001757>] ? cpu_idle+0x97/0xe0
[ 8914.751500]  [<c14731ba>] ? rest_init+0x62/0x68
[ 8914.751502]  [<c16437a9>] ? start_kernel+0x36d/0x373
[ 8914.751504]  [<c16431c1>] ? loglevel+0x2b/0x2b
[ 8914.751505]  [<c164311a>] ? reserve_ebda_region+0x67/0x69
[ 8914.751507]  [<c16430ac>] ? i386_start_kernel+0xac/0xb3
[ 8914.751508] handlers:
[ 8914.751516] [<f8465e90>] mpt_interrupt
[ 8914.751517] Disabling IRQ #17

There is no difference after changing the slot of my PCI controller.

Slackware-current, Linux zonk 3.2.29-smp #1 SMP Mon Sep 17 13:02:10 CDT 2012
i686 Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz GenuineIntel GNU/Linux

If you need more info about my pc/soft. please ask.

Thanks.
Marek

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-10-31 19:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 19:23 bugzilla-daemon [this message]
2012-11-01 14:12 ` [Bug 49821] Random Call traces when using tape device bugzilla-daemon
2012-11-01 15:56 ` bugzilla-daemon
2012-11-01 15:58 ` bugzilla-daemon
2012-11-01 16:03 ` bugzilla-daemon
2012-11-01 16:05 ` bugzilla-daemon
2013-11-19 22:27 ` bugzilla-daemon

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=bug-49821-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).