[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Vivid) Status: Triaged => Invalid -- 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:

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Ming Lei, yes, on Mustang. We're using U-Boot. -- 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:

Re: [Bug 1440536] Re: Oops __d_lookup+0x88/0x194

On Tue, Oct 27, 2015 at 11:03 PM, Fathi Boudra wrote: > Ming Lei, > > yes, on Mustang. We're using U-Boot. OK, we found the issue is triggered during booting, and finally APM's fix on firmware can make the issue disappeared, but it isn't released yet. > > -- > You

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

I flashed 1.15.22 firmware and indeed it helped. I don't observe the oops anymore. -- 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

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

This is an known issue with FW build number 1.15.20 or below. This issue is resolved with FW build 1.15.22 or above. This FW is currently under testing and will be release when ready for Mustang board. -Loc -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Riku, Did you reproduce the issue with UEFI booting or U-boot booting? And it is on Mustang? Thanks, -- 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

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

This has also been reproduced on wilu 4.2.0-16-generic #19-Ubuntu -- 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

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

From dann's reports: 1) system1 Code: 1412 f9400273 b4000213 d1002274 (b9402280) 2) system2 Code: 1412 f9400273 b4000213 d1002274 (b9402280) And the upstem report in #15, Code: 1403 f9400273 b4000213 d1002274 (b9402282) The code snippet should be the following in __d_lookup():

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

BTW, looks it isn't related with specific filesystem, and from the recent triger, it happened when walking path inside proc filesystem: [24993.562923] Call trace: [24993.565357] [ffc00022a278] __d_lookup+0x88/0x194 [24993.570467] [ffc00022a3bc] d_lookup+0x38/0x64 [24993.575319]

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Looks there was similar report from upstream: http://marc.info/?l=linux-fsdevelm=142865378923064w=2 but still don't have resolution or further report. Also I tried to use fbench to create lots of files, list dirs concurently for reproducing the issue, but can't reproduce it yet. -- You

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Reopening as this has now been seen on 2 other systems. ** Changed in: linux (Ubuntu Vivid) Status: Invalid = Confirmed ** Changed in: linux (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

** Changed in: linux (Ubuntu) Status: Confirmed = Triaged ** Changed in: linux (Ubuntu Vivid) Status: Confirmed = Triaged -- 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:

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

I'm going to mark this as invalid for the following reasons: - I reinstalled the system and the issue persisted. - I was unable to reproduce on another, identically configured system. - After removing one of the two DIMMs, the system is no longer seeing the problem. This all points to a

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

https://bugzilla.kernel.org/show_bug.cgi?id=96641 ** Bug watch added: Linux Kernel Bug Tracker #96641 http://bugzilla.kernel.org/show_bug.cgi?id=96641 ** Changed in: linux (Ubuntu Vivid) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Tested w/ 4.0, still exists. -- 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:

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

** Changed in: linux (Ubuntu Vivid) Status: Confirmed = Triaged ** Changed in: linux Importance: Undecided = Unknown ** Changed in: linux Status: Incomplete = Unknown ** Changed in: linux Remote watch: None = Linux Kernel Bug Tracker #96641 -- You received this bug

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Thank you for taking the time to file a bug report on this issue. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Diagnosing further, I've found that this happens when accessing a certain file: dannf@mustang:~$ ls -l /usr/bin/qemu-system-aarch64 -rwxr-xr-x 1 root root 4998496 Mar 12 21:17 /usr/bin/qemu-system-aarch64 dannf@mustang:~$ ls -l /usr/lib/python2.7/six.pyc [

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

** Changed in: linux (Ubuntu) Importance: Undecided = Critical -- 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

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Please: 1. Report to https://bugzilla.kernel.org/. 2. Paste the new report URL here. 3. Set this bug status back to confirmed. Thank you. ** Tags added: kernel-net ** Tags added: kernel-bug-exists-upstream kernel-oops ** Also affects: linux Importance: Undecided Status: New **

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

** Also affects: linux (Ubuntu Vivid) Importance: Critical Status: Incomplete ** Changed in: linux (Ubuntu Vivid) Status: Incomplete = Triaged ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

@ Joseph Salisbury Could you explain your change? ** Changed in: linux (Ubuntu Vivid) Status: Triaged = Incomplete -- 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

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

Which are the visible consequences of this bug? When answered, please set this bug status back to confirmed. Thank you. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

It seems like a corruption issue. The machine is sometimes usable for short periods after this errors occurs, but is otherwise deadlocked. I did go back to 3.19.0-4.4, and the problem is persisting. I also tried building a kernel from Linus' git tree and the problem is still there. My guess is

[Bug 1440536] Re: Oops __d_lookup+0x88/0x194

From what version did you upgrade ? -- 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:

Re: [Bug 1440536] Re: Oops __d_lookup+0x88/0x194

On Mon, Apr 6, 2015 at 6:26 AM, Tim Gardner tim.gard...@canonical.com wrote: From what version did you upgrade ? It looks like 3.19.0-4.4. I'll downgrade to see if going back resolves the issue and, if so, try and bisect it down. -- You received this bug notification because you are a member