Bug#1010365: linux: failure to boot on Raspberry Pi Compute Module 4 (black screen)
Cyril Brulebois (2022-04-29): > > I'll try and pinpoint when it broke using the various intermediary > > versions: > > > > - 5.17~rc3-1~exp1 > > The first attempt was sufficient: it breaks as early as that version. Using the same base image as before, and only updating the kernel: I've tested upstream builds, starting from the .config found in the Debian 5.16.18-1 package, using oldconfig and accepting everything by default: - v5.16 is confirmed a first good; - v5.17-rc1 is confirmed a first bad; - the culprit seems to be 3ceff4ea07410763d5d4cccd60349bf7691e7e61 Here's the git bisect log: git bisect start # good: [df0cc57e057f18e44dac8e6c18aba47ab53202f9] Linux 5.16 git bisect good df0cc57e057f18e44dac8e6c18aba47ab53202f9 # bad: [e783362eb54cd99b2cac8b3a9aeac942e6f6ac07] Linux 5.17-rc1 git bisect bad e783362eb54cd99b2cac8b3a9aeac942e6f6ac07 # good: [fef8dfaea9d6c444b6c2174b3a2b0fca4d226c5e] Merge tag 'regulator-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator git bisect good fef8dfaea9d6c444b6c2174b3a2b0fca4d226c5e # bad: [3ceff4ea07410763d5d4cccd60349bf7691e7e61] Merge tag 'sound-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound git bisect bad 3ceff4ea07410763d5d4cccd60349bf7691e7e61 # good: [57ea81971b7296b42fc77424af44c5915d3d4ae2] Merge tag 'usb-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb git bisect good 57ea81971b7296b42fc77424af44c5915d3d4ae2 # good: [feb7a43de5ef625ad74097d8fd3481d5dbc06a59] Merge tag 'irq-msi-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip git bisect good feb7a43de5ef625ad74097d8fd3481d5dbc06a59 # good: [10674ca9ea02491fd3f8ffe303861b7a6837994b] ASoC/SoundWire: improve suspend flows and use set_stream() instead of set_tdm_slots() for HDAudio git bisect good 10674ca9ea02491fd3f8ffe303861b7a6837994b # good: [c77b1f8a8faeeba43c694d9d09d0b25a4f52cf37] scsi: mpi3mr: Bump driver version to 8.0.0.61.0 git bisect good c77b1f8a8faeeba43c694d9d09d0b25a4f52cf37 # good: [f66229aa355f7e0dc0dc20cbc1f4d45c3176eed2] Merge tag 'asoc-v5.17-2' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus git bisect good f66229aa355f7e0dc0dc20cbc1f4d45c3176eed2 # good: [59aa7fcfe2e44afbe9736e5cfa941699021d6957] IB/mthca: Use memset_startat() for clearing mpt_entry git bisect good 59aa7fcfe2e44afbe9736e5cfa941699021d6957 # good: [18451db82ef7f943c60a7fce685f16172bda5106] RDMA/core: Calculate UDP source port based on flow label or lqpn/rqpn git bisect good 18451db82ef7f943c60a7fce685f16172bda5106 # good: [1f43e5230aebb17aea35238dc26e297a61095ac0] mailbox: qcom-ipcc: Support more IPCC instance git bisect good 1f43e5230aebb17aea35238dc26e297a61095ac0 # good: [747c19eb7539b5e6bb15ed57a0a14ebf9f3adb8e] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma git bisect good 747c19eb7539b5e6bb15ed57a0a14ebf9f3adb8e # good: [e1a7aa25ff45636a6c1930bf2430c8b802e93d9c] Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi git bisect good e1a7aa25ff45636a6c1930bf2430c8b802e93d9c # good: [19980aa10d2d944ed8fe345ce2eb87c2cb4bedf8] ALSA: hda: intel-dsp-config: add JasperLake support git bisect good 19980aa10d2d944ed8fe345ce2eb87c2cb4bedf8 # good: [081c73701ef0c2a4f6a127da824a641ae6505fbe] ALSA: hda: intel-dsp-config: reorder the config table git bisect good 081c73701ef0c2a4f6a127da824a641ae6505fbe # first bad commit: [3ceff4ea07410763d5d4cccd60349bf7691e7e61] Merge tag 'sound-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound I'll try and find out more in a couple of hours, and get in touch with upstream. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
Hi I've done more tests (basically recompiled and installed 2 times the same kernel) with linux-5.17.5 but I am still having no luck : I can't figure out why it does not detect the controller ... I've checked the config and the drivers for the controller (ata_piix , ata_generic ) are built but they are not loaded at the initramfs stage. I've tried to put them explicitly in the initramfs via /etc/initramfs-tools/modules but nothing worked. So I decided to give a try to linux 5.18-rc4 : I've reverted the commit d6b88ce2eb9d , recompiled , installed in the target machine , rebooted and BINGO !! The system boots almost with the same config used for compiling linux 5.17.5 :) uname -a Linux 5.18.0-rc4 #1 PREEMPT Fri Apr 29 11:12:55 CEST 2022 i686 GNU/Linux cat /proc/version Linux version 5.18.0-rc4 (@<64bit_hostname>) (gcc (Debian 11.3.0-1) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1 PREEMPT Fri Apr 29 11:12:55 CEST 2022 The deb package I built is basically an optimized kernel for my machine with only the modules for the internal devices and the external components I have , so to be quick at building a new kernel ; it's not suitable for other systems. For who would like to try to build standard deb-flavour kernels in a quicker way in a faster machine, I can say that in the past I managed a 32 bit build host via virtual machine in my 64 bit machine to build deb packages I needed for my 32 bit system (basically, it was a minimal 32 bit debian unstable distribution installed as a virtualbox machine) : it was - and it is still now in my opinion - the easiest way to have a build host for 32 bit packages in a 64 bit environment because I found more complicated setting up a full cross compile environment .
Bug#998627: linux: please enable the new NTFS3 driver in 5.15
Hi, On Sun, Mar 20, 2022 at 10:25:23PM +0100, Ben Hutchings wrote: > On Fri, 2022-03-18 at 20:58 +0100, lenni_na1 wrote: > > Hi, > > > > are there any news on this? > > > > We are now at kernel 5.16 in testing and as far as I can tell the ntfs3 > > driver still hasn't been enabled. > > The recent traffic on the ntfs3 list seems to consist of bug reports > and small fixes, none of them being addressed by the supposed > maintainer of the filesystem (who last posted at the end of November). > > I think that we would be doing our users a disservice by enabling ntfs3 > in this state. In meanwhile the current state of NTFS3 driver has been discussed upstream starting in https://lore.kernel.org/lkml/da20d32b-5185-f40b-48b8-2986922d8...@stargateuniverse.net/ . Regards, Salvatore
Processed: reassign 1010343 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1010343 src:linux 5.17.3-1 Bug #1010343 [linux-image-5.17.0-1-amd64] linux-image-5.17.0-1-amd64 ACPI errors Bug reassigned from package 'linux-image-5.17.0-1-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/5.17.3+1. Ignoring request to alter fixed versions of bug #1010343 to the same values previously set Bug #1010343 [src:linux] linux-image-5.17.0-1-amd64 ACPI errors Marked as found in versions linux/5.17.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1010346 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 1010346 src:linux 4.19.235-1 Bug #1010346 [linux-image-cloud-amd64] linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel Bug reassigned from package 'linux-image-cloud-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/105+deb10u15. Ignoring request to alter fixed versions of bug #1010346 to the same values previously set Bug #1010346 [src:linux] linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel Marked as found in versions linux/4.19.235-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to linux, tagging 1006346
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1006346 + pending Bug #1006346 [src:linux] cloud.debian.org: bullseye AMIs don't boot on Amazon EC2 Xen instances with Enhanced Networking Bug #1007144 [src:linux] linux-image-cloud-amd64: Network doesn't come up on AWS Xen-based EC2 instances (ex c4.large) Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006346 1007144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1010365: linux: failure to boot on Raspberry Pi Compute Module 4 (black screen)
Processing control commands: > found -1 5.17~rc3-1~exp1 Bug #1010365 [src:linux] linux: failure to boot on Raspberry Pi Compute Module 4 (black screen) Marked as found in versions linux/5.17~rc3-1~exp1. -- 1010365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010365: linux: failure to boot on Raspberry Pi Compute Module 4 (black screen)
Control: found -1 5.17~rc3-1~exp1 Cyril Brulebois (2022-04-29): > The usual start-up rainbow is displayed, the screen turns to black and > nothing happens. My first stop was trying to downgrade the bootloader > (shipped by the raspi-firmware package) to the bullseye's version, but > that didn't help. > > Then I moved to starting from a bullseye image (which boots), upgrading > the raspi-firmware package, that still boots. > > Then I deployed 5.16.18-1 (from snapshot.debian.org), that still boots. > > Then I deployed 5.17.3-1, and it broke booting. > > I'll try and pinpoint when it broke using the various intermediary > versions: > > - 5.17~rc3-1~exp1 The first attempt was sufficient: it breaks as early as that version. > and then try to figure out what broke exactly. Contrary to my earlier > efforts to introduce support for that hardware a few months ago, I > haven't been following upstream changes recently, so I'll need to catch > up. Checking the upstream diff, nothing obvious on the DTB side. Trying to use 5.16.18-1's DTB with 5.17~rc3-1~exp1 kernel didn't help anyway. I've also tried latest mainline: v5.18-rc4-192-g38d741cb70b3 built with: cp ~/config-5.17.0-1-arm64 .config time PATH=/usr/lib/ccache:$PATH make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- oldconfig # accept everything time PATH=/usr/lib/ccache:$PATH make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- bindeb-pkg -j32 and the symptoms are the same: black screen at start-up. I've also checked the serial console (which is confirmed to work if I boot 5.16.18-1), and I'm not getting anything there either, with either 5.17~rc3-1~exp1 or my local v5.18-rc4-192-g38d741cb70b3 build. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1010365: linux: failure to boot on Raspberry Pi Compute Module 4 (black screen)
Source: linux Version: 5.17.3-1 Severity: important X-Debbugs-Cc: raspi-firmw...@packages.debian.org Hi, In the process of testing patches for the Raspberry Pi Compute Modules (CM3 and CM4), for bullseye[1][2] and bookworm[2], I discovered that bookworm images don't boot on the CM4. 1. https://bugs.debian.org/1010317 2. https://bugs.debian.org/996937 The usual start-up rainbow is displayed, the screen turns to black and nothing happens. My first stop was trying to downgrade the bootloader (shipped by the raspi-firmware package) to the bullseye's version, but that didn't help. Then I moved to starting from a bullseye image (which boots), upgrading the raspi-firmware package, that still boots. Then I deployed 5.16.18-1 (from snapshot.debian.org), that still boots. Then I deployed 5.17.3-1, and it broke booting. I'll try and pinpoint when it broke using the various intermediary versions: - 5.17~rc3-1~exp1 - 5.17~rc4-1~exp1 - 5.17~rc5-1~exp1 - 5.17~rc6-1~exp1 - 5.17~rc7-1~exp1 - 5.17~rc8-1~exp1 - 5.17.1-1~exp1 and then try to figure out what broke exactly. Contrary to my earlier efforts to introduce support for that hardware a few months ago, I haven't been following upstream changes recently, so I'll need to catch up. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel
Hi Vasudev On Fri, Apr 29, 2022 at 03:27:26PM +0530, Vasudev Kamath wrote: > Booting a KVM based VM with UEFI enabled using Buster image with cloud kernel > will have > a non working VNC console. Console seems to be frozen on debugging we figured > out that > its because buster cloud kernel does not have CONFIG_FB_EFI enabled. The cloud kernel is marked for specific environments only. All of them use the serial console first. > This issue is not present in Bullseye kernel as it was enabled in following > commit [1]. > Can we also enable same option for Buster cloud kernel?. Else for using VNC > like console > VM image needs to be running regular kernel (linux-image-amd64). Buster is in maintenance mode. So, why? Bastian -- Time is fluid ... like a river with currents, eddies, backwash. -- Spock, "The City on the Edge of Forever", stardate 3134.0
Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel
Package: linux-image-cloud-amd64 Version: 4.19+105+deb10u15 Severity: important Dear Maintainer, Booting a KVM based VM with UEFI enabled using Buster image with cloud kernel will have a non working VNC console. Console seems to be frozen on debugging we figured out that its because buster cloud kernel does not have CONFIG_FB_EFI enabled. This issue is not present in Bullseye kernel as it was enabled in following commit [1]. Can we also enable same option for Buster cloud kernel?. Else for using VNC like console VM image needs to be running regular kernel (linux-image-amd64). [1] https://salsa.debian.org/kernel-team/linux/-/commit/aa2bac77ef935f38b64a080a29318792c895eb12 Thanks and Regads, Vasudev -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-cloud-amd64 depends on: pn linux-image-5.17.0-1-cloud-amd64 linux-image-cloud-amd64 recommends no packages. linux-image-cloud-amd64 suggests no packages.
Bug#1010343: linux-image-5.17.0-1-amd64 ACPI errors
Package: linux-image-5.17.0-1-amd64 Version: 5.17.3-1 After upgrading from kernel 5.16 to 5.17 there are *ACPI* errors like this : kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR08._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR09._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR10._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) kernel: ACPI Error: Aborting method \_PR.PR11._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Is it caused by *ACPI_PFRUT* ? . If yes maybe this should be disabled on desktop systems by default. Is there any kernel boot option to disable this functionality ? Regards Edi
Bug#1010333: linux-image-4.9.0-18-amd64: USB keyboard and mouse erratic behavior and USB ports stop working
Package: src:linux Version: 4.9.303-1 Severity: important Dear Maintainer, The USB keyboard and mouse have been intermittently misbehaving on Debian 9, 10, and 11 for over a year: - Random mouse and/or keyboard event storms when I move the mouse. - Repeating keys when no key is pressed. - Keyboard and mouse stop functioning completely. I have been discussing these symptoms on the debian-user mailing list: https://www.mail-archive.com/debian-user@lists.debian.org/msg781396.html Tonight, I was erasing USB flash drives. After a several drives, I inserted another drive and it was not recognized. I removed it, and tried again -- no help. I rebooted. I then continued. When I insert a USB flash drive into a USB 3.0 port, both ports on that chipset stopped working. I do not have sudo configured. I have pasted dmesg(1) output at the end of this bug report. David -- Package-specific info: ** Version: Linux version 4.9.0-18-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.303-1 (2022-03-07) ** Command line: BOOT_IMAGE=/vmlinuz-4.9.0-18-amd64 root=UUID=9e15b950-3239-41ee-9f35-afb6e515d63a ro noresume ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor: Intel Corp. bios_version: SWQ6710H.86A.0068.2017.0601.1423 board_vendor: Intel Corporation board_name: DQ67SW board_version: AAG12527-310 ** Loaded modules: uas usb_storage nls_utf8 cifs sha256_ssse3 cmac md4 des_generic arc4 dns_resolver fscache vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_userspace cpufreq_powersave cpufreq_conservative intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic evdev irqbypass i915 intel_cstate intel_uncore intel_rapl_perf lpc_ich pcspkr snd_hda_intel serio_raw video mfd_core snd_hda_codec snd_hda_core snd_hwdep snd_pcm drm_kms_helper sg snd_timer snd drm soundcore mei_me i2c_algo_bit mei shpchp button parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache algif_skcipher af_alg dm_crypt dm_mod sr_mod cdrom sd_mod hid_generic usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ata_generic aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse xhci_pci ahci firewire_ohci ehci_pci libahci i2c_i801 xhci_hcd i2c_smbus firewire_core ehci_hcd crc_itu_t libata e1000e usbcore ptp usb_common pps_core scsi_mod ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09) Subsystem: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:2008] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snb_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2008] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Subsystem: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller [8086:2008] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:16.2 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset Family IDE-r Controller [8086:1c3c] (rev 04) (prog-if 85 [Master SecO PriO]) Subsystem: Intel Corporation 6 Series/C200 Series Chipset Family IDE-r
