* Kernel Failure - 3.4.24
@ 2013-01-16 23:42 John L. Males
2013-01-27 16:14 ` Sebastian Andrzej Siewior
0 siblings, 1 reply; 6+ messages in thread
From: John L. Males @ 2013-01-16 23:42 UTC (permalink / raw)
To: linux-kernel; +Cc: Sebastian Andrzej Siewior
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I copied Sebastian in on the post my review of Changelogs
suggests Sebastian is the one who will want to know about this
kernel failure or will know who should be.
I am not on the LKML so it would be appreciated if I was CC on
any related replies to this kernel failure which appeared to
occur when a USB MP3 player was inserted or removed from the HP
NC6400 laptop.
The kernel failure trace information was:
Kernel failure message 1:
[327619.690505] ------------[ cut here ]------------
[327619.690518] WARNING: at fs/buffer.c:1106 mark_buffer_dirty
+0x8b/0xb0() [327619.690523] Hardware name: HP Compaq nc6400
(RM100AW#ABA) [327619.690526] Modules linked in: nls_utf8
nls_cp437 vfat fat usb_storage option usb_wwan usbserial
snd_hrtimer ip6table_filter ip6_tables iptable_filter ip_tables
kvm_intel kvm ebtable_nat ebtables x_tables cpufreq_userspace
cpufreq_stats cpufreq_powersave cpufreq_conservative bridge stp
bnep rfcomm bluetooth crc16 ppdev lp binfmt_misc i915
drm_kms_helper drm i2c_algo_bit i2c_core uinput fuse loop
snd_hda_codec_si3054 snd_hda_codec_analog snd_hda_intel
snd_hda_codec tpm_infineon arc4 snd_hwdep snd_pcm_oss
snd_mixer_oss snd_pcm iwl3945 snd_seq_dummy iwlegacy
snd_seq_oss usbhid snd_seq_midi snd_rawmidi coretemp hid
snd_seq_midi_event snd_seq mac80211 pcmcia snd_timer irda
snd_seq_device microcode snd cfg80211 yenta_socket psmouse
joydev parport_pc tifm_7xx1 tpm_tis soundcore pcmcia_rsrc
tifm_core pcspkr evdev snd_page_alloc pcmcia_core parport tpm
crc_ccitt hp_wmi hp_accel lis3lv02d sparse_keymap serio_raw
acpi_cpufreq tpm_bios rng_core rfkill mperf input_polldev wmi
battery ac container power_supply processor video button ext2
mbcache dm_mod btrfs zlib_deflate crc32c libcrc32c sg sr_mod
cdrom sd_mod crc_t10dif ata_generic pata_acpi uhci_hcd ata_piix
libata ehci_hcd sdhci_pci scsi_mod ide_pci_generic tg3 ide_core
sdhci mmc_core libphy usbcore thermal usb_common fan
thermal_sys [last unloaded: scsi_wait_scan] [327619.690737]
Pid: 31574, comm: sync Tainted: G W
3.4.24-kernel.org-jlm-010-amd64 #1 [327619.690741] Call Trace:
[327619.690751] [<ffffffff8105177f>] warn_slowpath_common
+0x7f/0xc0 [327619.690757] [<ffffffff810517da>]
warn_slowpath_null+0x1a/0x20 [327619.690762]
[<ffffffff811b67fb>] mark_buffer_dirty+0x8b/0xb0
[327619.690774] [<ffffffffa028b734>] ext2_sync_super
+0x94/0x100 [ext2] [327619.690784] [<ffffffffa028b809>]
ext2_sync_fs+0x69/0x80 [ext2] [327619.690790]
[<ffffffff811b4480>] ? __sync_filesystem+0x90/0x90
[327619.690795] [<ffffffff811b4453>] __sync_filesystem
+0x63/0x90 [327619.690801] [<ffffffff811b449f>] sync_one_sb
+0x1f/0x30 [327619.690807] [<ffffffff81188c77>] iterate_supers
+0xb7/0xf0 [327619.690812] [<ffffffff811b44fa>] sys_sync
+0x4a/0x70 [327619.690819] [<ffffffff814c51a9>]
system_call_fastpath+0x16/0x1b [327619.690942] ---[ end trace
7e4761e5ee97ad0c ]---
If you need additional information please advise.
Regards,
John L. Males
Toronto, Ontario
Canada
16 January 2013 18:42
==============================================================
2013-01-16 18:19:55.448036096-0500-EST
16 Jan 18:19:55 ntpdate[17025]: ntpdate 4.2.6p2@1.2194-o Sun
Oct 17 13:35:14 UTC 2010 (1)
16 Jan 18:20:09 ntpdate[17030]: step time server 192.75.12.10
offset -3.181109 sec
Linux 3.4.24-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Sun Dec 23
10:06:41 EST 2012
Modified Debian GNU/Linux 6.0.3 (squeeze)
(Evaluating alternatives to Debian)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlD3Ot0ACgkQ+V/XUtB6aBBNzwCdFcVnM+qtUoIpArxVlr8fAN/E
Se0Anj/z1hTzMmktfTHMeuDQHNj6GMh1
=auyh
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Kernel Failure - 3.4.24
2013-01-16 23:42 Kernel Failure - 3.4.24 John L. Males
@ 2013-01-27 16:14 ` Sebastian Andrzej Siewior
2013-01-28 19:57 ` Re[02]: " John L. Males
0 siblings, 1 reply; 6+ messages in thread
From: Sebastian Andrzej Siewior @ 2013-01-27 16:14 UTC (permalink / raw)
To: jlmales; +Cc: linux-kernel
On 01/17/2013 12:42 AM, John L. Males wrote:
> Hello,
Hi,
> I copied Sebastian in on the post my review of Changelogs suggests
> Sebastian is the one who will want to know about this kernel
> failure or will know who should be.
I did what? I reviewed patches since they went in this problem occurs?
> I am not on the LKML so it would be appreciated if I was CC on any
> related replies to this kernel failure which appeared to occur when
> a USB MP3 player was inserted or removed from the HP NC6400
> laptop.
Next time you post logs try to format them like this (or people might
ignore it because it is too hard to read):
> The kernel failure trace information was:
>
> Kernel failure message 1: [327619.690505] ------------[ cut here
> ]------------ [327619.690518] WARNING: at fs/buffer.c:1106
> mark_buffer_dirty +0x8b/0xb0() [327619.690523]
Hardware name: HP Compaq nc6400 (RM100AW#ABA)
[327619.690526] Modules linked in: nls_utf8
> nls_cp437 vfat fat usb_storage option usb_wwan usbserial
> snd_hrtimer ip6table_filter ip6_tables iptable_filter ip_tables
> kvm_intel kvm ebtable_nat ebtables x_tables cpufreq_userspace
> cpufreq_stats cpufreq_powersave cpufreq_conservative bridge stp
> bnep rfcomm bluetooth crc16 ppdev lp binfmt_misc i915
> drm_kms_helper drm i2c_algo_bit i2c_core uinput fuse loop
> snd_hda_codec_si3054 snd_hda_codec_analog snd_hda_intel
> snd_hda_codec tpm_infineon arc4 snd_hwdep snd_pcm_oss snd_mixer_oss
> snd_pcm iwl3945 snd_seq_dummy iwlegacy snd_seq_oss usbhid
> snd_seq_midi snd_rawmidi coretemp hid snd_seq_midi_event snd_seq
> mac80211 pcmcia snd_timer irda snd_seq_device microcode snd
> cfg80211 yenta_socket psmouse joydev parport_pc tifm_7xx1 tpm_tis
> soundcore pcmcia_rsrc tifm_core pcspkr evdev snd_page_alloc
> pcmcia_core parport tpm crc_ccitt hp_wmi hp_accel lis3lv02d
> sparse_keymap serio_raw acpi_cpufreq tpm_bios rng_core rfkill mperf
> input_polldev wmi battery ac container power_supply processor video
> button ext2 mbcache dm_mod btrfs zlib_deflate crc32c libcrc32c sg
> sr_mod cdrom sd_mod crc_t10dif ata_generic pata_acpi uhci_hcd
> ata_piix libata ehci_hcd sdhci_pci scsi_mod ide_pci_generic tg3
> ide_core sdhci mmc_core libphy usbcore thermal usb_common fan
> thermal_sys
[last unloaded: scsi_wait_scan]
[327619.690737] Pid: 31574, comm: sync Tainted: G W
3.4.24-kernel.org-jlm-010-amd64 #1
This line looks like you have custom patches on your tree.
[327619.690741] Call Trace:
[327619.690751] [<ffffffff8105177f>] warn_slowpath_common +0x7f/0xc0
[327619.690757] [<ffffffff810517da>] warn_slowpath_null+0x1a/0x20
[327619.690762] [<ffffffff811b67fb>] mark_buffer_dirty+0x8b/0xb0
[327619.690774] [<ffffffffa028b734>] ext2_sync_super +0x94/0x100 [ext2]
[327619.690784] [<ffffffffa028b809>] ext2_sync_fs+0x69/0x80 [ext2]
[327619.690790] [<ffffffff811b4480>] ? __sync_filesystem+0x90/0x90
[327619.690795] [<ffffffff811b4453>] __sync_filesystem+0x63/0x90
[327619.690801] [<ffffffff811b449f>] sync_one_sb+0x1f/0x30
[327619.690807] [<ffffffff81188c77>] iterate_supers+0xb7/0xf0
[327619.690812] [<ffffffff811b44fa>] sys_sync+0x4a/0x70
[327619.690819] [<ffffffff814c51a9>] system_call_fastpath+0x16/0x1b
[327619.690942] ---[ end trace 7e4761e5ee97ad0c ]---
> If you need additional information please advise.
This looks like https://bugzilla.redhat.com/show_bug.cgi?id=468794
I think that I am innocent here. You probably unpluged the device
before the content was written back to the media. Could it be?
>
> Regards,
>
> John L. Males Toronto, Ontario Canada 16 January 2013 18:42
Sebastian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re[02]: Kernel Failure - 3.4.24
2013-01-27 16:14 ` Sebastian Andrzej Siewior
@ 2013-01-28 19:57 ` John L. Males
2013-01-29 21:32 ` Sebastian Andrzej Siewior
0 siblings, 1 reply; 6+ messages in thread
From: John L. Males @ 2013-01-28 19:57 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: linux-kernel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sebastian,
Message replied to:
Date: Sun, 27 Jan 2013 17:14:14 +0100
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: jlmales@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Failure - 3.4.24
> On 01/17/2013 12:42 AM, John L. Males wrote:
> > Hello,
>
> Hi,
>
> > I copied Sebastian in on the post my review of Changelogs
> > suggests Sebastian is the one who will want to know about
> > this kernel failure or will know who should be.
>
> I did what? I reviewed patches since they went in this
> problem occurs?
I was not suggesting you are responsible for the bug at all. On
various links I looked at for reporting kernel bugs it is
suggested it is best to copy in a kernel person in when posting
to the LKML otherwise the posting will likely not receive a
response. When I looked through recent ChangeLogs your name was
often related to USB issues. As I believed this kernel failure
was a USB related I copied you in. I was expecting upon your
review of the kernel failure you determined that you knew who
best to look at the kernel failure you could then direct
the issue to that person. Doing so I would have been be very
grateful. I am not a kernel developer and I therefore do not
know how to read these failures, let alone know what code
failed. I also therefore do not know who this kernel failure
should be directed to. I was hoping your higher Linux kernel
and LKML knowledge would assist me in ensuring this kernel
failure was directed to the correct kernel developer.
>
> > I am not on the LKML so it would be appreciated if I was CC
> > on any related replies to this kernel failure which
> > appeared to occur when a USB MP3 player was inserted or
> > removed from the HP NC6400 laptop.
>
> Next time you post logs try to format them like this (or
> people might ignore it because it is too hard to read):
Thank you for the formatting tip.
>
> > The kernel failure trace information was:
> >
> > Kernel failure message 1: [327619.690505] ------------[ cut
> > here ]------------ [327619.690518] WARNING: at
> > fs/buffer.c:1106 mark_buffer_dirty +0x8b/0xb0()
> > [327619.690523]
> Hardware name: HP Compaq nc6400 (RM100AW#ABA)
> [327619.690526] Modules linked in: nls_utf8
> > nls_cp437 vfat fat usb_storage option usb_wwan usbserial
> > snd_hrtimer ip6table_filter ip6_tables iptable_filter
> > ip_tables kvm_intel kvm ebtable_nat ebtables x_tables
> > cpufreq_userspace cpufreq_stats cpufreq_powersave
> > cpufreq_conservative bridge stp bnep rfcomm bluetooth crc16
> > ppdev lp binfmt_misc i915 drm_kms_helper drm i2c_algo_bit
> > i2c_core uinput fuse loop snd_hda_codec_si3054
> > snd_hda_codec_analog snd_hda_intel snd_hda_codec
> > tpm_infineon arc4 snd_hwdep snd_pcm_oss snd_mixer_oss
> > snd_pcm iwl3945 snd_seq_dummy iwlegacy snd_seq_oss usbhid
> > snd_seq_midi snd_rawmidi coretemp hid snd_seq_midi_event
> > snd_seq mac80211 pcmcia snd_timer irda snd_seq_device
> > microcode snd cfg80211 yenta_socket psmouse joydev
> > parport_pc tifm_7xx1 tpm_tis soundcore pcmcia_rsrc
> > tifm_core pcspkr evdev snd_page_alloc pcmcia_core parport
> > tpm crc_ccitt hp_wmi hp_accel lis3lv02d sparse_keymap
> > serio_raw acpi_cpufreq tpm_bios rng_core rfkill mperf
> > input_polldev wmi battery ac container power_supply
> > processor video button ext2 mbcache dm_mod btrfs
> > zlib_deflate crc32c libcrc32c sg sr_mod cdrom sd_mod
> > crc_t10dif ata_generic pata_acpi uhci_hcd ata_piix libata
> > ehci_hcd sdhci_pci scsi_mod ide_pci_generic tg3 ide_core
> > sdhci mmc_core libphy usbcore thermal usb_common fan
> > thermal_sys
>
> [last unloaded: scsi_wait_scan]
>
> [327619.690737] Pid: 31574, comm: sync Tainted: G W
> 3.4.24-kernel.org-jlm-010-amd64 #1
>
> This line looks like you have custom patches on your tree.
I have no custom patches to the kernel.
For the last several kernels over about 12 months I download the
kernel source directly from kernel.org. The first time I
downloaded a kernel from kernel.org I used the kernel
configuration GUI and configured the kernel from scratch.
Thereafter as was the case with this kernel I use "make
oldconfig" using the last kernel configuration I used with the
new items added since the last kernel I compiled that "make
oldconfig" identifies.
>
> [327619.690741] Call Trace:
> [327619.690751] [<ffffffff8105177f>] warn_slowpath_common
> +0x7f/0xc0 [327619.690757] [<ffffffff810517da>]
> warn_slowpath_null+0x1a/0x20 [327619.690762]
> [<ffffffff811b67fb>] mark_buffer_dirty+0x8b/0xb0
> [327619.690774] [<ffffffffa028b734>] ext2_sync_super
> +0x94/0x100 [ext2] [327619.690784] [<ffffffffa028b809>]
> ext2_sync_fs+0x69/0x80 [ext2] [327619.690790]
> [<ffffffff811b4480>] ? __sync_filesystem+0x90/0x90
> [327619.690795] [<ffffffff811b4453>] __sync_filesystem
> +0x63/0x90 [327619.690801] [<ffffffff811b449f>] sync_one_sb
> +0x1f/0x30 [327619.690807] [<ffffffff81188c77>] iterate_supers
> +0xb7/0xf0 [327619.690812] [<ffffffff811b44fa>] sys_sync
> +0x4a/0x70 [327619.690819] [<ffffffff814c51a9>]
> system_call_fastpath+0x16/0x1b [327619.690942] ---[ end trace
> 7e4761e5ee97ad0c ]---
>
> > If you need additional information please advise.
>
> This looks like
> https://bugzilla.redhat.com/show_bug.cgi?id=468794
>
> I think that I am innocent here. You probably unpluged the
> device before the content was written back to the media.
> Could it be?
I looked at the RedHat bug 468794. The bug seems to indicate
it was never fixed. The bug was reported against
2.6.27.4-47.rc3.fc10.i686 #1 on 2008-10-27 21:34:04 EDT and
was closed 2009-12-18 01:40:33 EST. The differences are a bug
of at least 5 years ago and a 2.6 kernel verses 5 years later
and current at time stable kernel 3.4.24 from kernel.org with no
patches I applied when this kernel failure I encountered
occurred. If this is the same bug then there is a bug that may
have been about for a while or perhaps a regression. The fact
is the RedHat bug 468794 was never fixed.
At no point was I suggesting you were to blame for the kernel
failure. My eM2008-10-27 21:34:04 EDT ail with you copied in
was simply my best guess after looking at the last few
ChangLogs as a good place to start in copying in someone more
in the know that me that could determine who is best to look at
this kernel failure.
No content was written to the device by me. The device was
simply plugged in and then removed just to confirm the device
was seen by my system. After this kernel failure the device
was plugged back in a few minutes later, browsed, a file copied
from, a file copied/erased as part of validating this device
behaved like a USB flash device. The device was then removed
with no issue or kernel failure. The exact same device has
been plugged in/out on two seperate days since the day of the
kernel failure with no kernel failures or issues associated
with the device.
>
> >
> > Regards,
> >
> > John L. Males Toronto, Ontario Canada 16 January 2013 18:42
>
> Sebastian
Again if there is further information required please advise.
Regards,
John L. Males
Toronto, Ontario
Canada
28 January 2013 14:57
==============================================================
2013-01-28 14:04:01.922357120-0500-EST
28 Jan 14:04:01 ntpdate[5798]: ntpdate 4.2.6p2@1.2194-o Sun Oct
17 13:35:14 UTC 2010 (1)
28 Jan 14:04:25 ntpdate[5803]: step time server 199.102.46.72
offset -7.091489 sec
Linux 3.4.24-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Sun Dec 23
10:06:41 EST 2012
Modified Debian GNU/Linux 6.0.3 (squeeze)
(Evaluating alternatives to Debian)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlEG2BQACgkQ+V/XUtB6aBA2+ACggsK4Zeu0ApJ1Qn5wtXX4rXp8
RyMAnjfKg0G08E2tViOA9UFQRBcworK6
=vgDl
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Kernel Failure - 3.4.24
2013-01-28 19:57 ` Re[02]: " John L. Males
@ 2013-01-29 21:32 ` Sebastian Andrzej Siewior
2013-01-30 18:58 ` Re[04]: " John L. Males
0 siblings, 1 reply; 6+ messages in thread
From: Sebastian Andrzej Siewior @ 2013-01-29 21:32 UTC (permalink / raw)
To: jlmales; +Cc: linux-kernel
On 01/28/2013 08:57 PM, John L. Males wrote:
> I was not suggesting you are responsible for the bug at all. On
Okay then :)
> I have no custom patches to the kernel.
okay.
> I looked at the RedHat bug 468794. The bug seems to indicate it
> was never fixed. The bug was reported against
> 2.6.27.4-47.rc3.fc10.i686 #1 on 2008-10-27 21:34:04 EDT and was
> closed 2009-12-18 01:40:33 EST. The differences are a bug of at
> least 5 years ago and a 2.6 kernel verses 5 years later and current
> at time stable kernel 3.4.24 from kernel.org with no patches I
> applied when this kernel failure I encountered occurred. If this
> is the same bug then there is a bug that may have been about for a
> while or perhaps a regression. The fact is the RedHat bug 468794
> was never fixed.
Lets see. According to the backtrace it seems that the kernel was not
able to write the buffer back to disk. The RH bug says that someone
unplugged the device without an unmount of the disk.
My question are:
- what were you doing by the time this happened?
- can you reproduce it (reliably)?
- Is this *new* meaning is there a kernel where did not happen?
Sebastian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re[04]: Kernel Failure - 3.4.24
2013-01-29 21:32 ` Sebastian Andrzej Siewior
@ 2013-01-30 18:58 ` John L. Males
2014-05-16 21:30 ` Kernel Failure - 3.4.24 Similar USB MO To 3.4.89 Kernel Failure John L. Males
0 siblings, 1 reply; 6+ messages in thread
From: John L. Males @ 2013-01-30 18:58 UTC (permalink / raw)
To: Sebastian Andrzej Siewior; +Cc: linux-kernel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sebastian,
Message replied to:
Date: Tue, 29 Jan 2013 22:32:53 +0100
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: jlmales@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Failure - 3.4.24
> On 01/28/2013 08:57 PM, John L. Males wrote:
> > I was not suggesting you are responsible for the bug at
> > all. On
> Okay then :)
>
> > I have no custom patches to the kernel.
> okay.
>
> > I looked at the RedHat bug 468794. The bug seems to
> > indicate it was never fixed. The bug was reported against
> > 2.6.27.4-47.rc3.fc10.i686 #1 on 2008-10-27 21:34:04 EDT and
> > was closed 2009-12-18 01:40:33 EST. The differences are a
> > bug of at least 5 years ago and a 2.6 kernel verses 5 years
> > later and current at time stable kernel 3.4.24 from
> > kernel.org with no patches I applied when this kernel
> > failure I encountered occurred. If this is the same bug
> > then there is a bug that may have been about for a while or
> > perhaps a regression. The fact is the RedHat bug 468794
> > was never fixed.
>
> Lets see. According to the backtrace it seems that the kernel
> was not able to write the buffer back to disk. The RH bug
> says that someone unplugged the device without an unmount of
> the disk.
Yes I read that someone unplugged the device without an unmount
of the device in the RedHat log.
>
> My question are:
> - what were you doing by the time this happened?
I plugged the USB device into my laptop, then removed it. There
was no user activity related to activity on the device. If
there was activity, as opposed to user based activity, to
warrant the kernel needing to write a buffer to the USB flash
drive it was not a result of any user activity to the USB
drive. Based on your findings in the back trace the kernel was
not able to write a buffer to the USB device from what happened
at the time. I would be concerned that the kernel thought
there was a buffer to write when the user, which was me,
performed no activity upon the USB device. The person who owns
the USB device knows next to nothing about computers, let alone
Windows or Linux, so I would be the only one performing any
actions related to the device.
> - can you reproduce it (reliably)?
No, I did try exactly what I did when the kernel failure
happened and sadly could not recreate the issue. I know how
important that question is and tried a few times to cause the
problem. I was hoping the kernel failure information would
have information indicating the cause of the failure. I often
placed my system in hibernate such that my system will go a
month or bit more before I will reboot my kernel or to boot a
newly compiled kernel. I know for a while in the early 3.2.x
releases doing so caused the kernel some issues and the system
would need to be rebooted or would just reboot on its own.
There are a number of variable to this. I do not know if this
USB failure is an artifact of that often necessary practive I
have to place my system in hibernate almost daily, sometimes a
few times during the day.
As an FYI I had a full kernel opps a few 3.2.x versions ago.
It was my first one in years. I was hoping there would be a
file of the information that displayed on the screen. My
research after the kernel opps suggests one has to write down
the information on the screen from a kernel opps, which I did
not do as I did not think I would need to anymore. The reason I
mention this is that kernel opps was with a USB device as
well. The difference was it was a USB Wireless BGN device that
I have used many times over the last 12 months with a number
of 3.2.x kernels with no kernel opps/failure, just odd
functional issues that seem to resolve in later kernel
versions. The kernel opps that occurred with this Wireless BGN
device only occurred once with that exact older 3.2.x kernel
version and I have no clue why. I have no information I know
of about that kernel opps that might help with this kernel
failure. I did not know I needed to write down the screen from
the opps. I therefore cannot provide the kernel opps
information that might share some common findings with the
kernel failure of this issue. I suspect there may be nothing
in common, but without the kernel opps information we will not
know for certain.
The USB device was a MP3 player that acts like a flash USB
drive when it is plugged into a computer. This means one can
copy to/from, rename, delete files using the command line or
any file manager one uses.
> - Is this *new* meaning is there a kernel where did not
> happen?
I am not sure where the "new" reference you are referring to is
from. That said, the only time this person's MP3 player/USB
flash was used was with the kernel.org 3.2.24 kernel I noted.
The only other USB problem I had was once with a USB Wireless
BGN device that has see alot of activity on my system and had
one opps on a 3.2.x kernel prior to 3.2.24 and again only once
on that kernel version.
>
> Sebastian
I know you know, but for those that do not, I am not on the
LKML. It would be appreciated if I was copied in on any LKML
replies.
As always if there is more information or clarification needed
please ask.
Regards,
John L. Males
Toronto, Ontario
Canada
30 January 2013 13:58
==============================================================
2013-01-30 13:09:05.479017366-0500-EST
30 Jan 13:09:05 ntpdate[17854]: ntpdate 4.2.6p2@1.2194-o Sun
Oct 17 13:35:14 UTC 2010 (1)
30 Jan 13:09:32 ntpdate[17863]: step time server 142.4.209.106
offset -7.350323 sec
Linux 3.4.24-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Sun Dec 23
10:06:41 EST 2012
Modified Debian GNU/Linux 6.0.3 (squeeze)
(Evaluating alternatives to Debian)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlEJbUcACgkQ+V/XUtB6aBAh4ACeKQIM7vMWliG9iHpUfmhwQPKo
58sAoMiUS1AgNtfj0oBBPydcP60m3dyH
=8sUO
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Kernel Failure - 3.4.24 Similar USB MO To 3.4.89 Kernel Failure
2013-01-30 18:58 ` Re[04]: " John L. Males
@ 2014-05-16 21:30 ` John L. Males
0 siblings, 0 replies; 6+ messages in thread
From: John L. Males @ 2014-05-16 21:30 UTC (permalink / raw)
To: linux-kernel; +Cc: Sebastian Andrzej Siewior
[-- Attachment #1: Type: text/plain, Size: 12689 bytes --]
-----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 /dev/sda8 (Swap):
sda8 reads read sectors writes requested writes
3742213 53151675 1158726 43339752
sar -b:
Linux 3.4.89-kernel.org-jlm-010-amd64
(pwsdhhuesloejsgegsjwilastwhsk) 05/16/2014
_x86_64_ (2 CPU)
12:00:01 AM pgpgin/s pgpgout/s fault/s majflt/s pgfree/s
pgscank/s pgscand/s pgsteal/s %vmeff
04:35:01 PM 426.19 146.11 1143.15 21.68
1542.74 243.70 64.92 113.82 36.88 04:45:01 PM
1121.83 332.40 965.00 47.56 1442.54 526.49
108.97 300.88 47.35 04:55:02 PM 151.93 55.71
971.67 9.88 1745.04 103.53 28.38 42.41
32.16 Average: 294.06 141.73 1084.45 16.18
1411.21 163.03 22.25 80.41 43.40
ps -A:
%CPU START TIME C CLS COMMAND TIME NI PID
POL PRI SZ RSS VSZ SIZE MAJFL MINFL SCH STAT
TIME WCHAN
0.1 May 9 14:26 0 TS kswapd0 00:14:26 0 26
TS 19 0 0 0 0 0 0 0 S
00:14:26 kswapd
Message replied to:
Date: Wed, 30 Jan 2013 13:58:15 -0500
From: "John L. Males" <jlmales@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re[04]: Kernel Failure - 3.4.24
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sebastian,
>
> Message replied to:
>
> Date: Tue, 29 Jan 2013 22:32:53 +0100
> From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> To: jlmales@gmail.com
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Kernel Failure - 3.4.24
>
>
> > On 01/28/2013 08:57 PM, John L. Males wrote:
> > > I was not suggesting you are responsible for the bug at
> > > all. On
> > Okay then :)
> >
> > > I have no custom patches to the kernel.
> > okay.
> >
> > > I looked at the RedHat bug 468794. The bug seems to
> > > indicate it was never fixed. The bug was reported
> > > against 2.6.27.4-47.rc3.fc10.i686 #1 on 2008-10-27
> > > 21:34:04 EDT and was closed 2009-12-18 01:40:33 EST. The
> > > differences are a bug of at least 5 years ago and a 2.6
> > > kernel verses 5 years later and current at time stable
> > > kernel 3.4.24 from kernel.org with no patches I applied
> > > when this kernel failure I encountered occurred. If this
> > > is the same bug then there is a bug that may have been
> > > about for a while or perhaps a regression. The fact is
> > > the RedHat bug 468794 was never fixed.
> >
> > Lets see. According to the backtrace it seems that the
> > kernel was not able to write the buffer back to disk. The
> > RH bug says that someone unplugged the device without an
> > unmount of the disk.
>
> Yes I read that someone unplugged the device without an
> unmount of the device in the RedHat log.
>
> >
> > My question are:
> > - what were you doing by the time this happened?
>
> I plugged the USB device into my laptop, then removed it.
> There was no user activity related to activity on the
> device. If there was activity, as opposed to user based
> activity, to warrant the kernel needing to write a buffer to
> the USB flash drive it was not a result of any user activity
> to the USB drive. Based on your findings in the back trace
> the kernel was not able to write a buffer to the USB device
> from what happened at the time. I would be concerned that
> the kernel thought there was a buffer to write when the user,
> which was me, performed no activity upon the USB device. The
> person who owns the USB device knows next to nothing about
> computers, let alone Windows or Linux, so I would be the only
> one performing any actions related to the device.
>
>
> > - can you reproduce it (reliably)?
>
> No, I did try exactly what I did when the kernel failure
> happened and sadly could not recreate the issue. I know how
> important that question is and tried a few times to cause the
> problem. I was hoping the kernel failure information would
> have information indicating the cause of the failure. I often
> placed my system in hibernate such that my system will go a
> month or bit more before I will reboot my kernel or to boot a
> newly compiled kernel. I know for a while in the early 3.2.x
> releases doing so caused the kernel some issues and the system
> would need to be rebooted or would just reboot on its own.
> There are a number of variable to this. I do not know if this
> USB failure is an artifact of that often necessary practive I
> have to place my system in hibernate almost daily, sometimes a
> few times during the day.
>
> As an FYI I had a full kernel opps a few 3.2.x versions ago.
> It was my first one in years. I was hoping there would be a
> file of the information that displayed on the screen. My
> research after the kernel opps suggests one has to write down
> the information on the screen from a kernel opps, which I did
> not do as I did not think I would need to anymore. The
> reason I mention this is that kernel opps was with a USB
> device as well. The difference was it was a USB Wireless BGN
> device that I have used many times over the last 12 months
> with a number of 3.2.x kernels with no kernel opps/failure,
> just odd functional issues that seem to resolve in later
> kernel versions. The kernel opps that occurred with this
> Wireless BGN device only occurred once with that exact older
> 3.2.x kernel version and I have no clue why. I have no
> information I know of about that kernel opps that might help
> with this kernel failure. I did not know I needed to write
> down the screen from the opps. I therefore cannot provide
> the kernel opps information that might share some common
> findings with the kernel failure of this issue. I suspect
> there may be nothing in common, but without the kernel opps
> information we will not know for certain.
>
> The USB device was a MP3 player that acts like a flash USB
> drive when it is plugged into a computer. This means one can
> copy to/from, rename, delete files using the command line or
> any file manager one uses.
>
> > - Is this *new* meaning is there a kernel where did not
> > happen?
>
> I am not sure where the "new" reference you are referring to
> is from. That said, the only time this person's MP3
> player/USB flash was used was with the kernel.org 3.2.24
> kernel I noted.
>
> The only other USB problem I had was once with a USB Wireless
> BGN device that has see alot of activity on my system and had
> one opps on a 3.2.x kernel prior to 3.2.24 and again only once
> on that kernel version.
>
> >
> > Sebastian
>
> I know you know, but for those that do not, I am not on the
> LKML. It would be appreciated if I was copied in on any LKML
> replies.
>
> As always if there is more information or clarification needed
> please ask.
>
>
> Regards,
>
> John L. Males
> Toronto, Ontario
> Canada
> 30 January 2013 13:58
>
>
> ==============================================================
> 2013-01-30 13:09:05.479017366-0500-EST
>
> 30 Jan 13:09:05 ntpdate[17854]: ntpdate 4.2.6p2@1.2194-o Sun
> Oct 17 13:35:14 UTC 2010 (1)
>
> 30 Jan 13:09:32 ntpdate[17863]: step time server 142.4.209.106
> offset -7.350323 sec
>
> Linux 3.4.24-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Sun Dec
> 23 10:06:41 EST 2012
>
> Modified Debian GNU/Linux 6.0.3 (squeeze)
> (Evaluating alternatives to Debian)
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAlEJbUcACgkQ
> +V/XUtB6aBAh4ACeKQIM7vMWliG9iHpUfmhwQPKo
> 58sAoMiUS1AgNtfj0oBBPydcP60m3dyH =8sUO
> -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlN2g1gACgkQ+V/XUtB6aBBBWACgyCfzfETF9d1GNI6Ci2MIbIvA
nwEAn1Q+k+ogNczAoBOvZGWEQp2YUdhs
=MxB8
-----END PGP SIGNATURE-----
[-- Attachment #2: kernel-linux-failure-20140516-1449-PerLXDE-WithNotes.txt --]
[-- Type: text/plain, Size: 4613 bytes --]
20140516 14:49 Window of LXDE popped up saying had kernel failure.
Failure occurred yet again as handful of times prior versions in past couple years related to USB
Last time was USB TV adaptor was inserted after had been removed.
This time umounted wip 8gb ArchLinux USB created on T5730 with umount command in system since early hours of this morning,
then inserted 2gb USB that has boot/install image of ArchLinux used on T5730 to create the WIP ArchLinux on 8GB flash
at which point kernel failure occurred.
unmount was done via console which already has console logging enabled:
20140516 14:47:26 -0400 EDT keypunch@pwsdhhuesloejsgegsjwilastwhsk:/vm/ISOs/linux/ArchLinux/archlinux/2014.05.01 tty0 $ pumount /media/0ad46398-13a0-4c3d-93f9-34e67510f053
20140516 14:47:42 -0400 EDT keypunch@pwsdhhuesloejsgegsjwilastwhsk:/vm/ISOs/linux/ArchLinux/archlinux/2014.05.01 tty0 $ cd /vm/ISOs/linux/debian/debian/debian-cd/7.5.0-live/i386/iso-hybrid
Choose not to send, but show details of:
Kernel failure message 1:
[619141.142769] ------------[ cut here ]------------
[619141.142784] WARNING: at block/genhd.c:1573 disk_clear_events+0x11f/0x130()
[619141.142788] Hardware name: HP Compaq nc6400 (RM100AW#ABA)
[619141.142791] Modules linked in: ext4 jbd2 ufs isofs nls_iso8859_1 nls_utf8 nls_cp437 vfat fat cryptd aes_x86_64 aes_generic snd_hrtimer kvm_intel kvm ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative bridge stp bnep rfcomm bluetooth crc16 ppdev lp binfmt_misc i915 drm_kms_helper drm i2c_algo_bit i2c_core uinput fuse loop snd_hda_codec_si3054 snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss arc4 snd_mixer_oss snd_pcm iwl3945 snd_seq_dummy snd_seq_oss iwlegacy snd_seq_midi tpm_infineon snd_rawmidi snd_seq_midi_event mac80211 snd_seq usbhid snd_timer pcmcia hid snd_seq_device cfg80211 coretemp yenta_socket hp_wmi irda pcmcia_rsrc snd sparse_keymap microcode joydev psmouse pcmcia_core tifm_7xx1 parport_pc rfkill tpm_tis soundcore tifm_core crc_ccitt tpm evdev parport pcspkr rng_core hp_accel snd_page_alloc serio_raw tpm_bios acpi_cpufreq lis3lv02d container battery wmi ac input_polldev video mperf power_supply processor button ext2 mbcache dm_mod btrfs zlib_deflate crc32c libcrc32c usb_storage sg sd_mod sr_mod cdrom crc_t10dif ata_generic pata_acpi ata_piix libata uhci_hcd scsi_mod ide_pci_generic ide_core ehci_hcd sdhci_pci sdhci mmc_core usbcore usb_common tg3 libphy fan thermal thermal_sys [last unloaded: scsi_wait_scan]
[619141.143003] Pid: 13035, comm: hald-probe-volu Not tainted 3.4.89-kernel.org-jlm-010-amd64 #1
[619141.143007] Call Trace:
[619141.143018] [<ffffffff8105275f>] warn_slowpath_common+0x7f/0xc0
[619141.143024] [<ffffffff810527ba>] warn_slowpath_null+0x1a/0x20
[619141.143029] [<ffffffff8125e12f>] disk_clear_events+0x11f/0x130
[619141.143039] [<ffffffff811c1461>] check_disk_change+0x31/0x80
[619141.143051] [<ffffffffa01a0215>] sd_open+0xb5/0x1f0 [sd_mod]
[619141.143058] [<ffffffff811c0a71>] __blkdev_get+0x341/0x4b0
[619141.143064] [<ffffffff8125ec79>] ? disk_get_part+0x19/0xa0
[619141.143071] [<ffffffff811c0924>] __blkdev_get+0x1f4/0x4b0
[619141.143076] [<ffffffff811c0f70>] ? blkdev_get+0x390/0x390
[619141.143081] [<ffffffff811c0c34>] blkdev_get+0x54/0x390
[619141.143086] [<ffffffff811c0f70>] ? blkdev_get+0x390/0x390
[619141.143093] [<ffffffff814c5619>] ? sub_preempt_count+0xa9/0xe0
[619141.143098] [<ffffffff811c0f70>] ? blkdev_get+0x390/0x390
[619141.143103] [<ffffffff814c17d5>] ? _raw_spin_unlock+0x35/0x60
[619141.143109] [<ffffffff811c0f70>] ? blkdev_get+0x390/0x390
[619141.143114] [<ffffffff811c0fe1>] blkdev_open+0x71/0x90
[619141.143120] [<ffffffff81185213>] __dentry_open+0x2c3/0x3d0
[619141.143125] [<ffffffff81185421>] nameidata_to_filp+0x71/0x80
[619141.143132] [<ffffffff81194c88>] do_last+0x3f8/0x840
[619141.143137] [<ffffffff811963b9>] path_openat+0xd9/0x3e0
[619141.143144] [<ffffffff8101cce9>] ? sched_clock+0x9/0x10
[619141.143150] [<ffffffff8108c2bf>] ? local_clock+0x6f/0x80
[619141.143156] [<ffffffff811967d9>] do_filp_open+0x49/0xa0
[619141.143161] [<ffffffff814c5619>] ? sub_preempt_count+0xa9/0xe0
[619141.143166] [<ffffffff814c17d5>] ? _raw_spin_unlock+0x35/0x60
[619141.143173] [<ffffffff811a4915>] ? alloc_fd+0x105/0x130
[619141.143178] [<ffffffff8118650a>] do_sys_open+0x10a/0x1f0
[619141.143183] [<ffffffff81186631>] sys_open+0x21/0x30
[619141.143189] [<ffffffff814c9169>] system_call_fastpath+0x16/0x1b
[619141.143193] ---[ end trace 809f92614ebeaf75 ]---
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-05-16 21:30 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-16 23:42 Kernel Failure - 3.4.24 John L. Males
2013-01-27 16:14 ` Sebastian Andrzej Siewior
2013-01-28 19:57 ` Re[02]: " John L. Males
2013-01-29 21:32 ` Sebastian Andrzej Siewior
2013-01-30 18:58 ` Re[04]: " John L. Males
2014-05-16 21:30 ` Kernel Failure - 3.4.24 Similar USB MO To 3.4.89 Kernel Failure John L. Males
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).