Bug 8993 - Parselogs error: tcgetattr: Input/output error^M in lsb image on NUC
Summary: Parselogs error: tcgetattr: Input/output error^M in lsb image on NUC
Status: VERIFIED DUPLICATE of bug 5351
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-runtime (show other bugs)
Version: 2.0.1
Hardware: NUC x86_64
: Undecided normal
Target Milestone: ---
Assignee: Bruce Ashfield
QA Contact: Cristina Agurida
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-01-25 13:30 UTC by Cristina Agurida
Modified: 2016-02-15 14:54 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cristina Agurida 2016-01-25 13:30:46 UTC
STATUS: FAILED
BUILD: 2.0.1_RC2:dd0ba9ea4a11ab15348d4fe3574e4b28784db82f
ENVIRONMENT: genericx86-64-LSB on NUC
IMAGE: core-image-lsb-sdk
STEPS TO REPRODUCE: 
  
 Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc.
Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored.

The image can be found at the following link: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1.rc2/machines/genericx86-64-lsb/core-image-lsb-sdk-genericx86-64.hddimg


EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:

This error appears:

Central error: Jan 26 19:25:09 genericx86-64 getty[1150]: tcgetattr: Input/output error^M
| ***********************
| Jan 26 18:16:49 genericx86-64 kernel: hid-generic 0003:04F3:0103.0002: input: USB HID v1.11 Device [HID 04f3:0103] on usb-0000:00:14.0-3/input1
| Jan 26 18:16:49 genericx86-64 kernel: usb 2-4: new low-speed USB device number 3 using xhci_hcd
| Jan 26 18:16:49 genericx86-64 kernel: usb 2-4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
| Jan 26 18:16:49 genericx86-64 kernel: input: HP HP as /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/0003:03F0:0C4A.0003/input/input9
| Jan 26 18:16:49 genericx86-64 kernel: hid-generic 0003:03F0:0C4A.0003: input: USB HID v1.11 Mouse [HP HP] on usb-0000:00:14.0-4/input0
| Jan 26 18:16:49 genericx86-64 kernel: usb 2-7: new full-speed USB device number 4 using xhci_hcd
| Jan 26 18:16:49 genericx86-64 kernel: usb 2-7: No LPM exit latency info found.  Power management will be impacted.
| Jan 26 18:16:49 genericx86-64 kernel: Switched to clocksource tsc
| Jan 26 18:16:49 genericx86-64 kernel: uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
| Jan 26 18:16:49 genericx86-64 kernel: uvesafb: vbe_init() failed with -22
| Jan 26 18:16:49 genericx86-64 kernel: uvesafb: probe of uvesafb.0 failed with error -22
| Jan 26 18:16:49 genericx86-64 kernel: <30>udevd[113]: starting version 182
| Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:03.0: enabling device (0000 -> 0002)
| Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
| Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:03.0: irq 60 for MSI/MSI-X
| Jan 26 18:16:49 genericx86-64 kernel: snd_hda_intel 0000:00:1b.0: irq 61 for MSI/MSI-X
| Jan 26 18:16:49 genericx86-64 kernel: Too many HDMI devices
| Jan 26 18:16:49 genericx86-64 kernel: Consider building the kernel with CONFIG_SND_DYNAMIC_MINORS=y
| Jan 26 18:16:49 genericx86-64 kernel: Adding 5860348k swap on /dev/sda3.  Priority:-1 extents:1 across:5860348k SS
| Jan 26 18:16:49 genericx86-64 kernel: random: dd urandom read with 109 bits of entropy available
| Jan 26 18:16:49 genericx86-64 kernel: random: nonblocking pool is initialized
Comment 1 Saul Wold 2016-01-25 18:12:06 UTC
This is a duplicate of 5351 as they are both the tcgetattr failure, trying to get the console

*** This bug has been marked as a duplicate of bug 5351 ***
Comment 2 Alexandru Georgescu 2016-02-15 14:54:17 UTC
(In reply to comment #1)
> This is a duplicate of 5351 as they are both the tcgetattr failure, trying
> to get the console
> 
> *** This bug has been marked as a duplicate of bug 5351 ***

Verified as per above comment.