On 4/10/20 3:29 PM, Stephen Berman wrote:
I've built current development LFS using jhalfs and when I invoke (via
sudo or logged in as root) `shutdown -h now', the system appears to hang
while trying to detach the cdrom block device. Here are the last two
lines printed to the terminal after issuing that command:
Bringing down the loopback interface..........[OK]
sr 5:0:0:0: tag#21 timing out command, waited 120s
and every 2 minutes, the last line repeats with a different tag#. So
far I haven't had the patience to wait more than six minutes, then I
power off the machine with the start button. I know this is the cdrom
because on booting there are these messages:
[ 6.633004] scsi 5:0:0:0: CD-ROM HL-DT-ST DVDRAM GH24NSD1 LW00
PQ: 0 ANSI: 5
[ 6.679083] sr 5:0:0:0: [sr0] scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 6.679101] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 6.689325] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 6.689399] sr 5:0:0:0: Attached scsi generic sg1 type 5
In addition, the message "timing out command, waited %lus\n" comes from
the function scsi_softirq_done in linux-5.5.9/drivers/scsi/scsi_lib.c.
This only happens with `shutdown -h' or `shutdown -hP', not with
`shutdown -r'. Moreover, on the same computer I also have LFS 8.4 with
kernel 4.20.12, and there `shutdown -h' works fine. So it seems to be
an issue with kernel 5.5.9. When I built the latter I used `make
oldconfig' with the config file of kernel 4.20.12, accepting the
defaults for all new options. Comparing the two config files, I didn't
notice any evidently relevant difference, e.g. involving SCSI options.
I suppose it's also possible there is some other difference between LFS
8.4 and the current development version that could be involved, but I
have no idea what to look for. Does anyone here have any ideas or
suggestions for how to track down what's causing the hang and stop it?
Since it is bringing down the loopback interface it is running the
bootscript S90localnet properly. The only other script is S99halt and
that only does 'halt -d -f -i -p'.
-d Don't write the wtmp record.
-f Force halt or reboot, don't call shutdown(8).
-i Shut down all network interfaces just before halt or reboot.
-p When halting the system, switch off the power.
Try using 'poweroff' or 'init 0' and see if anything changes. You can
also try using an older kernel with the current build to validate that
it is a kernel problem.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
