** Changed in: eilt
Status: Incomplete => 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/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications abou
This bug was fixed in the package linux-armadaxp - 3.2.0-1605.8
---
linux-armadaxp (3.2.0-1605.8) precise-proposed; urgency=low
* Release Tracking Bug
-LP: #1020888
[ Jani Monoses ]
* Fix warnings.
* Adapt to new sched_clock API
[ Ubuntu: 3.2.0-27.43 ]
* No change u
I have verified that this fix is in 3.2.0-1605 and that the "bad:
scheduling from the idle thread!" no longer shows up during a reboot.
ubuntu@n2:~$ uname -a
Linux n2 3.2.0-1605-armadaxp #8-Ubuntu SMP Sat Jul 7 22:36:46 UTC 2012 armv7l
armv7l armv7l GNU/Linux
--
You received this bug notifica
** Branch linked: lp:ubuntu/precise-proposed/linux-armadaxp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about
I commited this patch in the precise git repo, and is in the 3.2.0-1604.7
package that will go into precise-proposed as soon as the previous upload gets
promoted to updates.
I verified the deb built in the Canonical kernel team PPA and indeed it no
longer prints these messages on the screen and
@Seif, could you please provide an update as to what you would like to
see happen? Thank you.
** Changed in: linux-armadaxp (Ubuntu)
Status: In Progress => Incomplete
** Changed in: eilt
Status: In Progress => Incomplete
--
You received this bug notification because you are a mem
So the attached patch is not good for SRU and we should wait for a
better fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage n
Me, either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
https://bugs.launchpad.net/eilt/
@Ike, no updates from me. So I am assuming this patch will go in, I
believe there are others asking for it. What's the ETA for Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
Hi, any update?
** Tags added: ike-radar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
ht
@Seif, cool~
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
https://bugs.launchpad.net/eilt
sorry for the delay on this one.
we have done the same work on an earlier kernel, I'll work on porting, and
testing this patch your latest stable source.
Patch should be ready in the next couple of days.
Seif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Enabling this hotplug config provides the possibility to save more power (as
well as introducing advanced error
reporting and correction capabilities theoretically). Meanwhile, according to
kernel document, SMP support for suspend/resume is a work in progress. I would
suggest we enable this by d
Hi Seif,
Another possible reason is CONFIG_HOTPLUG_CPU is enabled and I checked
defconfig its also enabled.
config HOTPLUG_CPU
bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
depends on SMP && HOTPLUG && EXPERIMENTAL
help
Say Y here to experiment with turnin
** Description changed:
+ SRU Justification:
+
+ Impact: when reboot and console shows "bad: scheduling from the idle thread!"
+ Fix: Using the patch from Marvell solves this issue.
+ Testcase: With patched kernel, this issue is gone.
+
+
Build Version/Date: Linux armadaxp3 3.2.0-1600-armadax
** Changed in: linux-armadaxp (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-armadaxp (Ubuntu)
Assignee: Bryan Wu (cooloney) => Ike Panhc (ikepanhc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
update the patch with author's signed-off
** Patch added:
"0001-DSMP-fix-the-bad-scheduling-from-the-idle-thread-mes.patch"
https://bugs.launchpad.net/eilt/+bug/959604/+attachment/3140210/+files/0001-DSMP-fix-the-bad-scheduling-from-the-idle-thread-mes.patch
--
You received this bug notific
Aha, I saw you pasted a new log and misunderstood that. Thank you and
Seif a lot! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To ma
@Li, I tested your kernel with the patch and there were no messages in
the log so the patch fixed the problem it appears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: sc
@MMorana, I didn't see "bad: scheduling from the idle thread!" in the
new log you posted. Are you pasting comments about another bug of "MS
card could make kernel panic"? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
@Li, your patched kernel does not exhibit this problem:
...
[ 40.606710] md0: detected capacity change from 0 to 19994247168
udevd[222]: inotify_add_watch(6, /dev/dm-0, 10) failed: Invalid argument
done.
[ 44.238967] pool #0: pkt_size=1536, buf_size=1632 - 2048 of 2048 buffers
added
Ubuntu
Hi MMorana, please find the patched kernel at
https://chinstrap.canonical.com/~lli5/959604/linux-
image-3.2.0-1602-armadaxp_3.2.0-1602.5_armhf.deb. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
@MMorana, has Seif's patch fixed this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
Thank you, Seif. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Changed in: eilt
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
https://bugs.launchpad.
here u go guys.
this should fix it btw this issues was not in the original drop.
Seif
** Patch added: "fix the "bad: scheduling from the idle thread" error"
https://bugs.launchpad.net/eilt/+bug/959604/+attachment/3064618/+files/0001-DSMP-fix-the-bad-scheduling-from-the-idle-thread-mes.p
@Seif,
There's nothing special that's causing the problem, it just happens on
shutdown/reboot.
The kernel lives here: https://launchpad.net/ubuntu/+source/linux-
armadaxp/ and http://ports.ubuntu.com/ubuntu-ports/pool/main/l/linux-
armadaxp/.
Have you tried to recreate it?
--
You received this
hi guys,
would you also try helping me understand any special kernel configuration ?
have you guys compiled with anything special ?
from this thread seem that guys are not doing anything with the system after
prompt, is this the case ? any special setup ?
Seif
--
You received this bug noti
Thanks for the new log. It looks like a certain driver failed to clean
up itself and reschedule happened within its interrupt handler.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[pu
^ Linux armadaxp3 3.2.0-1602-armadaxp #5-Ubuntu SMP Thu Apr 5 13:27:03
UTC 2012 armv7l armv7l armv7l GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling fr
@Li Li, the problem appears during reboot (shutdown) and that log
contained the startup and the shutdown logs - here's another one in
startup-shutdown order for you:
** Attachment added: "armadaxp3a-lp959604.log"
https://bugs.launchpad.net/eilt/+bug/959604/+attachment/3024152/+files/armadaxp3
Thanks. I saw that. And it's really strange that this error
disappeared after the board reboot.
Could you paste a full log which shows (from boot-up) when the first error
message is printed? It's helpful for us to understand which device driver
is likely to cause this unexpected scheduling (within
Here's fresh log with Linux version 3.2.0-1602-armadaxp (buildd@nasl)
(gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #5-Ubuntu SMP Thu
Apr 5 13:27:03 UTC 2012 (Ubuntu 3.2.0-1602.5-armadaxp 3.2.14):
** Attachment added: "armadaxp-lp959604.log"
https://bugs.launchpad.net/eilt/+bug/959604/+a
However, I didn't see this "scheduling" error in the log on the board
(xx.xx.37.252). Good or bad luck... :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from
Well, I get it already. Thanks Ike and the remote access. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about
** Changed in: eilt
Assignee: Bryan Wu (cooloney) => Li Li (lli5)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notificat
Can anybody upload a full log from power-on. We need to understand from
which point this unexpected schedule is happening. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959604
Title:
[public] bad: scheduling from the idle thread!
To manage notifications about this bug go to:
https://bugs
** Also affects: linux-armadaxp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-armadaxp (Ubuntu)
Status: New => Confirmed
** Changed in: linux-armadaxp (Ubuntu)
Importance: Undecided => High
** Changed in: linux-armadaxp (Ubuntu)
Assignee: (unassigned) =
40 matches
Mail list logo
