Re: [coreboot] [solved] ASUS KFSN4-DRE (K8) Automated Test Failure [master]

[Paul Menzel]

Dear coreboot folks,


Am Donnerstag, den 10.03.2016, 19:30 -0600 schrieb REACTS:
> The ASUS KFSN4-DRE (K8) fails verification for branch master as of
> commit c7a1a3e994135bb405662e2f52d0b22efa899c3d
> 
> The following tests failed:
> BOOT_FAILURE
> 
> Commits since last successful test:
> c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness
> a2176d8 soc/apollolake: Add memory and reserve MMIO resources
> 555d6c2 cbmem: Add utility to get memory region occupied by cbmem

[…]

it seems to have loaded the SeaBIOS payload but then stopped.

```
[…]
Searching bootorder for: /pci@i0cf8/pci-bridge@b/*@0
Searching bootorder for: /pci@i0cf8/pci-bridge@c/*@0

Press ESC for boot menu.

No VBE2 found.
Searching bootorder for: HALT
Space available for UMB: c9800-ef000, f69a0-f70e0
Returned 262144 bytes of ZoneHigh
e820 map has 4 items:
  0:  - 0009fc00 = 1 RAM
  1: 0009fc00 - 000a = 2 RESERVED
  2: 000f - 0010 = 2 RESERVED
  3: 0010 - 0100 = 1 RAM
enter handle_19:
  NULL
Booting from ROM...
Booting from c780:0373
```

It’s probably solved by Change-Id
Ib8e1add3547cda01f71bf1dea14d3e58bdd99730 [1] up for review.


Thanks,

Paul


[1] https://review.coreboot.org/#/c/14033/

signature.asc
Description: This is a digitally signed message part
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] ASUS KFSN4-DRE (K8) Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

The ASUS KFSN4-DRE (K8) fails verification for branch master as of commit 
c7a1a3e994135bb405662e2f52d0b22efa899c3d

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness
a2176d8 soc/apollolake: Add memory and reserve MMIO resources
555d6c2 cbmem: Add utility to get memory region occupied by cbmem

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS 
KFSN4-DRE (K8) test stand
Want to test on your own equipment?  Check out 
https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit 
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering 
 regarding any issues stemming from this 
notification


1457659793-2-automaster.log.bz2
Description: Binary data
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] ASUS KFSN4-DRE Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

The ASUS KFSN4-DRE fails verification for branch master as of commit 
c7a1a3e994135bb405662e2f52d0b22efa899c3d

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness
a2176d8 soc/apollolake: Add memory and reserve MMIO resources
555d6c2 cbmem: Add utility to get memory region occupied by cbmem

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS 
KFSN4-DRE test stand
Want to test on your own equipment?  Check out 
https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit 
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering 
 regarding any issues stemming from this 
notification


1457659912-0-automaster.log.bz2
Description: Binary data
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] ASUS KGPE-D16 Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

The ASUS KGPE-D16 fails verification for branch master as of commit 
c7a1a3e994135bb405662e2f52d0b22efa899c3d

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness
a2176d8 soc/apollolake: Add memory and reserve MMIO resources
555d6c2 cbmem: Add utility to get memory region occupied by cbmem

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS 
KGPE-D16 test stand
Want to test on your own equipment?  Check out 
https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit 
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering 
 regarding any issues stemming from this 
notification


1457659937-3-automaster.log.bz2
Description: Binary data
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] QEMU x86_64 Q35 Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

The QEMU x86_64 Q35 fails verification for branch master as of commit 

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness
a2176d8 soc/apollolake: Add memory and reserve MMIO resources
555d6c2 cbmem: Add utility to get memory region occupied by cbmem
1e70cda soc/intel/apollolake: Avoid UART BAR relocation at ramstage
e953dce soc/intel/apollolake: Add ids of internal SoC PCI devices

<172 commits skipped>

a95baf9 device: Add device path display support
800e964 arch/arm64: Compile arm-trusted-firmware with coreboot timestamp
2be intel/kunimitsu: Set USB Type A current limit to 2A
9f54297 board_status.sh: Be smarter about cbfstool usage
f43e51d board_status: Add script that will set up a ubuntu live image

See attached log for details

This message was automatically generated from Raptor Engineering's QEMU x86_64 
Q35 test stand
Want to test on your own equipment?  Check out 
https://www.raptorengineeringinc.com/content/REACTS/intro.html

Raptor Engineering also offers coreboot consulting services!  Please visit 
https://www.raptorengineeringinc.com for more information

Please contact Timothy Pearson at Raptor Engineering 
 regarding any issues stemming from this 
notification


1457659467-1-automaster.log.bz2
Description: Binary data
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] [GSOC 2016] Coreboot panic room

[Antonello Dettori]

Hello everyone,
I am currently a computing student at the University of Abertay in 
Scotland and I would like to take part in this year GSOC.


The proposal that I want to submit concerns the coreboot panic room idea 
since it looks like something that could really benefit the project as a 
whole and also because it seems like a really interesting technical 
challenge.


I already digged through the blog and the mail exchanges of the previous 
developer working on this, Tadas Slotkus, and took a look at the patches 
that he wrote so I already have a general understanding of their aim.


I would like to concentrate most of my efforts towards improving and 
upstreaming the previous efforts, implementing a way to easily access 
the recovery mode when needed and further the integration between 
coreboot, serialICE and flashrom for this use-case.


Regarding the existing patches I would like to know if they would need 
to stay romc-compatible or should the scope be limited to CAR boards?


Any suggestions on how to tackle this project or GSOC in general?

Thanks in advance.

--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] GSoC proposal

[Haran Sivaram]

Hello CoreBoot,
Loved reading about what you do and hoping I'd get a chance to help with it.

I'd started programming pretty late in highschool, around the time I was
15-16 years old. Once I got into college 2 years later was when I really
started getting into programming.
In college I first got into a robotics automation and building team that
participates in RoboCon in every year. I was primarily working with
interfacing components like sensors, encoders, communication modules to
arduino and avr boards. Majority of my knowledge with hardware and firmware
stems from here.
Later on I moved into android app development and have done multiple
projects ranging from freelance, my own projects and interning with app
based startups.
My contribution to open source code is something I'm quite ashamed of.
Though I feel like I have worked on projects(apps) which would do really
well on the OS platforms, I cannot put the code up as the organisations I
built these apps for are trying to start a business with it. My own
projects comprise of libraries put together to make life a little easier
for users, so not really worth open source mention.
The idea I would like to propose to you isn't something that would fall
completely into your field of work, but a company like this could really
help build the technology needed. As an overview it's a way for an
individual to talk to his/her car, preferably using a smart phone or a dash
board interface, to not only read car info but also to remap the ECU of the
car and to control a variety of the electronic components in the vehicle. I
had worked individually using an arduino board plugged into a 9pin car On
Board Diagnostics (OBD) port. Using a Bluetooth module I relayed
information from my ardunio board to my Android device, but my more
ambitious plans required better technology and more insight into the
operating system of the car.

I hope that gives you brief idea about me and what I want to do, waiting to
hear from you.


-- 

Regards

Haran Sivaram
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot