[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_hurd]] # IRC, freenode, #hurd, 2013-12-05 Creating device nodes: fd fdX std vcs hdX hdXsY hdXs1Y sdX sdXsY sdXs1Y cdX netdde ethX loopX ttyX ptyp ptyq/sbin/MAKEDEV: 75: /sbin/MAKEDEV: cannot create /dev/null: Interrupted system call that's new teythoon: ouch braunr: everything works fine though teythoon: that part isn't too surprising y? teythoon: /dev/null already existed, didn't it ? braunr: sure, yes ## IRC, freenode, #hurd, 2013-12-19 hm i'm seeing those /sbin/MAKEDEV: cannot create /dev/null: Interrupted system call messages too ## IRC, freenode, #hurd, 2013-12-20 braunr: interesting, I've seen some of those as well ## IRC, freenode, #hurd, 2014-01-26 cannot create /dev/null: Interrupted system call http://gnashdev.org:8010/builders/z-sid-hurd-i386/builds/26/steps/system_upgrade/logs/stdio ## IRC, freenode, #hurd, 2014-01-27 gg0: I had same /dev/null error after upgrading my old image (more than 6 months old) a week ago. But I got such message only on boot and it didn't autostart hurd console. Tried to upgrade current qemu image (from topic) to reproduce it but it works OK after upgrade i can reproduce it with # apt-get install --reinstall python2.7 dbus # for instance http://paste.debian.net/plain/78566/ gg0: i've seen those as well, but i cannot reliably reproduce it to track it down i believe it's benign though in shell scripts if -e is set, it aborts on failures like those uh, it does? :/ so if this happens in prerm/postinst scripts, package is not properly installed/removed/configured and it fails redirecting stdout and strerr to /dev/null shouldn't be so problematic, anything wrong in my setup? can you reproduce it? not reliably gg0: but i do not believe that anything is wrong with your machine any way to debug it? having a minimal test case that triggers this reliably would be great but i fear it might be a race ## IRC, freenode, #hurd, 2014-01-28 have you seen the /dev/null issue ? yes what do you make of it ? no idea i believe it is related to the inlining work i've done just like the bogus deallocation at boot, it needs debugging :) hm i don't think so no ? i think we saw it even before your started working on the hurd ;p i've never seen it before my recent patches maybe i made it worse not worse, just exposed more right ## IRC, freenode, #hurd, 2014-01-29 cannot reproduce "cannot create /dev/null: Interrupted system call" on a faster VM might depend on that? ## IRC, OFTC, #debian-hurd, 2014-02-02 but now saw a strange message at the end of the boot: /etc/init.dhurd-console: 55: /etc/init.d/hurd-console: cannot create /dev/null: Interrupted system call oh well known on a slow VM (even old qemu/kvm btw), i can't reproduce it on a faster/more recent one slow VM = gnash buildbot slave http://gnashdev.org:8010/builders/z-sid-hurd-i386/builds/26/steps/system_upgrade/logs/stdio especially bad on system upgrade because it doesn't finish to run prerm/postinst scripts :/ ## IRC, freenode, #hurd, 2014-02-05 Creating device nodes: fd fdX std vcs hdX hdXsY/sbin/MAKEDEV: 75: /sbin/MAKEDEV: cannot create /dev/null: Interrupted system call hdXs1Y sdX sdXsY sdXs1Y cdX netdde ethX loopX ttyX ptyp ptyq lprX comX random urandom kbd mouse shm. ## IRC, freenode, #hurd, 2014-02-11 typical dist-upgrade http://paste.debian.net/plain/81346/ many fewer cannot create /dev/null: Interrupted system call on a faster machine gg0: wow, so many interrupted system call messages i don't get as many, but makedev produces a few every time i run it as well ## IRC, OFTC, #debian-hurd, 2014-02-16 anyone here got any idea why upgrading initscripts fail on the hurd gnash autobuilder, as reported on ? pere: cannot create /dev/null: Interrupted system call gg0: I noticed the message, but fail to understand how this could happen. 13:16 < gg0> oh well known on a slow VM (even old qemu/kvm btw), i can't reproduce it on a faster/more recent one 13:17 < gg0> slow VM = gnash buildbot slave http://gnashdev.org:8010/builders/z-sid-hurd-i386/builds/26/steps/system_upgrade/logs/stdio 13:18 < gg0> especially bad on system upgrade because it doesn't finish to run prerm/postinst scripts :/ i remember teythoon talking about something racy gg0: the /dev/null issue is known for a long time gg0: some of the recent work (i believe mine) has made the problem more apparent gg0: that's what braunr told me i see. it would be really nice fixing it. really annoying. i workaround it by moving null away and moving it back under /dev before halting/rebooting ## IRC, freenode, #hurd, 2014-02-17 Earlier today, I upgraded my Debian GNU/Hurd installation from several months ago, and I'm now seeing bogus things as follows; is that a known issue? checking for i686-unknown-gnu0.5-ar... ar configure: updating cache ./config.cache configure: creating ./config.status +./config.status: 299: ./config.status: cannot create /dev/null: Interrupted system call config.status: creating Makefile (The plus is from a build log diff.) 13:36 < gg0> pere: cannot create /dev/null: Interrupted system call 20:10 < teythoon> gg0: the /dev/null issue is known for a long time Anyone working on resolving this? I't causing build issues: checking for i686-unknown-gnu0.5-ranlib... (cached) ranlib checking command to parse nm output from gcc-4.8 object... [...]/opcodes/configure: 6760: ./configure.lineno: cannot create /dev/null: Interrupted system call failed checking for dlfcn.h... yes Anyway, will go researching IRC logs. tschwinge: (that one was from #debian-hurd) I assume teythoon and/or braunr can comment once he's back they're* tschwinge: we've been seing this more often lately but noone has attempted to fix it yet tschwinge: if you have a reliable way to reproduce that /dev/null: Interrupted system call error, please let us know ## IRC, freenode, #hurd, 2014-02-23 braunr: cool. i'd vote /dev/null one as next one in your todo still frequent on this slow vm http://gnashdev.org:8010/builders/z-sid-hurd-i386/builds/30/steps/system_upgrade/logs/stdio especially during setup-translators -k yes