Without CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3474480 2009-05-07 15:39 arch/x86/boot/bzImage
With CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3592560 2009-05-07 15:26 arch/x86/boot/bzImage
It take us at leas
How else do you propose that a user track down hard to reproduce kernel
panics? If there's a better, more preferred method I'm all ears. I've
been dealing with sporadic kernel panics (hard lock with flashing caps
lock) since just after upgrading to 8.10. Trying to track down the root
cause is wh
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
please add ftrace to default configuration
https://bug
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
please add ftrace to default configuration
https://bugs.launchpad.net/bugs/355431
You received this bug notification because you are
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24824733/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24824734/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24824735/Dependencies.txt
** A
Forgot to mention the specific tracing that was missing. The existing
kernels to provide ftrace capability but only some of the tracing
options, specifically:
$ cat /sys/kernel/debug/tracing/available_tracers
open sched_switch nop
I'm not sure that any of these would help shed light on hard sys
Hi Jamin,
Indeed this does not appear to be enabled. The only issue is the kernel
is currently frozen for Jaunty's final release. This may have to wait
and be considered for a Stable Release Update but I'll leave that for
the kernel team to decide. Thanks.
ogasaw...@yoji:~/ubuntu-jaunty/debian
Hi Jamin,
We value your suggestion, and we appreciate your effort on open source
software and Ubuntu. I am thinking about your words and try to have
balance with debug and cost.
Therefore, I make AMD64 and i386 Jaunty kernel images with generic
config and turning on CONFIG_FUNCTION_TRACER. If it
Hi Jamin,
We value your suggestion, and we appreciate your effort on open source
software and Ubuntu. I am thinking about your words and try to have
balance with debug and cost.
Therefore, I make AMD64 and i386 Jaunty kernel images with generic
config and turning on CONFIG_FUNCTION_TRACER. If it
Without CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3474480 2009-05-07 15:39 arch/x86/boot/bzImage
With CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3592560 2009-05-07 15:26 arch/x86/boot/bzImage
It take us at leas
How else do you propose that a user track down hard to reproduce kernel
panics? If there's a better, more preferred method I'm all ears. I've
been dealing with sporadic kernel panics (hard lock with flashing caps
lock) since just after upgrading to 8.10. Trying to track down the root
cause is wh
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
please add ftrace to default configuration
https://bug
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
please add ftrace to default configuration
https://bugs.launchpad.net/bugs/355431
You received this bug notification because you are
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24824733/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24824734/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24824735/Dependencies.txt
** A
Forgot to mention the specific tracing that was missing. The existing
kernels to provide ftrace capability but only some of the tracing
options, specifically:
$ cat /sys/kernel/debug/tracing/available_tracers
open sched_switch nop
I'm not sure that any of these would help shed light on hard sys
Hi Jamin,
We value your suggestion, and we appreciate your effort on open source
software and Ubuntu. I am thinking about your words and try to have
balance with debug and cost.
Therefore, I make AMD64 and i386 Jaunty kernel images with generic
config and turning on CONFIG_FUNCTION_TRACER. If it
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
please add ftrace to default configuration
https://bug
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
please add ftrace to default configuration
https://bugs.launchpad.net/bugs/355431
You received this bug notification because you are
Without CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3474480 2009-05-07 15:39 arch/x86/boot/bzImage
With CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3592560 2009-05-07 15:26 arch/x86/boot/bzImage
It take us at leas
How else do you propose that a user track down hard to reproduce kernel
panics? If there's a better, more preferred method I'm all ears. I've
been dealing with sporadic kernel panics (hard lock with flashing caps
lock) since just after upgrading to 8.10. Trying to track down the root
cause is wh
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24824733/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24824734/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24824735/Dependencies.txt
** A
Forgot to mention the specific tracing that was missing. The existing
kernels to provide ftrace capability but only some of the tracing
options, specifically:
$ cat /sys/kernel/debug/tracing/available_tracers
open sched_switch nop
I'm not sure that any of these would help shed light on hard sys
Hi Jamin,
Indeed this does not appear to be enabled. The only issue is the kernel
is currently frozen for Jaunty's final release. This may have to wait
and be considered for a Stable Release Update but I'll leave that for
the kernel team to decide. Thanks.
ogasaw...@yoji:~/ubuntu-jaunty/debian
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
please add ftrace to default configuration
https://bug
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
please add ftrace to default configuration
https://bugs.launchpad.net/bugs/355431
You received this bug notification because you are
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24824733/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24824734/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24824735/Dependencies.txt
** A
Forgot to mention the specific tracing that was missing. The existing
kernels to provide ftrace capability but only some of the tracing
options, specifically:
$ cat /sys/kernel/debug/tracing/available_tracers
open sched_switch nop
I'm not sure that any of these would help shed light on hard sys
Hi Jamin,
Indeed this does not appear to be enabled. The only issue is the kernel
is currently frozen for Jaunty's final release. This may have to wait
and be considered for a Stable Release Update but I'll leave that for
the kernel team to decide. Thanks.
ogasaw...@yoji:~/ubuntu-jaunty/debian
Hi Jamin,
We value your suggestion, and we appreciate your effort on open source
software and Ubuntu. I am thinking about your words and try to have
balance with debug and cost.
Therefore, I make AMD64 and i386 Jaunty kernel images with generic
config and turning on CONFIG_FUNCTION_TRACER. If it
Without CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3474480 2009-05-07 15:39 arch/x86/boot/bzImage
With CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3592560 2009-05-07 15:26 arch/x86/boot/bzImage
It take us at leas
How else do you propose that a user track down hard to reproduce kernel
panics? If there's a better, more preferred method I'm all ears. I've
been dealing with sporadic kernel panics (hard lock with flashing caps
lock) since just after upgrading to 8.10. Trying to track down the root
cause is wh
Hi Jamin,
We value your suggestion, and we appreciate your effort on open source
software and Ubuntu. I am thinking about your words and try to have
balance with debug and cost.
Therefore, I make AMD64 and i386 Jaunty kernel images with generic
config and turning on CONFIG_FUNCTION_TRACER. If it
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
please add ftrace to default configuration
https://bug
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
please add ftrace to default configuration
https://bugs.launchpad.net/bugs/355431
You received this bug notification because you are
Without CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3474480 2009-05-07 15:39 arch/x86/boot/bzImage
With CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3592560 2009-05-07 15:26 arch/x86/boot/bzImage
It take us at leas
How else do you propose that a user track down hard to reproduce kernel
panics? If there's a better, more preferred method I'm all ears. I've
been dealing with sporadic kernel panics (hard lock with flashing caps
lock) since just after upgrading to 8.10. Trying to track down the root
cause is wh
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24824733/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24824734/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24824735/Dependencies.txt
** A
Forgot to mention the specific tracing that was missing. The existing
kernels to provide ftrace capability but only some of the tracing
options, specifically:
$ cat /sys/kernel/debug/tracing/available_tracers
open sched_switch nop
I'm not sure that any of these would help shed light on hard sys
Hi Jamin,
Indeed this does not appear to be enabled. The only issue is the kernel
is currently frozen for Jaunty's final release. This may have to wait
and be considered for a Stable Release Update but I'll leave that for
the kernel team to decide. Thanks.
ogasaw...@yoji:~/ubuntu-jaunty/debian
Hi Jamin,
Indeed this does not appear to be enabled. The only issue is the kernel
is currently frozen for Jaunty's final release. This may have to wait
and be considered for a Stable Release Update but I'll leave that for
the kernel team to decide. Thanks.
ogasaw...@yoji:~/ubuntu-jaunty/debian
Hi Jamin,
We value your suggestion, and we appreciate your effort on open source
software and Ubuntu. I am thinking about your words and try to have
balance with debug and cost.
Therefore, I make AMD64 and i386 Jaunty kernel images with generic
config and turning on CONFIG_FUNCTION_TRACER. If it
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
please add ftrace to default configuration
https://bug
I just test with the config options, seems ok
I will do more testing and sending the patch
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
please add ftrace to default configuration
https://bugs.launchpad.net/bugs/355431
You received this bug notification because you are
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24824733/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24824734/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24824735/Dependencies.txt
** A
Forgot to mention the specific tracing that was missing. The existing
kernels to provide ftrace capability but only some of the tracing
options, specifically:
$ cat /sys/kernel/debug/tracing/available_tracers
open sched_switch nop
I'm not sure that any of these would help shed light on hard sys
Hi Jamin,
Indeed this does not appear to be enabled. The only issue is the kernel
is currently frozen for Jaunty's final release. This may have to wait
and be considered for a Stable Release Update but I'll leave that for
the kernel team to decide. Thanks.
ogasaw...@yoji:~/ubuntu-jaunty/debian
Without CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3474480 2009-05-07 15:39 arch/x86/boot/bzImage
With CONFIG_FUNCTION_TRACER
# ls -al arch/x86/boot/bzImage
-rw-r--r-- 1 ikepanhc ikepanhc 3592560 2009-05-07 15:26 arch/x86/boot/bzImage
It take us at leas
How else do you propose that a user track down hard to reproduce kernel
panics? If there's a better, more preferred method I'm all ears. I've
been dealing with sporadic kernel panics (hard lock with flashing caps
lock) since just after upgrading to 8.10. Trying to track down the root
cause is wh
Ike Panhc wrote:
>
> I put the packages at http://people.ubuntu.com/~ikepanhc/lp355431/
> I will update these packages if any important update from Jaunty kernel
> source tree
>
> I hope the packages will be useful for both of us
I appreciate the effort, but if I'm following correctly I don't b
Ike Panhc wrote:
>
> I put the packages at http://people.ubuntu.com/~ikepanhc/lp355431/
> I will update these packages if any important update from Jaunty kernel
> source tree
>
> I hope the packages will be useful for both of us
I appreciate the effort, but if I'm following correctly I don't b
Ike Panhc wrote:
>
> I put the packages at http://people.ubuntu.com/~ikepanhc/lp355431/
> I will update these packages if any important update from Jaunty kernel
> source tree
>
> I hope the packages will be useful for both of us
I appreciate the effort, but if I'm following correctly I don't b
Ike Panhc wrote:
>
> I put the packages at http://people.ubuntu.com/~ikepanhc/lp355431/
> I will update these packages if any important update from Jaunty kernel
> source tree
>
> I hope the packages will be useful for both of us
I appreciate the effort, but if I'm following correctly I don't b
Ike Panhc wrote:
>
> I put the packages at http://people.ubuntu.com/~ikepanhc/lp355431/
> I will update these packages if any important update from Jaunty kernel
> source tree
>
> I hope the packages will be useful for both of us
I appreciate the effort, but if I'm following correctly I don't b
Ike Panhc wrote:
>
> I put the packages at http://people.ubuntu.com/~ikepanhc/lp355431/
> I will update these packages if any important update from Jaunty kernel
> source tree
>
> I hope the packages will be useful for both of us
I appreciate the effort, but if I'm following correctly I don't b
54 matches
Mail list logo
