[Revert "ppdev] 1701f68040: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080 (goldfish_pdev_bus)
4:28 p.m.
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 1701f680407c6cc05121566cef5293d33881fe71
Author: Linus Torvalds <torvalds(a)linux-foundation.org>
AuthorDate: Fri Mar 25 09:02:13 2016 -0700
Commit: Linus Torvalds <torvalds(a)linux-foundation.org>
CommitDate: Fri Mar 25 09:02:13 2016 -0700
Revert "ppdev: use new parport device model"
This reverts commit e7223f18603374d235d8bb0398532323e5f318b9.
It causes problems when a ppdev tries to register before the parport
driver has been registered with the device model. That will trigger the
BUG_ON(!drv->bus->p);
at drivers/base/driver.c:153. The call chain is
kernel_init ->
kernel_init_freeable ->
do_one_initcall ->
ppdev_init ->
__parport_register_driver ->
driver_register *BOOM*
Reported-by: kernel test robot <fengguang.wu(a)intel.com>
Reported-by: Ross Zwisler <zwisler(a)gmail.com>
Reported-by: Petr Mladek <pmladek(a)suse.com>
Cc: Sudip Mukherjee <sudipm.mukherjee(a)gmail.com>
Cc: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org>
+------------------------------------------------------------+------------+------------+-------------+
| | 3b3b3bd977 | 1701f68040 |
v4.6_052910 |
+------------------------------------------------------------+------------+------------+-------------+
| boot_successes | 0 | 0 | 0
|
| boot_failures | 92 | 26 |
13 |
| kernel_BUG_at_drivers/base/driver.c | 92 | |
|
| invalid_opcode:#[##] | 92 | |
|
| invalid_opcode:#[##]PREEMPT_PREEMPT_SMP_SMP | 92 | |
|
| EIP_is_at_driver_register | 92 | |
|
| Kernel_panic-not_syncing:Fatal_exception | 92 | |
|
| backtrace:__parport_register_driver | 92 | |
|
| backtrace:ppdev_init | 92 | |
|
| backtrace:kernel_init_freeable | 92 | |
|
| genirq:Flags_mismatch_irq##(serial)vs.#(goldfish_pdev_bus) | 0 | 26 |
13 |
| WARNING:at_arch/x86/mm/dump_pagetables.c:#note_page | 0 | 24 |
13 |
| backtrace:mark_rodata_ro | 0 | 24 |
13 |
| genirq:Flags_mismatch_irq | 0 | 1 | 2
|
| genirq:Flags_mismatch_irq##(serial)vs | 0 | 0 | 2
|
+------------------------------------------------------------+------------+------------+-------------+
[ 14.172557] Bluetooth: Starting self testing
[ 14.173765] Bluetooth: Finished self testing
[ 14.173765] Bluetooth: Finished self testing
[ 14.180471] genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080
(goldfish_pdev_bus)
[ 14.180471] genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000080
(goldfish_pdev_bus)
[ 14.184737] Freeing unused kernel memory: 2312K (8239a000 - 825dc000)
[ 14.184737] Freeing unused kernel memory: 2312K (8239a000 - 825dc000)
[ 14.186874] Write protecting the kernel text: 12348k
git bisect start v4.6 v4.5 --
git bisect bad 7b367f5dba5c5162a7308e85d3fc9170b0cb3e5f # 14:23 0- 22 Merge
branch 'core-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
git bisect good 46e595a17dcf11404f713845ecb5b06b92a94e43 # 14:31 22+ 24 Merge
tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect good 70c5eb84738cba88e08526fa14e06418cb2bd473 # 14:36 22+ 23 Merge
branch 'misc' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild
git bisect bad 8b8c877febd2610050758f1b7b97050a7d2dc794 # 17:12 0- 24 Merge
tag 'hwmon-for-linus-v4.6-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
git bisect bad c155c7492c9ab81f3d358a10eb4f29376ae53d85 # 19:50 0- 29 Merge
branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
git bisect good 8407ef4685895759f111190d091394ef974f52fb # 22:27 22+ 48 Merge
tag 'rtc-4.6-2' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux
git bisect good f98c2135f8e73f1cfba640dfb80beb0dad75f278 # 22:37 22+ 26 Merge
branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect good 3b3b3bd97788e1f574c71f865d8465b00a6b8708 # 22:44 22+ 26 Merge
tag 'firewire-update2' of
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394
git bisect bad 1701f680407c6cc05121566cef5293d33881fe71 # 22:51 0- 18 Revert
"ppdev: use new parport device model"
# first bad commit: [1701f680407c6cc05121566cef5293d33881fe71] Revert "ppdev: use new
parport device model"
git bisect good 3b3b3bd97788e1f574c71f865d8465b00a6b8708 # 22:53 66+ 92 Merge
tag 'firewire-update2' of
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394
# extra tests with CONFIG_DEBUG_INFO_REDUCED
git bisect bad 1701f680407c6cc05121566cef5293d33881fe71 # 22:58 0- 13 Revert
"ppdev: use new parport device model"
# extra tests on HEAD of linux-devel/devel-hourly-2016052910
git bisect bad cab701ace412fb3a265289932d84b4d0496608ef # 22:58 0- 13 0day
head guard for 'devel-hourly-2016052910'
# extra tests on tree/branch linus/master
# extra tests with first bad commit reverted
# extra tests on tree/branch linus/master
# extra tests on tree/branch linux-next/master
This script may reproduce the error.
----------------------------------------------------------------------------
#!/bin/bash
kernel=$1
initrd=quantal-core-i386.cgz
wget --no-clobber
https://github.com/fengguang/reproduce-kernel-bug/raw/master/initrd/$initrd
kvm=(
qemu-system-x86_64
-enable-kvm
-cpu kvm64
-kernel $kernel
-initrd $initrd
-m 300
-smp 2
-device e1000,netdev=net0
-netdev user,id=net0
-boot order=nc
-no-reboot
-watchdog i6300esb
-rtc base=localtime
-serial stdio
-display none
-monitor null
)
append=(
hung_task_panic=1
earlyprintk=ttyS0,115200
systemd.log_level=err
debug
apic=debug
sysrq_always_enabled
rcupdate.rcu_cpu_stall_timeout=100
panic=-1
softlockup_panic=1
nmi_watchdog=panic
oops=panic
load_ramdisk=2
prompt_ramdisk=0
console=ttyS0,115200
console=tty0
vga=normal
root=/dev/ram0
rw
drbd.minor_count=8
)
"${kvm[@]}" --append "${append[*]}"
----------------------------------------------------------------------------
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/lkp Intel Corporation
5:25 p.m.
On Sun, May 29, 2016 at 8:28 AM, kernel test robot
<fengguang.wu(a)intel.com> wrote:
0day kernel testing robot got the below dmesg and the first bad commit is
This bisection seems unlikely.
I *think* what is going on is that the previous kernels ended up with
boot failures:
+------------------------------------------------------------+------------+------------+-------------+
| | 3b3b3bd977 | 1701f68040 |
v4.6_052910 |
+------------------------------------------------------------+------------+------------+-------------+
| kernel_BUG_at_drivers/base/driver.c | 92 | |
|
and then when that went away (thanks to the commit you bisected to),
the "genirq: Flags mismatch" warning showed up because it now got past
that original bug.
I'm not sure what the fix to the 0day bisection should be. Maybe add
some test that the last "good" kernel actually booted?
Linus
8:23 p.m.
On Sun, May 29, 2016 at 09:25:28AM -0700, Linus Torvalds wrote:
On Sun, May 29, 2016 at 8:28 AM, kernel test robot
<fengguang.wu(a)intel.com> wrote:
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
This bisection seems unlikely.
I *think* what is going on is that the previous kernels ended up with
boot failures:
>
+------------------------------------------------------------+------------+------------+-------------+
> | | 3b3b3bd977 |
1701f68040 | v4.6_052910 |
>
+------------------------------------------------------------+------------+------------+-------------+
> | kernel_BUG_at_drivers/base/driver.c | 92 |
| |
and then when that went away (thanks to the commit you bisected to),
the "genirq: Flags mismatch" warning showed up because it now got past
that original bug.
That's right. It's a bug fix that discloses a less serious warning.
I'm not sure what the fix to the 0day bisection should be. Maybe
add
some test that the last "good" kernel actually booted?
Yes, we do have tests on whether the parent boots fine or has more
serious boot errors, however they are wrongly bypassed when we
recently try to add a new test to report out errors which look
relevant to the code change.
I'll fix it up, sorry for the noise!
Boot tests are pretty noisy and often a commit and its parent commit
both have error/warnings. A better long term solution would be to
compare their time stamps to get the clue whether it's a bug fix that
makes the kernel live longer to produce another warning.
Thanks,
Fengguang
11:11 a.m.
On Sun, 29 May 2016 23:28:41 +0800
kernel test robot <fengguang.wu(a)intel.com> wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad
commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
No.. it just happens to look different. It's an ancient ancient clash
between Goldfish and standard PC over IRQ4. Unfortunately Goldfish
doesn't provide a sane detection mechanism.
Alan
11:51 a.m.
Hi Alan,
On Tue, May 31, 2016 at 11:11:55AM +0100, Alan wrote:
On Sun, 29 May 2016 23:28:41 +0800
kernel test robot <fengguang.wu(a)intel.com> wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad
> commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
No.. it just happens to look different. It's an ancient ancient clash
between Goldfish and standard PC over IRQ4. Unfortunately Goldfish
doesn't provide a sane detection mechanism.
Got it, I'll blacklist this error, thank you for the info!
Thanks,
Fengguang
2271
days inactive
2273
days old
4 comments
4 participants
participants (4)
-
Alan -
Fengguang Wu -
kernel test robot
-
Linus Torvalds