date:20141008

Re: [coreboot] Suggested readings

2014-10-08 Thread prasnik


Hello Greg,
I think I got it.

When you say that Intel "retires some part number", you probably mean 
that
Intel has stopped to talk about some architectures (or cpu families) in 
its official documentation.
And "working entry" should mean that those cpu-families are still valid, 
at least conceptually, today.
Furthermore, today's "part numbers"/architectures/cpu-families on Intel 
manuals are them of the QUARK family.


Finally, as for the book you suggested (Computer organization: 
hardware/software by Gorsline),
the point is simply the fact that it talks about those "part 
numbers"/architectures/cpu-families

that are not anymore on official Intel's documentation.

Cheers

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

Re: [coreboot] Suggested readings

2014-10-08 Thread Peter Stuge

pras...@anche.no wrote:
> today's "part numbers"/architectures/cpu-families on Intel 
> manuals are them of the QUARK family.

Yes and no. Quark is geared toward makers and hobbyists, seems to
basically be a 486 machine with some funky addons, and Intel has put
a fair bit of effort into documenting it well.

The "regular" x86 platforms are geared toward the Windows market, and
also used by the quickly emerging Chrome market. The Windows market
has, just like x86 machines, a not insignificant structural legacy,
and there is little to no useful documentation available unless you
are an ODM who will turn over millions and millions of devices per
year.

//Peter

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

Re: [coreboot] Suggested readings

2014-10-08 Thread Gregg Levine

Hello!
Very good Peter. Prasnik, the summary that Peter gave is even better
then I could arrange for. But I will add to it anyway.

The part numbers covered in that book are largely the ones that the
Intel team behind the 8086 family were making and selling then. Its
been a generation in people years and an untold number of them in
computer years (times the machines have spent working for us) the part
numbers we have now reflect all of that.

And as to what you stated there Peter:
"
Yes and no. Quark is geared toward makers and hobbyists, seems to
basically be a 486 machine with some funky addons, and Intel has put
a fair bit of effort into documenting it well.

The "regular" x86 platforms are geared toward the Windows market, and
also used by the quickly emerging Chrome market. The Windows market
has, just like x86 machines, a not insignificant structural legacy,
and there is little to no useful documentation available unless you
are an ODM who will turn over millions and millions of devices per
year."

That goes along with what I just stated.
-
Gregg C Levine gregg.drw...@gmail.com
"This signature fought the Time Wars, time and again."

On Wed, Oct 8, 2014 at 5:28 AM, Peter Stuge  wrote:
> pras...@anche.no wrote:
>> today's "part numbers"/architectures/cpu-families on Intel
>> manuals are them of the QUARK family.
>
> Yes and no. Quark is geared toward makers and hobbyists, seems to
> basically be a 486 machine with some funky addons, and Intel has put
> a fair bit of effort into documenting it well.
>
> The "regular" x86 platforms are geared toward the Windows market, and
> also used by the quickly emerging Chrome market. The Windows market
> has, just like x86 machines, a not insignificant structural legacy,
> and there is little to no useful documentation available unless you
> are an ODM who will turn over millions and millions of devices per
> year.
>
>
> //Peter
>
> --
> coreboot mailing list: coreboot@coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot

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

Re: [coreboot] X60: ethernet LED still on when machine is powered off or suspended

2014-10-08 Thread Werner Zeh




Is it possible that NIC is left on due to Wake on LAN feature?
Is it enabled at all in your case?

Werner
Am 02.10.2014 um 06:45 schrieb Denis 'GNUtoo' Carikli:

On Fri, 22 Aug 2014 02:22:01 +0100
The Gluglug  wrote:

Haven't tried it on factory.bin. Will let you know.

i945 doesn't have ME/AMT, as far as I know.

I remember reading about such things in intel datasheets.

I remember (very vaguely) reading about the fact that i945 can have AMT,
but that the "BIOS flash" has to be partitioned to allow that.

I'm also unsure where would the AMT run, maybe in the NIC? In that case
it may be able to fetch its firmware from a flash directly connected to
the NIC, and it may have nothing to do with the BIOS flash, I really
can't remember, sorry.

In any case, all the lenovo i945 laptops that we have in coreboot are
not setup for AMT.

