Having binary chopped through http://kernel.ubuntu.com/~kernel-
ppa/mainline/, it seems that the problem was introduced between
3.1.0-0301rc2 (working) and 3.1.0-0301rc3 (broken as in the original
report).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Filed an upstream kernel bug for this issue.
** Bug watch added: Linux Kernel Bug Tracker #43244
http://bugzilla.kernel.org/show_bug.cgi?id=43244
** Changed in: linux
Importance: Undecided = Unknown
** Changed in: linux
Status: New = Unknown
** Changed in: linux
Remote watch:
** Changed in: linux
Status: Unknown = Confirmed
** Changed in: linux
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981936
Title:
Firewire prevents booting
To
Found a work-around :
Disable the firewire module from loading during boot.
edit:
/etc/modprobe.d/blacklist-firewire.conf
uncommented the line:
blacklist firewire-ohci
Run:
sudo update-initramfs -k all -u
Im now able to boot the release kernel 3.2.0-24 without any problem only
** Tags removed: found-workaround
** Tags added: needs-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981936
Title:
Firewire prevents booting
To manage notifications about this bug go to:
Sten Bennetsen, the issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel . If you have done so,
please tell us the number of
** Description changed:
When trying to boot using kernel 3.2.x kernel the screen just goes blank and
harddisk IO stops.
Removing the quiet and splash options in combination with nomodeset seems to
reveal
that the booting stops due to an error in setting the firewire's power levels
(see
Didt a manual bisect instead.
I've found the problem all the way back to the Ubuntu-3.1.0-1.1 tag.
I where not able to build the 3 earlier tags due to compliation errors.
Hope this helps so you can find and fix this error that seems to be
related to firewire and power settings.
--
You received
I've tried following the guide but I always end up loosing the ubuntu specific
folders for doing a build when bisecting.
Heres what I've done:
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git
sudo apt-get build-dep linux-image-$(uname -r) -- this would then be
the 3.0.0-17 stuff
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981936
Title:
Firewire prevents booting
To manage notifications about this bug go
** 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/981936
Title:
Firewire prevents booting
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981936
Title:
Firewire prevents booting
To manage notifications about this bug go
apport information
** Tags added: apport-collected
** Description changed:
When trying to boot using kernel 3.2.x kernel the screen just goes blank and
harddisk IO stops.
Removing the quiet and splash options in combination with nomodeset seems to
reveal
that the booting stops due to an
I cannot reinstall the system using the iso images as I have data I do not want
to delete on this machine.
I did intall the linux-image-3.4.0-999-generic_3.4.0-999.201204150427_i386.deb
+ headers and the booting problem persists.
- It stops at the same place as the previously attached jpeg
Sten Bennetsen, thank you for apporting in Precise and testing mainline.
The next step is to perform a kernel bisect to identify which commit
introduced this problem. Could you please do so following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
--
You received this bug notification because
** Attachment added: picture of boot output
https://bugs.launchpad.net/bugs/981936/+attachment/3068075/+files/firewire_bug.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981936
Title:
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
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981936
Title:
Firewire prevents booting
To manage notifications about this bug go
The problem persists of halting boot on firewire initialization.
It appears from the package description that the kernel is 64 bit
(Linux kernel image for version 3.2.0 on 64 bit x86 SMP )
But my machine is a Intel Duo T2300 (32-bit) which should then be a
Linux kernel image for version 3.2.0
** Tags removed: kernel-request-3.2.0-23.36
** Tags added: bot-stop-nagging needs-bisect needs-upstream-testing
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/981936
Title:
Sten Bennetsen, thank you for reporting this and helping make Ubuntu
better. Please be sure to confirm this issue exists with the latest
development release of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please
run the following command
21 matches
Mail list logo
