[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/1430164
T
My dmesg for : Linux optiplex 3.16.0-4-686-pae #1 SMP Debian
3.16.7-ckt7-1 (2015-03-01) i686 GNU/Linux
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-4-686-pae (deb
dino99, the next step is to fully commit bisect from kernel 2 to 3.19 in
order to identify the last good kernel commit, followed immediately by
the first bad one. This will allow for a more expedited analysis of the
root cause of your issue. Could you please do this following
https://wiki.ubuntu.co
@#10
never seen that issue when kernel 2 family was used with the current stock
ubuntu
** 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/bu
dino, just to clarify, you personally did not experience this on a 2.x
series kernel (not someone else on some other report)?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Christopher
- this is quite old as it appear around the HAL drop and kernel moving from 2
family to 3, so you confirm you does not read #5
- the system is able to get around that issue, reallocating a new address as
the first checked is faulty
- so known trouble for user, only this mess
So th
@Christopher
- this is quite old as it appear around the HAL drop and kernel moving from 2
family to 3, so you confirm you does not read #5
- the system is able to get around that issue, reallocating a new address as
the first checked is faulty
- so known trouble for user, only this mess
So th
dino99, could you please advise what specific usability impact this
issue has, if any?
As well, did this issue not occur in a release prior to Vivid?
** Tags added: kernel-bug-exists-upstream-4.0-rc3
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kernel: ACPI Warning: SystemIO range 0x04b0-0x04bf conflicts with
OpRegion 0x0480-0x04bf (\_SB_.PCI0.SBRG.GPIO) (20141107/utaddress-258)
kernel: ACPI: If an ACPI driver is available for this device, you should use
Have also tested the latest upstream: get the same issue
but that faulty address is refering to an old known error reported many times
since kernel 3 family:
kernel: pci :00:1f.0: can't claim BAR 13 [io 0x0800-0x087f]: address
conflict with ACPI CPU throttle [io 0x0810-0x0815]
https://bu
** Tags added: latest-bios-3001
** 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/1430164
Title:
pci :00:1f.0: BAR 13: [io 0x0
I have not seen that error logged with 3.19.0.6
Looks like this happened with the many systemd changes the past days, even if i
was already booting with systemd-sysv since a while.
It seems to be a race with the faulty address (maybe 2 processes try to use it
at the same time)
So is it a kernel i
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430164
Title:
pci :00:1f.0: BAR 13: [io 0x0800-0x087f] has bogus alignment
To man
14 matches
Mail list logo
