Thanks for the response Guilherme.
I will work with my team to see if there is anything specific that needs to be
filter out. Will provide you an update soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Hi Guilherme,
There is some confidential data present in sosreport and it is scattered all
over the place. So team is evaluating if .xz file can be sanitize.
Meanwhile, Can you please let me know, specific information that I can
extract from the system to share with you?
--
You received this bu
Hi Guilherme,
Here is the update from my side.
1. sosreport command hung at below message,
Setting up archive ...
Setting up plugins ...
Running plugins. Please wait ...
Finishing plugins [Running: block btrfs]
Hi Guilherme,
Please find attachment containing output of commands,
"dmesg", "lspci -vvv", "lsblk", "ls -l /sys/block", "mount".
Also please note that Ubuntu host is running in a virtualized
environment.
** Attachment added: "cmd_output.txt"
https://bugs.launchpad.net/ubuntu/+source/open-iscs
Hey Guilherme,
Please find below response,
(#a) We are using Cisco Hyperflex iSCSI storage. Following link has more
details about it.
https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/AdminGuide/4-5/b-hxdp-admin-guide-4-5/m-hxdp-iscsi-manage.html
(#b)
Following command failed
root# echo w > /proc/sysrq
bash: /proc/sysrq: No such file or directory
So tried below command and it worked,
root# echo w > /proc/sysrq-trigger
** Attachment added: "Output of dmesg > /root/dmesg.w"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/19
** Attachment added: "Output of dmesg -c > /root/dmesg.out"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1914456/+attachment/5472100/+files/dmesg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "Output of dmesg > /root/dmesg.l"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1914456/+attachment/5472103/+files/dmesg.l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Hi Guilherme,
I am doing good. Thank you.
About the bug, I am still trying to reproduce it. Because of some other issues
I could not get to the number of test cycles after which this bug reproduce.
Now, I am working on two different setups to reproduce this. I suggest to wait
until mid next wee
Hi Guilherme,
We have started doing focused long-run, performance, stress testing on multiple
setups. This is expected to take more than a month time.
So based on the internal discussion, we request to keep this bug open until
July end.
Please let me know if you have any concerns.
Regards
Jit
Hi Guilherme,
I have configured kdump, enabled "/proc/sys/kernel/hung_task_panic" and started
the test.
Observed couple of test failures but those are unrelated.
Will keep monitoring setup and update you as soon as I hit repro.
Jitendra
--
You received this bug notification because you are a mem
Hi Guilherme,
Quick update on this, test is still running and haven't seen kernel panic so
far.
I will keep it running for few more days.
Regards
Jitendra
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Thank you Guilherme for the response and taking time to look at this.
Thought of checking with you,
if there is any further update on reproducing issue at your end? or
need more information from the repro setup that I have?
Regards
Jitendra
--
You received this bug notification because you ar
Hi Guilherme,
Sorry to bother you again.
Just thought of checking with you if you have any update on below,
1. Are you able to repro issue at your end?
2. Were you able to confirm if its a lock issue?
Thanks
Jitendra
--
You received this bug notification because you are a member of Ubuntu
Bugs
Thank you so much for the update, Guilherme.
I can surely try to reproduce issue again to collect kdump, Please share
the configuration setting for kdump.
One question,
Is there anything more that can be captured from the current repro setup? If
not, then I will repurpose the same setup.
Thanks
Just for reference,
Following command is used to delete SCSI device.
echo "1" >> /sys/block//device/delete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914456
Title:
120 sec kernel timeout is seen
Private bug reported:
Ubuntu Release
--
#lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
#cat /proc/version_signature
Ubuntu 4.15.0-122.124-generic 4.15.18
Package version
---
#apt-cache policy open-iscsi
open-iscsi:
Installed: 2.0.874-5ubuntu2.
Thanks Guilherme for the details to setup KDUMP.
I tried these steps on Ubuntu VM (just to ensure I don't mess up with physical
setup) and but landed into some issues.
I am still working on to configure KDUMP and repro the issue.
Will keep you posted as things progress.
Regards
Jitendra
--
You
18 matches
Mail list logo
