Nothing to do ??
I beg to differ!
kernel.org #111901 is a kind of RfC whether CRS usage with old hardware should
be levitated or whether users are---even in future---entitled to boot their <
4.4.0 kernels with pci=nocrs.
And as the forced enabling of CRS was causing the problems that Sergey
Besides, about your "fixed upstream": I think it was entirely accidental.
Something got modified in PCI handling, and abracadabra, it made old hardware
work again.
But as fas as I could read the code fix, it didn't look as if Sergey's and mine
hardware was actually targeted.
We were LUCKY that
** Description changed:
- The system is 15.04.
-
Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I can
boot the system only with 3.19.0-15-generic.
- I always update the system and check new kernel packages, but they have
- the same error.
-
In dmesg I found:
-
A. Eibach, this report has nothing to do with the bugzilla report you
linked, as the bug this report is scoped to is already fixed upstream.
** Changed in: linux
Importance: Unknown => Undecided
** Changed in: linux
Status: Unknown => New
** Changed in: linux
Remote watch: Linux
I tested "pci=nocrs" kernel option on the 3.19.0-50-generic. System can
to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
To manage
Guessed so. Oleg did a marvellous job in figuring that out. That was not
easy-peasy by any means.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't
Sergey:
>"System can to boot."
Are you saying it can boot successfully, or it is not able to boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't
My system can boot successfully with this workaround (kernel option
"pci=nocrs").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
To manage
** Bug watch added: Linux Kernel Bug Tracker #111901
http://bugzilla.kernel.org/show_bug.cgi?id=111901
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=111901
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Oleg, huge thanks for your hard work!!
Ты чудо!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
To manage notifications about this bug go to:
Actually, this leads to a workaround. Adding kernel option "pci=nocrs"
in grub allows to boot currents kernels. I'm not sure whether it leads
to some other problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It was impossible to resist temptation to find where the story began. It
all started between 4.1 and 4.2-rc1. Bisecting points to this commit:
3d9fecf6bfb8b12bc2f9a4c7109895a2a2bb9436 is the first bad commit
commit 3d9fecf6bfb8b12bc2f9a4c7109895a2a2bb9436
Author: Bjorn Helgaas
** 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/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
To manage notifications
And the winner is
4d6b4e69a245e9df4b84dba387596086cb66887d is the first bad commit
commit 4d6b4e69a245e9df4b84dba387596086cb66887d
Author: Jiang Liu
Date: Wed Oct 14 14:29:41 2015 +0800
x86/PCI/ACPI: Use common interface to support PCI host bridge
** Tags removed: needs-reverse-bisect
** Tags added: cherry-pick reverse-bisect-done
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
By the
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
I can't to do "Reverse commit bisecting upstream kernel versions"
$ git bisect good v4.3.5
fatal: Needed a single revision
Bad rev input: v4.3.5
$ git bisect good v4.3-5
fatal: Needed a single
Error message from 4.3.5-generic:
pata_amd :00:09.0: can't enable device: BAR 0 [io size 0x0008] not assigned
pata_acpi :00:09.0: can't enable device: BAR 0 [io size 0x0008] not assigned
** Attachment added: "4.3.5-040305-generic error message"
Hi!
About my system:
3.19.0-25-generic = fail
3.19.0-26-generic = fail
I tested mainline kernels from 4.4.0 to 4.3.4.
4.4.0-040400rc1-generic = ok (from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc1+cod1-wily/ )
4.3.5-040305-generic = fail ( from
4.4-rc1 works just fine, so now I'm bisecting from 4.3 to 4.4-rc1, but it's
also few thousand commits, something about 13 rounds to find.
I'm on 14.04 LTS and bug appeared only in 3.16 and 3.19 kernels, all
installations with 3.13 works OK.
3.16.45 - ok
3.16.46 and higher - error
3.19.25 - ok
Christopher, it's NOT that simple in this case.
I can confirm that 4.3.4 fails and that 4.4.0 works.
But there is definitely nothing in the mainline that might give a chance to
find the "offending" patch, that broke it.
All we _could_ probably do is test 4.4.rc1 ... 4.4rc8.
But that might
Sergey, the next step is to fully reverse commit bisect from kernel 4.3
to 4.4 in order to identify the last bad commit, followed immediately by
the first good one. Once this good commit has been identified, it may be
reviewed for backporting. Could you please do this following
I tried to load Xubuntu 15.10 installation LiveCD from USB Stick. It was
loaded normally. (4.2.0-16-generic)
I tested next kenrels from mainline (i386):
3.19.0-031900-generic = ok
3.19.8-031908-generic = ok
4.2.8-040208-generic = pata_amd, pata_acpi error
4.3.0-040300-generic = pata_amd,
@Sergey, to find the actual bugger we'd have to test somewhere _between_ 4.3.5
and 4.3.9[99].
However, there was nothing like that available for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>4.3.0-040300-generic = pata_amd, pata_acpi error
>4.3.4-040304-generic = pata_amd, pata_acpi error
Confirmed!
> I tried to load Xubuntu 15.10 installation LiveCD from USB Stick. It
was loaded normally. (4.2.0-16-generic)
Aha, _that_ worked?
Well, my 4.2.x was exactly ... let me see ...
Many, many thanks Sergey!!
This problem really fussed me as I thought it's my hardware (as usual).
They must really have fixed a huge bug in 4.4.0.
For the Ubuntu folks here, note that 4.3.4 from Kernel Mainline will
still NOT work. (neither does 4.3.0-7, which made it into main repo only
2 days
apport information
** Tags added: apport-collected vivid
** Description changed:
The system is 15.04.
Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I can
boot the system only with 3.19.0-15-generic.
I always update the system and check new kernel packages, but
** 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/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
To manage notifications
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.4 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
I installed 4.4.0 kernel from wily. My system loaded correctly.
** Tags added: kernel-fixed-upstream
** 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.
29 matches
Mail list logo