Kernel Failure - 3.4.24 Similar USB MO To 3.4.89 Kernel Failure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Please CC me in on replies as I am not part of the LKML. As the prior round of discussion about this ongoing USB Kernel problem was with Sebastian, I have CC'ed Sebastian in on this posting as well. Again this is because the Linux Kernel information suggests CCing in someone that might be able to assist for the area of concern. My hope is that this will assist in determining who should be the kernel developer that needs to look at these Kernel failures and the crash/opps if need be. I have a very very busy and unpredictable schedule, so I would ask for patience in a reply from me if one is so needed. For the last few years I have had about a half dozen Kernel failures that all appear to be related to USB devices being plugged in. The last occurrence a few months ago to the one today actually caused a kernel crash/opps to the console resulting in the only option was to power off the machine and power it back on. I took a high quality DSLR image of the screen which clearly has important information roll off as the screen was not large enough to hold the information. I also searched high and low using a my tablet for a few days to see if I could find out how I might be able to secure the information that rolled off the screen, not to mention have it in a easy to use form for the Kernel developers to work with. I have looked since powering up the machine from that event and many times since and can only find references, as then, to using a second machine connected to the machine had had the Kernel crash/opps via serial using a debugger. I do not have the kernel experience or such at this point to know how to do this and reading suggested some one or few Kernel options were needed in the Kernel for this serial debugging approach to work. So on that note if anyone can advise me if there is a way to find where a kernel crash/opps is stored that one can collect and send to the Kernel Developers I would be most appreciative. I have and still do make efforts to find the information. It is possible I am not using the correct search terms or know where I need to look to read the about the information. About 14:49 EDT my system experienced yet another Linux Kernel failure. Again it was related to inserting a basic USB, not a MP3 player USB, just a plain data USB. This followed my removing a different USB after issuing a pumount command that returned as successful. I have attached a copy of the kernel failure details. If there is a desire to see the DSLR screen image of the prior kernel crash/opps please advise me to do so. Please be aware I do not use any drivers other than those in the Linux Kernel other than those in the stock Kernel. I do not need any unique drivers for my machine or the devices I use with my laptop. Also be aware all of the 3.x Linux Kernels I have used are from Kernel.org and I compile these myself using the same configuration file plus any additional config file item options I set that are added to the next 3.4.x kernel version I compile. This means there is no reason for my kernel to ever be tainted. If my Linux 3.4.x Kernel is listed as tainted, it is the stock Linux Kernel that has so decided for some reason. Regards, John L. Males Toronto, Ontario Canada 16 May 2014 17:30 -0400 EDT 2014-05-16 16:56:58.344920846-0400-EDT Time: 1400273818 16 May 16:56:58 ntpdate[14149]: ntpdate 4.2.6p2@1.2194-o Sun Oct 17 13:35:14 UTC 2010 (1) 16 May 16:57:12 ntpdate[14154]: step time server 208.80.96.70 offset 0.003026 sec Linux 3.4.89-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Wed May 7 22:33:10 EDT 2014 Modified Debian GNU/Linux 6.0.3 (squeeze) (Alternative to Debian determined, work in progress) cat /proc/cpuinfo (Selected): model name : Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz vmstat -s: 3452464 K total memory 3381088 K used memory 2608984 K active memory 570068 K inactive memory 71376 K free memory 2796 K buffer memory 106480 K swap cache 8225244 K total swap 1875240 K used swap 6350004 K free swap 36725845 non-nice user cpu ticks 692898 nice user cpu ticks 4757452 system cpu ticks 78815904 idle cpu ticks 2909319 IO-wait cpu ticks 5590 IRQ cpu ticks 1678486 softirq cpu ticks 0 stolen cpu ticks 81758774 pages paged in 66779328 pages paged out 6643777 pages swapped in 5417469 pages swapped out 431124356 interrupts 567863734 CPU context switches 1399647013 boot time 175501 forks /proc/vmstat (Selected): pgpgin 81758774 pgpgout 66779328 pswpin 6643777 pswpout 5417469 pgfree 776294670 pgfault 546643863 pgmajfault 2018217 /proc/meminfo (Selected): Mlocked:6604 kB VmallocTotal: 34359738367 kB VmallocChunk: 34359322080 kB HugePages_Total: 0 vmstat --partition
Kernel Failure - 3.4.24 Similar USB MO To 3.4.89 Kernel Failure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Please CC me in on replies as I am not part of the LKML. As the prior round of discussion about this ongoing USB Kernel problem was with Sebastian, I have CC'ed Sebastian in on this posting as well. Again this is because the Linux Kernel information suggests CCing in someone that might be able to assist for the area of concern. My hope is that this will assist in determining who should be the kernel developer that needs to look at these Kernel failures and the crash/opps if need be. I have a very very busy and unpredictable schedule, so I would ask for patience in a reply from me if one is so needed. For the last few years I have had about a half dozen Kernel failures that all appear to be related to USB devices being plugged in. The last occurrence a few months ago to the one today actually caused a kernel crash/opps to the console resulting in the only option was to power off the machine and power it back on. I took a high quality DSLR image of the screen which clearly has important information roll off as the screen was not large enough to hold the information. I also searched high and low using a my tablet for a few days to see if I could find out how I might be able to secure the information that rolled off the screen, not to mention have it in a easy to use form for the Kernel developers to work with. I have looked since powering up the machine from that event and many times since and can only find references, as then, to using a second machine connected to the machine had had the Kernel crash/opps via serial using a debugger. I do not have the kernel experience or such at this point to know how to do this and reading suggested some one or few Kernel options were needed in the Kernel for this serial debugging approach to work. So on that note if anyone can advise me if there is a way to find where a kernel crash/opps is stored that one can collect and send to the Kernel Developers I would be most appreciative. I have and still do make efforts to find the information. It is possible I am not using the correct search terms or know where I need to look to read the about the information. About 14:49 EDT my system experienced yet another Linux Kernel failure. Again it was related to inserting a basic USB, not a MP3 player USB, just a plain data USB. This followed my removing a different USB after issuing a pumount command that returned as successful. I have attached a copy of the kernel failure details. If there is a desire to see the DSLR screen image of the prior kernel crash/opps please advise me to do so. Please be aware I do not use any drivers other than those in the Linux Kernel other than those in the stock Kernel. I do not need any unique drivers for my machine or the devices I use with my laptop. Also be aware all of the 3.x Linux Kernels I have used are from Kernel.org and I compile these myself using the same configuration file plus any additional config file item options I set that are added to the next 3.4.x kernel version I compile. This means there is no reason for my kernel to ever be tainted. If my Linux 3.4.x Kernel is listed as tainted, it is the stock Linux Kernel that has so decided for some reason. Regards, John L. Males Toronto, Ontario Canada 16 May 2014 17:30 -0400 EDT 2014-05-16 16:56:58.344920846-0400-EDT Time: 1400273818 16 May 16:56:58 ntpdate[14149]: ntpdate 4.2.6p2@1.2194-o Sun Oct 17 13:35:14 UTC 2010 (1) 16 May 16:57:12 ntpdate[14154]: step time server 208.80.96.70 offset 0.003026 sec Linux 3.4.89-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Wed May 7 22:33:10 EDT 2014 Modified Debian GNU/Linux 6.0.3 (squeeze) (Alternative to Debian determined, work in progress) cat /proc/cpuinfo (Selected): model name : Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz vmstat -s: 3452464 K total memory 3381088 K used memory 2608984 K active memory 570068 K inactive memory 71376 K free memory 2796 K buffer memory 106480 K swap cache 8225244 K total swap 1875240 K used swap 6350004 K free swap 36725845 non-nice user cpu ticks 692898 nice user cpu ticks 4757452 system cpu ticks 78815904 idle cpu ticks 2909319 IO-wait cpu ticks 5590 IRQ cpu ticks 1678486 softirq cpu ticks 0 stolen cpu ticks 81758774 pages paged in 66779328 pages paged out 6643777 pages swapped in 5417469 pages swapped out 431124356 interrupts 567863734 CPU context switches 1399647013 boot time 175501 forks /proc/vmstat (Selected): pgpgin 81758774 pgpgout 66779328 pswpin 6643777 pswpout 5417469 pgfree 776294670 pgfault 546643863 pgmajfault 2018217 /proc/meminfo (Selected): Mlocked:6604 kB VmallocTotal: 34359738367 kB VmallocChunk: 34359322080 kB HugePages_Total: 0 vmstat --partition
