Also confirming that with Intel BIOS LF94510J.86A, Ubuntu 9.04 (64-bit)
installs and operates correctly.
Note that even with updated BIOS, I am unable to correctly boot or operate the
8.10 OS release.
On the other hand, going WAY back to an old v6 disc I found, works fine
(presumably due to
** Changed in: linux (Ubuntu)
Assignee: Amit Kucheria (amitk) = (unassigned)
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm the issue was solved for me with Intel BIOS Update [LF94510J.86A]
on a Intel® Desktop Board D945GCLF2
Linux * 2.6.27-11-generic #1 SMP Wed Apr 1 20:53:41 UTC 2009 x86_64
GNU/Linux
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
I have been getting the same error for some time - I continue to boot from the
last working version of the amd64 kernel (2.6.24-21). Whenever I do try and
boot from the latest kernel version (currently a 2.6.27-11) I get the
following error at boot:
PANIC: early exception 0e rip
This also affects the new Shuttle X27D Barebone (Dual Core Intel Atom
330). I hope they will update their BIOS :-(
(http://global.shuttle.com/download03.jsp?PI=1209PL=1)
I found no way to boot this machine with X86_64
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
MSI won't FIX (WIND PC bought @ egg). I'd avoid the MSI. I guess I'm
running i386 only
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
For the record, that system is now installed, booting and running
Mythbuntu 8.10 x64 quite happily with the 140 BIOS.
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member of Ubuntu
I'm just building an Atom system for MythTV based on the D945GCLF2
motherboard, and it wouldn't boot Mythbuntu 8.10 x64 with the 099 BIOS,
but I upgraded to the latest 140 BIOS and now it's going through the CD
check prior to installing. So that version appears to be OK.
--
x86_64 kernel oops on
As an additional note, I have the same Intel LF2 Atom 330 board, and the
current BIOS (0137, dated 12/19/2008) causes the same panic. Does
anyone else here see the same behavior?
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You
J. Alexander,
I wonder if they re'broke' it with the 12/19/2008 Bios.
All my testing was done with the Intel D945GCLF2 atom 330 based
motherboard and the bios version 0122 - 11/18/2008 fixed all issues. (
i never flashed the 12/19 update)
Intel's archive versions can be found here:
Well, it looks like the problem might be in the 0137 flash image,
because flashing the specific version listed in this bug allows the
system to boot.
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification
This does not fix it for those of us NOT using the intel board. I have
an MSI wind PC (nettop) and I am still having this issue.
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member
Whoops, I have the atom230. Same issue however.
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
For the intel board it was a purely Bios issue.
Please check if you have an upgrade for your netbook.
Otherwise I think you should write to the MSI support, highlighting this bug
report. MSI may have to update their Bios's board.
Yusef.
--
x86_64 kernel oops on boot (dual-core Atom 330 board
This seems to have been fixed via a BIOS update from Intel. So moving
this bug closed; I am marking it Invalid because it was not a bug in
Linux not because it was not a bug. If you are still seeing issues with
this BIOS update installed please re-open this bug by moving the linux
task 'New'.
Cool, the BIOS upgrade fixed it for me too! I can now fully boot the
64-bit live CD all the way to the desktop. Thanks, everybody!
Now, if I just could just get the integrated Ethernet working... The
32-bit version of 8.10 works fine with the integrated Ethernet. Well,
that's a different
People still experiencing this issue might try the new bios update from
intel ver.0122. It seems to have helped here on a D945GCLF and Fedora
rawhide x86_64.
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug
Thanks Yanko,
The release notes look promising, I'll give it a try over lunch on my
Atom 330, now just to find a winxp harddrive and floppy drive... ;)
http://downloadcenter.intel.com/filter_results.aspx?strTypes=allProductID=2926OSFullName=OS+Independentlang=engstrOSs=38submit=Go
BIOS Version
Thanks Yanko,
Bios LF94510J.86A.0122.2008.1117.0113, seems to do the trick, so far
after 2-3 reboots no issues..
Linux myth-living 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008
x86_64 GNU/Linux
Everyone else, give this a try, and report your results.
Regards,
Robert
--
x86_64 kernel
Robert, All,
Yes, with this BIOS upgrade I was able to boot the ubuntu generic kernel on the
atom 230 (single core) as well.
Great work.
Regards
Andre
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification
Fantastic.
With the new BIOS, 8.10 Alternate Desktop 64-bit CD now installs, reboots and
md5 checks its CD perfectly.
This on an Intel D945GCLF motherboard/CPU
Many thanks to whoever here or at Intel has worked on this. This is
going to make a very cute little file server.
--
x86_64 kernel
Over 10 reboots I have a 100% success rate.
My BIOS is 2008.0427.2223
I followed Robert's exact steps, using 2.6.27-7-generic (not server) kernel
config
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification
Robert, Dan,
I confirm that reverting 67d9b90 according to your instructions gives a
bootable system also on a single core atom board:
[EMAIL PROTECTED]:~$ cat /proc/cpuinfo | grep model
model : 28
model name : Intel(R) Atom(TM) CPU 230 @ 1.60GHz
model : 28
and it took 5 hours 50 minutes ;-)
Andre
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for the update Andre and taking the time to recompile the kernel.
- Amit/Luka Can you bump the heading to include the Atom 230 (x86_64)...
It's been awhile, (playing with mainline 2.6.28-rc's for gem/kms/etc..),
but Linus's original 2.6.27 release did not show this problem. (I never
Robert,
in my atom box the patched kernel still doesn't work...
I have to admit that I have used no conventional method:
I have compiled the kernel with a live 8.10 x86_64 kubuntu on a Core2Duo (and
it compiles in less than 5 hours ;)
I have booted the atom box with a netboot debian live
Yusef, strange...
Well the only pre-final amd64 i could find was alpha-3. PS, I saw no
difference when building it on an athlon x2 vs an atom 330, so don't
waste the time building on a slower platform and transfer the *.deb
over.
http://old-releases.ubuntu.com/releases/intrepid/
Regards,
I have done my test with an Ubuntu Hardy server (8.04.1) x86_64.
The new kernel doesn't work... :(
I get the same kernel panic...
It is behaving in a very strange way, because the third time I've tried to
boot, it worked!!
After that, only kernel panics.
Very very strange...
I need to buy a
Hi Yusef,
That boot pattern is similar to what i saw in alpha-5/6.. (50/50 chance
it would work)
The kernel in my case was around 250-300MB's, so I won't ask for you to
post it. Can you post your .config used? I'll rebuild it. For reference
i've attached the one pulled from 2.6.27-7,
Robert,
thanks for your help!
Yes, it is a random pattern... sometimes it boots, sometimes it don't...
Also in my case the kernel is around 250Mb, as you suggest I have attached my
.config
I'm rebuilding with your config file. With a simple diff, I'm not able
to see if there are differences
and the git log (~100 lines...)
Thanks again.
Yusef
** Attachment added: git.log
http://launchpadlibrarian.net/19709787/git.log
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a
But the config file you have attached, is the one installed with a clean
Intrepid x86_64 server edition?
I was started from that one.
Thanks,
Yusef
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification
Thanks Yusef!
Not a complete expert on kernel options, but there's one thing in the
config file that might have hit the bug:
--- config-2.6.27.4-custom 2008-11-16 21:33:14.0 -0600
+++ config-2.6.27-7-generic 2008-11-16 20:14:44.0 -0600
(lots of lines)
CONFIG_TRACING=y
Hi Yusef,
That's right you are using the server edition (with server kernel), the
one i posted was for the standard intrepid desktop kernel (amd64 7.16).
That might require a full git bisect from a working kernel. Do standard
and server editions share the same git tree?
Regards,
Robert
--
I'm a newbie to linux development so I'd have to learn quite a bit to
follow the above instruction. I'm guessing that 'git' means something
like 'get latest version of code from source repository' and 'make'
invokes the compiler and linker but I don't know what the (no's)
refers to. There's some
See also my comments screenshots attached to Bug #54020
As with Yusef Dan I'm using the single core D945GCLF board/processor.
In brief, 8.04.1 3264 bit are fine, 8.10 64 bit panics immediately after
boot-up menu for installation or CD check.
One further piece of information... I still get the
Hi Jon, Dan Yusef,
Thru git bisecting on the atom 330 i found commit
67d9b90a1c844bf1c6daaffd2c60561fc8c445f7 to be the issue with x86_64.
Can you confirm this on the single core Atom? (you may have to install
with alpha-5/6 x86_64 to get an initial bootable kernel...)
git clone
git checkout Ubuntu-2.6.27-8.17
git revert 67d9b90 - opps, don't forget this..
cp /boot/config-2.6.27-7-generic .config
--
x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
https://bugs.launchpad.net/bugs/279186
You received this bug notification because you are a member of
I'm not a kernel expert but I'm having the same issue with the little
sister of your board, the D945GCLF with the Intel Atom 230 (single
core, HT capable).
I've tried to install the intrepid x86_64 server edition and:
- with the iso, I get an early kernel panic with an hard lock.
- with the
I want to corroborate Yusef Maali's comment; I have the D945GCLF single
core atom 230 motherboard and the latest distro (downloaded last night)
gives a kernel panic when trying to run intrepid x86_64 from the live CD
and even when trying to verify the live CD from the Live boot menu. For
some
I have just installed Kubuntu 8.10 release, but this time i386 packages -
everything works without problems.
It seems that this issue is clearly related to 64-bit version of kernel only
(x86_64).
** Summary changed:
- kernel oops on boot (dual-core Atom 330 board D945GCLF2)
+ x86_64 kernel
Retested with 2.6.27-8.17, Reverting 67d9b90a1 still fixes the issue...
2.6.27-8.17 (x86_64)
commit c39815a9d77967dd058175b89457db5ca81d80cf
Author: Robert Nelson [EMAIL PROTECTED](none)
Date: Sun Nov 9 07:39:56 2008 -0600
Revert disable CONFIG_DYNAMIC_FTRACE due to possible memory
42 matches
Mail list logo
