coreboot March 2007

coreboot@coreboot.org

118 participants
226 discussions

[LinuxBIOS] AMD K8 kernel oopses
by Stefan Reinauer 26 Mar '07

26 Mar '07

I am having trouble getting Opteron CPUs up in an SMP system. The below is from 2.6.18.8 All CPUs except cpu0 seem to oops doring startup. Any ideas? CPU0: AMD Opteron(tm) Processor 844 stepping 08 Booting processor 1/17 eip 2000 Initializing CPU#1 ------------[ cut here ]------------ Kernel BUG at [verbose debug info unavailable] invalid opcode: 0000 [#1] SMP last sysfs file: CPU: 1 EIP: 0060:[<c010ae82>] Not tainted VLI EFLAGS: 00010046 (2.6.18.8-0.1-coresystems #9) eax: 00000000 ebx: 00000001 ecx: 00000000 edx: fffede92 esi: 00040010 edi: 00000000 ebp: 00000000 esp: c9103f94 ds: 007b es: 007b ss: 0068 Process swapper (pid: 0, ti=c9102000 task=c9118d20 task.ti=c9102000) Stack: 00000001 00000000 c010a443 00000000 00000000 00000000 01000800 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Call Trace: [<c010a443>] <0>Code: 9d 5b 5e c3 a1 38 ca 23 c0 eb e0 56 53 8b 35 30 d0 ff ff a1 20 d0 ff ff c1 e8 18 83 e0 0f 0f a3 05 a0 80 23 c0 19 c0 85 c0 75 02 <0f> 0b 89 e0 25 00 e0 ff ff c7 05 e0 d0 ff ff ff ff ff ff 8b 15 EIP: [<c010ae82>] SS:ESP 0068:c9103f94 <0>Kernel panic - not syncing: Attempted to kill the idle task! Stuck ?? Inquiring remote APIC #17... ... APIC #17 ID: 11000000 ... APIC #17 VERSION: 00040010 ... APIC #17 SPIV: 000000ff CPU #17 not responding - cannot use it. Booting processor 1/18 eip 2000 Initializing CPU#1 ------------[ cut here ]------------ Kernel BUG at [verbose debug info unavailable] invalid opcode: 0000 [#2] SMP last sysfs file: CPU: 1 EIP: 0060:[<c010ae82>] Not tainted VLI EFLAGS: 00010046 (2.6.18.8-0.1-coresystems #9) eax: 00000000 ebx: 00000001 ecx: 00000000 edx: fffee37a esi: 00040010 edi: 00000000 ebp: 00000000 esp: c9143f94 ds: 007b es: 007b ss: 0068 Process swapper (pid: 0, ti=c9142000 task=c91199b0 task.ti=c9142000) Stack: 00000001 00000000 c010a443 00000000 00000000 00000000 02000800 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Call Trace: [<c010a443>] <0>Code: 9d 5b 5e c3 a1 38 ca 23 c0 eb e0 56 53 8b 35 30 d0 ff ff a1 20 d0 ff ff c1 e8 18 83 e0 0f 0f a3 05 a0 80 23 c0 19 c0 85 c0 75 02 <0f> 0b 89 e0 25 00 e0 ff ff c7 05 e0 d0 ff ff ff ff ff ff 8b 15 EIP: [<c010ae82>] SS:ESP 0068:c9143f94 <0>Kernel panic - not syncing: Attempted to kill the idle task! Stuck ?? Inquiring remote APIC #18... ... APIC #18 ID: 12000000 ... APIC #18 VERSION: 00040010 ... APIC #18 SPIV: 000000ff CPU #18 not responding - cannot use it. Booting processor 1/19 eip 2000 Initializing CPU#1 ------------[ cut here ]------------ Kernel BUG at [verbose debug info unavailable] invalid opcode: 0000 [#3] SMP last sysfs file: CPU: 1 EIP: 0060:[<c010ae82>] Not tainted VLI EFLAGS: 00010046 (2.6.18.8-0.1-coresystems #9) eax: 00000000 ebx: 00000001 ecx: 00000000 edx: fffee862 esi: 00040010 edi: 00000000 ebp: 00000000 esp: c9145f94 ds: 007b es: 007b ss: 0068 Process swapper (pid: 0, ti=c9144000 task=c911a640 task.ti=c9144000) Stack: 00000001 00000000 c010a443 00000000 00000000 00000000 03000800 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Call Trace: [<c010a443>] <0>Code: 9d 5b 5e c3 a1 38 ca 23 c0 eb e0 56 53 8b 35 30 d0 ff ff a1 20 d0 ff ff c1 e8 18 83 e0 0f 0f a3 05 a0 80 23 c0 19 c0 85 c0 75 02 <0f> 0b 89 e0 25 00 e0 ff ff c7 05 e0 d0 ff ff ff ff ff ff 8b 15 EIP: [<c010ae82>] SS:ESP 0068:c9145f94 <0>Kernel panic - not syncing: Attempted to kill the idle task! Stuck ?? Inquiring remote APIC #19... ... APIC #19 ID: 13000000 ... APIC #19 VERSION: 00040010 ... APIC #19 SPIV: 000000ff CPU #19 not responding - cannot use it. Total of 1 processors activated (3612.12 BogoMIPS). -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/

