dino99, Ubuntu does not provide BIOS fixes. Fixes for BIOS problems, as
confirmed in your test, come from the vendor of your motherboard.
linux (Ubuntu) - Won't Fix
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member
I know what to do, be sure; its not a reason to mark it as invalid.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740857
Title:
MTR
dino99, thank you for at least trying to test the newer BIOS. However,
as your prior test results indicate a BIOS issue, this would have to be
fixed by the BIOS vendor. Your welcome to attempt to work around the
problems by following https://wiki.ubuntu.com/Kernel/Reference/fwts . As
well, feel fre
Well for a bad joke, that was one : this crappy bios update have failed
(i know now why it still is a beta) and its a nightmare to recover then
update again. Next time i surely not follow such advice and waste so
much time.
--
You received this bug notification because you are a member of 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/740857
Title:
MTRR failures revealed by fwts
To manage notifications about this bu
** 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/740857
Title:
MTRR failures revealed by fwts
To manage notifications about this bu
Ok will do, thanks for your time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740857
Title:
MTRR failures revealed by fwts
To manage notifications about this bug go to:
https://bugs.launchpad.net
dino99, please disregard my comment: "The website makes no mention of
the BIOS being a beta." Could you please try it anyways and if it does
not help, revert back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
dino99, regarding your comments:
"As its still a beta and is not related to "resume from S3" , i will stay with
3001."
The website makes no mention of the BIOS being a beta. Hence, we would
still need you to update the BIOS and report back the results.
** Changed in: linux (Ubuntu)
Status
hi Christopher,
upstream kernels already used:
0.00] Linux version 3.2.0-21-generic-pae (buildd@aluminium) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu3) ) #35~pre201203310400-Ubuntu SMP Sat Mar
31 09:52:38 UTC 2012 (Ubuntu 3.2.0-21.35~pre201203310400-generic-pae 3.2.13)
Uname: Linux 3.3
dino99, as per
http://www.asus.com/Motherboards/Intel_Socket_775/P5W_DH_Deluxe/#download
your BIOS is outdated. If you update your BIOS, does the situation
improve? As well, we still need you to test the mainline kernel after
the BIOS update noted in
https://bugs.launchpad.net/ubuntu/+source/linux/
** Attachment added: "fwts_20120401"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740857/+attachment/2980700/+files/results20120401.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740857
** Attachment added: "dmesg20120401"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740857/+attachment/2980589/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740857
Title:
MTRR
oem@oem-desktop:~$ uname -a
Linux oem-desktop 3.2.0-21-generic-pae #35~pre201203310400-Ubuntu SMP Sat Mar
31 09:52:38 UTC 2012 i686 i686 i386 GNU/Linux
I dont attached again lspci -vvnn as it has been reported the first time and
there is no hardware change.
As the issue is with the readahead pro
** Tags removed: natty
** Tags added: nattybot-stop-nagging
** Tags removed: nattybot-stop-nagging
** Tags added: bot-stop-nagging natty
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
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 s
Sadly apport is also broken actually:
oem@oem-desktop:~$ apport-collect -p linux 740857
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 718, in
add_hooks_info
symb['add_info'](s
dino99, thank you for reporting this 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? If so, could
you please capture the oops following
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugP
** 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/740857
Title:
MTRR failures revealed by fwts
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Attachment added: "results.log"
https://bugs.launchpad.net/bugs/740857/+attachment/1932740/+files/results.log
** Description changed:
on natty i386 updated
got troubles to boot easily (often have kernel panic on first try and
- need a cold boot again which often work) so i'v' run FWT
20 matches
Mail list logo
