* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
[not found] <888ef2e56b2ab414fdb72771db8d673f.squirrel@luminoussheep.net>
@ 2011-01-21 21:03 ` Andrew Morton
2011-01-21 21:49 ` Andreas Dilger
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Morton @ 2011-01-21 21:03 UTC (permalink / raw)
To: M; +Cc: Jan Kara, linux-fsdevel
On Fri, 21 Jan 2011 20:55:35 -0000 (GMT)
"M" <martin@luminoussheep.net> wrote:
> Hi,
>
> I hope I'm sending this to the right person.
I added the appropriate cc's.
> I'm getting very regular crashes on a stock 2.6.37 kernel that I've
> compiled myself. The crashes seem to regularly contain references to
> filesystem code but are difficult to capture.
>
> I was about to type but for once it was captured in the log. I was seeing
> similar issues with the previous release 2.6.36 so I'm guessing it's
> something triggering on my machine more than most peoples.
>
> Please let me know if I've sent this to the wrong person or if you need
> any more information.
>
> Jan 7 19:30:43 griffin kernel: [ 145.809827] lo: Disabled Privacy Extensions
> Jan 7 19:50:41 griffin kernel: [ 1344.008391] general protection fault: 0000 [#1] SMP
> Jan 7 19:50:41 griffin kernel: [ 1344.008482] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:39/PNP0C09:00/PNP0C0A:00/power_supply/BAT1/energy_full
> Jan 7 19:50:41 griffin kernel: [ 1344.008628] CPU 0
> Jan 7 19:50:41 griffin kernel: [ 1344.008657] Modules linked in: i915 acpi_cpufreq mperf drm_kms_helper drm i2c_algo_bit cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace parport_pc ppdev lp parport sco bnep rfcomm l2cap crc16 uinput binfmt_misc fuse firewire_sbp2 loop dm_crypt dm_mod snd_hda_codec_idt arc4 ecb snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss iwlagn btusb bluetooth snd_mixer_oss snd_pcm iwlcore snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq mac80211 cfg80211 tifm_7xx1 tifm_core snd_timer snd_seq_device snd soundcore pcmcia sony_laptop joydev i2c_i801 snd_page_alloc rfkill i2c_core yenta_socket pcmcia_rsrc video pcmcia_core psmouse shpchp pci_hotplug battery ac evdev serio_raw output button processor sg sd_mod sr_mod cdrom crc_t10dif ata_generi
c ata_piix ahci libahci libata firewire_ohci thermal scsi_mod firewire_core thermal_sys sky2 crc_itu_t uhci_hcd [last unloaded: scsi_wait_scan]
> Jan 7 19:50:41 griffin kernel: [ 1344.010171]
> Jan 7 19:50:41 griffin kernel: [ 1344.010199] Pid: 643, comm: flush-8:0 Not tainted 2.6.37 #10 VAIO /VGN-SZ680N
> Jan 7 19:50:41 griffin kernel: [ 1344.010311] RIP: 0010:[<ffffffff8114d1a6>] [<ffffffff8114d1a6>] walk_page_buffers+0x22/0x97
> Jan 7 19:50:41 griffin kernel: [ 1344.010429] RSP: 0018:ffff8801386dfaa0 EFLAGS: 00010283
> Jan 7 19:50:41 griffin kernel: [ 1344.010496] RAX: 00000000ffdca996 RBX: ffff8801229f90d0 RCX: ffd5a193ffdca797
> Jan 7 19:50:41 griffin kernel: [ 1344.010580] RDX: 0000000000000000 RSI: ffd5a193ffdca797 RDI: ffff88013bbee1b0
> Jan 7 19:50:41 griffin kernel: [ 1344.010665] RBP: ffff88013bbee1b0 R08: 0000000000000000 R09: ffffffff8114d21b
> Jan 7 19:50:41 griffin kernel: [ 1344.010749] R10: 0000000000000000 R11: 000000000000000e R12: 0000000000001000
> Jan 7 19:50:41 griffin kernel: [ 1344.010833] R13: 00000000ffb9532c R14: 00000000ffdca996 R15: 00000000ffdca996
> Jan 7 19:50:41 griffin kernel: [ 1344.010921] FS: 0000000000000000(0000) GS:ffff8800bf400000(0000) knlGS:0000000000000000
> Jan 7 19:50:41 griffin kernel: [ 1344.011019] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> Jan 7 19:50:41 griffin kernel: [ 1344.011089] CR2: 00007face71ff000 CR3: 0000000139a5c000 CR4: 00000000000006f0
> Jan 7 19:50:41 griffin kernel: [ 1344.011174] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> Jan 7 19:50:41 griffin kernel: [ 1344.011259] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Jan 7 19:50:41 griffin kernel: [ 1344.011343] Process flush-8:0 (pid: 643, threadinfo ffff8801386de000, task ffff880138a83cc0)
> Jan 7 19:50:41 griffin kernel: [ 1344.011442] Stack:
> Jan 7 19:50:41 griffin kernel: [ 1344.011472] ffffffff8114d21b 0000000000000000 0000000000000000 ffd5a193ffdca797
> Jan 7 19:50:41 griffin kernel: [ 1344.011584] 0000000000000000 ffffea0003ab1bf0 000000003bbee1b0 ffff88013bbee1b0
> Jan 7 19:50:41 griffin kernel: [ 1344.011696] ffff8801229f90d0 ffff8801386dfd40 0000000000000000 ffffffff8114dc29
> Jan 7 19:50:41 griffin kernel: [ 1344.011810] Call Trace:
> Jan 7 19:50:41 griffin kernel: [ 1344.011848] [<ffffffff8114d21b>] ? bget_one+0x0/0x7
> Jan 7 19:50:41 griffin kernel: [ 1344.011915] [<ffffffff8114dc29>] ? ext3_ordered_writepage+0x123/0x1a9
> Jan 7 19:50:41 griffin kernel: [ 1344.012001] [<ffffffff810bc2d6>] ? __writepage+0xa/0x21
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff810bd471>] ? write_cache_pages+0x221/0x321
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff810bc2cc>] ? __writepage+0x0/0x21
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110e78f>] ? writeback_single_inode+0x9a/0x1af
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110eb98>] ? writeback_sb_inodes+0x9b/0x10e
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f2e0>] ? writeback_inodes_wb+0x100/0x112
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f4ca>] ? wb_writeback+0x1d8/0x2e7
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff813617b3>] ? schedule+0x58b/0x5cb
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f745>] ? wb_do_writeback+0x16c/0x18a
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff81361bed>] ? schedule_timeout+0xa8/0xd7
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f828>] ? bdi_writeback_thread+0xc5/0x201
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f763>] ? bdi_writeback_thread+0x0/0x201
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f763>] ? bdi_writeback_thread+0x0/0x201
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8106003b>] ? kthread+0x7a/0x82
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8100a824>] ? kernel_thread_helper+0x4/0x10
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8105ffc1>] ? kthread+0x0/0x82
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8100a820>] ? kernel_thread_helper+0x0/0x10
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] Code: 5c 41 5d 41 5e 41 5f c3 90 41 57 31 c0 41 56 41 55 41 54 41 89 cc 55 48 89 fd 53 48 89 f3 48 83 ec 28 4c 8b 6e 20 45 89 ee eb 5b <48> 8b 4e 08 44 39 e0 46 8d 3c 30 48 89 4c 24 18 73 05 41 39 d5
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] RIP [<ffffffff8114d1a6>] walk_page_buffers+0x22/0x97
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] RSP <ffff8801386dfaa0>
> Jan 7 19:50:41 griffin kernel: [ 1344.039612] ---[ end trace 632f32cda7255591 ]---
hm, odd. It looks like a page's buffer_head ring got corrupted.
Do the traces all look like this? If you have other traces, please send them.
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
2011-01-21 21:03 ` PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage? Andrew Morton
@ 2011-01-21 21:49 ` Andreas Dilger
2011-01-21 22:06 ` M
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Andreas Dilger @ 2011-01-21 21:49 UTC (permalink / raw)
To: M; +Cc: Jan Kara, Linux FS Devel
On Fri, 21 Jan 2011 20:55:35 -0000 (GMT)
"M" <martin@luminoussheep.net> wrote:
> I'm getting very regular crashes on a stock 2.6.37 kernel that I've
> compiled myself. The crashes seem to regularly contain references to
> filesystem code but are difficult to capture.
>
> I was about to type but for once it was captured in the log. I was seeing
> similar issues with the previous release 2.6.36 so I'm guessing it's
> something triggering on my machine more than most peoples.
I assume from the subject that you do NOT have crashes on some other kernel version that you are running? It isn't really clear from your email. Otherwise, the first suspect in frequent and mysterious crashes is bad RAM, and running memtest86 for a couple of days is the recommended course of action.
> Please let me know if I've sent this to the wrong person or if you need
> any more information.
>
> Jan 7 19:30:43 griffin kernel: [ 145.809827] lo: Disabled Privacy Extensions
> Jan 7 19:50:41 griffin kernel: [ 1344.008391] general protection fault: 0000 [#1] SMP
> Jan 7 19:50:41 griffin kernel: [ 1344.008482] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:39/PNP0C09:00/PNP0C0A:00/power_supply/BAT1/energy_full
> Jan 7 19:50:41 griffin kernel: [ 1344.008628] CPU 0
> Jan 7 19:50:41 griffin kernel: [ 1344.008657] Modules linked in: i915 acpi_cpufreq mperf drm_kms_helper drm i2c_algo_bit cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace parport_pc ppdev lp parport sco bnep rfcomm l2cap crc16 uinput binfmt_misc fuse firewire_sbp2 loop dm_crypt dm_mod snd_hda_codec_idt arc4 ecb snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss iwlagn btusb bluetooth snd_mixer_oss snd_pcm iwlcore snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq mac80211 cfg80211 tifm_7xx1 tifm_core snd_timer snd_seq_device snd soundcore pcmcia sony_laptop joydev i2c_i801 snd_page_alloc rfkill i2c_core yenta_socket pcmcia_rsrc video pcmcia_core psmouse shpchp pci_hotplug battery ac evdev serio_raw output button processor sg sd_mod sr_mod cdrom crc_t10dif ata_generi
c ata_piix ahci libahci libata firewire_ohci thermal scsi_mod firewire_core thermal_sys sky2 crc_itu_t uhci_hcd [last unloaded: scsi_wait_scan]
> Jan 7 19:50:41 griffin kernel: [ 1344.010171]
> Jan 7 19:50:41 griffin kernel: [ 1344.010199] Pid: 643, comm: flush-8:0 Not tainted 2.6.37 #10 VAIO /VGN-SZ680N
> Jan 7 19:50:41 griffin kernel: [ 1344.010311] RIP: 0010:[<ffffffff8114d1a6>] [<ffffffff8114d1a6>] walk_page_buffers+0x22/0x97
> Jan 7 19:50:41 griffin kernel: [ 1344.010429] RSP: 0018:ffff8801386dfaa0 EFLAGS: 00010283
> Jan 7 19:50:41 griffin kernel: [ 1344.010496] RAX: 00000000ffdca996 RBX: ffff8801229f90d0 RCX: ffd5a193ffdca797
> Jan 7 19:50:41 griffin kernel: [ 1344.010580] RDX: 0000000000000000 RSI: ffd5a193ffdca797 RDI: ffff88013bbee1b0
> Jan 7 19:50:41 griffin kernel: [ 1344.010665] RBP: ffff88013bbee1b0 R08: 0000000000000000 R09: ffffffff8114d21b
> Jan 7 19:50:41 griffin kernel: [ 1344.010749] R10: 0000000000000000 R11: 000000000000000e R12: 0000000000001000
> Jan 7 19:50:41 griffin kernel: [ 1344.010833] R13: 00000000ffb9532c R14: 00000000ffdca996 R15: 00000000ffdca996
> Jan 7 19:50:41 griffin kernel: [ 1344.010921] FS: 0000000000000000(0000) GS:ffff8800bf400000(0000) knlGS:0000000000000000
> Jan 7 19:50:41 griffin kernel: [ 1344.011019] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> Jan 7 19:50:41 griffin kernel: [ 1344.011089] CR2: 00007face71ff000 CR3: 0000000139a5c000 CR4: 00000000000006f0
> Jan 7 19:50:41 griffin kernel: [ 1344.011174] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> Jan 7 19:50:41 griffin kernel: [ 1344.011259] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Jan 7 19:50:41 griffin kernel: [ 1344.011343] Process flush-8:0 (pid: 643, threadinfo ffff8801386de000, task ffff880138a83cc0)
> Jan 7 19:50:41 griffin kernel: [ 1344.011442] Stack:
> Jan 7 19:50:41 griffin kernel: [ 1344.011472] ffffffff8114d21b 0000000000000000 0000000000000000 ffd5a193ffdca797
> Jan 7 19:50:41 griffin kernel: [ 1344.011584] 0000000000000000 ffffea0003ab1bf0 000000003bbee1b0 ffff88013bbee1b0
> Jan 7 19:50:41 griffin kernel: [ 1344.011696] ffff8801229f90d0 ffff8801386dfd40 0000000000000000 ffffffff8114dc29
> Jan 7 19:50:41 griffin kernel: [ 1344.011810] Call Trace:
> Jan 7 19:50:41 griffin kernel: [ 1344.011848] [<ffffffff8114d21b>] ? bget_one+0x0/0x7
> Jan 7 19:50:41 griffin kernel: [ 1344.011915] [<ffffffff8114dc29>] ? ext3_ordered_writepage+0x123/0x1a9
> Jan 7 19:50:41 griffin kernel: [ 1344.012001] [<ffffffff810bc2d6>] ? __writepage+0xa/0x21
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff810bd471>] ? write_cache_pages+0x221/0x321
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff810bc2cc>] ? __writepage+0x0/0x21
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110e78f>] ? writeback_single_inode+0x9a/0x1af
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110eb98>] ? writeback_sb_inodes+0x9b/0x10e
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f2e0>] ? writeback_inodes_wb+0x100/0x112
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f4ca>] ? wb_writeback+0x1d8/0x2e7
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff813617b3>] ? schedule+0x58b/0x5cb
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f745>] ? wb_do_writeback+0x16c/0x18a
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff81361bed>] ? schedule_timeout+0xa8/0xd7
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f828>] ? bdi_writeback_thread+0xc5/0x201
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f763>] ? bdi_writeback_thread+0x0/0x201
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8110f763>] ? bdi_writeback_thread+0x0/0x201
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8106003b>] ? kthread+0x7a/0x82
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8100a824>] ? kernel_thread_helper+0x4/0x10
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8105ffc1>] ? kthread+0x0/0x82
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] [<ffffffff8100a820>] ? kernel_thread_helper+0x0/0x10
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] Code: 5c 41 5d 41 5e 41 5f c3 90 41 57 31 c0 41 56 41 55 41 54 41 89 cc 55 48 89 fd 53 48 89 f3 48 83 ec 28 4c 8b 6e 20 45 89 ee eb 5b <48> 8b 4e 08 44 39 e0 46 8d 3c 30 48 89 4c 24 18 73 05 41 39 d5
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] RIP [<ffffffff8114d1a6>] walk_page_buffers+0x22/0x97
> Jan 7 19:50:41 griffin kernel: [ 1344.012013] RSP <ffff8801386dfaa0>
> Jan 7 19:50:41 griffin kernel: [ 1344.039612] ---[ end trace 632f32cda7255591 ]---
Cheers, Andreas
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
2011-01-21 21:49 ` Andreas Dilger
@ 2011-01-21 22:06 ` M
2011-01-22 13:38 ` M
2011-02-12 8:01 ` martin
2 siblings, 0 replies; 7+ messages in thread
From: M @ 2011-01-21 22:06 UTC (permalink / raw)
To: Andreas Dilger; +Cc: M, Jan Kara, Linux FS Devel
> I assume from the subject that you do NOT have crashes on some other
> kernel version that you are running? It isn't really clear from your
> email. Otherwise, the first suspect in frequent and mysterious crashes is
> bad RAM, and running memtest86 for a couple of days is the recommended
> course of action.
I have no stability issues with the old debian 2.6.31.6 kernel.
I have run the memtest86 before with no issues, I will run it over night
tonight, I had considered this.
I've run a few newer kernels on this machine but I was trying some new
code from debain testing and the 2.6.36rc5 kernel was the first that
started the filesystem errors:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599118
There is another different panic attached:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=kern.log;att=1;bug=599118
The kernel before that was 2.6.34-1 (again a debian release) which was
stable except for the intel graphics driver but that's another problem and
I'm not alone there... In fact it was the graphics driver that was my
reason for running the memory test, that is somewhat improved do to a
patch but I get these filesystem panics before the graphics driver dies
now... :(
I'll do some memory testing.
Will everyone be OK with screen shots if the memory test is OK and I
capture some more.
--
Thanks,
M
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
2011-01-21 21:49 ` Andreas Dilger
2011-01-21 22:06 ` M
@ 2011-01-22 13:38 ` M
2011-02-12 8:01 ` martin
2 siblings, 0 replies; 7+ messages in thread
From: M @ 2011-01-22 13:38 UTC (permalink / raw)
To: Andreas Dilger; +Cc: Jan Kara, Linux FS Devel
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Andreas Dilger wrote:
> I assume from the subject that you do NOT have crashes on some other
> kernel version that you are running? It isn't really clear from your
> email. Otherwise, the first suspect in frequent and mysterious crashes is
> bad RAM, and running memtest86 for a couple of days is the recommended
> course of action.
OK the memtest86+ test ran for over 12 hours with no problem.
I then booted and as luck would have it got another stack trace in the
logs, please find attached.
Curiously it seems to happen under light load sometime when just browsing
the RC releases could easily be triggered with find -type f |xargs cat >
dev null but that isn't the case now.
Thanks,
M
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: kern2.log --]
[-- Type: text/x-log; name="kern2.log", Size: 7897 bytes --]
Jan 22 13:22:45 griffin kernel: [ 1872.155037] general protection fault: 0000 [#1] SMP
Jan 22 13:22:45 griffin kernel: [ 1872.155130] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:39/PNP0C09:00/PNP0C0A:00/power_supply/BAT1/energy_full
Jan 22 13:22:45 griffin kernel: [ 1872.155274] CPU 0
Jan 22 13:22:45 griffin kernel: [ 1872.155304] Modules linked in: sky2 iwlagn iwlcore mac80211 i915 drm_kms_helper drm i2c_algo_bit acpi_cpufreq mperf cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace sco parport_pc ppdev bnep lp parport rfcomm l2cap crc16 binfmt_misc uinput fuse firewire_sbp2 loop dm_crypt dm_mod arc4 ecb snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq btusb snd_timer tifm_7xx1 snd_seq_device bluetooth tifm_core snd soundcore cfg80211 joydev pcmcia snd_page_alloc video shpchp psmouse i2c_i801 sony_laptop rfkill pci_hotplug i2c_core yenta_socket pcmcia_rsrc pcmcia_core serio_raw output evdev processor battery ac button sg sd_mod crc_t10dif sr_mod cdrom ahci at
a_generic libahci ata_piix libata firewire_ohci scsi_mod firewire_core thermal crc_itu_t thermal_sys uhci_hcd [last unloaded: sky2]
Jan 22 13:22:45 griffin kernel: [ 1872.156814]
Jan 22 13:22:45 griffin kernel: [ 1872.156842] Pid: 2537, comm: chrome Not tainted 2.6.37 #10 VAIO /VGN-SZ680N
Jan 22 13:22:45 griffin kernel: [ 1872.156952] RIP: 0010:[<ffffffff81113f5a>] [<ffffffff81113f5a>] __find_get_block_slow+0x68/0xeb
Jan 22 13:22:45 griffin kernel: [ 1872.157073] RSP: 0018:ffff8801393b19b8 EFLAGS: 00010287
Jan 22 13:22:45 griffin kernel: [ 1872.157140] RAX: 0000000000000001 RBX: ffffea00040195a8 RCX: fffafafafffafa20
Jan 22 13:22:45 griffin kernel: [ 1872.157226] RDX: ffff88013314f6e8 RSI: 0000000000000003 RDI: ffff88013babcf78
Jan 22 13:22:45 griffin kernel: [ 1872.157312] RBP: ffff88013babcf08 R08: 0000000000000015 R09: 00000000000001c0
Jan 22 13:22:45 griffin kernel: [ 1872.157396] R10: ffff880139929800 R11: ffff8801315369c0 R12: ffff88013babcde0
Jan 22 13:22:45 griffin kernel: [ 1872.157481] R13: 0000000005470050 R14: fffafafafffafafa R15: 000000000151c4ed
Jan 22 13:22:45 griffin kernel: [ 1872.157567] FS: 00007fbdbe0c5710(0000) GS:ffff8800bf400000(0000) knlGS:0000000000000000
Jan 22 13:22:45 griffin kernel: [ 1872.157665] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 22 13:22:45 griffin kernel: [ 1872.157735] CR2: 00007f7cf4041000 CR3: 0000000123016000 CR4: 00000000000006f0
Jan 22 13:22:45 griffin kernel: [ 1872.157821] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 22 13:22:45 griffin kernel: [ 1872.157906] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 22 13:22:45 griffin kernel: [ 1872.157991] Process chrome (pid: 2537, threadinfo ffff8801393b0000, task ffff88013846a880)
Jan 22 13:22:45 griffin kernel: [ 1872.158088] Stack:
Jan 22 13:22:45 griffin kernel: [ 1872.158119] 0000000000000000 ffff8800bf4109a0 0000000000001000 0000000005470050
Jan 22 13:22:45 griffin kernel: [ 1872.158233] 0000000005470050 ffffffff8111438c ffff88013babcf08 ffff88013babcde0
Jan 22 13:22:45 griffin kernel: [ 1872.158346] 000000000552a985 ffffffff810603b3 0000000000000000 ffffffff8116658d
Jan 22 13:22:45 griffin kernel: [ 1872.158459] Call Trace:
Jan 22 13:22:45 griffin kernel: [ 1872.158498] [<ffffffff8111438c>] ? __find_get_block+0x99/0x175
Jan 22 13:22:45 griffin kernel: [ 1872.158575] [<ffffffff810603b3>] ? bit_waitqueue+0x14/0xa1
Jan 22 13:22:45 griffin kernel: [ 1872.158647] [<ffffffff8116658d>] ? __journal_file_buffer+0xc2/0x161
Jan 22 13:22:45 griffin kernel: [ 1872.158728] [<ffffffff81114484>] ? __getblk+0x1c/0x2d4
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff8114e398>] ? __ext3_get_inode_loc+0xed/0x29a
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff8114e580>] ? ext3_reserve_inode_write+0x23/0x7c
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff81167ea4>] ? journal_get_write_access+0x2d/0x39
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff8114e5fa>] ? ext3_mark_inode_dirty+0x21/0x3c
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff81152339>] ? add_dirent_to_buf+0x26a/0x2b1
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff81152896>] ? ext3_add_entry+0x516/0x8a4
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff8114e60c>] ? ext3_mark_inode_dirty+0x33/0x3c
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff8114ceec>] ? ext3_new_inode+0x8c7/0x91a
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff81153262>] ? ext3_add_nondir+0x18/0x5d
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff81153789>] ? ext3_create+0xda/0x11b
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff810fc480>] ? vfs_create+0x66/0x88
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff810fce2a>] ? do_last+0x25f/0x526
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff810fea9d>] ? do_filp_open+0x1e2/0x538
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff810f1f80>] ? do_sys_open+0x56/0xde
Jan 22 13:22:45 griffin kernel: [ 1872.158774] [<ffffffff81009a12>] ? system_call_fastpath+0x16/0x1b
Jan 22 13:22:45 griffin kernel: [ 1872.158774] Code: 7d 70 e8 de eb 24 00 48 8b 03 f6 c4 08 0f 84 80 00 00 00 48 8b 03 f6 c4 08 75 04 0f 0b eb fe 48 8b 53 10 b8 01 00 00 00 49 89 d6 <49> 8b 0e 80 e1 20 74 0d 4d 39 6e 18 75 09 f0 41 ff 46 60 eb 56
Jan 22 13:22:45 griffin kernel: [ 1872.158774] RIP [<ffffffff81113f5a>] __find_get_block_slow+0x68/0xeb
Jan 22 13:22:45 griffin kernel: [ 1872.158774] RSP <ffff8801393b19b8>
Jan 22 13:22:45 griffin kernel: [ 1872.180195] ---[ end trace 3663bbde1886819e ]---
Jan 22 13:26:39 griffin kernel: [ 2106.187411] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) dump-ftrace-buffer(Z)
Jan 22 13:26:41 griffin kernel: [ 2107.451726] SysRq : Emergency Sync
Jan 22 13:26:41 griffin kernel: [ 2107.452766] Emergency Sync complete
Jan 22 13:26:41 griffin kernel: [ 2107.748624] SysRq : Emergency Sync
Jan 22 13:26:41 griffin kernel: [ 2107.749084] Emergency Sync complete
Jan 22 13:26:41 griffin kernel: [ 2107.907294] SysRq : Emergency Sync
Jan 22 13:26:41 griffin kernel: [ 2107.907614] Emergency Sync complete
Jan 22 13:26:43 griffin kernel: [ 2110.000820] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) dump-ftrace-buffer(Z)
Jan 22 13:26:44 griffin kernel: [ 2110.466616] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) dump-ftrace-buffer(Z)
Jan 22 13:26:44 griffin kernel: [ 2111.249770] SysRq : Emergency Sync
Jan 22 13:26:44 griffin kernel: [ 2111.250206] Emergency Sync complete
Jan 22 13:26:45 griffin kernel: [ 2111.459629] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb(V) show-blocked-tasks(W) dump-ftrace-buffer(Z)
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
2011-01-21 21:49 ` Andreas Dilger
2011-01-21 22:06 ` M
2011-01-22 13:38 ` M
@ 2011-02-12 8:01 ` martin
2 siblings, 0 replies; 7+ messages in thread
From: martin @ 2011-02-12 8:01 UTC (permalink / raw)
To: Andreas Dilger; +Cc: Jan Kara, Linux FS Devel
On 21/01/11 21:49, Andreas Dilger wrote:
> On Fri, 21 Jan 2011 20:55:35 -0000 (GMT)
> "M"<martin@luminoussheep.net> wrote:
>
>> I'm getting very regular crashes on a stock 2.6.37 kernel that I've
>> compiled myself. The crashes seem to regularly contain references to
>> filesystem code but are difficult to capture.
>>
>> I was about to type but for once it was captured in the log. I was seeing
>> similar issues with the previous release 2.6.36 so I'm guessing it's
>> something triggering on my machine more than most peoples.
>>
> I assume from the subject that you do NOT have crashes on some other kernel version that you are running? It isn't really clear from your email. Otherwise, the first suspect in frequent and mysterious crashes is bad RAM, and running memtest86 for a couple of days is the recommended course of action.
>
Good news, though memtest86 wasn't showing any errors I tried my laptop
with some other memory and it's working fine now even the graphics
problems have gone away.
Sorry to trouble you with these reports, many thanks for the advice.
Not quite sure why the memory isn't failing the test program but I'll
try a few more things...
--
M
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
@ 2011-01-21 21:27 M
2011-01-21 21:45 ` Andrew Morton
0 siblings, 1 reply; 7+ messages in thread
From: M @ 2011-01-21 21:27 UTC (permalink / raw)
To: Andrew Morton; +Cc: Jan Kara, linux-fsdevel
> Do the traces all look like this? If you have other traces, please send
them.
They seem fairly regular but for some reason more often than not don't end
up in the log, this is the only one I have so far.
I've tried a serial dongle but I can't seem to get the kernel parameter to
set the speed.
I have:
console=ttyUSB0,9600n8r console=tty
And without it I can use minicom to test and the port works fine with it I
just get some garbage... Any ideas? I've also built in usb and the usb
dongle support (i.e. not a module).
Would it be worth my time typing in a transcript? It looks quite a lot to
type and would be error prone :( but if another trace would make the
difference. I'd give it a go.
--
Thanks,
M
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
2011-01-21 21:27 M
@ 2011-01-21 21:45 ` Andrew Morton
0 siblings, 0 replies; 7+ messages in thread
From: Andrew Morton @ 2011-01-21 21:45 UTC (permalink / raw)
To: M; +Cc: Jan Kara, linux-fsdevel
On Fri, 21 Jan 2011 21:27:58 -0000 (GMT)
"M" <martin@luminoussheep.net> wrote:
> > Do the traces all look like this? If you have other traces, please send
> them.
>
> They seem fairly regular but for some reason more often than not don't end
> up in the log, this is the only one I have so far.
>
> I've tried a serial dongle but I can't seem to get the kernel parameter to
> set the speed.
> I have:
> console=ttyUSB0,9600n8r console=tty
>
> And without it I can use minicom to test and the port works fine with it I
> just get some garbage... Any ideas? I've also built in usb and the usb
> dongle support (i.e. not a module).
hm, capturing oopses over USB is likely to be problematic - there's a
heck of a lot of software involved :( I've never tried it.
> Would it be worth my time typing in a transcript? It looks quite a lot to
> type and would be error prone :( but if another trace would make the
> difference. I'd give it a go.
Cellphone photographs work well.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-02-12 8:01 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <888ef2e56b2ab414fdb72771db8d673f.squirrel@luminoussheep.net>
2011-01-21 21:03 ` PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage? Andrew Morton
2011-01-21 21:49 ` Andreas Dilger
2011-01-21 22:06 ` M
2011-01-22 13:38 ` M
2011-02-12 8:01 ` martin
2011-01-21 21:27 M
2011-01-21 21:45 ` Andrew Morton
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).