[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964810
Ti
Well I will try your instructions. But when I said that the upstream
kernel failed to boot, I just had the system freeze at the blank purple
screen after making grub selection. This is even with disabling the
splash stuff in /etc/grub/default.
There is one new problem though. I have returned the p
Also, can you try to capture the additional debug info using the latest
precise kernel(3.2.0-22.35)? You can upgrade following the instructions
in comment #44
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
@Eshwar,
Ok, I understand, sorry for the confusion.
Can you follow the "Boot options" instructions on the following wiki to
enable additional output on boot:
https://wiki.ubuntu.com/DebuggingKernelBoot
As mentioned on the wiki, it would be great if you can attach a log file
which may have captu
@jsalisbury but the upstream kernel did not boot even with the drive
out. So we are not sure the bug exists upstream do we? if it booted
normally and then didn't because the drive was plugged in then I can see
why.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you are
Well I tried testing as instructed. The upstream kernel did not boot for
some reason even with the offending drive removed. So I updated the tags
also like you asked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Were you able to test the mainline kernel mentioned in #37? It would
help since you have a reproducable test case now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964810
Title:
boot delay or fa
Same story since I am testing with 3.2.0-21
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-request-3.2.0-20.32
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
Ok so I narrowed down to a case that I could repeat - Booting while
connected to a drive that the system can't access while booted. In this
case a corrupt hard drive. In dmesg this kind of device gives me the
errors:
[ 212.201991] ata5: exception Emask 0x10 SAct 0x0 SErr 0x40d action 0xe
fro
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.3 kernel[1] (Not a kernel in the daily directory). Once you've
tested the upstream kernel, please remove the 'needs-upstream-testing'
tag(Only that on
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
Suggested newer development kernel i.e. 3.2.0-20.32 is older than the
current kernel I am running. This means that the problem exists in the
latest kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: kernel-request-3.2.0-20.32
** Description changed:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964810
Title:
boot delay or failure when external drives are connected
To manage notif
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
It ran ok I think. Last line was "No package found matching linux" yet
the logs seem to all be here. wish they were collated together into 1
post but ok!
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
apport information
** Tags added: apport-collected staging
** Description changed:
Its a strange problem that I have seen come and go.
So the problem: Whenever a USB drive or eSATA drive is connected to the
computer, the boot process takes extra long and sometimes fails (I mean
fail a
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964810
Title:
boot delay or failure when external drives are connected
To manage notification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964810
Title:
boot delay or failure when external drives are connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
21 matches
Mail list logo
