search for: uninteruptable

...s.org/view.php?id=4220 dd if=/dev/zero of=/dev/my_usb_stick_device_name bs=4096 count=10000 can not be stopped with ctrl-c and is not responding to signals (count=10000 can be modified to give you enough time to test) The bug has been closed with the following comment: "As said: dd is in an uninteruptable state when you do that. This is not a bug" This is wrong, because IMHO dd should receive the signal after it finishes the current read()/write() and returns to user space, but this is not happening. How can I reopen the bug? Thanks Adrian Buciuman

Adam Tauno Williams wrote: > On Mon, 2017-08-07 at 15:26 +0000, KM wrote: >> All,This happens on all of our CentOS 7 VMs.? but as stated in the >> email trail, the file softlockup_thresh does not exist.? Should it be >> added?? What is the best way to get rid of this behavior. >> Thanks in advance and sorry if I missed something along the way.KM > > Yes, I see this

...see this behavior as well. Never have found a solution - other >> than increasing the threshold and pretending it doesn't happen. >> > We see it a fair bit, and this is on server running on bare metal, not VMs. > On bare metal is usually means some hardware has gone into an uninteruptable IRQ and the CPU is waiting for it to go away. I saw this with systems with Green disk drives a while ago. Something going to talk to the drive would just sit for long times while the drive spun up, the cache was validated etc. Other things would be drives on USB disks too when some other USB item s...

After several days of uninterupted operation (about 4 or 5 days I believe), ices-0.4 starts to return this error countless times: "Could not open cuefile [/tmp/ices.cue] for writing, cuefile not updated" This error eventually causes the stream to misreport the name of the currently playing song. Instead of reporting the current song, it reports the song found in the now defunct cue

I apologize with what may be some very basics questions. I''m trying to go through sections 9 and 15 of the LARTC FAQ, but my head can''t quite grasp what''s going on. I''ll keep going through them to see if something clicks, but meanwhile I was hoping someone might point me in the direction that I should focus my efforts. The server at our church is running

Hello. I would like to know if promise RAID cards are compatible with CentOS / RHEL ? I have seen that only SATA is supported on the RHEL hardware compatibility list. The other ATA raid cards seems not to be compatible. They give source code and promise grants compatibility with RedHat 8 and 9 but not RHEL. I would like to know if somebody tried a ATA raid card like Fasttrack TX2000, SX4000,