I should try to find the datasheets I was talking about, and document
that since that question comes up way too often.

Denis.





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

Re: [coreboot] [coreboot-gerrit] Patch set updated for coreboot: 851c693 intel/minnowmax: Enable S3 suspend/resume

2014-10-08 Thread Marc Jones

Hi Mohan,

Thanks for the S3 patches. What OSs have you tested S3 with? Have you
tested that all the peripherals are working? I'm debugging a resume
hang on Mint:

[   66.091759] PM: resume of devices complete after 1237.808 msecs
[   66.675574] PM: Finishing wakeup.
[   66.679321] Restarting tasks ...
[   66.683058] BUG: unable to handle kernel paging request at 4b86d1d8
[   66.698356] IP: [] cpus_share_cache+0xc/0x40
[   66.708645] PGD 1c11067 PUD 0
[   66.715812] Oops:  [#2] SMP
[   66.723179] Modules linked in: coretemp kvm_intel kvm
crct10dif_pclmul crc32_pi
[   66.774920] CPU: 1 PID: 2067 Comm: pm-suspend Tainted: G  D
 3.13.0-24u
[   66.789363] Hardware name: Intel Minnow Max 2GB/Minnow Max 2GB,
BIOS 4.0 10/074
[   66.802465] task: 880064072fe0 ti: 88005efe6000 task.ti:
88005efe60
[   66.815416] RIP: 0010:[]  []
cpus_share_ca0
[   66.829327] RSP: :88005efe7ce0  EFLAGS: 00010017
[   66.839943] RAX:  RBX: f936b707 RCX: 880077c35fc0
[   66.852661] RDX: 88007b714440 RSI: 0001 RDI: f936b707
[   66.865387] RBP: 88005efe7d88 R08: 0010 R09: 
[   66.878133] R10:  R11: 03f9 R12: 0001
[   66.890902] R13: 00014440 R14: 0001 R15: f936b707
[   66.903678] FS:  7f40204b7740() GS:88007b70()
knlGS:000
[   66.917524] CS:  0010 DS:  ES:  CR0: 8005003b
[   66.928724] CR2: 4b86d1d8 CR3: 5081c000 CR4: 001007e0
[   66.941523] Stack:
[   66.948602]  88005efe7d88 8109fa92 5efe7d18
005b8d0
[   66.961788]  88007b714440 880074432fe0 8810
000
[   66.974951]  0001 88005efe7d40 0001
880074432f0
[   66.988138] Call Trace:
[   66.995783]  [] ? select_task_rq_fair+0x582/0x6f0
[   67.007754]  [] ? ttwu_do_wakeup+0x19/0xc0
[   67.019002]  [] try_to_wake_up+0x141/0x2c0
[   67.030212]  [] wake_up_process+0x23/0x40
[   67.041269]  [] __thaw_task+0x2c/0x40
[   67.051900]  [] thaw_processes+0xa0/0x130
[   67.062938]  [] pm_suspend+0x18e/0x260
[   67.073698]  [] state_store+0x79/0xf0
[   67.084369]  [] kobj_attr_store+0xf/0x20
[   67.095326]  [] sysfs_write_file+0x128/0x1c0
[   67.106672]  [] vfs_write+0xb4/0x1f0
[   67.117246]  [] SyS_write+0x49/0xa0
[   67.127682]  [] tracesys+0xe1/0xe6
[   67.137998] Code: e0 ff ff a8 08 0f 84 8d fe ff ff e9 3a ff ff ff
66 66 66 66
[   67.164624] RIP  [] cpus_share_cache+0xc/0x40
[   67.176349]  RSP 
[   67.185315] CR2: 4b86d1d8
[   67.194031] ---[ end trace 7f6401edfae25206 ]---
[   96.598277] [ cut here ]
[   96.603441] WARNING: CPU: 1 PID: 36 at
/build/buildd/linux-3.13.0/kernel/watch)
[   96.616163] Watchdog detected hard LOCKUP on cpu 1
[   96.621308] Modules linked in: coretemp kvm_intel kvm
crct10dif_pclmul crc32_pi
[   96.664488] CPU: 1 PID: 36 Comm: kswapd0 Tainted: G  D
3.13.0-24-geneu
[   96.673916] Hardware name: Intel Minnow Max 2GB/Minnow Max 2GB,
BIOS 4.0 10/074
[   96.682469]  0009 88007b706c20 81715ac4
88007b706c8
[   96.690752]  88007b706c58 810676bd 880075a25800
000
[   96.699037]  88007b706d88  88007b706ef8
88007b706c8
[   96.707320] Call Trace:
[   96.710047][] dump_stack+0x45/0x56
[   96.716483]  [] warn_slowpath_common+0x7d/0xa0
[   96.723196]  [] warn_slowpath_fmt+0x4c/0x50
[   96.729618]  [] ? restart_watchdog_hrtimer+0x50/0x50
[   96.736914]  [] watchdog_overflow_callback+0x9c/0xd0
[   96.744209]  [] __perf_event_overflow+0x8e/0x240
[   96.751117]  [] ? x86_perf_event_set_period+0xe8/0x150
[   96.758606]  [] perf_event_overflow+0x14/0x20
[   96.765222]  [] intel_pmu_handle_irq+0x1cd/0x3d0
[   96.772132]  [] perf_event_nmi_handler+0x2b/0x50
[   96.779039]  [] nmi_handle.isra.3+0x88/0x180
[   96.785559]  [] do_nmi+0xd0/0x340
[   96.791009]  [] end_repeat_nmi+0x1e/0x2e
[   96.797140]  [] ? _raw_spin_lock_irq+0x3f/0x60
[   96.803851]  [] ? _raw_spin_lock_irq+0x3f/0x60
[   96.810563]  [] ? _raw_spin_lock_irq+0x3f/0x60
[   96.817271]  <>  [] __refrigerator+0x7e/0x1a0
[   96.824385]  [] kswapd+0x39a/0x410
[   96.829934]  [] ? prepare_to_wait_event+0x100/0x100
[   96.837133]  [] ? balance_pgdat+0x610/0x610
[   96.843555]  [] kthread+0xd2/0xf0
[   96.849005]  [] ? kthread_create_on_node+0x1d0/0x1d0
[   96.856300]  [] ret_from_fork+0x7c/0xb0
[   96.862333]  [] ? kthread_create_on_node+0x1d0/0x1d0
[   96.869626] ---[ end trace 7f6401edfae25207 ]---


