Per matthias' last comment, I'm marking this Fix Released against Gutsy.
And just as an additional note, Feisty Fawn 7.04 has reached it's end of
life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . Thanks.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: linux-source-2.6.20
Hi All,
finally I had the time to open my box, put the additional memory-sticks
back in and have a look...
It seems that, at least for me, Gutsy Gibbon fixes the problem. I
haven't done any thorough testing yet, but it looks like my machine
doesn't freeze anymore.
So, for me, this issue is close
Hi All,
This bug was opened a while ago but there hasn't been any recent
activity. The Hardy Heron Alpha series is currently under development
and contains an updated version of the kernel. It would be helpful if
you could test the latest Hardy Alpha release:
http://www.ubuntu.com/testing . You
This bug may have several duplicates : #107325, #123223, #123243 and
#134996. They all report the same problem about Eeek!
page_mapcount(page) went negative! and usually with value (-1).
The only difference I see is that the 2.6.20 kernel says it's located in
rmap.c line 588 and 2.6.22 says it'
Email me if you need any more information.
** Attachment added: "lcpci -vvnn"
http://launchpadlibrarian.net/9628206/lspci-vvnn.log
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: "After boot."
http://launchpadlibrarian.net/9628199/newboot.log
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
I'm experiencing similar freezes, including the logs for your
convenience.
Code: 0f 0b eb fe 8b 77 18 48 83 c4 08 5b 5d 83 f6 01 83 e6 01 e9 is
similar in all crashes.
Linux mediabox 2.6.20-16-generic #2 SMP Thu Aug 30 23:16:15 UTC 2007
x86_64 GNU/Linux
** Attachment added: "After OOPS"
htt
Thank you.
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
Here my lspci-vvnn.log
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/9196608/lspci-vvnn.log
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
Here my dmesg.log
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/9196602/dmesg.log
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
I've also these freezes on a ubuntu-server running
qmail/tcpserver/amavisd/clamav/spamassassin
Normally I didn't get detailed infos in kernel.log, but today I got many
log-lines - see the attachement.
Maybe these infos help to fix this issue.
# uname -a
Linux 2.6.20-16-server #2 SMP Fri Aug
Thank you, I'm marking this as triaged and assigning to the kernel team.
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team
Status: Incomplete => Triaged
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug n
** Attachment added: "Dmesg of a fresh boot"
http://launchpadlibrarian.net/9016580/dmesg.txt
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
does not yet have enough information.
Please run the command "dmesg > dmesg.log" after a fresh boot and attach
the resulting file "dmesg.log" to this bug repo
I completely forgot to mention: While I was testing the memory with
memtest86+ I figured out, that I could only get the system to fail if
all 4 slots are populated with 1gb sticks. Whenever I ran the system
with just 2 sticks of ram the system was fine (that's why I got my
motherboard replaced in t
** Attachment added: "lspci -vvnn output"
http://launchpadlibrarian.net/9004826/lspci.txt
--
Memory related kernel Oops
https://bugs.launchpad.net/bugs/134996
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
16 matches
Mail list logo
