[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/880130
Ti
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notif
I updated to 12.04 last Saturday. My computer has been power cycled at
least 3 times a day since then without a boot failure. It looks like
there is a chance this bug is finally fixed.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because yo
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notification
DAP, as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880130/comments/22
both a test of Precise and the mainline kernel was requested. Your
comments indicate neither occurred.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Usually when one marks a bug "incomplete", a comment on what is missing
is included. Care to fill us in on what you are looking for? Perhaps
then we might be able to do something about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notif
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notification
This is still an issue. Just this morning my computer dumped me into
busybox when booting. I have been updating my computer with the latest
updated daily since I have reported this bug with no change in behavior
(hence no updates)
In my view, there are a bunch of race conditions in the current ups
DAP, thank you for reporting this bug and helping make Ubuntu better.
This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest development release of Ubuntu? ISO CD images are
available from http://
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notifications about this bug go to:
http
Just thought I'd chime in here... I have 11.10 Oneiric (installed fresh,
not an upgrade from 11.04) and have encountered exactly the same
symptoms as Douglas.
Currently on 3.0.0-15-server kernel
Also have a Linux Software RAID
I think I found a workaround, which is the noauto option for the RAID
OK, that screen shot looks the same as your previous captures from when
it booted OK.
The busybox prompt you get there happens when the boot process in the
initramfs didn't apparently complete correctly - and it's giving you a
chance to fix it; so there isn't much point in a timeout when it's got
I have attached the results of the requested 'cat's in the form of a
screen photo (pasted to gather from three photos since the results would
not fit on the screen).
** Attachment added: "Requested screen output from hang state."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880130/+at
I'm not entirely sure what an "initramfs" prompt is.
When I have been able to see the prompt, it has been a busybox prompt.
There have been a handful of hangs where it is a blank screen with a
mouse cursor in the center.
In either case, typing "exit" and hitting the return key has always
continue
Hmm ok, I was wrong on that - that mdadm.conf doesn't specify the
devices, so it found the devices from the UUID anyway.
I think this might need someone with more udev foo to look at; if you get to
the (initramfs) prompt again please
get a copy of /proc/partitions and /proc/mdstat at that point t
$ cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices wit
(I say this having hit that problem a few years back - see bug 67299 and
bug 6)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
Right I think I see the problem:
md127 : active raid1 sdd1[1] sdc1[0]
1953510841 blocks super 1.2 [2/2] [UU]
You can't rely on sdc and sdd being fixed device names these days (for
the last few years) - sometimes they'll initialise in the opposite
order; what does your /etc/mdadm/mdadm.conf
$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
md127 : active raid1 sdd1[1] sdc1[0]
1953510841 blocks super 1.2 [2/2] [UU]
unused devices:
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vend
Hi Douglas,
Right, I've looked at your images - and I see you're landing at the initramfs
prompt. Can you include (from a successful boot) a cat of /proc/mdstat and cat
/proc/scsi/scsi /proc/partitions and /etc/fstab?
Also if you land at that initramfs prompt you might try capturing the
conte
Thank you for the shift-pageup clue, that worked. I will now attempt to
upload the 14 pages of screen captures I did for the last hang. I don't
see anything that looks like an error message among the status messages,
but then I don't know what I'm looking for.
I ziped them up. The number in the fi
I'm not sure on the way to set the text mode on the newer grub; but if
it's not completely died then you should be able to scroll back with
shift-page up.
If it hangs again grab a screenshot with a camera or phone.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bu
I have had two more hangs. The messages are not consistent. In these
most recent hangs, there was no mention of a degraded raid. In fact I
did not see anything at all go by that looked like an error message
before it dumped me into busybox.
Is there a way I can get a larger console when booting? I
Hi DAP,
I'm not aware of a list like that; however the mainline kernels normally boot
ok, and you should
be able to switch back to the ubuntu one easily enough from the GRUB menu if
the mainline one
isn't happy.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bu
So far, I've only seen one hang with these new grub settings, I'd like
to see a couple more before I make any more changes to make sure they
are all the same.
The KernelMainlineBuilds wiki mentions that these kernals do not have
patches done by Ubuntu. Is there a page that lists the differences? I
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test
the latest release candidate kernel (Not a kernel in the daily
directory). Once you'
I edited the /etc/default/grub, turned off the splash and quiet flags,
and also turned off graphical console.
I got a hang today. It had dumped me into busybox.
There was something about a raid being degraded, but it was not clear
what it was talking about since it scrolled off too fast to read,
If you use shift right as it starts to boot, it should get you the grub
menu, then you can edit the boot line and you should see splash and
quiet on the end of the boot line, delete those and then let it continue
booting.
I think you could make the same thing permenantly by editing /etc/default/gr
Where would I find the splash/quiet flags to change them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notifications ab
Hi,
If I had this problem I think I'd boot every time without the splash/quiet
flags and then when it hung see if it always stops at the same point and see if
there is any text to tell you where it is upto.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880130
Title:
Computer locks up just after grub about 10% of boots
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/880130
Title:
Computer locks up just after grub about 10% of boots
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
33 matches
Mail list logo
