summaryrefslogtreecommitdiff
path: root/flowtop.8
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2015-08-19 17:49:46 +0200
committerTobias Klauser <tklauser@distanz.ch>2015-08-19 17:49:46 +0200
commit71c28eff00a8a8896c45fa20330b623d265ae5c7 (patch)
treed13462434b03898fc522c203ada463110e8c1cf3 /flowtop.8
parent1898c5396e8e2d36386716cac2d5971ce4a4d8b0 (diff)
build: Only use tput if $TERM is defined
Otherwise we clutter the build log with warnings such as: tput: No value for $TERM and no -T specified on head-less CI/build systems (e.g. Debian's buildd). Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'flowtop.8')
0 files changed, 0 insertions, 0 deletions
> Set blkfront to XenbusStateInitialised front changed() > Connect() > Set blkback to XenbusStateConnected blkback_changed() > Skip talk_to_blkback() because frontstate == XenbusStateInitialised > blkfront_connect() > Set blkfront to XenbusStateConnected ----- And here we get another XenbusStateConnected notification leading to: ----- blkback_changed() > because now frontstate != XenbusStateInitialised talk_to_blkback() is also called again > blkfront state changed from XenbusStateConnected to XenbusStateInitialised (Which is not correct!) front_changed(): > Do nothing because blkback already in XenbusStateConnected Now blkback is in XenbusStateConnected but blkfront is still in XenbusStateInitialised - leading to no disks. Poking of the XenbusStateConnected state is allowed (to deal with block disk change) and has to be dealt with. The most likely cause of this bug are custom udev scripts hooking up the disks and then validating the size. Signed-off-by: Bob Liu <bob.liu@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'Documentation/debugging-via-ohci1394.txt')