[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.
Christopher:
Assuming I'm on a 64-bit laptop, is this the correct page to grab the
Lucid kernel from?
https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/5297703
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi, from this link http://www.pbehnke.com/main/node/11, I have managed
to make a shutdown anyway --
For some reason, if the usb controls are set to 'auto', the shutdown-
reboot loop starts. The solution was to make them forcefully turn 'on'.
I have added a function in the /etc/init.d/halt script
** Description changed:
- I first removed the ~/.Xauthority file it worked fine for the next two-
- three shutdowns, then it started again. Then I added acpi=noirq switch
- in the kernel parameter and seemed to be fixed for couple of weeks, then
- it started again. Moreover, after acpi=noirq, the
Hi, is there any way I can test lucid kernel wihout installing? I have
only one machine and there are many personal settings I need to keep.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ramgorur, sure. If testing the live environment of Lucid wouldn't work
out, you could install a Lucid kernel in your current install via
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
and then remove it immediately after.
--
You received this bug notification
hi, tested with http://cdimage.ubuntu.com/daily-live/current/, the
shutdown-reboot loop still persists. Moreover, after the shutdown-reboot
loop, keyboard does not work on the login screen, I need to do a suspend
and a wakeup then the keyboard responds.
--
You received this bug notification
ramgorur, thank you for performing the requested test. Did this problem
not occur in a release prior to Saucy?
** Tags added: trusty
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
You received this bug notification because you are a member of
This bug existed as of 13.04 for sure. 12.10, not sure, but I can't
install that on my laptop as it's a production laptop with work on it.
What else can we do to move towards a solution for this bug??
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi, I reverted back to 12.04, according to
http://www.ubuntu.com/certification/hardware/201305-13524/, it is
mentioned that this version is certified for ThinkPad S431. But still
that shutdown-reboot loop exists. What is the problem ?
--
You received this bug notification because you are a
ramgorur, thank you for testing 12.04.03. For regression testing
purposes, could you please test Lucid via http://old-
releases.ubuntu.com/releases/lucid/ and advise to the results?
** Tags added: raring
--
You received this bug notification because you are a member of Kernel
Packages, which is
hi penalvch and jsalisbury, rc3 kernel did not solve the problem, the
shutdown and reboot loop has started again. My machine was working
normally for the next couple of shutdowns but it started again from the
last night. So, I am modifying the tag as 'kernel-bug-exists-upstream'
(according to
penalvch and jsalisbury, http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc3-trusty/ solved the problem of shutdown-reboot
loop.
However, I had tp-smapi-dkms installed on my system, during the
installation of rc3 it was throwing an error message regarding DKMS (I
do not exactly remember the
penalvch, I have also found this message in dmesg --
microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x19
platform microcode: Direct firmware load failed with error -2
platform microcode: Falling back to user helper
microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x19
platform microcode: Direct
ramgorur, thank you for testing the mainline kernel. 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, could you please just make a
comment to this?
**
** Description changed:
I first removed the ~/.Xauthority file it worked fine for the next two-
three shutdowns, then it started again. Then I added acpi=noirq switch
in the kernel parameter and seemed to be fixed for couple of weeks, then
it started again. Moreover, after acpi=noirq, the
** Description changed:
I first removed the ~/.Xauthority file it worked fine for the next two-
three shutdowns, then it started again. Then I added acpi=noirq switch
in the kernel parameter and seemed to be fixed for couple of weeks, then
it started again. Moreover, after acpi=noirq, the
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
ramgorur, you would want to test http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.13-rc3-trusty/ as rc4 doesn't have all the necessary
files in it.
** Tags added: latest-bios-1.07 needs-upstream-testing regression-
potential
** Summary changed:
- lenovo thinkpad S431 - boots up after shutdown
19 matches
Mail list logo