On Sat, Sep 27, 2014 at 8:27 AM, Mohan D'Costa  wrote:
> Mohan D'Costa (mo...@ndr.co.jp) just uploaded a new patch set to gerrit, 
> which you can find at http://review.coreboot.org/6972
>
> -gerrit
>
> commit 851c6936af062badc746abb4cc7fe8468c9c5745
> Author: Mohan D'Costa 
> Date:   Thu Sep 25 18:17:08 2014 +0900
>
> intel/minnowmax: Enable S3 suspend/resume
>
> This enables

[coreboot] #203: [Coreboot] Misalignment with GCC 4.9.1

2014-10-08 Thread coreboot

#203: [Coreboot] Misalignment with GCC 4.9.1
+--
Reporter:  Ryan Lin | Owner:  stepan@…
Type:  enhancement  |Status:  new
Priority:  major| Milestone:
   Component:  coreboot |  Keywords:
Dependencies:   |  Patch Status:  there is no patch
+--
 Hello Coreboot,

 I compiled coreboot with GCC 4.9.1 for x86 system, and found a
 misalignment issue. :

 Here is the abnormal segment of ramstage.map:

 0001d1d0 T _bs_init_begin
 0001d1e0 t mrc_cache_update
 0001d200 t pch_log
 0001d220 t finalize
 0001d248 t spi_init_bscb
 0001d25c t cbmem_bscb
 0001d280 t disable_rom_cache_bscb
 0001d2a8 T _bs_init_end

 Issue 1 : the address of "mrc_cache_update" should be 0001d1d0, but it is
 shifted to 0001d1e0.
 Issue 2 : the size of "mrc_cache_update" is 20 bytes, so the start adress
 of "pch_log" should be 0001d1f4, but it is shifted to 0001d200.

 Does there any compiler options need to be added for GCC 4.9.1?

 Thank you,
 Ryan

--
Ticket URL: 
coreboot 

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

[coreboot] [Coreboot] Misalignment with GCC 4.9.1

2014-10-08 Thread Lin, Ryan

