Hello Roland,[...]
On Sun, Jun 29, 2025 at 11:46:00AM +0200, Roland Sommer wrote:
[correcting CC recipients]
Huh, how did I manage that (rhetorical question)? Thanks
Ahh, now that makes sense. pktsetup calls `/sbin/modprobe pktcdvd` explicitly, the blacklist entry doesn't help for that. Without the
kernel module renamed, does the 2nd DVD-RAM result in the blocking behaviour?
Yes.
OK, that makes sense. So udev does in this order:
- auto-load the module (which is suppressed with the backlist entry)
- call blkid (which blocks if the module is loaded)
- call pktsetup (which loads the module even in presence of the
blacklist entry).
Control: reassign -1 src:linux
On Sun, Jun 08, 2025 at 08:59:22AM +0200, Roland Sommer wrote:
blkid works all the time as expected but hangs forever after inserting any DVD-
RAM in the drive. dmesg then reports every approx. 120s (up to 10 times):
[ 363.635218] INFO: task blkid:2224 blocked for more than 120 seconds.
[ 363.635232] Tainted: P OE 6.1.0-37-amd64 #1 Debian 6.1.140-1
[ 363.635235] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 363.635238] task:blkid state:D stack:0 pid:2224 ppid:2216 flags:0x00004002
[ 363.635245] Call Trace:
[ 363.635247] <TASK>
[ 363.635252] __schedule+0x34d/0x9e0
[ 363.635266] schedule+0x5a/0xd0
[ 363.635271] schedule_preempt_disabled+0x11/0x20
[ 363.635276] __mutex_lock.constprop.0+0x399/0x700
[ 363.635283] pkt_ioctl+0x42/0x120 [pktcdvd]
[ 363.635294] pkt_ioctl+0xce/0x120 [pktcdvd]
[ 363.635302] ? do_syscall_64+0x61/0xb0
[ 363.635308] ? do_filp_open+0xaf/0x160
[ 363.635313] blkdev_ioctl+0x133/0x270
Looks like pktcdvd isn't returning to userspace. Reassigning to the
kernel, as blkid won't be able to do anything about that. Might also
be a hardware issue if it works elsewhere?
My conslusion is that pktcdvd is eqaully broken for CD-RWs.
Not surprising. Maybe we should take another stab at killing it
from the kernel.
On 7/2/25 5:08 PM, Ben Hutchings wrote:
On Sun, 2025-06-29 at 12:26 +0200, Uwe Kleine-König wrote:
On Sun, Jun 29, 2025 at 11:46:00AM +0200, Roland Sommer wrote:[...]
Huh, how did I manage that (rhetorical question)? Thanks
Ahh, now that makes sense. pktsetup calls `/sbin/modprobe pktcdvd`
explicitly, the blacklist entry doesn't help for that. Without the
kernel module renamed, does the 2nd DVD-RAM result in the blocking
behaviour?
Yes.
OK, that makes sense. So udev does in this order:
- auto-load the module (which is suppressed with the backlist entry)
- call blkid (which blocks if the module is loaded)
- call pktsetup (which loads the module even in presence of the
blacklist entry).
I tested with a CD-RW, and the behaviour was slightly different:
- Nothing automtically created a pktcdvd device, so blkid initially
worked with a CD-RW inserted and the pktcdvd modules loaded.
- After running pktsetup to create the block device /dev/pktcdvd/0,
blkid and any other program attempting to open that device hung.
My conslusion is that pktcdvd is eqaully broken for CD-RWs.
Not surprising. Maybe we should take another stab at killing it
from the kernel.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 42:53:53 |
Calls: | 10,392 |
Files: | 14,064 |
Messages: | 6,417,215 |