Bug 216420
Summary: | Unable to handle kernel NULL pointer dereference at virtual address 00000008 | ||
---|---|---|---|
Product: | Drivers | Reporter: | frc.gabriel |
Component: | MMC/SD | Assignee: | drivers_mmc-sd |
Status: | NEW --- | ||
Severity: | normal | CC: | regressions |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 6.0.0-rc2 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
full dmesg output
good dmesg 5.19 6.0.0-rc3-next-20220901-dmesg.txt good-6.0-rc2-plus-Zhen-Lei-patch-plus-Isaac-J-Manjarres-patch.txt 6.0.0-rc4-dmesg.txt |
(In reply to frc.gabriel from comment #0) > my device is currently crashing during boot with kernel 6.0.0-rc2. I also > tried next-20220826 and the outcome is the same. Just to understand this properly: I assume 5.19.y worked fine I suppose (and this is thus a regression)? Created attachment 301689 [details]
good dmesg 5.19
Hi, Yes, your assumption is correct! I quickly checked and it works ok with v5.19. The dmesg log for v5.19 can be found at "good-dmesg-5.19.txt" file. Thank you! Gabriel Francisco Created attachment 301738 [details]
6.0.0-rc3-next-20220901-dmesg.txt
Hi,
with 6.0.0-rc3-next-20220901 it reaches the initramfs prompt and ls /dev shows no mmcblk device.
Sharing in case it helps,
Thank you
You might want to test this patch and add your "Tested-by" to speed things up: https://lore.kernel.org/lkml/20220818172852.3548-1-isaacmanjarres@google.com/ (that's the one mentioned in https://lore.kernel.org/lkml/CAGETcx9YvpYFf1mxHi1iA--sE5G2MZLS1x8vHnTu6Wj30ScaOA@mail.gmail.com/ which you iirc are CCed on) Created attachment 301739 [details]
good-6.0-rc2-plus-Zhen-Lei-patch-plus-Isaac-J-Manjarres-patch.txt
Done, I added the Tested-by in that patch (but it only works when combining with Zhen-Lei's patch)
I'm sharing the dmesg in case might be helpful at "good-6.0-rc2-plus-Zhen-Lei-patch-plus-Isaac-J-Manjarres-patch.txt" file.
My device boots successfully and I compared (one of) the addresses from
[ 21.017179] amba fc33c000.etm: deferred probe pending
[ 21.017327] amba fc33d000.etm: deferred probe pending
[ 21.021356] amba fc33e000.etm: deferred probe pending
[ 21.026352] amba fc33f000.etm: deferred probe pending
[ 21.031414] amba fc345000.funnel: deferred probe pending
[ 21.036419] amba fc307000.etf: deferred probe pending
[ 21.041829] amba fc318000.tpiu: deferred probe pending
[ 21.046748] amba fc31a000.funnel: deferred probe pending
[ 21.051819] amba fc31b000.funnel: deferred probe pending
[ 21.057256] amba fc31c000.replicator: deferred probe pending
[ 21.062585] amba fc322000.etr: deferred probe pending
with the "qcom-msm8974.dtsi" file and looks like I have a amba device (never heard about it) :D
Thank you!
Gabriel Francisco
Created attachment 301756 [details]
6.0.0-rc4-dmesg.txt
|
Created attachment 301682 [details] full dmesg output Hi, good morning! my device is currently crashing during boot with kernel 6.0.0-rc2. I also tried next-20220826 and the outcome is the same. The full dmesg log can be found attached on crash-boot.txt file. Thank you and have a good day, Gabriel Francisco