>From dann's reports:
1) system1
Code: 14000012 f9400273 b4000213 d1002274 (b9402280)
2) system2
Code: 14000012 f9400273 b4000213 d1002274 (b9402280)
And the upstem report in #15,
Code: 14000003 f9400273 b4000213 d1002274 (b9402282)
The code snippet should be the following in __d_lookup(): fs/dcache.c
ffffffc0001aae68: 14000003 b ffffffc0001aae74
<__d_lookup+0x84>
*
* See Documentation/filesystems/path-lookup.txt for more details.
*/
rcu_read_lock();
hlist_bl_for_each_entry_rcu(dentry, node, b, d_hash) {
ffffffc0001aae6c: f9400273 ldr x19, [x19]
ffffffc0001aae70: b40001f3 cbz x19, ffffffc0001aaeac
<__d_lookup+0xbc>
if (dentry->d_name.hash != hash)
ffffffc0001aae74: d1002274 sub x20, x19, #0x8
ffffffc0001aae78: b9402282 ldr w2, [x20,#32]
#faulted instruction
Then the problem should be caused by bad pointer of dcache.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440536
Title:
Oops __d_lookup+0x88/0x194
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1440536/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
