From: Adam Williamson <awilliam@redhat.com>
To: davej@codemonkey.org.uk
Cc: hch@lst.de, linux-kernel@vger.kernel.org, labbott@redhat.com,
jforbes@redhat.com
Subject: Re: 5.3-rc1 panic in dma_direct_max_mapping_size
Date: Mon, 22 Jul 2019 11:08:53 -0700 [thread overview]
Message-ID: <ea24edb0d81d8fd93ef3805699e4f4da264b093a.camel@redhat.com> (raw)
In-Reply-To: <20190722163759.GA28686@codemonkey.org.uk>
Seeing something similar but not identical here. I updated a Fedora
Rawhide virt-manager/libvirt VM (installed with the previous Fedora
kernel build) to the Fedora rc1 kernel build, and it doesn't boot any
more, with this trace:
[ 3.018311] scsi host8: Virtio SCSI HBA
[ 3.019234] BUG: kernel NULL pointer dereference, address: 0000000000000000
[ 3.020321] #PF: supervisor read access in kernel mode
[ 3.021114] #PF: error_code(0x0000) - not-present page
[ 3.021898] PGD 0 P4D 0
[ 3.022299] Oops: 0000 [#1] SMP PTI
[ 3.022836] CPU: 1 PID: 164 Comm: kworker/u4:5 Not tainted 5.3.0-0.rc1.git0.1.fc31.x86_64 #1
[ 3.024120] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190617_165236-buildvm-18.phx2.fedoraproject.org-1.fc31 04/01/2014
[ 3.025924] Workqueue: events_unbound async_run_entry_fn
[ 3.026727] RIP: 0010:dma_direct_max_mapping_size+0x2b/0x64
[ 3.027573] Code: 66 66 66 90 55 48 89 fd 53 e8 81 13 00 00 84 c0 75 0a 48 c7 c0 ff ff ff ff 5b 5d c3 48 8b 85 28 02 00 00 48 8b 9d 38 02 00 00 <48> 8b 00 48 85 c0 74 0c 48 85 db 74 27 48 39 c3 48 0f 47 d8 48 89
[ 3.030444] RSP: 0000:ffffb60d001ebc20 EFLAGS: 00010202
[ 3.031234] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 3.032269] RDX: ffff8ef87b3dbe80 RSI: 000000000000007e RDI: ffff8ef87535c810
[ 3.033333] RBP: ffff8ef87535c810 R08: ffff8ef87bb2e0e0 R09: ffff8ef87b003340
[ 3.034403] R10: 000000000002f3a0 R11: 0000000000000011 R12: ffff8ef87535c810
[ 3.035469] R13: 000000000000ffff R14: ffff8ef87371c828 R15: 0000000000000000
[ 3.036540] FS: 0000000000000000(0000) GS:ffff8ef87bb00000(0000) knlGS:0000000000000000
[ 3.037748] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3.038612] CR2: 0000000000000000 CR3: 0000000134b24006 CR4: 0000000000060ee0
[ 3.039689] Call Trace:
[ 3.040073] __scsi_init_queue+0x75/0x140
[ 3.040685] scsi_mq_alloc_queue+0x34/0x50
[ 3.041307] scsi_alloc_sdev+0x1f9/0x2c0
[ 3.041902] scsi_probe_and_add_lun+0x9a2/0xd70
[ 3.042589] ? _cond_resched+0x15/0x30
[ 3.043148] ? mutex_lock+0xe/0x30
[ 3.043669] __scsi_scan_target+0xec/0x5c0
[ 3.044299] ? __switch_to_asm+0x34/0x70
[ 3.044896] ? __switch_to_asm+0x40/0x70
[ 3.045495] ? __switch_to_asm+0x34/0x70
[ 3.046092] ? __switch_to_asm+0x34/0x70
[ 3.046692] ? __switch_to_asm+0x40/0x70
[ 3.047292] scsi_scan_channel+0x57/0x90
[ 3.047890] scsi_scan_host_selected+0xdb/0x110
[ 3.048581] do_scan_async+0x18/0x150
[ 3.049140] async_run_entry_fn+0x39/0x160
[ 3.049765] process_one_work+0x19d/0x340
[ 3.050377] worker_thread+0x50/0x3b0
[ 3.050933] kthread+0xfb/0x130
[ 3.051418] ? process_one_work+0x340/0x340
[ 3.052052] ? kthread_park+0x80/0x80
[ 3.052613] ret_from_fork+0x35/0x40
[ 3.053157] Modules linked in: virtio_net ata_generic net_failover failover serio_raw virtio_scsi pata_acpi qemu_fw_cfg fuse
[ 3.054832] CR2: 0000000000000000
[ 3.055342] ---[ end trace c6389143c53d3973 ]---
Happens whether the disk image is attached to the VM as virtio or IDE.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
prev parent reply other threads:[~2019-07-22 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 16:37 Dave Jones
2019-07-22 18:08 ` Adam Williamson [this message]
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=ea24edb0d81d8fd93ef3805699e4f4da264b093a.camel@redhat.com \
--to=awilliam@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=hch@lst.de \
--cc=jforbes@redhat.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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®