*** This bug is a duplicate of bug 1016556 ***
https://bugs.launchpad.net/bugs/1016556
** This bug has been marked a duplicate of bug 1016556
MCE Kernel Panic with 1394 Firewire Enabled on Z7S MB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags removed: 2.6.38 mce panic testing
** Tags added: needs-upstream-testing regression-release
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream performing-bisect
** Description changed:
Repeatable kernel panics after upgrade to 11.04 on kernel 2.6.38-08.
YEAH
Recently I've switched job and to be able to work from home I've had to
negotiate with my miss to use her laptop as dev rig (development is done
101% in ubuntu) so now I've just made my self a fantastic gift as well
because I can compile whole project in under 10 minutes vs. 2h ;
Success Tomasz! Many thanks - now happily running on 12.04.
I have logged it also as a new bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1016556 under the
12.04 / 3.x kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/801840
Title:
MCE Kernel Panic on kernel 2.6.38
To manage notifications about this bug
** 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/801840
Title:
MCE Kernel Panic on kernel 2.6.38
To manage notifications about this
@ ALL
BUAHAHAHAHAHAHAHHAHAHAHAHAHAHAHHA I GOT IT
IT WORKS ! 4 HOURS AND RUNNING UPDATING TO 12.04 IN BACKGROUND
!
Anyway, long story short - been updating my home server - by accident
plugged in this stick to my machine - booted up by accdent -
@Tomasz you are a legend! Hopefully I'll get a chance to try it myself
in a couple of hours.. Was just looking at that big bit of tin
yesterday thinking I might have to install Windoze or bsd on it..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes please Daniel. I think I'm at the limit of my experience But
still keen to solve the problem and learn what I can on the way.
There is at least one crash photo attached already. I've got a couple
more from recent tests which I'll attach if the existing one is
insufficient. Let me know.
@Tomasz thanks for your comments. re each of your points:
1. So we are unlikley to get a bisect between 2.6.35 and 2.6.36 to
compile. prior to doing git bisects I tested mainline kernels and
determined the error to have entered somewhere between 2.6.35-14 and
2.6.36-rc1. So these have been focus
@brendan:
Tip #3 from Tomasz is good, if you can take a picture of the crashed
scren that may give a clue as to where the problem is. If you do, please
attach picture here and we can help diagnose it.
Also, from some stuff I happened to read this week, commits to kernel
mainline are *supposed*
Boys / Girls
1.
To clear out things - AFAIK when version x.y.z of kernel is made a release
version - it's taken at ground for next release x.y.(z+1) -dev or -rc
(whatever). So if version 2.6.35 was stable there had to be some prerelease of
2.6.36 that was stable - and here is catch - when
thanks Daniel. and thanks for your email reply too. Glad to see that you
ended up in the second best country in the world :)
Ive tried your suggestion. Still failing to compile.
I think the git issue was simply from local files I had hanging aroung
after doing things out of order. so git stash
On 12-03-31 08:28 AM, Brendan McLearie wrote:
thanks Daniel. and thanks for your email reply too. Glad to see that you
ended up in the second best country in the world :)
Ive tried your suggestion. Still failing to compile.
I think the git issue was simply from local files I had hanging
Woo hoo. progress being made.
Compile worked fine on the natty install.
Working version on natty:
linux-stable:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
kernel-package: 12.036+nmu1
Broken version on 3.0.0
linux: git clone
Dead end again grrr. Starting to second guess myself that it must be
something stupid I am doing with git.
@Daniel Would be great if you could give it a try.
The first bisect is good.
I cant compile the second.
It gets up to here:
CC [M] drivers/net/wireless/rt2x00/rt2500pci.o
CC [M]
On 12-03-29 09:37 AM, Brendan McLearie wrote:
OK. have been burried in this and staring to get my head around it,
but have now hit a problem (apart from my wife starting to call me a
git!)
I'll try to reassemble my path here in case Ive done something stupid in
the earlier steps.
1.
OK. have been burried in this and staring to get my head around it,
but have now hit a problem (apart from my wife starting to call me a
git!)
I'll try to reassemble my path here in case Ive done something stupid in
the earlier steps.
1. new virtual machine version 11.10 upgraded to 3.0.0-17
Thanks Daniel. Sounds like fun.
I've had a quick read of the wiki. Before I get underway, a few
questions:
1. It sounds like the ubuntu versions are going to be easier to work
with because there already looks to be a fari bit of guiding material.
Is there any problem with using the ubuntu
On 12-03-28 09:16 AM, Brendan McLearie wrote:
Thanks Daniel. Sounds like fun.
I've had a quick read of the wiki. Before I get underway, a few
questions:
It's OK, I'm glad to be able to help with any questions.
1. It sounds like the ubuntu versions are going to be easier to work
with
OK, have been madly testing mainline kernels. My log below.
Questions:
1. Is the order I have sequenced correct?
2. v2.6.35-12,12,13 was confusing. Not sure of history, but the
.13-original-maverick has a date much earlier than the .13-maverick, yet
the later athough in a .13 folder acutally
Awesome! So per your results, the problem was introduced with the 2.6.36
series, in 2.6.36-rc1, which chronologically is the first one that
fails.
Since 2.6.35 works fine (all the 2.6.35.x are maintenance releases for
that series, done *after* work started on the 2.6.36 series) I think the
** Tags removed: needs-upstream-testing
** Tags added: testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801840
Title:
MCE Kernel Panic on kernel 2.6.38
To manage notifications about this bug
OK have tested with mainline kernel 3.3.0-999-generic today.
Looks like the same problem. I didnt see the first panic (but know it
did becuase it restarted).
In the next test I booted into single user mode without any kernel
options and it locked up without even reporting a panic, however it did
OK, we will try to narrow down the mainline kernel release on which this
started occurring, or if it even happens on mainline kernels; if we
can't reproduce the problem with the mainline kernels, then it's
probably something related to an Ubuntu kernel patch.
If possible please test the following
Thanks Daniel and Christopher.
Underway. I expect the first one to take a while since I expect it to be
stable. I'll come back to it in a few hours.
I understand the approach and will continue bisecting. Is there any
value to keeping to the release versions rather than the release
candidates?
Hi,
I'd advise to treat rc kernels as you would any other, since the change
may have been introduced in one of the rc (release candidate) versions.
Also, please note that the rc kernels go *before* any others in that
series; that is, 2.6.37-natty comes after 2.6.37-rc8-natty.
- RC kernels are
Brendan McLearie, thank you for reporting this bug and helping make Ubuntu
better. If you could also please test the latest upstream kernel available that
would be great. It will allow additional upstream developers to examine the
issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
@Daniel Manrique and anyone esle interested.
Bug update:
I've tried booting from USB with 11.10. Idea was to log a new bug
report. However, the system won't run long enough to be able to do much
of anything.
2.6.35-28-server: Stable
2.6.38-8,10,11-server,generic: All Crash.
@ Frank, really sorry to hear that beastie is on the scene :)
I also tried the black list recently and it failed to solve the problem.
However I've had very little time recently to do anything.
I recall from ages ago when trying to blacklist other drivers that for
some reason, sometimes its not
Update: dont bother. I tried and failed too. I've posted my results back
to the Daniel / Jakub thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801840
Title:
MCE Kernel Panic on kernel 2.6.38
Using the old kernel I update now to oneric but the kernel panics still
occur with the 3.00.14 (or was it 3.00.12?) kernel that came with this
update. On top, networking seems to work no longer when you boot in
oneric with an old kernel, it does not detect the connected network
cable any longer.
The Bug still exist as far as I can tell:
- Installed Kubuntu 10.10
- added blacklist ene_ir to /etc/modprobe.d/blacklist.conf
- updated to Kubuntu 11.04
- a few minutes after login again the Kernel Panic occured, so the workaround
seems to be of no effect on my hardware
- booted from
People we may have a solution. Could be the infrared driver. A
workaround has been proposed.
This is an associated bug - its a long post, but look right to the
bottom where Daniel proposes a solution that may work. Others have
reported sucess.
I havent had a chance to try it yet myself but will
In case you were referering to me I am afraid I can't do that atm. I
would have to rely on the hardware that I use on my production machine,
and building a test setup for a newer linux kernel would require to move
huge amounts of data to make space for a linux partition. I will not
test my luck
That's OK--perhaps one of the other 3+ people who is affected by this
bug can perform the testing instead. Any takers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801840
Title:
MCE Kernel Panic
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release
candidate kernel versus the daily build. Once you've tested the
upstream kernel,
Just to confirm beyond any doubt that it's the motherboard, the latest
kernel release used in Oneiric still has this issue, crashing after
about ten minutes (confirmed with a LiveCD). I have now swapped out the
motherboard with my backup, an Asus DSGC-DW, and left it running with
the same liveCD;
I want to note that I too used another Asus Board of different Type for
test reference which is unaffected by this bug. In my case Asus DSEB-DG.
Otherwise I'm tired to come back here in vain hope of a sign that the
kernel developers could ever be bothered to fix what they trashed with
whatever
It later occurred to me that every such error has usually been resolved
through instructions provided by some kind person or other. I'm
guessing something involving a live cd and a chroot will be required.
(This sort of thing usually has my systems down for a few weeks, as it
did take me a while
I can confirm the same errors on a Supermicro board, with the only change
being the extremely regrettable click on the upgrade button.
http://www.supermicro.com/products/motherboard/Xeon1333/5100/X7DCL-i.cfm
Two Xeon 5400's, 4 gb ram, disconnected several bits of hardware that
worked great
I confirm this bug too, Z7S with 24GB Ram.
rant
This Issue broke a Setup that was running stable for more than 8 months and it
is extremly dissapointing to see that it does not seem worthy of any attention
nearly 3 months after the initial report, and something like 4 to 5 months
after this
I have the exact same problem and it seems to occur for me with
2.6.38-11 but not 2.6.38-10 as often. It does not occur with 2.6.35.
I'm attaching a screenshot from my low-end Android, so I apologize for
the quality. Let me know what other info you need and I will provide it.
I can't seem to
In all cases (2.6.38-8 2.6.38-10 2.6.38-11) this is a mce_panic
MCE (machine check exception).
** Summary changed:
- Kernel Panic 2.6.38-xx
+ MCE Kernel Panic on kernel 2.6.38
** Tags added: 2.6.38 mce panic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
44 matches
Mail list logo