2 2

[LinuxBIOS] RFC - Support for Compaq Deskpro 2000 Motherboard
by Graeme Brett Houston 25 Mar '07

25 Mar '07

CPU: Pentium Pro:Socket 8: KB80521EX200 SL22T 256K Northbridge: SB82441FX/SB82442FX Southbridge: SB82371SB BIOS CHIP? CSI CAT28FO10N-15 096077F other chip(SuperIO?) NS9706FP PC87306-1BR/VUL 225410-002 Is this supported or can this be supported from LinuxBIOS Thanks

2 1

[LinuxBIOS] Support for VIA K8T890/VT8237
by Rudolf Marek 25 Mar '07

25 Mar '07

Hello, Anyone is working on VIA K8T890/VT8237? + K8. I have in plan to start in near future. I'm missing the datasheet for the K8T890. Do you think I will need it? Maybe just writing the PCI registers to match the BIOS values would be enough? My board is Asus A8V-E SE. My BIOS ROM is 512KB. (PMC 49... perhaps it should work with flashrom). If someone wants to help with that it would be cool. Some hint is bellow ;) Please keep me CCed. Rudolf jtrg -B - "uggc://jjj.ivn.pbz.gj/ra/erfbheprf/qbjaybnq-pragre/puvcfrgf/" | terc rgf/puv | njx -S\" '{cevag $4}' | juvyr ernq yvar; qb jtrg uggc://jjj.ivn.pbz.gj/$yvar; qbar

4 4

[LinuxBIOS] Problem on Compilation
by ccases＠navista.fr 24 Mar '07

24 Mar '07

I have change my parameter in LinuxBiosV2/targets/advantech/pcm-5823/Config.lb target pcm-5823 mainboard advantech/pcm-5823 option DEFAULT_CONSOLE_LOGLEVEL=8 option MAXIMUM_CONSOLE_LOGLEVEL=8 option CONFIG_COMPRESSED_PAYLOAD_NRV2B=1 option ROM_SIZE=(256*1024)-(64*1024)-(32*1024) #option FALLBACK_SIZE = ROM_SIZE romimage "normal" option USE_FALLBACK_IMAGE=0 option LINUXBIOS_EXTRA_VERSION=".0Normal" option ROM_IMAGE_SIZE=64*1024 payload ../../../../etherboot-5.2.6/src/bin/rtl8139.elf end romimage "fallback" option USE_FALLBACK_IMAGE=1 option LINUXBIOS_EXTRA_VERSION=".0Fallback" option ROM_IMAGE_SIZE=64*1024 payload ../../../../etherboot-5.2.6/src/bin/rtl8139.elf end buildrom ./linuxbios.rom ROM_SIZE "fallback" "normal" Adn I have the same error : LOVER_IMAGE='0' -Os -nostdinc -nostdlib -fno-builtin -Wall -o rom_stream.o /home/ccases/LinuxBIOSv2/src/stream/rom_stream.c /home/ccases/LinuxBIOSv2/src/stream/rom_stream.c:47:90: invalid suffix "x" on integer constant /home/ccases/LinuxBIOSv2/src/stream/rom_stream.c: In function `stream_init': /home/ccases/LinuxBIOSv2/src/stream/rom_stream.c:83: warning: comparison between pointer and integer /home/ccases/LinuxBIOSv2/src/stream/rom_stream.c:83: warning: comparison between pointer and integer /home/ccases/LinuxBIOSv2/src/stream/rom_stream.c:84: warning: assignment makes pointer from integer without a cast make[1]: *** [rom_stream.o] Error 1 make[1]: Leaving directory `/home/ccases/LinuxBIOSv2/targets/advantech/pcm-5823/pcm-5823/normal' make: *** [normal/linuxbios.rom] Error 1 I don't now why :( If anyone has a solution, thank's by advance for your help regards CCASES

