Bug#994453: Hit with linux-image-5.14.0-1-amd64 on Ryzen 5 3500U
I've hit this issue with the linux-image-5.14.0-1-amd64 (5.14.6-2) that has made its way to testing this week; symptom is grub never shows anything after the loading the initrd message. earlycon=efifb and earlyprintk=efi didn't give any extra output. mem_encrypt=off resulted in a successful boot. Hardware is a Ryzen 3 3500U laptop. It seems like this is a potential interaction between the memory encryption and amdgpu? J. -- ... "What's the philosophical difference between a killfile and the automoderation?" "A killfile throws away good posts. Automoderation throws away bad posts." -- Jonathan H N Chin to Calle Dybedahl
Bug#890902: firmware-misc-nonfree: Please include ti_3410.fw / ti_5052.fw firmwares
Package: firmware-misc-nonfree Version: 20170823-1 Severity: wishlist I've recently obtained a TI 3410 device using the ti_usb_3410_5052 driver. It seems that although the appropriate firmware for this (ti_3410.fw) is included in the upstream linux-firmware git tree it is not included in the firmware-misc-nonfree. Please consider adding it, and the accompanying ti_5052.fw for the dual port version of this adaptor. Thanks, J. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.4 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-misc-nonfree depends on no packages. firmware-misc-nonfree recommends no packages. Versions of packages firmware-misc-nonfree suggests: ii initramfs-tools 0.130 -- no debconf information
Bug#714974: [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
On Thu, Aug 29, 2013 at 03:48:03PM -0700, Jonathan McDowell wrote: On Sat, Aug 17, 2013 at 10:01:31PM +0200, Ben Hutchings wrote: On Thu, 2013-08-15 at 14:26 -0700, Christian Kujau wrote: On Thu, 15 Aug 2013 at 15:48, Dave Kleikamp wrote: This patch replaces the one I posted yesterday. I like this better since it doesn't require fixing existing on-disk cookies or skipping a position in the in-inode index table. Thanks. Applied to 3.11-rc5 and tested, no more readdir loop messages and with unique inode numbers, great! Tested-by: Christian Kujau li...@nerdbynature.de Karl and Jonathan, could you test the attached backport to 3.2? I finally managed to be able to schedule some downtime yesterday for one of the machines I've been seeing this issue with. So far since the reboot to this kernel (3.2.46-1 + the patch) I haven't seen a recurrence of the problem; will update if I see anything. I see the patch hit 3.11, but just to confirm the 3.2 backport on top of the Debian 3.2.46-1 kernel has seen no recurrence or issues in the past week (with a set of JFS filesystems that are fairly extensively used over NFS). J. -- Web [ Aunt Em: Hate Kansas. Hate you. Taking dog. Bye. Dorothy. ] site: http:// [ ] Made by www.earth.li/~noodles/ [ ] HuggieTag 0.0.24 signature.asc Description: Digital signature
Bug#714974: [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
On Sat, Aug 17, 2013 at 10:01:31PM +0200, Ben Hutchings wrote: On Thu, 2013-08-15 at 14:26 -0700, Christian Kujau wrote: On Thu, 15 Aug 2013 at 15:48, Dave Kleikamp wrote: This patch replaces the one I posted yesterday. I like this better since it doesn't require fixing existing on-disk cookies or skipping a position in the in-inode index table. Thanks. Applied to 3.11-rc5 and tested, no more readdir loop messages and with unique inode numbers, great! Tested-by: Christian Kujau li...@nerdbynature.de Karl and Jonathan, could you test the attached backport to 3.2? I finally managed to be able to schedule some downtime yesterday for one of the machines I've been seeing this issue with. So far since the reboot to this kernel (3.2.46-1 + the patch) I haven't seen a recurrence of the problem; will update if I see anything. J. -- Just 'cause I remembered one thing doesn't make me smart! signature.asc Description: Digital signature
Bug#687442: Success with 3.2.0-4.drm-amd64 / nVidia GF106
On Mon, Jan 28, 2013 at 11:30:24AM -0800, Jonathan McDowell wrote: I'd like to report success with my HP EliteBook 8560w sporting an nVidia GF106 video card and the 3.2.0-4.drm-amd64 kernel. The stock 3.2.35-2 kernel image results in a black screen once KMS kicks in and I've been following the linux-image trunk packages from experimental instead. The 3.2.35-3~jcristau.1 boots to a GDM login just fine and has survived several suspend/resume cycles. I have not yet tried an external monitor - won't be able to do so until this weekend. Just to follow up - still looks good. No issue with external monitor attached via docking station, or a week of several suspend/resumes a day. $ uname -a ; uptime Linux thukpa 3.2.0-4.drm-amd64 #1 SMP Debian 3.2.35-3~jcristau.1 x86_64 GNU/Linux 11:48:02 up 7 days, 19:02, 8 users, load average: 0.48, 0.52, 0.90 J. -- xmpp:nood...@earth.li I don't bite. Well, that's wrong. I do bite. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130204194827.gr27...@earth.li
Bug#687442: Success with 3.2.0-4.drm-amd64 / nVidia GF106
I'd like to report success with my HP EliteBook 8560w sporting an nVidia GF106 video card and the 3.2.0-4.drm-amd64 kernel. The stock 3.2.35-2 kernel image results in a black screen once KMS kicks in and I've been following the linux-image trunk packages from experimental instead. The 3.2.35-3~jcristau.1 boots to a GDM login just fine and has survived several suspend/resume cycles. I have not yet tried an external monitor - won't be able to do so until this weekend. Thanks Julien! J. -- Every bug you find is the last one. This .sig brought to you by the letter N and the number 17 Product of the Republic of HuggieTag -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130128193024.gy27...@earth.li
Bug#685407: [wheezy] jfs + nfs duplicate cookies problem
On Wed, Dec 12, 2012 at 10:56:54PM -0800, Jonathan Nieder wrote: Jonathan McDowell wrote: [Subject: Seeing this with wheezy kernel; any ETA for fix?] Please keep in mind that these appear as emails in a crowded inbox, so the subject line can be a good place to put valuable context. Sorry, yes, though further investigating I can see this happening on exports that are JFS on the server side, so I'm not sure the patches already in this bug report are applicable. I've done a little digging but I can't see anything similar in upstream for anything other than ext3/4 but I'm not entirely clear if that's because it's not necessary, or because things like JFS aren't in use as much. I'll keep digging and update if I find anything. J. -- If I could, I would, but I can't, so I won't. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121213170650.gd3...@earth.li
Bug#685407: [wheezy] jfs + nfs duplicate cookies problem
On Thu, Dec 13, 2012 at 09:54:45AM -0800, Jonathan Nieder wrote: Jonathan McDowell wrote: Sorry, yes, though further investigating I can see this happening on exports that are JFS on the server side, so I'm not sure the patches already in this bug report are applicable. Do you have logs of the failure? JFS uses 32-bit readdir cookies but if I understand fs/jfs/jfs_dtree.c::add_index() correctly then they are sequential, unlike the hashes ext2/3/4 use. I see things like: [593351.877678] NFS: directory fs/nfsd contains a readdir loop.Please contact your server vendor. The file: .nfs3proc.o.cmda.com has duplicate cookie 73 [593351.904689] NFS: directory fs/nfsd contains a readdir loop.Please contact your server vendor. The file: .nfs3proc.o.cmda.com has duplicate cookie 73 J. -- Evil will always triumph over Good, because Good is dumb. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121213193335.ge3...@earth.li
Bug#685407: Seeing this with wheezy kernel; any ETA for fix?
I'm seeing this on a set of machines running squeeze with the wheezy (2.6.32-46) kernel on the client + server, as well as a client running 3.6.0 taking to a wheezy kernel server. Any indication of whether the fix will hit wheezy, or the reasons why not (i.e. will it cause me problems if I do a manual backport as Brian did)? Thanks, J. -- No program done by an undergrad will work after she graduates. This .sig brought to you by the letter T and the number 49 Product of the Republic of HuggieTag -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121212215724.gw3...@earth.li
Bug#685407: Seeing this with wheezy kernel; any ETA for fix?
On Wed, Dec 12, 2012 at 01:57:24PM -0800, Jonathan McDowell wrote: I'm seeing this on a set of machines running squeeze with the wheezy (2.6.32-46) kernel on the client + server, as well as a client running I mean 3.2.32-1 here; I still have the squeeze kernel installed and looked at the wrong dpkg line. 3.6.0 taking to a wheezy kernel server. Any indication of whether the fix will hit wheezy, or the reasons why not (i.e. will it cause me problems if I do a manual backport as Brian did)? J. -- Coming off Usenet is worse than | .''`. Debian GNU/Linux Developer coming off heroin. -- Peter| : :' : Happy to accept PGP signed Corlett | `. `' or encrypted mail - RSA | `-key on the keyservers. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121213004524.gx3...@earth.li
Bug#690990: linux-image-3.2.0-4-amd64: Soft lockup in scsi_remove_target on FC path down
Package: src:linux Version: 3.2.30-1 Severity: important I had a fibre channel path go down on my host (running Squeeze but with the kernel from unstable) and hit the following backtrace in dmesg repeatedly, resulting in having to reboot the machine as it became unresponsive. I've seen the same issue in a vanilla 3.6 kernel, the patch at: http://marc.info/?l=linux-scsim=134621716223056w=2 solved the issue for me there. [605808.104913] Pid: 25012, comm: kworker/0:0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.30-1 HP ProLiant BL465c Gen8 [605808.104960] RIP: 0010:[8107088a] [8107088a] arch_local_irq_restore+0x2/0x8 [605808.105004] RSP: 0018:8801b0a37e28 EFLAGS: 0202 [605808.105028] RAX: 88042e1e1050 RBX: 0200 RCX: 5a84 [605808.105066] RDX: 5a845a84 RSI: 0202 RDI: 0202 [605808.105123] RBP: 88042e440c00 R08: 0200 R09: 8168dc80 [605808.105162] R10: 880a36cf6c10 R11: 880a36cf6c10 R12: 880a36cf6c10 [605808.105200] R13: 880a36cf6c10 R14: 880a36cf6c10 R15: 88042e440c00 [605808.105240] FS: 7f8507eea7a0() GS:88043fc0() knlGS:f77bf8d0 [605808.105280] CS: 0010 DS: ES: CR0: 8005003b [605808.105305] CR2: 7fffd3012c48 CR3: 01605000 CR4: 000406f0 [605808.105344] DR0: DR1: DR2: [605808.105391] DR3: DR6: 0ff0 DR7: 0400 [605808.105429] Process kworker/0:0 (pid: 25012, threadinfo 8801b0a36000, task 88042e578fa0) [605808.105470] Stack: [605808.105488] a000bf77 88042eb6c800 0202 a008722e [605808.105534] 8801005dbf40 88043fc0e640 88043fc1b700 a008722e [605808.105581] 88043fc1b7a5 8105af9e 88043fc0e640 [605808.105627] Call Trace: [605808.105653] [a000bf77] ? scsi_remove_target+0x101/0x11d [scsi_mod] [605808.105697] [a008722e] ? store_fc_host_system_hostname+0x64/0x64 [scsi_transport_fc] [605808.105743] [a008722e] ? store_fc_host_system_hostname+0x64/0x64 [scsi_transport_fc] [605808.105785] [8105af9e] ? process_one_work+0x163/0x284 [605808.105811] [8105bf66] ? worker_thread+0xc2/0x145 [605808.105836] [8105bea4] ? manage_workers.isra.24+0x15b/0x15b [605808.105863] [8105f095] ? kthread+0x76/0x7e [605808.105887] [81352c34] ? kernel_thread_helper+0x4/0x10 [605808.105913] [8105f01f] ? kthread_worker_fn+0x139/0x139 [605808.105939] [81352c30] ? gs_change+0x13/0x13 [605808.105962] Code: b2 2d 00 66 ff 05 67 39 59 00 c3 48 c7 c7 d0 41 60 81 e9 ba b2 2d 00 66 ff 05 53 39 59 00 fb 66 66 90 66 66 90 c3 c3 90 90 57 9d 66 66 90 66 90 c3 fa 66 66 90 66 66 90 c3 50 9c 58 66 66 90 66 [605808.106166] Call Trace: [605808.106192] [a000bf77] ? scsi_remove_target+0x101/0x11d [scsi_mod] [605808.106235] [a008722e] ? store_fc_host_system_hostname+0x64/0x64 [scsi_transport_fc] [605808.106281] [a008722e] ? store_fc_host_system_hostname+0x64/0x64 [scsi_transport_fc] [605808.106340] [8105af9e] ? process_one_work+0x163/0x284 [605808.106366] [8105bf66] ? worker_thread+0xc2/0x145 [605808.106391] [8105bea4] ? manage_workers.isra.24+0x15b/0x15b [605808.106417] [8105f095] ? kthread+0x76/0x7e [605808.106441] [81352c34] ? kernel_thread_helper+0x4/0x10 [605808.108012] [8105f01f] ? kthread_worker_fn+0x139/0x139 [605808.108012] [81352c30] ? gs_change+0x13/0x13 [605836.104017] BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:0:25012] [605836.104044] Modules linked in: sg joydev usbhid hid autofs4 quota_v2 quota_tree nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc loop snd_pcm snd_timer snd mperf crc32c_intel amd64_edac_mod edac_core soundcore sp5100_tco i2c_piix4 i2c_core ghash_clmulni_intel edac_mce_amd psmouse snd_page_alloc hpilo hpwdt container processor tpm_tis tpm thermal_sys aesni_intel evdev serio_raw pcspkr k10temp button fam15h_power acpi_power_meter tpm_bios cryptd aes_x86_64 aes_generic ext4 mbcache jbd2 crc16 dm_round_robin ses enclosure dm_multipath scsi_dh dm_mod sd_mod crc_t10dif be2iscsi ahci ata_generic iscsi_boot_sysfs libiscsi ohci_hcd scsi_transport_iscsi libahci uhci_hcd lpfc scsi_transport_fc pata_atiixp scsi_tgt libata ehci_hcd usbcore hpsa be2net scsi_mod usb_common [last unloaded: scsi_wait_scan] [605836.104466] CPU 0 [605836.104470] Modules linked in: sg joydev usbhid hid autofs4 quota_v2 quota_tree nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc loop snd_pcm snd_timer snd mperf crc32c_intel amd64_edac_mod edac_core soundcore sp5100_tco i2c_piix4 i2c_core ghash_clmulni_intel edac_mce_amd psmouse snd_page_alloc hpilo hpwdt container processor tpm_tis tpm thermal_sys aesni_intel evdev serio_raw pcspkr k10temp button fam15h_power
Bug#690100: Debian 6.0.6 d-i image fails to see HP RAID controller
On Wed, Oct 10, 2012 at 05:54:35AM +0100, Ben Hutchings wrote: On Tue, 2012-10-09 at 16:52 -0700, Jonathan McDowell wrote: Package: src:linux-2.6 Version: 2.6.32-46 Tried to do an install on an HP Gen8 blade server today which has a SAS RAID controller. This wasn't detected during d-i; I got at: hpsa :03:00.0: unrecognized board ID: 0x3355103c, ignoring. error in dmesg. I flipped to a console and tried: # modprobe -r hpsa # modprobe hpsa hpsa_allow_any=1 and then was able to see my sda RAID device. lspci info is: 03:00.0 RAID bus controller [0104]: Hewlett-Packard Company Device [103c:323b] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:3355] Upstream kernel revision 9143a9612277abc6e4ddced2bc54a120734834c6 looks appropriate and adds this subsystem ID to the device table. There have been a whole lot of bug fixes to this driver since the initial backport so I think a larger update is in order. Could you test this version backported from 3.2.31: http://people.debian.org/~benh/driver-test/hpsa.ko (this is built for 2.6.32-5-amd64, which I assume is what you're using). I can confirm this installs, finds the card and correctly sees the attached HDD. J. -- Save usenet: rmgroup ox.colleges.keble -- Simon Cozens, ox.test signature.asc Description: Digital signature
Bug#673347: nfs-common: idmapd crashes due to race condition
Package: nfs-common
Version: 1:1.2.2-4squeeze3
Severity: important
Tags: squeeze patch
Hit this on a relatively busy NFSv4 client having had a much more lightly
loaded client talking to the same server for several months without
issues.
rpc.idmapd crashes causing a failure to lookup username/group
information for files; less than ideal when that's home directories.
Some investigation found:
https://bugzilla.redhat.com/show_bug.cgi?id=684308
pointing to a race condition between doing an fcntl F_SETSIG and
F_NOTIFY. I've applied the patch from that bug report and been running
successfully for over a month (having previously had rpc.idmapd die
every couple of days). debdiff of what I'm using attached.
-- System Information:
Debian Release: 6.0.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nfs-common depends on:
ii adduser3.112+nmu2add and remove users and groups
ii initscripts2.88dsf-13.1+squeeze1 scripts for initializing and shutt
ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib
ii libcap21:2.19-3 support for getting/setting POSIX.
ii libcomerr2 1.41.12-4stable1 common error description library
ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification
ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - k
ii libgssglue10.1-4 mechanism-switch gssapi library
ii libk5crypto3 1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries - C
ii libkrb5-3 1.8.3+dfsg-4squeeze5 MIT Kerberos runtime libraries
ii libnfsidmap2 0.23-2An nfs idmapping library
ii librpcsecgss3 0.19-2allows secure rpc communication us
ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii netbase4.45 Basic TCP/IP networking system
ii portmap6.0.0-2 RPC port mapper
ii ucf3.0025+nmu1 Update Configuration File: preserv
nfs-common recommends no packages.
nfs-common suggests no packages.
-- no debconf information
diff -Nru nfs-utils-1.2.2/debian/changelog nfs-utils-1.2.2/debian/changelog
--- nfs-utils-1.2.2/debian/changelog 2011-12-30 09:59:58.0 -0800
+++ nfs-utils-1.2.2/debian/changelog 2012-05-17 16:19:02.0 -0700
@@ -1,3 +1,9 @@
+nfs-utils (1:1.2.2-4squeeze3) stable; urgency=high
+
+ * Fix rpc.idmapd dying.
+
+ -- Jonathan McDowell nood...@hp.com Mon, 16 Apr 2012 13:44:20 -0700
+
nfs-utils (1:1.2.2-4squeeze2) stable; urgency=high
* Fix CVE-2011-1749: Avoid leaving a corrupt mtab file (Closes: #629420)
diff -Nru nfs-utils-1.2.2/debian/patches/18-fix-idmapd-crash.patch nfs-utils-1.2.2/debian/patches/18-fix-idmapd-crash.patch
--- nfs-utils-1.2.2/debian/patches/18-fix-idmapd-crash.patch 1969-12-31 16:00:00.0 -0800
+++ nfs-utils-1.2.2/debian/patches/18-fix-idmapd-crash.patch 2012-05-17 16:18:31.0 -0700
@@ -0,0 +1,18 @@
+
+Fix issue with rpc.idmapd dying under load conditions due to a race condition
+in registering for signal notification.
+
+Taken from https://bugzilla.redhat.com/show_bug.cgi?id=684308
+
+--- nfs-utils-1.2.2/utils/idmapd/idmapd.c.orig 2010-02-18 04:35:00.0 -0800
nfs-utils-1.2.2/utils/idmapd/idmapd.c 2012-04-16 13:43:47.0 -0700
+@@ -766,8 +766,8 @@ nfsopen(struct idmap_client *ic)
+ } else {
+ event_set(ic-ic_event, ic-ic_fd, EV_READ, nfscb, ic);
+ event_add(ic-ic_event, NULL);
+- fcntl(ic-ic_dirfd, F_SETSIG, 0);
+ fcntl(ic-ic_dirfd, F_NOTIFY, 0);
++ fcntl(ic-ic_dirfd, F_SETSIG, 0);
+ if (verbose 0)
+ xlog_warn(Opened %s, ic-ic_path);
+ }
diff -Nru nfs-utils-1.2.2/debian/patches/series nfs-utils-1.2.2/debian/patches/series
--- nfs-utils-1.2.2/debian/patches/series 2011-12-30 09:57:46.0 -0800
+++ nfs-utils-1.2.2/debian/patches/series 2012-05-17 16:18:43.0 -0700
@@ -9,3 +9,4 @@
15-mountd-fix-path-comparison-for-v4-crossmnt.patch
16-negotiate-des-only.patch
17-fix-CVE-2011-1749.patch
+18-fix-idmapd-crash.patch
Bug#590653: Seeing this on recent Squeeze update
I'm seeing this on a machine recently upgraded to Squeeze. Seems to be due to vsftpd (see #601456). Upstream mainline removed this message in commit 2fdc1c8093255f9da877d7b9ce3f46c2098377dc. J. -- Revd. Jonathan McDowell, ULC | I don't tip. signature.asc Description: Digital signature
Bug#599771: linux-image-2.6.32-5-amd64: Please consider adding support for Atheros AR8151 ethernet
Package: linux-2.6 Version: 2.6.32-23 Severity: wishlist Please consider adding the patch at: http://kernel.org/pub/linux/kernel/people/mcgrof/ethernet/0001-add-AR8152-and-AR8152.patch to the 2.6.32 kernel. It enables support for the AR8151/AR8152 Atheros ethernet chipsets. Applying this patch to Debian 2.6.32 image allowed me to complete a networked Debian install on my Acer 1830T. (Support is already included in more recent upstream kernels.) -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Acer product_name: Aspire 1830T product_version: V1.11 chassis_vendor: Chassis Manufacturer chassis_version: Chassis Version bios_vendor: INSYDE bios_version: V1.11 board_vendor: Intel Corp. board_name: Base Board Product Name board_version: Base Board Version ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02) Subsystem: Acer Incorporated [ALI] Device [1025:040e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:040e] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 40 Region 0: Memory at d000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at c000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 3050 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) Subsystem: Acer Incorporated [ALI] Device [1025:040e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 10 Region 0: Memory at d4406100 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) (prog-if 20 [EHCI]) Subsystem: Acer Incorporated [ALI] Device [1025:040e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at d4405c00 (32-bit, non-prefetchable) [size=1K] Capabilities: access denied Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) Subsystem: Acer Incorporated [ALI] Device [1025:040e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 42 Region 0: Memory at d440 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) (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- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: d340-d43f Prefetchable memory behind bridge: d040-d13f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied 00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root
