mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Anatoly Pugachev <matorola@gmail.com>, linux-block@vger.kernel.org
Cc: Sparc kernel list <sparclinux@vger.kernel.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [sparc64] pktcdvd: setup of pktcdvd device failed
Date: Fri, 20 Sep 2019 07:01:45 -0600	[thread overview]
Message-ID: <c02d0e0c-e468-003f-6b66-8592a987cbf8@kernel.dk> (raw)
In-Reply-To: <CADxRZqz_TF7jyGtbg9cVSnCGh2VzfCoRGBdCU_yE_v1cveq1Pg@mail.gmail.com>

On 9/20/19 4:27 AM, Anatoly Pugachev wrote:
> Hello!
> 
> Getting the following call trace on boot on sparc64 ldom/machine with
> current git kernel:
> 
> ...
> [   13.352975] aes_sparc64: Using sparc64 aes opcodes optimized AES
> implementation
> [   13.428002] ------------[ cut here ]------------
> [   13.428081] WARNING: CPU: 21 PID: 586 at
> drivers/block/pktcdvd.c:2597 pkt_setup_dev+0x2e4/0x5a0 [pktcdvd]
> [   13.428147] Attempt to register a non-SCSI queue
> [   13.428184] Modules linked in: pktcdvd libdes cdrom aes_sparc64
> n2_rng md5_sparc64 sha512_sparc64 rng_core sha256_sparc64 flash
> sha1_sparc64 ip_tables x_tables ipv6 crc_ccitt nf_defrag_ipv6 autofs4
> ext4 crc16 mbcache jbd2 raid10 raid456 async_raid6_recov async_memcpy
> async_pq async_xor xor async_tx raid6_pq raid1 raid0 multipath linear
> md_mod crc32c_sparc64
> [   13.428452] CPU: 21 PID: 586 Comm: pktsetup Not tainted
> 5.3.0-10169-g574cc4539762 #1234
> [   13.428507] Call Trace:
> [   13.428542]  [00000000004635c0] __warn+0xc0/0x100
> [   13.428582]  [0000000000463634] warn_slowpath_fmt+0x34/0x60
> [   13.428626]  [000000001045b244] pkt_setup_dev+0x2e4/0x5a0 [pktcdvd]
> [   13.428674]  [000000001045ccf4] pkt_ctl_ioctl+0x94/0x220 [pktcdvd]
> [   13.428724]  [00000000006b95c8] do_vfs_ioctl+0x628/0x6e0
> [   13.428764]  [00000000006b96c8] ksys_ioctl+0x48/0x80
> [   13.428803]  [00000000006b9714] sys_ioctl+0x14/0x40
> [   13.428847]  [0000000000406294] linux_sparc_syscall+0x34/0x44
> [   13.428890] irq event stamp: 4181
> [   13.428924] hardirqs last  enabled at (4189): [<00000000004e0a74>]
> console_unlock+0x634/0x6c0
> [   13.428984] hardirqs last disabled at (4196): [<00000000004e0540>]
> console_unlock+0x100/0x6c0
> [   13.429048] softirqs last  enabled at (3978): [<0000000000b2e2d8>]
> __do_softirq+0x498/0x520
> [   13.429110] softirqs last disabled at (3967): [<000000000042cfb4>]
> do_softirq_own_stack+0x34/0x60
> [   13.429172] ---[ end trace 2220ca468f32967d ]---
> [   13.430018] pktcdvd: setup of pktcdvd device failed
> [   13.455589] des_sparc64: Using sparc64 des opcodes optimized DES
> implementation
> [   13.515334] camellia_sparc64: Using sparc64 camellia opcodes
> optimized CAMELLIA implementation
> [   13.522856] pktcdvd: setup of pktcdvd device failed
> [   13.529327] pktcdvd: setup of pktcdvd device failed
> [   13.532932] pktcdvd: setup of pktcdvd device failed
> [   13.536165] pktcdvd: setup of pktcdvd device failed
> [   13.539372] pktcdvd: setup of pktcdvd device failed
> [   13.542834] pktcdvd: setup of pktcdvd device failed
> [   13.546536] pktcdvd: setup of pktcdvd device failed
> [   15.431071] XFS (dm-0): Mounting V5 Filesystem

Someone is running pktsetup to set up a device, at boot time. The device
being passed in doesn't support pass-through commands.

I believe there are two questions here:

1) Why is pktsetup being called? I don't expect anyone to use pktcdvd
   anymore.

2) Given #1, what kind of device is being passed in?

Do  you have some ancient funky init scripts?

-- 
Jens Axboe


  reply	other threads:[~2019-09-20 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 10:27 Anatoly Pugachev
2019-09-20 13:01 ` Jens Axboe [this message]
2019-09-22  8:37   ` Anatoly Pugachev
2019-09-22 16:00     ` Jens Axboe

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=c02d0e0c-e468-003f-6b66-8592a987cbf8@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matorola@gmail.com \
    --cc=sparclinux@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

all inboxes | Powered by JetHome®