5 7

[LinuxBIOS] memtest as a payload, 115200 baud
by Adam Talbot 24 Mar '07

24 Mar '07

I have compiled memtest with serial support, but when I boot it from grub, it only runs at 9600 baud. Am I missing a compile option? What am I missing, what do I need? -Adam Grub.conf default 0 timeout 5 serial --unit=0 --speed=115200 terminal --timeout=10 serial console title=Gentoo Linux 2.6.19 root (hd0,0) kernel /kernel-genkernel-x86-2.6.19-gentoo-r5 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 console=tty0 console=ttyS0,115200 initrd /initramfs-genkernel-x86-2.6.19-gentoo-r5 title=memtest86 root (hd0,0) kernel /memtest.bin console=tty0 console=ttyS0,115200

2 1

[LinuxBIOS] #76: LinuxBIOS messages should be accessible in dmesg
by LinuxBIOS 24 Mar '07

24 Mar '07

#76: LinuxBIOS messages should be accessible in dmesg ---------------------------------+------------------------------------------ Reporter: stepan | Owner: rminnich Type: defect | Status: new Priority: major | Milestone: Setting up LinuxBIOS v3 Component: code | Version: v3 Keywords: | Dependencies: Patchstatus: there is no patch | ---------------------------------+------------------------------------------ The LinuxBIOS messages should be written to a log buffer so they can be read from Linux' dmesg command. -- Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/76> LinuxBIOS <http://www.linuxbios.org/>

1 0

Re: [LinuxBIOS] Fallback checking normal
by Stefan Reinauer 23 Mar '07

23 Mar '07

* Thomas Ekstrand (AL/EAB) <thomas.ekstrand(a)ericsson.com> [070323 17:02]: > I'm wondering wether the fallback ever checks the normal image to see if it is > ok before jumping to it? LinuxBIOSv3 will do this. > If not, why? The mechanism works in a real life check. A flag is set before the image is jumped to, and that flag is cleared by the OS loader (or by the OS, if you wish). Whenever the system is booted with the flag set, it uses the fallback image instead of the normal image. So this check does not only check for a correct checksum, but whether the normal image was actually able to boot the OS. This makes this feature not only usable for flash failures but also for developer failures. ;-) > How is LinuxBIOS support for: > SMBIOS > SMI LinuxBIOS does "support" having those (ie. it does not prevent them) but does not implement any system management functionality, as it is not needed (and even discouraged) to have them. What do you need them for? > Vmware Some people on this list have been working on vmware support. See the web archive. Stefan -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/

1 0

[LinuxBIOS] Fallback checking normal
by Thomas Ekstrand (AL/EAB) 23 Mar '07

23 Mar '07

I'm wondering wether the fallback ever checks the normal image to see if it is ok before jumping to it? If not, why? How is LinuxBIOS support for: SMBIOS SMI Vmware Does it exist? /Thomas

1 0

[LinuxBIOS] Question about UEFI payload for LinuxBIOS
by xiongyi 23 Mar '07

23 Mar '07

I am a potential student applicant for the Google SoC 2007 program. And I am strongly interested in the LinuxBIOS project, especially for the "GNUFI or TianoCore payloads" idea. I have some background of EFI-related development, such as knowledge about (U)EFI spec. and EFI driver/application development in the Tiano platform, etc. But I know little about hardware or chips. The "GNUEFI or TianoCore payloads" idea is to get an UEFI implementation as the LinuxBIOS payload. Essentially, LinuxBIOS need to provide the interfaces for the GNUFI or TianoCore core foundation for this purpose, I think. I wonder whether this project idea, namely "GNUEFI or Tiano payloads", needs the LinuxBIOS hardware platform for development environment and some chips knowledge. Or some emulation development environments are enough.

2 1

[LinuxBIOS] Linutop runs LinuxBIOS
by Uwe Hermann 23 Mar '07

23 Mar '07

Hi, I just stumbled over a nice use case of LinuxBIOS: Linutop http://www.linutop.com It's a small diskless box with a Geode LX700 processor, 256 MB RAM, Linux stored on an external USB stick, audio, ethernet, VGA, 4x USB, and: it comes with LinuxBIOS pre-installed :-) http://www.linutop.com/wiki/index.php/Developers#Upgrading_to_LinuxBIOS http://www.linutop.com/wiki/index.php/Photos http://en.wikipedia.org/wiki/Linutop Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org

4 3

← Newer
1
...
4
5
6
7
8
9
10
...
23
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot March 2007