Christopher, this is no longer giving me a problem as bug 806032 has
been fixed. However I have checked with Trusty (kernel 3.12.0-7 32 bit)
and the problem described here does still exist. The bug is therefore
not invalid, but from my point of view it does not need fixing. I don't
know what
Colin Law, thank you for your comments. As outlined in
https://wiki.ubuntu.com/Bugs/Status Won't Fix would be more appropriate,
for example, if you desired the outcome noted in the Bug Description,
and the maintainers didn't want to implement it on technical grounds.
Given you are no longer
Colin Law, given bug 806032 is resolved for you, would you need anyone
to look into this, or may this be closed as Status Invalid?
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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[0]? That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.
If you are comfortable with
Joseph, having looked at the link for reporting upstream, the first
thing I have to do is to identifier the maintainer from [1] and email a
report to him. However I have no idea how to find the right maintainer
for this problem from the massive list. Can you help?
[1]
Joseph, you have asked me to try the latest 3.5 kernel, but the link is
to 3.6 rc1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037094
Title:
writing `/dev/mem': Bad address Error writing to
Joseph, you have asked me to try the latest 3.5 kernel, but the link is to 3.6
rc1, but I have assumed that it is the 3.6 that is required.
Tested against 3.6.0-030600rc1-generic_3.6.0-030600rc1.201208022056_i386,
problem still seen.
** Tags removed: needs-upstream-testing
** Tags added:
When I tested it, it also applies for reading.
sudo dd if=/dev/mem bs=1 count=1 skip=$ADDR
This was a 32-bit Ubuntu 12.04 Live CD on a 64-bit desktop machine. ADDR
is any address higher than or equal to 0xf7bfe000 (see below).
Using strace and writing a minimalistic C program, I could
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037094
Title:
writing `/dev/mem': Bad address Error writing to ACPI area with 32
bit kernel
To manage notifications about this bug go to:
** 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/1037094
Title:
writing `/dev/mem': Bad address Error writing to ACPI area with 32
bit
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.5kernel[0] (Not a kernel in the daily directory) and install both the
linux-image and linux-image-extra .deb packages.
Once you've tested the
11 matches
Mail list logo
