The reverts are applied for some time now on Natty, leaving as fix
released.
** Changed in: linux (Ubuntu Natty)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-2.6 (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications
same thing in ubuntu oernic beta, kernel 3.0.0-12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications about this bug go to:
** Changed in: linux-2.6 (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications about
** Bug watch added: Debian Bug tracker #634681
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634681
** Also affects: linux-2.6 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634681
Importance: Unknown
Status: Unknown
--
You received this bug notification
r6 panics
** Attachment added: r6 panic picture
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793796/+attachment/2208740/+files/r6panic.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@setubens: that's good news, thanks for your testing so far. While going
to report this upstream (plus the fixes), I found another bug for the
same problem (https://bugzilla.kernel.org/show_bug.cgi?id=38842). There
is a new patch for the problem available, I would like you to test it
and validate
r5 does not panic after 3 trials; currently running the kernel :]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications about
Hi steubens, any success in testing kernel from comment #43?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications about this bug
I just saw this bug last night after upgrading to the 2.6.38-10.46
kernel on Natty. For me it *appears* to manifest as a panic talking to
my DVD-ROM, after I had done some I/O to a USB device and ejected it (I
used the nautilus safely remove device on the USB stick). The panic
occurred several
@mcelrath: it seems you have a different bug, may be related to libata.
If you can get the oops, please open a new bug report with 'ubuntu-bug
-p linux' from a terminal on the affected machine, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@steubens: ok, by the trace r4 kernel really fixed the problem of
previous trace (thanks for the pictures, they were valuable to check),
but you hit another crash. I made another additional fix, please test
the kernel I uploaded at
http://people.canonical.com/~herton/lp793796/r5/
--
You received
r3 and r4 panic
** Attachment added: picture of r3 panic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793796/+attachment/2193229/+files/r3panic.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: picture of r4 panic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793796/+attachment/2193230/+files/r4panic.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
@steubens: ok, scsi plus block fix from comment #36 should be needed
(without one or another you can hit problems at different locations),
but on the trace it seems you're not reaching the conditions that they
fix. At least I think you need one more fix, I built a kernel with the
probable fix, but
Sorry about that, I picked the wrong fix to be tested.
@steubens: can you try the kernel I put at
http://people.canonical.com/~herton/lp793796/r2/ ? I expect it to fix
the issue, please report the results here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
ok, r2 panics
i'm thinking that the different stacks in one of the panics (that i
noticed) might mean there are 2 problems with the same steps to
reproduce, if you can give me instructions on how to run the series
again i can bang it out here and mind the different panic signatures
only thing
Ok, should be last step now:
# bad: [39a0cfed63b656486fb2feee063aa033816a90e0] put stricter guards on queue
dead checks
git bisect bad 39a0cfed63b656486fb2feee063aa033816a90e0
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[048e21a4c8f39ccbbbf6b3f7cb65eff1fe209f8b] scsi_dh:
b8 does not panic
the last 3 or so revs that haven't panicked seemed to have markedly
better io throughput to the drive i am using, compared to the ones that
panic; but b8 also gave me an io error on the junk file i've been using
on the drive; i'll inspect it and see if it wasn't just the drive
Ok, bisect found this commit as the faulty one:
put stricter guards on queue dead checks
2.6.38.8 has a bug fix for this specific commit, but as you tested on
comment #10 it seems you still have the problem even with 2.6.38.8, so
another fix probably is required. Just to confirm, I'll cherry-pick
ok, i also checked that drive and it was fine; but the io error was
probably a fluke
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage
To clear up the situation here, this is what we have so far (note,
commit hashes are from the Ubuntu natty git kernel tree):
Linux 2.6.38-10.44, which is based on 2.6.38.7, has the regression
reported here. Bisecting it, we found that regression is related to
patch
commit
@steubens: can you try the kernel at
http://people.canonical.com/~herton/lp793796/r1/ ?
Report here if you still get the crash with it. If you get the crash,
please try to get the oops info/picture of the screen and post here.
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oneiric)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Natty)
Status: New = In Progress
** Changed in: linux (Ubuntu Natty)
Assignee:
r1 still panics, that's a bit disheartening
** Attachment added: r1 panic picture
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793796/+attachment/2184144/+files/DSCN0969.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
At this point I suspect one of these two changes caused the regression, as I
suspected initially:
scsi_dh: fix reference counting in scsi_dh_activate error path
put stricter guards on queue dead checks
although 2.6.38.8 has a fix for the second one, testing on comment #10
showed no good results
ok b6 panics; but i noticed the stack was different this time, it never
makes the elv_ call it's all in scsi stuff
i wasn't paying much attention to the actual output with the other ones,
when i have access to a notcrap camera again i'll see if they're
different as well
--
You received this bug
Thanks for testing, next step:
# bad: [fbe388be5c48ecfef898567858e5d8f8ab2396b9] ALSA: HDA: Fix automute for
Gateway NV79
git bisect bad fbe388be5c48ecfef898567858e5d8f8ab2396b9
Bisecting: 0 revisions left to test after this (roughly 1 step)
[39a0cfed63b656486fb2feee063aa033816a90e0] put
b7 panics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications about this bug go to:
b5 does not panic, sorry for the delay
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To manage notifications about this bug go to:
# bad: [a02e3b98ac916d3d544c55f644c566aae2ad1918] i2c-parport: Fix adapter list
handling
git bisect bad a02e3b98ac916d3d544c55f644c566aae2ad1918
Bisecting: 10 revisions left to test after this (roughly 4 steps)
[e1594df7d3d13d12036bd5fb40d13037f9f635dd] iwlegacy: fix tx_power initialization
Yes, the modules are still loaded. Look at ProcModules.txt above,
gathered from the system. There are vm* modules loaded, which are from
vmware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
yea but i made the report from -9 ... but i'll make sure they're not
loaded when i test b4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
To
jeeze, launchpad is not pleasant over gprs; tried b4, it does not panic.
i also verified that no vmware modules were loading on -10, as i've
never started it there, kernel panicked quite quickly after i installed
it started regular routine stuff :]
--
You received this bug notification because
ok, thanks for the update. That's valuable information. The best thing
we can do is keep bisecting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
Progressing forward with the bisect:
# good: [e1594df7d3d13d12036bd5fb40d13037f9f635dd] iwlegacy: fix tx_power
initialization
git bisect good e1594df7d3d13d12036bd5fb40d13037f9f635dd
Bisecting: 5 revisions left to test after this (roughly 3 steps)
[a29ae2d0b5e069c4226b69a70d70198d809a6489]
It looks from the logs like this machine is running as vmware host.
Could you please see whether the problem still happens when you are not
running vmware?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
b3 panics, sorry for the delay, it's my daily driver
Steve: i've never launched it on -10 so no modules are loaded, some
daemons start though, could that still matter?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ok b2 works, does not panic, tried several times where it would only
take one on the bad versions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
Thanks for the testing. Marked as good:
# good: [e350f7cf12149a8c79095268e1b6da14901fa754] m68k/mm: Set all online
nodes in N_NORMAL_MEMORY
git bisect good e350f7cf12149a8c79095268e1b6da14901fa754
Bisecting: 22 revisions left to test after this (roughly 5 steps)
@steubens: please try next step
@steubens: ok, please try the next bisect step:
http://people.canonical.com/~herton/lp793796/b2/
for this, git says:
Bisecting: 44 revisions left to test after this (roughly 6 steps)
current bisect log:
git bisect start
# good: [1463cecc1d1b35fb25ae11051184cc19f0254b32] UBUNTU:
@steubens: ok, lets try to bisect which change broke in your case, can
you try the first kernel at
http://people.canonical.com/~herton/lp793796/ and tell me if it works or
gives same issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
ok i will asap, how many steps does it say is left and where did you
start/end the bisect; i can probably see about running the entire series
locally (also going to see if it affects my netbook :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
that kernel you prepared also panics; i tried automating the tests with
udisks --unmount and --eject, but it wouldn't do it, so if you need to
reproduce the test be sure to use safely remove drive from nautilus; i
don't know what the distinction is but that's what i've been using
--
You received
i tried to reproduce on my netbook and it wasn't doing it; there's not a
lot of ram in it and it isn't fast enough to really stack up a lot of
i/o though; probably meaningless ;]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The scheduling while atomic should be happening in this case because a
panic happens in atomic context, and the panic calls its notifier list
which contains drm_fb_helper_panic (the switch to console on modesetting
framebuffer).
drm_fb_helper_panic calls
@steubens, any success running the tests I requested on comment #3? I
tried reproduce your problem but was unable to, so it would be
great/necessary if you could do the tests, especially if you reproduce
easily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
i'll see to running them asap, as to the other comments; as far as i
understand the panic from the mode switch is scheduling while atomic,
but the error that caused the mode switch (to display the other panic)
is from the elv_ / block layer further down the stack
--
You received this bug
ok, both the .7 and the .8 kernel do panic; just as easily
i'm using a 1tb bus powered usb drive and i wait for at least 20 seconds
while cat writes to the junk file, it does it with my other usb drive
as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hmm, there may be a plethora of rcu bugs in individual drivers as well
as global ones?
http://www.spinics.net/lists/linux-wireless/msg69597.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Seems like the issue lies on something related to block/scsi changes.
@steubens, can you do the following, so we can understand better and
isolate the problem:
- Install amd64 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.38.7-natty/ , and confirm
the issue still happens with
Either there are various device drivers all over with related bugs or
this is a bug in common code they all use.
Look at the JPG attachment of the panic: scheduling while atomic
during __do_softirq
LP: #790054 during bcmwl wifi driver __do_softirq BUG: scheduling while
atomic goes off.
Head of thread on recent RCU updates:
http://lkml.org/lkml/2011/6/8/321
from that:
4. Restore checks for blocking within RCU read-side critical
sections under CONFIG_PROVE_RCU.
More commentary about that here:
https://lkml.org/lkml/2011/6/4/115
http://lkml.org/lkml/2011/6/8/354
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Note that a picture of the panic is attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
--
ubuntu-bugs mailing list
** Attachment added: picture of the panic
https://bugs.launchpad.net/bugs/793796/+attachment/2157938/+files/DSCN0955.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793796
Title:
2.6.38-10 panic after ejecting drive
--
ubuntu-bugs mailing list
57 matches
Mail list logo
