Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Hmm, I wonder if this had something to do with it: > [ 25.856573] VFS: Disk quotas dquot_6.5.1 Was the system still pingable? Regards, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Hmm, I wonder if this had something to do with it: [ 25.856573] VFS: Disk quotas dquot_6.5.1 Was the system still pingable? Regards, Daniel -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Hi all, Thanks all. After lots of testing, I isolated the problem to one of the memory modules. Thought it might have been a kernel problem as I thought memtest should be exhaustive enough considering I ran it for so long, but apparently not... Even now, the bad module still does not show any errors in memtest... Thanks, Yucheng Ray Lee wrote: > On 9/19/07, Low Yucheng <[EMAIL PROTECTED]> wrote: > >> [1.] Summary >> System Freeze on Particular workload with kernel 2.6.22.6 >> >> [2.] Description >> System freezes on repeated application of the following command >> for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done >> >> Problem is consistent and repeatable. >> Problem persists when running on a different drive, and also in pure console >> (no X). >> >> One time, the following error logged in syslog: >> Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert >> Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset >> entry ff00 >> Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset >> entry 0300 >> Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset >> entry 0200 >> Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset >> entry ff00 >> Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset >> entry ff00 >> Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset >> entry 0100 >> >> Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no >> errors. >> Should not be a CPU problem either. I have been running CPU intensive tasks >> for days. >> > > The "Unused swap offset entry" is almost always a sign of bad memory, > if google can be trusted. Your workload is *extremely* CPU and memory > intensive (and even hits the disk!), so this looks like bad RAM, bad > cooling, or a marginal power supply that is failing under load. > > memtest86+ doesn't stress the CPU nearly as much, so it often doesn't > show all the problems. > > Take your RAM down to one stick and try again (looks like you have 2G > installed?). If that still fails, try different RAM. If that still > fails, then swap out the power supply for another if you can, and try > again. > > Ray > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
On 9/19/07, Low Yucheng <[EMAIL PROTECTED]> wrote: > [1.] Summary > System Freeze on Particular workload with kernel 2.6.22.6 > > [2.] Description > System freezes on repeated application of the following command > for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done > > Problem is consistent and repeatable. > Problem persists when running on a different drive, and also in pure console > (no X). > > One time, the following error logged in syslog: > Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert > Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset > entry ff00 > Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset > entry 0300 > Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset > entry 0200 > Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset > entry ff00 > Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset > entry ff00 > Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset > entry 0100 > > Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no > errors. > Should not be a CPU problem either. I have been running CPU intensive tasks > for days. The "Unused swap offset entry" is almost always a sign of bad memory, if google can be trusted. Your workload is *extremely* CPU and memory intensive (and even hits the disk!), so this looks like bad RAM, bad cooling, or a marginal power supply that is failing under load. memtest86+ doesn't stress the CPU nearly as much, so it often doesn't show all the problems. Take your RAM down to one stick and try again (looks like you have 2G installed?). If that still fails, try different RAM. If that still fails, then swap out the power supply for another if you can, and try again. Ray - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
On Thu, Sep 20, 2007 at 12:00:31PM +0200, Jarek Poplawski wrote: > On 19-09-2007 21:25, Ahmed S. Darwish wrote: > > Hi Low, > > > > On Wed, Sep 19, 2007 at 12:16:39PM -0400, Low Yucheng wrote: > >> There are no additional console messages. > >> Not sure what this is: * no relevant Cc (memory management added) > > > > Relevant CCs means CCing maintainers or subsystem mailing lists related to > > your > > bug report. i.e, if it's a networking bug, you need to CC the linux kernel > > networking mailing list. If it's a kobject bug, you need to CC its > > maintainer > > (Greg) and so on. > > So, which one do you recommend here? > I'm not really sure, just wanted to solve Jarek's confusion :). Regards, -- Ahmed S. Darwish HomePage: http://darwish.07.googlepages.com Blog: http://darwish-07.blogspot.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
On 19-09-2007 21:25, Ahmed S. Darwish wrote: > Hi Low, > > On Wed, Sep 19, 2007 at 12:16:39PM -0400, Low Yucheng wrote: >> There are no additional console messages. >> Not sure what this is: * no relevant Cc (memory management added) > > Relevant CCs means CCing maintainers or subsystem mailing lists related to > your > bug report. i.e, if it's a networking bug, you need to CC the linux kernel > networking mailing list. If it's a kobject bug, you need to CC its maintainer > (Greg) and so on. So, which one do you recommend here? Regards, Jarek P. PS#1: I don't think we should require from users so much expertise in bug reporting: after a few questions cc-ing should be no problem here. PS#2: Low Yucheng: maybe it's something else, but it seems your swap could be bigger for this amount of memory. (You could try to monitor this e.g. with "top" running in another console window.) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
On 19-09-2007 21:25, Ahmed S. Darwish wrote: Hi Low, On Wed, Sep 19, 2007 at 12:16:39PM -0400, Low Yucheng wrote: There are no additional console messages. Not sure what this is: * no relevant Cc (memory management added) Relevant CCs means CCing maintainers or subsystem mailing lists related to your bug report. i.e, if it's a networking bug, you need to CC the linux kernel networking mailing list. If it's a kobject bug, you need to CC its maintainer (Greg) and so on. So, which one do you recommend here? Regards, Jarek P. PS#1: I don't think we should require from users so much expertise in bug reporting: after a few questions cc-ing should be no problem here. PS#2: Low Yucheng: maybe it's something else, but it seems your swap could be bigger for this amount of memory. (You could try to monitor this e.g. with top running in another console window.) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
On 9/19/07, Low Yucheng [EMAIL PROTECTED] wrote: [1.] Summary System Freeze on Particular workload with kernel 2.6.22.6 [2.] Description System freezes on repeated application of the following command for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done Problem is consistent and repeatable. Problem persists when running on a different drive, and also in pure console (no X). One time, the following error logged in syslog: Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset entry 0300 Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset entry 0200 Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset entry 0100 Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no errors. Should not be a CPU problem either. I have been running CPU intensive tasks for days. The Unused swap offset entry is almost always a sign of bad memory, if google can be trusted. Your workload is *extremely* CPU and memory intensive (and even hits the disk!), so this looks like bad RAM, bad cooling, or a marginal power supply that is failing under load. memtest86+ doesn't stress the CPU nearly as much, so it often doesn't show all the problems. Take your RAM down to one stick and try again (looks like you have 2G installed?). If that still fails, try different RAM. If that still fails, then swap out the power supply for another if you can, and try again. Ray - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Hi all, Thanks all. After lots of testing, I isolated the problem to one of the memory modules. Thought it might have been a kernel problem as I thought memtest should be exhaustive enough considering I ran it for so long, but apparently not... Even now, the bad module still does not show any errors in memtest... Thanks, Yucheng Ray Lee wrote: On 9/19/07, Low Yucheng [EMAIL PROTECTED] wrote: [1.] Summary System Freeze on Particular workload with kernel 2.6.22.6 [2.] Description System freezes on repeated application of the following command for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done Problem is consistent and repeatable. Problem persists when running on a different drive, and also in pure console (no X). One time, the following error logged in syslog: Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset entry 0300 Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset entry 0200 Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset entry 0100 Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no errors. Should not be a CPU problem either. I have been running CPU intensive tasks for days. The Unused swap offset entry is almost always a sign of bad memory, if google can be trusted. Your workload is *extremely* CPU and memory intensive (and even hits the disk!), so this looks like bad RAM, bad cooling, or a marginal power supply that is failing under load. memtest86+ doesn't stress the CPU nearly as much, so it often doesn't show all the problems. Take your RAM down to one stick and try again (looks like you have 2G installed?). If that still fails, try different RAM. If that still fails, then swap out the power supply for another if you can, and try again. Ray - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Hi Low, On Wed, Sep 19, 2007 at 12:16:39PM -0400, Low Yucheng wrote: > There are no additional console messages. > Not sure what this is: * no relevant Cc (memory management added) Relevant CCs means CCing maintainers or subsystem mailing lists related to your bug report. i.e, if it's a networking bug, you need to CC the linux kernel networking mailing list. If it's a kobject bug, you need to CC its maintainer (Greg) and so on. Regards, -- Ahmed S. Darwish HomePage: http://darwish.07.googlepages.com Blog: http://darwish-07.blogspot.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
* Wed, 19 Sep 2007 04:45:17 -0400 > > [1.] Summary > System Freeze on Particular workload with kernel 2.6.22.6 > > [2.] Description > System freezes on repeated application of the following command > for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done > > Problem is consistent and repeatable. > Problem persists when running on a different drive, and also in pure console > (no X). > > One time, the following error logged in syslog: > Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert > Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset > entry ff00 > Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset > entry 0300 > Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset > entry 0200 > Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset > entry ff00 > Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset > entry ff00 > Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset > entry 0100 > > Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no > errors. > Should not be a CPU problem either. I have been running CPU intensive tasks > for days. > > [3.] Keywords > freeze, swap_free,VM Nice bug report, seems like from linux-source/REPORTING-BUGS. But still: * no relevant Cc (memory management added) + no output of `mount` (because if swap is on some file system, that *can* be another problem) + no information about amount of memory and its BIOS configuration FYI, latter two (and much more) is one `dmesg` output. This output, together with any other kernel information can be gathered by serial or net consoles: linux-source/Documentation/serial-console.txt linux-source/Documentation/networking/netconsole.txt If console messages after freeze can be seen in text mode VGA/CRT also, photos of it somewhere on ftp will be OK. > [4.] /proc/version > Linux version 2.6.22.6intelcore2 ([EMAIL PROTECTED]) (gcc version 4.1.2 > (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Sat Sep 15 00:29:00 EDT 2007 > > [5.] No Oops > > [6.] Trigger > - Create a large number of png images. (a few hundred) > > - repeatedly run > for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done > > - This might be subjective, but the freeze seems to show up sooner if there > is a CPU heavy > process running in the background. > > [7] Environment > [7.1] Software /script/ver_linux > > Linux mossnew 2.6.22.6intelcore2 #1 SMP Sat Sep 15 00:29:00 EDT 2007 x86_64 > GNU/Linux > [] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
[1.] Summary System Freeze on Particular workload with kernel 2.6.22.6 [2.] Description System freezes on repeated application of the following command for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done Problem is consistent and repeatable. Problem persists when running on a different drive, and also in pure console (no X). One time, the following error logged in syslog: Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset entry 0300 Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset entry 0200 Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset entry 0100 Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no errors. Should not be a CPU problem either. I have been running CPU intensive tasks for days. [3.] Keywords freeze, swap_free,VM [4.] /proc/version Linux version 2.6.22.6intelcore2 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Sat Sep 15 00:29:00 EDT 2007 [5.] No Oops [6.] Trigger - Create a large number of png images. (a few hundred) - repeatedly run for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done - This might be subjective, but the freeze seems to show up sooner if there is a CPU heavy process running in the background. [7] Environment [7.1] Software /script/ver_linux Linux mossnew 2.6.22.6intelcore2 #1 SMP Sat Sep 15 00:29:00 EDT 2007 x86_64 GNU/Linux Gnu C 4.1.2 Gnu make 3.81 binutils 2.17.50 util-linux 2.12r mount 2.12r module-init-tools 3.3-pre2 e2fsprogs 1.40-WIP reiserfsprogs 3.6.19 pcmciautils014 PPP2.4.4 Linux C Library> libc.2.5 Dynamic linker (ldd) 2.5 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 udev 108 wireless-tools 28 Modules Loaded isofs udf binfmt_misc ipv6 ppdev ac sbs battery video dock button container af_packet nls_iso8859_1 nls_cp437 vfat fat nls_utf8 ntfs w83627ehf i2c_isa i2c_core coretemp sbp2 parport_pc lp parport fuse snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq atl1 snd_timer snd_seq_device sr_mod cdrom mii psmouse snd pcspkr soundcore snd_page_alloc shpchp pci_hotplug serio_raw intel_agp tsdev evdev ext3 jbd mbcache usb_storage sg sd_mod generic usbhid hid ata_piix libusual ohci1394 ieee1394 floppy ata_generic libata scsi_mod ehci_hcd uhci_hcd usbcore thermal processor fan [7.2] Processor information processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping: 11 cpu MHz : 2671.602 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5346.72 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping: 11 cpu MHz : 2671.602 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5343.20 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: [7.3] Module info isofs 39268 1 - Live 0x883ac000 udf 90088 0 - Live 0x88395000 binfmt_misc 14604 1 - Live 0x8839 ipv6 313320 12 - Live 0x88342000 ppdev 11016 0 - Live 0x8833e000 ac 6984 0 - Live 0x8833b000 sbs 21200 0 - Live 0x88334000 battery 12168 0 - Live 0x8833 video 20240 0 - Live 0x8832a000 dock 12072 0 - Live 0x88326000
PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
[1.] Summary System Freeze on Particular workload with kernel 2.6.22.6 [2.] Description System freezes on repeated application of the following command for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done Problem is consistent and repeatable. Problem persists when running on a different drive, and also in pure console (no X). One time, the following error logged in syslog: Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset entry 0300 Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset entry 0200 Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset entry 0100 Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no errors. Should not be a CPU problem either. I have been running CPU intensive tasks for days. [3.] Keywords freeze, swap_free,VM [4.] /proc/version Linux version 2.6.22.6intelcore2 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Sat Sep 15 00:29:00 EDT 2007 [5.] No Oops [6.] Trigger - Create a large number of png images. (a few hundred) - repeatedly run for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done - This might be subjective, but the freeze seems to show up sooner if there is a CPU heavy process running in the background. [7] Environment [7.1] Software /script/ver_linux Linux mossnew 2.6.22.6intelcore2 #1 SMP Sat Sep 15 00:29:00 EDT 2007 x86_64 GNU/Linux Gnu C 4.1.2 Gnu make 3.81 binutils 2.17.50 util-linux 2.12r mount 2.12r module-init-tools 3.3-pre2 e2fsprogs 1.40-WIP reiserfsprogs 3.6.19 pcmciautils014 PPP2.4.4 Linux C Library libc.2.5 Dynamic linker (ldd) 2.5 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 udev 108 wireless-tools 28 Modules Loaded isofs udf binfmt_misc ipv6 ppdev ac sbs battery video dock button container af_packet nls_iso8859_1 nls_cp437 vfat fat nls_utf8 ntfs w83627ehf i2c_isa i2c_core coretemp sbp2 parport_pc lp parport fuse snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq atl1 snd_timer snd_seq_device sr_mod cdrom mii psmouse snd pcspkr soundcore snd_page_alloc shpchp pci_hotplug serio_raw intel_agp tsdev evdev ext3 jbd mbcache usb_storage sg sd_mod generic usbhid hid ata_piix libusual ohci1394 ieee1394 floppy ata_generic libata scsi_mod ehci_hcd uhci_hcd usbcore thermal processor fan [7.2] Processor information processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping: 11 cpu MHz : 2671.602 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5346.72 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping: 11 cpu MHz : 2671.602 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 5343.20 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: [7.3] Module info isofs 39268 1 - Live 0x883ac000 udf 90088 0 - Live 0x88395000 binfmt_misc 14604 1 - Live 0x8839 ipv6 313320 12 - Live 0x88342000 ppdev 11016 0 - Live 0x8833e000 ac 6984 0 - Live 0x8833b000 sbs 21200 0 - Live 0x88334000 battery 12168 0 - Live 0x8833 video 20240 0 - Live 0x8832a000 dock 12072 0 - Live 0x88326000
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
* Wed, 19 Sep 2007 04:45:17 -0400 [1.] Summary System Freeze on Particular workload with kernel 2.6.22.6 [2.] Description System freezes on repeated application of the following command for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done Problem is consistent and repeatable. Problem persists when running on a different drive, and also in pure console (no X). One time, the following error logged in syslog: Sep 19 04:22:11 mossnew kernel: [ 301.883919] VM: killing process convert Sep 19 04:22:11 mossnew kernel: [ 301.884382] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884421] swap_free: Unused swap offset entry 0300 Sep 19 04:22:11 mossnew kernel: [ 301.884456] swap_free: Unused swap offset entry 0200 Sep 19 04:22:11 mossnew kernel: [ 301.884491] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884527] swap_free: Unused swap offset entry ff00 Sep 19 04:22:11 mossnew kernel: [ 301.884562] swap_free: Unused swap offset entry 0100 Should not be a RAM problem. RAM has survived 12 hrs of Memtest with no errors. Should not be a CPU problem either. I have been running CPU intensive tasks for days. [3.] Keywords freeze, swap_free,VM Nice bug report, seems like from linux-source/REPORTING-BUGS. But still: * no relevant Cc (memory management added) + no output of `mount` (because if swap is on some file system, that *can* be another problem) + no information about amount of memory and its BIOS configuration FYI, latter two (and much more) is one `dmesg` output. This output, together with any other kernel information can be gathered by serial or net consoles: linux-source/Documentation/serial-console.txt linux-source/Documentation/networking/netconsole.txt If console messages after freeze can be seen in text mode VGA/CRT also, photos of it somewhere on ftp will be OK. [4.] /proc/version Linux version 2.6.22.6intelcore2 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 SMP Sat Sep 15 00:29:00 EDT 2007 [5.] No Oops [6.] Trigger - Create a large number of png images. (a few hundred) - repeatedly run for f in *png ; do convert -quality 100 $f `basename $f png`jpg; done - This might be subjective, but the freeze seems to show up sooner if there is a CPU heavy process running in the background. [7] Environment [7.1] Software /script/ver_linux Linux mossnew 2.6.22.6intelcore2 #1 SMP Sat Sep 15 00:29:00 EDT 2007 x86_64 GNU/Linux [] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: System Freeze on Particular workload with kernel 2.6.22.6
Hi Low, On Wed, Sep 19, 2007 at 12:16:39PM -0400, Low Yucheng wrote: There are no additional console messages. Not sure what this is: * no relevant Cc (memory management added) Relevant CCs means CCing maintainers or subsystem mailing lists related to your bug report. i.e, if it's a networking bug, you need to CC the linux kernel networking mailing list. If it's a kobject bug, you need to CC its maintainer (Greg) and so on. Regards, -- Ahmed S. Darwish HomePage: http://darwish.07.googlepages.com Blog: http://darwish-07.blogspot.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