Hello Coreboot,

I compiled coreboot with GCC 4.9.1 for x86 system, and found a misalignment 
issue. :

Here is the abnormal segment of ramstage.map:

0001d1d0 T _bs_init_begin
0001d1e0 t mrc_cache_update
0001d200 t pch_log
0001d220 t finalize
0001d248 t spi_init_bscb
0001d25c t cbmem_bscb
0001d280 t disable_rom_cache_bscb
0001d2a8 T _bs_init_end

Issue 1 : the address of "mrc_cache_update" should be 0001d1d0, but it is 
shifted to 0001d1e0.
Issue 2 : the size of "mrc_cache_update" is 20 bytes, so the start adress of 
"pch_log" should be 0001d1f4, but it is shifted to 0001d200.

Does there any compiler options need to be added for GCC 4.9.1? 

Thank you,
Ryan

ramstage.map
Description: ramstage.map
-- 
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] [coreboot-gerrit] Patch set updated for coreboot: 851c693 intel/minnowmax: Enable S3 suspend/resume

2014-10-08 Thread Mohan


Hi Marc,

I have tested it on Debian GNU/Linux Jessie, currently Linux version 
3.14-2-686-pae


The peripherals i have tested after S3 wakeup are:
Serial
HDMI
SATA
USB EHCI (Keyboard, usb storage)
Network
SDHC

Then ROM is (coreboot + grub2.elf)

What version of Mint are you using ?
Maybe i can also install it and have a look.

Mohan

On 10/09/14 02:58, Marc Jones wrote:

Hi Mohan,

Thanks for the S3 patches. What OSs have you tested S3 with? Have you
tested that all the peripherals are working? I'm debugging a resume
hang on Mint:

