From: Wim Osterholt <wim@djo.tudelft.nl>
To: linux-kernel@vger.kernel.org
Cc: Wim Osterholt <wim@djo.tudelft.nl>,
linux-acpi@vger.kernel.org, perex@perex.cz
Subject: kernel-4.7 bug in Intel sound and/or ACPI
Date: Mon, 20 Jun 2016 02:35:30 +0200 [thread overview]
Message-ID: <20160620003530.GA19571@djo.tudelft.nl> (raw)
L.S.
up to vanilla kernel-4.6.2 sound was working fine.
Switching to kernel-4.7.0-rc3 made sound disappear. No /dev/mixer etc.
There appears to be a bug in the Intel sound driver and/or ACPI driver.
Dmesg shows interesting lines like:
[ 11.498592] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7
[ 11.498605] PCI: setting IRQ 7 as level-triggered
[ 11.543903] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
[ 12.757735] genirq: Flags mismatch irq 7. 00000080 (snd_intel8x0m) vs. 00000000 (parport0)
[ 12.757751] snd_intel8x0m 0000:00:1f.6: unable to grab IRQ 7
[ 12.757875] snd_intel8x0m: probe of 0000:00:1f.6 failed with error -16
[ 12.900171] genirq: Flags mismatch irq 7. 00000080 (snd_intel8x0) vs. 00000000 (parport0)
[ 12.900189] snd_intel8x0 0000:00:1f.5: unable to grab IRQ 7
[ 12.900389] snd_intel8x0: probe of 0000:00:1f.5 failed with error -16
[ 12.922554] genirq: Flags mismatch irq 7. 00000080 (ipw2200) vs. 00000000 (parport0)
[ 12.922559] ipw2200: Error allocating IRQ 7
If I boot kernel-4.7.0-rc3 with acpi=off then sound is back!
If you need the full dmesg outputs then please get them here:
http://webserver.djo.tudelft.nl/dmesg460+ACPI
http://webserver.djo.tudelft.nl/dmesg473+ACPI
http://webserver.djo.tudelft.nl/dmesg473noACPI
(with excuses for the silly hostname which is out of our control)
Regards, Wim.
----- wim@djo.tudelft.nl -----
next reply other threads:[~2016-06-20 0:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 0:35 Wim Osterholt [this message]
2016-06-20 1:02 ` Rafael J. Wysocki
2016-06-20 21:25 ` Bjorn Helgaas
2016-06-20 22:25 ` Sinan Kaya
2016-06-21 12:47 ` Wim Osterholt
2016-06-21 13:40 ` Sinan Kaya
2016-06-21 22:13 ` Wim Osterholt
2016-06-23 3:54 ` okaya
2016-06-23 14:12 ` Wim Osterholt
2016-06-23 14:55 ` Sinan Kaya
2016-06-23 15:45 ` Sinan Kaya
2016-06-23 16:21 ` Bjorn Helgaas
2016-06-23 17:05 ` Alex Williamson
2016-06-23 23:25 ` Wim Osterholt
2016-06-24 6:09 ` Sinan Kaya
2016-06-25 1:39 ` Wim Osterholt
2016-06-25 8:51 ` okaya
2016-06-27 6:27 ` Wim Osterholt
2016-06-27 8:22 ` okaya
2016-06-27 13:04 ` Wim Osterholt
2016-06-27 21:05 ` okaya
2016-06-29 8:34 ` Sinan Kaya
2016-06-30 2:30 ` Wim Osterholt
2016-06-30 9:43 ` okaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160620003530.GA19571@djo.tudelft.nl \
--to=wim@djo.tudelft.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®