Both reboot & shutdown hang at the line "Disabling CD-RW packet-writing on /dev/hdc" the problem started with 2.6.14-rc1 and is the same in rc2. Also, if I do a cdrw stop from the command line I get the following hang: root@p4pe ~ # /etc/init.d/cdrw stop * Disabling CD-RW packet writing on /dev/hdc ... # rc-status -a cdrw [ stopping ] There is no problem with 2.6.13.1 and below. Reproducible: Always Steps to Reproduce: 1.Reboot or shutdown a system with the packet-writing cdrw script in place 2. 3. Actual Results: Hang at * Disabling CD-RW packet writing on /dev/hdc ... Expected Results: * Disabling CD-RW packet writing on /dev/hdc ... OK followed by the remaining shutdown steps. root@p4pe ~ # emerge info Portage 2.0.52-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.14-rc2 i686) ================================================================= System uname: 2.6.14-rc2 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.12.0_pre8 ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.1 sys-apps/sandbox: 1.2.13 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/mnt/hdb9/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo.chem.wisc.edu/gentoo http://mirror.gentoo.no/" MAKEOPTS="-j2" PKGDIR="/mnt/hdb9/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/mnt/hdb9/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.no/gentoo-portage/" USE="x86 X a52 aac aalib alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl directfb dts dvd dvdr eds emboss encode esd fam ffmpeg flac foomaticdb gd gdbm gif gphoto2 gpm gstreamer gtk2 imagemagick imlib ipv6 java javascript jpeg kde ldap libg++ libwww live lm_sensors mad mikmod mjpeg mmx motif mozilla mp3 mpeg nas ncurses network nls nptl ogg oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline real rtc sdl slang spell sse sse2 ssl svga tcltk tcpd theora tiff truetype truetype-fonts type1-fonts usb vorbis xine xml xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
The cdrw script from http://gentoo-wiki.com/HOWTO_Packet_Writing_on_CD-RW that gives the above symptoms is from 2.1.2005 7:50 - I have since discovered that the current one on the wiki page has stop/start problems with 2.6.13.1 too..
Works for me on 2.6.14-rc2 using the pktcdvd init script found in the udftools package. Any chance you can try that?
Thanks for the udftools init script tip Daniel.. under 2.6.13.1 it works ok, but for a lack of screen messages both during boot/reboot, or when manually /init.d/start/stopping, which works ok but simply returns to the prompt. however, with 2.6.14-rc2 it hangs like the cdrw script, ie reboot/shutdown hangs after 'stopping hddtemp ok', while manual /init.d/start/stopping actually does stop/start pktcdvd according to rc-status -a, but the console doesnt return to the prompt. reboot always hangs even if pktcdvd appears to have been manually stopped. I notice that CONFIG_ACPI_PCI=y no longer exists in 2.6.14* and wondered if that might have something to do with the problem..
I found a workaround for this problem via http://bugs.gentoo.org/show_bug.cgi?id=77726 where a pktcdvd init at http://bugs.gentoo.org/attachment.cgi?id=52573 works ok with my setup after copying conf.d/cdrw to conf.d/pktcdvd.. someone needs to have a look at the differences between the udftools and cdrw inits and the above attachment.
The udftools one automatically enables packet writing on all RW drives, whereas the one you describe allows you to select only certain drives. Is this causing a difference in configuration?
I currently have a Samsung DVD-ROM and an ND-3540A burner installed, so I was happy to get init.d/cdrw working back in January.. the the udftools init works ok from a packet-writing point of view, but it fails to cleanly 'stop' and therefore causes the reboot/shutdown hang. The http://bugs.gentoo.org/attachment.cgi?id=52573 init works perfectly.. I can boot up, check its ok, replace it with the udftools init, do an init.d/stop, and sure enough this hangs leaving an unkillable pktsetup process.
Yes, but my point is the udftools one enables packet writing on *all* drives that you have, whereas the one you link to only does it on a user-defined selection. Is the fact that you are choosing a selection (possibly just a subset of drives available) resulting in the end configuration being different?
The only configuration difference when booting the udftools init is I can stick packet-written media in the drive and mount it immediately, whereas with the other init I have to do a # pktsetup hdc (or pktcdvd0) /mnt/dvdwr for 'hdc' and 'pktcdvd0' to appear in /dev/pktcdvd - then I can mount & use media.
In that case you aren't really using the init script at all, and if you take it out of a runlevel and don't start it, you can continue to use packet writing in the current way (e.g. doing pktsetup manually), right?
Thats right, but it would be nice to use the udftools init, particularly when I add my second burner. Hopefully a solution to the hang will be found..
Good news! Just installed 2.6.14-rc3 and the udftools pktcdvd init now works perfectly.
Ok, thanks for letting us know.