[   66.091759] PM: resume of devices complete after 1237.808 msecs
[   66.675574] PM: Finishing wakeup.
[   66.679321] Restarting tasks ...
[   66.683058] BUG: unable to handle kernel paging request at 4b86d1d8
[   66.698356] IP: [] cpus_share_cache+0xc/0x40
[   66.708645] PGD 1c11067 PUD 0
[   66.715812] Oops:  [#2] SMP
[   66.723179] Modules linked in: coretemp kvm_intel kvm
crct10dif_pclmul crc32_pi
[   66.774920] CPU: 1 PID: 2067 Comm: pm-suspend Tainted: G  D
  3.13.0-24u
[   66.789363] Hardware name: Intel Minnow Max 2GB/Minnow Max 2GB,
BIOS 4.0 10/074
[   66.802465] task: 880064072fe0 ti: 88005efe6000 task.ti:
88005efe60
[   66.815416] RIP: 0010:[]  []
cpus_share_ca0
[   66.829327] RSP: :88005efe7ce0  EFLAGS: 00010017
[   66.839943] RAX:  RBX: f936b707 RCX: 880077c35fc0
[   66.852661] RDX: 88007b714440 RSI: 0001 RDI: f936b707
[   66.865387] RBP: 88005efe7d88 R08: 0010 R09: 
[   66.878133] R10:  R11: 03f9 R12: 0001
[   66.890902] R13: 00014440 R14: 0001 R15: f936b707
[   66.903678] FS:  7f40204b7740() GS:88007b70()
knlGS:000
[   66.917524] CS:  0010 DS:  ES:  CR0: 8005003b
[   66.928724] CR2: 4b86d1d8 CR3: 5081c000 CR4: 001007e0
[   66.941523] Stack:
[   66.948602]  88005efe7d88 8109fa92 5efe7d18
005b8d0
[   66.961788]  88007b714440 880074432fe0 8810
000
[   66.974951]  0001 88005efe7d40 0001
880074432f0
[   66.988138] Call Trace:
[   66.995783]  [] ? select_task_rq_fair+0x582/0x6f0
[   67.007754]  [] ? ttwu_do_wakeup+0x19/0xc0
[   67.019002]  [] try_to_wake_up+0x141/0x2c0
[   67.030212]  [] wake_up_process+0x23/0x40
[   67.041269]  [] __thaw_task+0x2c/0x40
[   67.051900]  [] thaw_processes+0xa0/0x130
[   67.062938]  [] pm_suspend+0x18e/0x260
[   67.073698]  [] state_store+0x79/0xf0
[   67.084369]  [] kobj_attr_store+0xf/0x20
[   67.095326]  [] sysfs_write_file+0x128/0x1c0
[   67.106672]  [] vfs_write+0xb4/0x1f0
[   67.117246]  [] SyS_write+0x49/0xa0
[   67.127682]  [] tracesys+0xe1/0xe6
[   67.137998] Code: e0 ff ff a8 08 0f 84 8d fe ff ff e9 3a ff ff ff
66 66 66 66
[   67.164624] RIP  [] cpus_share_cache+0xc/0x40
[   67.176349]  RSP 
[   67.185315] CR2: 4b86d1d8
[   67.194031] ---[ end trace 7f6401edfae25206 ]---
[   96.598277] [ cut here ]
[   96.603441] WARNING: CPU: 1 PID: 36 at
/build/buildd/linux-3.13.0/kernel/watch)
[   96.616163] Watchdog detected hard LOCKUP on cpu 1
[   96.621308] Modules linked in: coretemp kvm_intel kvm
crct10dif_pclmul crc32_pi
[   96.664488] CPU: 1 PID: 36 Comm: kswapd0 Tainted: G  D
3.13.0-24-geneu
[   96.673916] Hardware name: Intel Minnow Max 2GB/Minnow Max 2GB,
BIOS 4.0 10/074
[   96.682469]  0009 88007b706c20 81715ac4
88007b706c8
[   96.690752]  88007b706c58 810676bd 880075a25800
000
[   96.699037]  88007b706d88  88007b706ef8
88007b706c8
[   96.707320] Call Trace:
[   96.710047][] dump_stack+0x45/0x56
[   96.716483]  [] warn_slowpath_common+0x7d/0xa0
[   96.723196]  [] warn_slowpath_fmt+0x4c/0x50
[   96.729618]  [] ? restart_watchdog_hrtimer+0x50/0x50
[   96.736914]  [] watchdog_overflow_callback+0x9c/0xd0
[   96.744209]  [] __perf_event_overflow+0x8e/0x240
[   96.751117]  [] ? x86_perf_event_set_period+0xe8/0x150
[   96.758606]  [] perf_event_overflow+0x14/0x20
[   96.765222]  [] intel_pmu_handle_irq+0x1cd/0x3d0
[   96.772132]  [] perf_event_nmi_handler+0x2b/0x50
[   96.779039]  [] nmi_handle.isra.3+0x88/0x180
[   96.785559]  [] do_nmi+0xd0/0x340
[   96.791009]  [] end_repeat_nmi+0x1e/0x2e
[   96.797140]  [] ? _raw_spin_lock_irq+0x3f/0x60
[   96.803851]  [] ? _raw_spin_lock_irq+0x3f/0x60
[   96.810563]  [] ? _raw_spin_lock_irq+0x3f/0x60
[   96.817271]  <>  [] __refrigerator+0x7e/0x1a0
[   96.824385]  [] kswapd+0x39a/0x410
[   96.829934]  [] ? prepare_to_wait_event+0x100/0x100
[   96.837133]  [] ? balance_pgdat+0x610/0x610
[   96.843555]  [] kthread+0xd2/0xf0
[   96.849005]  [] ? kthread_create_on_node+0x1d0/0x1d0
[   96.856300]  [] ret_from_fork+0x7c/0xb0
[   96.862333]  [] ? kthread_create_on_node+0x1d0/0x1d0
[   96.869626] ---[ end trace 7f6401edfae25207 ]---


On Sat, Se

Re: [coreboot] Suggested readings

Re: [coreboot] Suggested readings

Re: [coreboot] Suggested readings

Re: [coreboot] X60: ethernet LED still on when machine is powered off or suspended

Re: [coreboot] [coreboot-gerrit] Patch set updated for coreboot: 851c693 intel/minnowmax: Enable S3 suspend/resume

[coreboot] #203: [Coreboot] Misalignment with GCC 4.9.1

[coreboot] [Coreboot] Misalignment with GCC 4.9.1

Re: [coreboot] [coreboot-gerrit] Patch set updated for coreboot: 851c693 intel/minnowmax: Enable S3 suspend/resume

8 matches

Site Navigation

Mail list logo

Footer information