Closed alext-mkrs closed 5 years ago
Got it for IRQs. Interesting page for 32 vs 64 bit. BTW while Edison's version of it was never advertised as 64bit (don't know why), the core/SoC used there was also used in Merrifield phone platform - and there it was officially 64bit from the very beginning (https://ark.intel.com/products/codename/41559/Merrifield?q=merrifield).
Ok, I've found it. Your note about the reset (even though I tested it today to no avail) got me thinking further and I've actually just fallen prey of my specific workflow I used. In short - everything works ok, it's just that reset (cold vs. warm) that makes all the difference. I used the following flow:
reboot
run do_force_flash_os
), flash the U-Boot via dfu-util
reset
from U-Boot, after it resets run edsboot
to try to boot into the new kernel. It would hang on that RTC driverAnd now if I do a poweroff instead of reset
in U-Boot, it would boot normally. The reason is apparently that booting into 3.10-based official image takes up something that isn't cleaned up by a simple warm reset. That's why it didn't come up in my testing earlier today - because I was only getting to the new kernel and U-Boot, never "old kernel->new kernel" - and did come up last week (because I was following the full flow described above).
Okay, mistery solved and luckily nothing to be done here, just remember to do cold resets all the time :)
Now back to 32 vs 64 and non-ACPI vs ACPI. I've noticed on your "ACPI or non-ACPI" page that
Work on providing non-acpi U-Boot patches will end with the release of U-Boot v2018.09
is this still the plan (@andy-shev - probably that's a question to you)? If so I think non-ACPI just makes no sense, I'd rather then join (for real this time) the enablement activity for ACPI, to avoid spending my [rather limited, alas] time for non-ACPI version. There are I guess anyway not that many "production" users of our image right now and it would be more beneficial to get ACPI enabled sooner than drag the non-ACPI around in "somewhat working"/"it boots so probably works" state.
And one more note about 32 vs 64 bits - those instruction-related drawbacks look significant enough, however I wonder if we can actually help it by using a different - targeted at Silvermont, unlike the current one - Yocto compiler optimizations. We currently use core2-*
, while according to the file comments, the one for Silvermont would be corei7-*
(link). Actually that was exactly the thing I was trying to test when I got into this boot stall problem. Let me proceed with this task then - if you have any specific benchmarks you want me to try, let me know.
All in all, I'm now strongly inclined to ditch 32bit-non-ACPI and focus on fully enabling and stabilizing 64bit-ACPI, unless there's any showstopper there (interrupt delay might be one, but I hope this is just something that needs more detailed investigation/fix).
With your reset problems you may have actually found a new issue. I believe (but can not prove) the one I had was related to i2c messages being interrupted mid message and the i2c muxes only get reset on cold reset. My suspicion was linux does not properly perform the sw reset sequence on power up.
Actually I had corei7- in the past. It didn't seem to bring any advantages. And when I found the hsu issues thought it was related, changed to core2, didn't see any change and just left it.
Thing is 32b non-acpi is working quite well, mraa works, blink-led, hsu, and I believe but did not test, i2c-6. Only thing is, the pin muxes are fixed. Would be a waste to ditch.
Maybe 64b will never work well, and then we should create 32b acpi branch. But acpi is where we should put our efforts.
The stuff in there that works now, is working well enough. There is just some things missing, like acpi code that tell the SCU to change the mode of i2c-6 pins. And stuff that Andy works on (pmic acpi). For me, I really would need to have Andy tell me how to do that, step-by-step. And I believe he got the USB gadget stuff working, but haven't tried all that yet.
Okay, makes sense. Let's then leave the master as-is for now and focus on ACPI.
Now, @andy-shev - do you use 32 or 64 bit for developing that (AFAIU - 64, but let me confirm)? And the next question would be - which part of what @htot described above (or described on those Edison-wiki pages) I can help you to test? I figure I'd start with just helping out with testing while I'm getting up to speed with ACPI in kernel in general (and Edison in particular).
So, to the discontinuation:
Now about WIP, kernel:
U-Boot:
So, please, focus on these items for now (one guy talked to me privately that he is interested to bring up I2C №6 solution to U-Boot, so, it's not listed above b/c of this).
P.S. Of course it doesn't cancel the necessity of testing all stuff separately and together.
Thanks Andy. Let me dig into this and see where I can help.
Hello, guys!
I'm the guy Andy told you about. Here's the PR with I2C#6 support. It's not ready yet but it's already working. You're welcome to take a look and comment/test it out.
@htot It would be nice if you can test it after I merge the mentioned PR. I'm expecting @staroselskii will address my comments today and tonight we will have this in my edison-acpi branch of U-Boot.
I've have been following your discussion closely :-) Do we need patches to the kernel as well or is this independent?
@htot
It doesn't need any kernel patches. I have tested it like this:
modprobe i2c-dev && i2cdetect -r -y 6
I also had a device connected to this bus that worked correctly.
With no device connected i2cdetect -r -y 6 prints very slowly, same as before (-r -y 1 prints fast). It that normal? Will try to connect a device tomorrow.
@htot
No, it's not normal. On my setups the former prints fast as well. I tested it on two boards. One of them had an external sensor connected and the other did not. Both gave good results.
Want to know what's wrong before sending upstream. Didn't expect it not to work.
Could you please share a log from U-Boot booting? I'd be very much interested if you could add "#define DEBUG" on the top of pinmux.c. It would give me more context. I've been mostly using only two Edisons for the tests. There's a slight possibility something would be working differently on others due to some different settings pins are configured in the firmware. But I seriously doubt it.
Where are you testing? I've been using rocko64-acpi as a base with kernel checked out at eds-4.16-unified. Built for 64-bit. I boot off an eMMC (i.e. I don't use run edsboot but rather use ACPI for default boot as well).
You can also try the latest Andy's branch with some of the newer commits I made with DTS configuration. It shouldn't really have a difference but why not try.
I am using ~ the same, rocko64-acpi, but with eds-4.18-unified (from my repo) booting off USB. I'll try making a log.
@htot
If you have the time to test, I'd really appreciate that.
Here's what my U-Boot prints out (with DEBUG in pinmux.c)
U-Boot 2018.09-rc2 (Sep 02 2018 - 14:53:01 +0000)
CPU: x86_64, vendor Intel, device 406a8h
DRAM: 980.6 MiB
scu: v: 0x203511 p: 0xff0c1d28 bits: 1, mask: 7 bufcfg: 0xff0c1d28
scu: v: 0x203591 p: 0xff0c1d2c bits: 1, mask: 7 bufcfg: 0xff0c1d2c
MMC: mmc@ff3fc000: 0, mmc@ff3fa000: 1
Loading Environment from MMC... OK
In: serial
Out: serial
Err: serial
Net: No ethernet found.
UPD:
I also just rechecked this with and w/o i2c6_scl, i2c6_sda in DTS. It did make a difference. The former yielded a good result whereas the latter reacted with timeouts. I hope I didnt make a change that was working only on my Edisons that happen to give some bufcfg I know how to cope with.
I wanted to check these things today but I have a fever and feel sick as a dog.
I remember in the first line (2018.09-rc2...) I have the SHA of the top commit and followed by 'dirty'.
Sorry to hear that. Get well! This thing waits for sure. I'll try to reproduce these on other Edisons. I might have a couple more available for testing.
I tested this patch series with 5 more Edisons and 2 different boards connected to them. All tests actually gave me what I wanted.
I contacted Andy on the issue and said that he got some timeouts but it was better than before.
I just tested it on Intel Breakout board for Edison and it just works as well.
Andy also recommended to share these:
acpidump -o tables.dat
ignore_loglevel
in itgrep -H 15 /sys/bus/acpi/devices/*/status
i2cdetect -y -r 6
You can find them all here
BTW: REACH is mostly a copy of Arduino.asl. I have also added an AML for a driver I used for testing (sc16is7xx). It works also.
Feeling better today. Today I hope to rebuild U-Boot without the 'dirty' and with the DEBUG flag. If that doesn't help it may be caused by the 4.18 and I'll collect debug info. And push my feature branch of meta-intel-edison that builds that.
@staroselskii Thanks for sharing. Now I got that you never tried on Edison/Arduino despite presence of SSDT for it. I think the issue I'm experiencing might be related to wrong external pin control configuration. That ASL code needs to be revisited.
@htot Awesome. Thanks!
@andy-shev
I tested the whole thing on three different boards: Intel Breakout board and two of our own Reach and ReachRS. Unfortunately, I don't have an Edison/Arduino board.
Ok, I rebuilt, the 'dirty' is gone, but no change.
This is with 08110c94 from https://github.com/htot/linux/commits/eds-4.18.0-unified (that is eds-4.18.0-no-acpi + Andy's acpi patches):
# uname -a
Linux edison 4.18.0-edison-acpi-standard #1 SMP Thu Aug 30 21:01:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
I don't have acpidump on the Edison, but I can copy/decompile the table you need of course, let me know which one.
Now I will turn on the DEBUG
in pinmux.c
and add here later.
@htot Thanks for your work! From what I can see in /sys/kernel/debug/pinctrl/*/pins
I2C#6 pins are actually getting configured as we intended them:
pin 111 (GP27_I2C_6_SCL) mode 1 0x00000511
pin 112 (GP28_I2C_6_SDA) mode 1 0x00000591
What board are you testing on? If you have by any chance any other board (not Arduini/Edison) to test it with, I'd be very eager to know how that works out for you.
The patchset's goal was to set these two pins in mode 1 rather than mode 2 as they had been before.
UPD:
I have taken a closer look at your logs and spotted these:
gpio-468 (MUX6_DIR |i2c6-sda-mux ) out hi
gpio-469 (MUX4_DIR |i2c6-scl-mux ) out hi
...
gpio-500 (MUX7_SEL |i2c6-sda-mux ) out lo
gpio-501 (MUX5_SEL |i2c6-scl-mux ) out lo
...
gpio-508 (A4_PU_PD |i2c6-sda-pu ) in lo
gpio-509 (A5_PU_PD |i2c6-scl-pu ) in lo
Could it be relevant? I'm not sure where exactly these come from. But I guess these are actually the pca95xx expanders I always see the mistakes in my logs from. I saw something in meta-acpi that makes use of libgpiod to set up some pins.
Can they somehow intervene? They have something about i2c6. So I guess this should be it. I'll take a closer look at the code that deals with this tomorrow. Nevertheless, this is actually the place I'd be looking into. This does look suspicious (from my perspective of course). Unforunately, I couldn't understand what do I need and what do I not need in arduino.asl because of MUX_I2C and MUX_SPI defines. I guess they mux something through some transistors soldered out on the board itself?
Here is the U-Boot print out (with DEBUG in pinmux.c):
U-Boot 2018.09-rc2 (Sep 03 2018 - 21:07:30 +0000)
CPU: x86_64, vendor Intel, device 406a8h
DRAM: 980.6 MiB
scu: v: 0x203511 p: 0xff0c1d28 bits: 1, mask: 7 bufcfg: 0xff0c1d28
scu: v: 0x203591 p: 0xff0c1d2c bits: 1, mask: 7 bufcfg: 0xff0c1d2c
MMC: mmc@ff3fc000: 0, mmc@ff3fa000: 1
Loading Environment from MMC... OK
In: serial
Out: serial
Err: serial
Net: No ethernet found.
ACPI: Writing ACPI tables at e4500
ACPI: * FACS
ACPI: * DSDT
Fix up global NVS in DSDT to 0x000e5070
ACPI: * FADT
ACPI: * MADT
ACPI: * MCFG
ACPI: * SPCR
current = e5350
ACPI: done
I am testing on the Edison-Arduino.
Is there anything else I need to do? Pins needs to be configured as in/out? I am now checking the Edison-Arduino hardware guide section 11.6. It looks like I need to set a whole bunch. I will look into that more tomorrow.
Thanks!
Is there anything else I need to do? Pins needs to be configured as in/out?
We need to figure out what interferes with I2C#6 on Edison-Arduino. Because from what I can see from the pinctrl log and from the U-Boot logs, we have exactly the same pin cofiguration on I2C#6 pins. With only one problem: it works only on my machine :)
As I understand your hw is different, so it might well be level translators and stuff on the arduino board that need to be set to the right direction. And looking from the hw guide, this is very likely the case.
@staroselskii I just found your edits above:
gpio-468 (MUX6_DIR |i2c6-sda-mux ) out hi
gpio-469 (MUX4_DIR |i2c6-scl-mux ) out hi
gpio-500 (MUX7_SEL |i2c6-sda-mux ) out lo
gpio-501 (MUX5_SEL |i2c6-scl-mux ) out lo
I was looking at exact the same thing. Acc. to the Edison-Arduino hardware guide dir should be out/low and mux sel should be out/high. So either I have it mixed up in the asl, or I am mixing up the pin function names. It's hard :-)
Let me just drop in here to tell you guys to keep it up :) I unfortunately am in the middle of time-sucking stuff, but I'm following you closely. Just as you discovered, the Arduino board has additional expanders in there, so yes, they must be configured as well. I have both Arduino and breakout boards and should be able to test (if that's still needed by then), but no sooner than the upcoming weekend, alas.
@htot Can you try setting these pin using sysfs while in Linux and see if my patch works for you? We can make ASL do the right thing after that.
@alext-mkrs I'd be very glad if anyone could test it out on a breakout board. There's no rush. I hope that the patches will have landed in upstream by the weekend.
Yes, that's it. Fixed my asl in https://github.com/htot/meta-acpi/commits/eds. Will send PR after I get a I2C device to respond :-)
@alext-mkrs the asli is already setting the external muxes/directions/pullups, there was just a mixup. Now fixed.
@htot
Awesome! Good job!
Could you please tell me if i2cdetect hangs or not?
i2cdetect does not hang or have time outs. But I am not detecting any device yet. When I connect TSL2561 SCL and SDA are pulled high (with nothing connected both are low). But connecting a oscilloscope to SCL doesn't show any clock from the edison-arduino.
At least now I have:
cat /sys/kernel/debug/gpio | grep -i i2c6
gpio-468 (MUX6_DIR |i2c6-sda-mux ) out lo
gpio-469 (MUX4_DIR |i2c6-scl-mux ) out lo
gpio-500 (MUX7_SEL |i2c6-sda-mux ) out hi
gpio-501 (MUX5_SEL |i2c6-scl-mux ) out hi
gpio-508 (A4_PU_PD |i2c6-sda-pu ) in lo
gpio-509 (A5_PU_PD |i2c6-scl-pu ) in lo
@htot
i2cdetect does not hang or have time outs.
This is a step forward!
When I connect TSL2561 SCL and SDA are pulled high (with nothing connected both are low).
Seems like an Arduino/Edison board doesn't have pull-ups whereas your TSL2561 does. So this sounds reasonable.
But connecting a oscilloscope to SCL doesn't show any clock from the edison-arduino.
Okay. This is something we need to crack. Let's try to actually see something. Could you please tell how can I quickly understand a mapping between our pin numbers and legacy ones?
@staroselskii When I connect my scope to GP27 is see the I2C clock (1.8V level), also for Q3.3 (3.3V level). But A5 and SCL are low and even seem to be high-Z. It looks like U5 is disabled. But I can verify that U5.B1 (INH) is switched L by TRI_STATE_ALL (when I do gpioset `gpiofind TRI_STATE_ALL`=1
).
AFAIKT the problem is not in your U-Boot patch.
I see the problem. In the Edison HW guide there is an error. According to Table 4 GPIO 204/205 (corresponding to MUX7_SEL/MUX5_SEL with ACPI) must be L to select I2C, but according to Section 11.6 they must be H (which is wrong, acc. to the schematics).
To be continued...
Gentlemen, just as a side note - this was for my kernel boot problems, so you may want to create a new one for I2C enabling :) Though it's probably a bit too late anyway, as it's a good deal underway and GH doesn't have any easy way to move messages between issues.
Yes, that was the problem. Now tested with TSL2561 device attached and address 0x39 detected. I fixed meta-acpi to reflect that and will update asl on the wiki as @andy-shev asked me. If more needs to be discussed on this we should create a new issue for it.
@alext-mkrs Would you like to close this issue?
@htot
I'm glad you got it working. This is such a bummer that the docs have these inconsistencies.
Yeah, let's close this one. And looks like we are done with the second discussion anyway :)
@htot, let me check something with you - looks like current master built from scratch (no saved state whatsoever, manually removed all the dirs) doesn't boot for me. The kernel boots up until the below and then just stalls, then in a short while the board gets reset by the watchdog timer, and the process repeats endlessly.
Have you seen anything like that? Could you please try building the image from scratch and checking if it boots for you?
Full log inside
``` U-Boot 2018.05 (Jun 17 2018 - 12:44:14 +0000) CPU: x86_64, vendor Intel, device 406a8h DRAM: 980.6 MiB MMC: mmc@ff3fc000: 0, mmc@ff3fa000: 1 Loading Environment from MMC... OK In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 => => run edsboot 10749632 bytes read in 473 ms (21.7 MiB/s) Valid Boot Flag Setup Size = 0x00003e00 Magic signature found Using boot protocol version 2.0d Linux kernel version 4.16.0-edison-no-acpi-standard (oe-user@oe-host) #1 SMP Sat Jul 21 19:26:21 UTC 2018 Building boot_params at 0x00090000 Loading bzImage at address 100000 (10733760 bytes) Magic signature found Kernel command line: "tty1 console=ttyS2,115200n8 root=/dev/mmcblk1 rootfstype=ext4 systemd.unit=multi-user.target hardware_id=00" Magic signature found Starting kernel ... [ 0.000000] Linux version 4.16.0-edison-no-acpi-standard (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP Sat Jul 21 19:26:21 UTC 2018 [ 0.000000] x86/fpu: x87 FPU will use FXSAVE [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000097fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable [ 0.000000] BIOS-e820: [mem 0x0000000004000000-0x0000000005ffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000006000000-0x000000003f4fffff] usable [ 0.000000] BIOS-e820: [mem 0x000000003f500000-0x000000003fffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec04000-0x00000000fec07fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! [ 0.000000] random: fast init done [ 0.000000] SMBIOS 2.6 present. [ 0.000000] DMI: Intel Corporation Merrifield/BODEGA BAY, BIOS 542 2015.01.21:18.19.48 [ 0.000000] e820: last_pfn = 0x3f500 max_arch_pfn = 0x100000 [ 0.000000] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.000000] Scanning 1 areas for low memory corruption [ 0.000000] ACPI: Early table checksum verification disabled [ 0.000000] ACPI BIOS Error (bug): A valid RSDP was not found (20180105/tbxfroot-244) [ 0.000000] 129MB HIGHMEM available. [ 0.000000] 883MB LOWMEM available. [ 0.000000] mapped low ram: 0 - 373fe000 [ 0.000000] low ram: 0 - 373fe000 [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.000000] Normal [mem 0x0000000001000000-0x00000000373fdfff] [ 0.000000] HighMem [mem 0x00000000373fe000-0x000000003f4fffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000001000-0x0000000000097fff] [ 0.000000] node 0: [mem 0x0000000000100000-0x0000000003ffffff] [ 0.000000] node 0: [mem 0x0000000006000000-0x000000003f4fffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000001000-0x000000003f4fffff] [ 0.000000] Reserved but unavailable: 1 pages [ 0.000000] Using APIC driver default [ 0.000000] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [ 0.000000] SFI: SYST E31F0, 0060 (v1 INTEL INTELFDK) [ 0.000000] SFI: CPUS E3296, 0020 (v1 INTEL INTELFDK) [ 0.000000] SFI: FREQ E32C2, 0030 (v1 INTEL INTELFDK) [ 0.000000] SFI: MMAP E32FE, 01A4 (v1 INTEL INTELFDK) [ 0.000000] SFI: XSDT E34B0, 002C (v1 INTEL INTELFDK) [ 0.000000] SFI: APIC E353E, 0020 (v1 INTEL INTELFDK) [ 0.000000] SFI: WAKE E356A, 0020 (v2 INTEL INTELFDK) [ 0.000000] SFI: DEVS E359E, 047D (v1 INTEL INTELFDK) [ 0.000000] SFI: GPIO E3A27, 0964 (v1 INTEL INTELFDK) [ 0.000000] SFI: OEMB E4397, 0060 (v5 UMGFDK CFGINFO!) [ 0.000000] SFI: registering lapic[0] [ 0.000000] SFI: registering lapic[2] [ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-54 [ 0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.000000] PM: Registered nosave memory: [mem 0x00098000-0x000fffff] [ 0.000000] PM: Registered nosave memory: [mem 0x04000000-0x05ffffff] [ 0.000000] e820: [mem 0x40000000-0xfebfffff] available for PCI devices [ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1 [ 0.000000] percpu: Embedded 29 pages/cpu @(ptrval) s87756 r0 d31028 u118784 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 249263 [ 0.000000] Kernel command line: tty1 console=ttyS2,115200n8 root=/dev/mmcblk1 rootfstype=ext4 systemd.unit=multi-user.target hardware_id=00 [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Initializing CPU#0 [ 0.000000] Initializing HighMem for node 0 (000373fe:0003f500) [ 0.000000] Initializing Movable for node 0 (00000000:00000000) [ 0.000000] Memory: 972060K/1004124K available (9562K kernel code, 987K rwdata, 2764K rodata, 8484K init, 620K bss, 32064K reserved, 0K cma-reserved, 132104K highmem) [ 0.000000] virtual kernel memory layout: [ 0.000000] fixmap : 0xfff16000 - 0xfffff000 ( 932 kB) [ 0.000000] cpu_entry : 0xff800000 - 0xff939000 (1252 kB) [ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB) [ 0.000000] vmalloc : 0xf7bfe000 - 0xff3fe000 ( 120 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf73fe000 ( 883 MB) [ 0.000000] .init : 0xcef1d000 - 0xcf766000 (8484 kB) [ 0.000000] .data : 0xceb56930 - 0xcef07f40 (3781 kB) [ 0.000000] .text : 0xce200000 - 0xceb56930 (9562 kB) [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU event tracing is enabled. [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 2304, nr_irqs: 512, preallocated irqs: 0 [ 0.000000] Console: colour dummy device 80x25 [ 0.000000] console [ttyS2] enabled [ 0.000000] APIC: Switch to symmetric I/O mode setup [ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs [ 0.000000] tsc: Detected 500.000 MHz processor [ 0.000046] tsc: Detected 499.200 MHz TSC [ 0.000048] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0xe642f98297, max_idle_ns: 881590439301 ns [ 0.000410] Calibrating delay loop (skipped), value calculated using timer frequency.. 998.40 BogoMIPS (lpj=499200) [ 0.000676] pid_max: default: 32768 minimum: 301 [ 0.000910] Security Framework initialized [ 0.001000] SELinux: Initializing. [ 0.001000] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001000] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.001000] CPU: Physical Processor ID: 0 [ 0.001000] CPU: Processor Core ID: 0 [ 0.001000] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.001000] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) [ 0.001000] mce: CPU supports 6 MCE banks [ 0.001000] CPU0: Thermal monitoring enabled (TM1) [ 0.001000] process: using mwait in idle threads [ 0.001000] Last level iTLB entries: 4KB 48, 2MB 0, 4MB 0 [ 0.001000] Last level dTLB entries: 4KB 128, 2MB 16, 4MB 16, 1GB 0 [ 0.001000] Spectre V2 : Mitigation: Full generic retpoline [ 0.001000] Freeing SMP alternatives memory: 40K [ 0.001000] SFI: MCFG E34F6, 003C (v1 INTEL INTELFDK) [ 0.001000] smpboot: CPU0: Genuine Intel(R) CPU 4000 @ 500MHz (family: 0x6, model: 0x4a, stepping: 0x8) [ 0.001000] Performance Events: PEBS fmt2+, generic architected perfmon, full-width counters, Intel PMU driver. [ 0.001035] ... version: 3 [ 0.001150] ... bit width: 40 [ 0.001264] ... generic registers: 2 [ 0.001376] ... value mask: 000000ffffffffff [ 0.001519] ... max period: 0000007fffffffff [ 0.001662] ... fixed-purpose events: 3 [ 0.001773] ... event mask: 0000000700000003 [ 0.002164] Hierarchical SRCU implementation. [ 0.008695] smp: Bringing up secondary CPUs ... [ 0.009550] x86: Booting SMP configuration: [ 0.009671] .... node #0, CPUs: #1 [ 0.001000] Initializing CPU#1 [ 0.010213] smp: Brought up 1 node, 2 CPUs [ 0.010213] smpboot: Max logical packages: 1 [ 0.010262] smpboot: Total of 2 processors activated (1996.80 BogoMIPS) [ 0.011456] devtmpfs: initialized [ 0.014290] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns [ 0.014454] kworker/u4:0 (20) used greatest stack depth: 7084 bytes left [ 0.014560] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.015085] pinctrl core: initialized pinctrl subsystem [ 0.015522] SFI: SFI sysfs interfaces init success [ 0.016245] RTC time: 8:37:37, date: 07/22/18 [ 0.016872] NET: Registered protocol family 16 [ 0.017677] audit: initializing netlink subsys (disabled) [ 0.018145] audit: type=2000 audit(1532248657.018:1): state=initialized audit_enabled=0 res=1 [ 0.019550] cpuidle: using governor menu [ 0.021055] Using generic wifi platform data [ 0.021898] PCI: MMCONFIG for domain 0000 [bus 00-00] at [mem 0x3f500000-0x3f5fffff] (base 0x3f500000) [ 0.022030] PCI: MMCONFIG at [mem 0x3f500000-0x3f5fffff] reserved in E820 [ 0.022211] PCI: Using MMCONFIG for extended config space [ 0.022356] Intel MID platform detected, using MID PCI ops [ 0.022505] PCI: Using configuration type 1 for base access [ 0.029676] kworker/u4:1 (68) used greatest stack depth: 6828 bytes left [ 0.063381] HugeTLB registered 4.00 MiB page size, pre-allocated 0 pages [ 0.065515] ACPI: Interpreter disabled. [ 0.065760] bcm43xx-vmmc-regulator: Failed to request enable GPIO96: -517 [ 0.065956] reg-fixed-voltage reg-fixed-voltage.0.auto: Failed to register regulator: -517 [ 0.066364] vgaarb: loaded [ 0.067105] SCSI subsystem initialized [ 0.067881] usbcore: registered new interface driver usbfs [ 0.068210] usbcore: registered new interface driver hub [ 0.068500] usbcore: registered new device driver usb [ 0.068931] pps_core: LinuxPPS API ver. 1 registered [ 0.069048] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[ 0.069340] PTP clock support registered
[ 0.070233] EDAC MC: Ver: 3.0.0
[ 0.070992] Advanced Linux Sound Architecture Driver Initialized.
[ 0.071112] PCI: Probing PCI hardware
[ 0.071391] PCI host bridge to bus 0000:00
[ 0.071526] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 0.071700] pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
[ 0.071888] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[ 0.088621] Bluetooth: Core ver 2.22
[ 0.088799] NET: Registered protocol family 31
[ 0.088928] Bluetooth: HCI device and connection manager initialized
[ 0.089036] Bluetooth: HCI socket layer initialized
[ 0.089178] Bluetooth: L2CAP socket layer initialized
[ 0.089376] Bluetooth: SCO socket layer initialized
[ 0.089542] NetLabel: Initializing
[ 0.089642] NetLabel: domain hash size = 128
[ 0.089761] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.090053] NetLabel: unlabeled traffic allowed by default
[ 0.091548] clocksource: Switched to clocksource tsc-early
[ 0.166406] VFS: Disk quotas dquot_6.6.0
[ 0.166625] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.167178] pnp: PnP ACPI: disabled
[ 0.182698] NET: Registered protocol family 2
[ 0.183774] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[ 0.184006] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.184346] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.184671] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.184966] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.185224] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.185632] NET: Registered protocol family 1
[ 0.186459] RPC: Registered named UNIX socket transport module.
[ 0.186625] RPC: Registered udp transport module.
[ 0.186755] RPC: Registered tcp transport module.
[ 0.186884] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.634512] DMA-API: preallocated 65536 debug entries
[ 0.634661] DMA-API: debugging enabled by kernel config
[ 0.635481] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0xe642f98297, max_idle_ns: 881590439301 ns
[ 0.635796] clocksource: Switched to clocksource tsc
[ 0.636223] platform rtc_cmos: registered platform RTC device (no PNP device found)
[ 0.638402] Scanning for low memory corruption every 60 seconds
[ 0.640171] pci 0000:00:04.1: Registered Bluetooth device: hci_bcm
[ 0.643195] Initialise system trusted keyrings
[ 0.643857] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.660208] NFS: Registering the id_resolver key type
[ 0.660379] Key type id_resolver registered
[ 0.660499] Key type id_legacy registered
[ 0.669266] Key type asymmetric registered
[ 0.669393] Asymmetric key parser 'x509' registered
[ 0.669600] bounce: pool size: 64 pages
[ 0.669809] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 0.670047] io scheduler noop registered
[ 0.670162] io scheduler deadline registered
[ 0.670642] io scheduler cfq registered (default)
[ 0.670778] io scheduler mq-deadline registered
[ 0.670906] io scheduler kyber registered
[ 0.682296] dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels
[ 0.684366] hsu_dma_pci 0000:00:05.0: Found HSU DMA, 12 channels
[ 0.685147] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.689055] 8250_mid: probe of 0000:00:04.0 failed with error -16
[ 0.689886] 0000:00:04.1: ttyS0 at MMIO 0xff010080 (irq = 28, base_baud = 1843200) is a TI16750
[ 0.691575] 0000:00:04.2: ttyS1 at MMIO 0xff010100 (irq = 29, base_baud = 1843200) is a TI16750
[ 0.692954] console [ttyS2] disabled
[ 0.693158] 0000:00:04.3: ttyS2 at MMIO 0xff010180 (irq = 54, base_baud = 1843200) is a TI16750
[ 1.931247] console [ttyS2] enabled
[ 1.935683] Non-volatile memory driver v1.3
[ 1.940487] Linux agpgart interface v0.103
[ 1.955127] loop: module loaded
[ 1.960427] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 1.966588] e100: Copyright(c) 1999-2006 Intel Corporation
[ 1.972246] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[ 1.979334] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 1.985241] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.991112] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.997216] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 2.004216] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 2.009941] sky2: driver version 1.30
[ 2.014404] usbcore: registered new interface driver r8152
[ 2.020049] usbcore: registered new interface driver asix
[ 2.025556] usbcore: registered new interface driver ax88179_178a
[ 2.031755] usbcore: registered new interface driver cdc_ether
[ 2.037696] usbcore: registered new interface driver net1080
[ 2.043462] usbcore: registered new interface driver cdc_subset
[ 2.049490] usbcore: registered new interface driver zaurus
[ 2.055173] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[ 2.062716] usbcore: registered new interface driver cdc_ncm
[ 2.069260] dwc3 dwc3.1.auto: Configuration mismatch. dr_mode forced to host
[ 2.077667] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.084256] ehci-pci: EHCI PCI platform driver
[ 2.088843] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 2.095078] ohci-pci: OHCI PCI platform driver
[ 2.099652] uhci_hcd: USB Universal Host Controller Interface driver
[ 2.106421] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[ 2.112273] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 1
[ 2.120190] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220f06c hci version 0x100 quirks 0x02010010
[ 2.129000] xhci-hcd xhci-hcd.2.auto: irq 34, io mem 0xf9100000
[ 2.135382] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.142234] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.149501] usb usb1: Product: xHCI Host Controller
[ 2.154417] usb usb1: Manufacturer: Linux 4.16.0-edison-no-acpi-standard xhci-hcd
[ 2.161932] usb usb1: SerialNumber: xhci-hcd.2.auto
[ 2.167571] hub 1-0:1.0: USB hub found
[ 2.171430] hub 1-0:1.0: 1 port detected
[ 2.175937] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[ 2.181729] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[ 2.189547] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.197888] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 2.204728] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.211985] usb usb2: Product: xHCI Host Controller
[ 2.216898] usb usb2: Manufacturer: Linux 4.16.0-edison-no-acpi-standard xhci-hcd
[ 2.224414] usb usb2: SerialNumber: xhci-hcd.2.auto
[ 2.230064] hub 2-0:1.0: USB hub found
[ 2.233897] hub 2-0:1.0: 1 port detected
[ 2.238788] usbcore: registered new interface driver usblp
[ 2.244474] usbcore: registered new interface driver usb-storage
[ 2.250681] usbcore: registered new interface driver pl2303
[ 2.256361] usbserial: USB Serial support registered for pl2303
```