Tomas Pospisek, as this report is closed, if you want your issue
addressed you would want to file a new report as previously requested of
you in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1115753/comments/33
.
--
You received this bug notification because you are a member of Kernel
I wrote:
> `umount -f` seems have fixed it. No problems until this point.
Nope, that didn't work either. Now I have instead doubled the lvsnapshot
'exception' space.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
`umount -f` seems have fixed it. No problems until this point.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1115753
Title:
Umount of Multiple LVM Snapshots Causes 'soft lockup CPU#0
So I'm reporting my current further findings here in case somebody else
than me stumbles upon this bug report in search of help.
I'll not create a new bug report as of now, since I'm still researching
the problem and I think there's no point in opening a new bug report if
it'll turn out to be
Craig, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1115753/comments/32
regarding you are no longer using the same hardware. For future
reference you can manage the status of your own bugs by clicking on the
current status in the
Tomas Pospisek, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
I switched from a Radeon graphics card to nVidia, and have not had a
problem since.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1115753
Title:
Umount of Multiple LVM Snapshots Causes
I am seeing the same problem as reported here. My system and kernel are:
Ubuntu Trusty 14.04
linux 3.13.0-66-generic
Also, since implementing the "sleep 120" workaround mentioned in [1]
(thanks a lot for that markusj!), my box is able to do backups cleanly.
I'm also seeing this kind of
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
markusj, would you mind filing a new report so your hardware may be reviewed
via a terminal:
ubuntu-bug linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1115753
Title:
Umount of
I can't say this with certainty, but seems to happen more often when
backup destination is tape, and less often when backup destination is
disk. Actually, I always backup to disk first, then copy disk backup to
tape. But if the tape drive is offline, it skips the last step (copy to
tape), and it
To add some more observations:
After running umount in the context of an at job, the issue nearly
disappeared completely. Before this change, i already suspected power saving
mechanisms to increase the probability of a freeze. Last week i had a freeze
again, as the lid of my laptop has been
Unfortunately, I don't have the resources available to build and
configure a clone of my existing system using one of the saucy iso
images.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Error messages from kernel module generator (fglrx and nvidia) -- and
other error messages -- during kernel install, and unable to boot, even
in safe mode.
** Tags added: kernel-unable-to-test-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is
Craig, could you please confirm this issue exists with the latest
development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
please make a comment to this.
--
You received this bug notification because you are a member of
Craig:
Just to confirm, I should install Index of
/~kernel-ppa/mainline/v3.12-rc2-saucy:
linux-headers-3.12.0-031200rc2-generic_3.12.0-031200rc2.201309231935_amd64.deb
linux-image-3.12.0-031200rc2-generic_3.12.0-031200rc2.201309231935_amd64.deb
The lockup happened again last night. kernel: [38460.336022] BUG: soft
lockup - CPU#3 stuck for 22s! [umount:24238]. This time there was more
information in the syslog than there has been in the past, including a
couple call traces and stack traces. The relevant portion of the syslog
is
Never installed an upstream kernel before. Just to confirm, I should
install:
Index of /~kernel-ppa/mainline/v3.12-rc2-saucy:
linux-headers-3.12.0-031200rc2-generic_3.12.0-031200rc2.201309231935_amd64.deb
linux-image-3.12.0-031200rc2-generic_3.12.0-031200rc2.201309231935_amd64.deb
So far, backups have run twice without incident after BIOS update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1115753
Title:
Umount of Multiple LVM Snapshots Causes 'soft lockup
Reproduced the bug. Again, just to repeat so as to avoid any confusion:
I have not updated the BIOS yet. I will do that next.
The lockup is a little different now. Whereas previously the system
would hang before any of the snapshots were removed, now some of the
snapshots are successfully
$ uname -a
Linux brain 3.2.0-53-generic #81-Ubuntu SMP Thu Aug 22 21:01:03 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1115753
Title:
Umount
Craig:
The lockup is a little different now. Whereas previously the system would
hang before any of the snapshots were removed, now some of the snapshots are
successfully umount'd and lvremove'd before the hang. This could be the
result of changes made to the script that does the umount and
Craig:
So the bug is occuring for me in the context I've shown above.
Strange. However, you guessed right, my script gets called by a RunAfter
directive.
Since the bug did not appear the last three times, the reason might be
different. Maybe its the two minute delay after the job has been
Markus:
Looking back at an earlier version of my script that I was using when I first
reported this bug, I used to do exactly what you describe: umount'ing all the
partitions before doing any lvremove on any partition. Now I umount and
lvremove each partition before proceeding to the next
I have just now updated the BIOS.
$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
1703
10/17/2012
** Tags removed: bios-outdated-1703
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks, Chris, for your attention to this matter. Sorry for my delay.
I did NOT update my BIOS as you suggested. Before doing so, I wanted to
see if the bug was still present. I've been trying to reproduce the bug
-- which was intermittent to begin with -- and have been unable to.
There have
Finally there is a bug report for my issue, yay!
This bug hits me on precise with any of the current LTS kernels, i am
struggling with it for more than a year, maybe even two. Sometimes all
just works fine, sometimes the system locks up. I wasn't able to see the
error message since i never had
27 matches
Mail list logo
