[opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2
The last days I got more than 5 crashes with the rpmdb, and must rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, in the first case I woluld to install a rpm package. The last case was installing a package compiled in the system and created by checkinstall: rpmdb: PANIC: Argumento inválido rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) storing record libc.so.6 into Requirename rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.1.3)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libc.so.6(GLIBC_2.2)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libdl.so.2" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libdl.so.2(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libdl.so.2(GLIBC_2.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgcc_s.so.1" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgcc_s.so.1(GCC_3.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libgcc_s.so.1(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libm.so.6(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0(GLIBC_2.0)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libpthread.so.0(GLIBC_2.2)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(CXXABI_1.3)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(CXXABI_1.3.1)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(GLIBCXX_3.4)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libstdc++.so.6(GLIBCXX_3.4.9)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu_net-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_baseu_net-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_adv-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_adv-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_core-2.8.so.0" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libwx_gtk2u_core-2.8.so.0(WXU_2.8)" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "libz.so.1" records from Requirename index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Providename index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Dirnames index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Requireversion index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Provideversion index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Installtid index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Sigmd5 index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Sha1header index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Filemd5s index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery With package from the opensuse I got: error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Sep 03, 2007 at 09:45:30PM -0300, Juan Erbes wrote:
The last days I got more than 5 crashes with the rpmdb, and must rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, in the first case I woluld to install a rpm package. The last case was installing a package compiled in the system and created by checkinstall:
rpmdb: PANIC: Argumento inválido rpmdb: PANIC: fatal region error detected; run recovery [...]
Hmm, a problem with your memory chips? Please run memtest. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/9/4, Michael Schroeder <mls@suse.de>:
On Mon, Sep 03, 2007 at 09:45:30PM -0300, Juan Erbes wrote:
The last days I got more than 5 crashes with the rpmdb, and must rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, in the first case I woluld to install a rpm package. The last case was installing a package compiled in the system and created by checkinstall:
rpmdb: PANIC: Argumento inválido rpmdb: PANIC: fatal region error detected; run recovery [...]
Hmm, a problem with your memory chips? Please run memtest.
How long time I must run memtest? I runed it for many minutes, and not appear any memory error. I changed the voltage from the memorys from 1.9 to 2.1 volts as recomended by OCZ: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_ed... (This is the exact model of the memorys) Yesterday I rebuilded the rpmdb, and now after adjusting the memorys voltage, the problem continues. Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote:
How long time I must run memtest? I runed it for many minutes, and not appear any memory error.
Then your memory is good. A couple of minutes should be enough to show errors.
I changed the voltage from the memorys from 1.9 to 2.1 volts as recomended by OCZ: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_ed... (This is the exact model of the memorys) Yesterday I rebuilded the rpmdb, and now after adjusting the memorys voltage, the problem continues.
Sorry, in that case I don't know what's wrong. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/9/5, Michael Schroeder <mls@suse.de>:
On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote:
How long time I must run memtest? I runed it for many minutes, and not appear any memory error.
Then your memory is good. A couple of minutes should be enough to show errors.
I changed the voltage from the memorys from 1.9 to 2.1 volts as recomended by OCZ: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_ed... (This is the exact model of the memorys) Yesterday I rebuilded the rpmdb, and now after adjusting the memorys voltage, the problem continues.
Sorry, in that case I don't know what's wrong.
I mean that the problem with the rpmdb is derived from a file system access error, because a inmature state of the ahci driver for the SB600/RD580 chipset . For example if I do: dmesg | grep ahci ahci 0000:00:12.0: version 3.0 ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio slum part scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci For installing the the 64 bits kde version I must resizing a partition for create a new partition. It was very difficult, and the only way was starting the install process with "safe settings", because the hard disk controller has restarted from time to time (driver ahci). Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 05/09/07, Juan Erbes <jerbes@gmail.com> wrote:
2007/9/5, Michael Schroeder <mls@suse.de>:
On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote:
How long time I must run memtest? I runed it for many minutes, and not appear any memory error.
Then your memory is good. A couple of minutes should be enough to show errors.
I changed the voltage from the memorys from 1.9 to 2.1 volts as recomended by OCZ: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_ed... (This is the exact model of the memorys) Yesterday I rebuilded the rpmdb, and now after adjusting the memorys voltage, the problem continues.
Sorry, in that case I don't know what's wrong.
I mean that the problem with the rpmdb is derived from a file system access error, because a inmature state of the ahci driver for the SB600/RD580 chipset . For example if I do:
dmesg | grep ahci ahci 0000:00:12.0: version 3.0 ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio slum part scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci
For installing the the 64 bits kde version I must resizing a partition for create a new partition. It was very difficult, and the only way was starting the install process with "safe settings", because the hard disk controller has restarted from time to time (driver ahci).
Could you set your ATA controller (in BIOS) to compatibility mode? The only problem that might cause is that different modes might expose different drive geometries to the kernel, so you might not be able to switch back later on. -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/9/5, Michel Salim <michel.sylvan@gmail.com>:
On 05/09/07, Juan Erbes <jerbes@gmail.com> wrote:
2007/9/5, Michael Schroeder <mls@suse.de>:
On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote:
How long time I must run memtest? I runed it for many minutes, and not appear any memory error.
Then your memory is good. A couple of minutes should be enough to show errors.
I changed the voltage from the memorys from 1.9 to 2.1 volts as recomended by OCZ: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_ed... (This is the exact model of the memorys) Yesterday I rebuilded the rpmdb, and now after adjusting the memorys voltage, the problem continues.
Sorry, in that case I don't know what's wrong.
I mean that the problem with the rpmdb is derived from a file system access error, because a inmature state of the ahci driver for the SB600/RD580 chipset . For example if I do:
dmesg | grep ahci ahci 0000:00:12.0: version 3.0 ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio slum part scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci
For installing the the 64 bits kde version I must resizing a partition for create a new partition. It was very difficult, and the only way was starting the install process with "safe settings", because the hard disk controller has restarted from time to time (driver ahci).
Could you set your ATA controller (in BIOS) to compatibility mode? The only problem that might cause is that different modes might expose different drive geometries to the kernel, so you might not be able to switch back later on.
The system (opensuse) asumes ahci, it not depends on the bios settings. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/9/4, Michael Schroeder <mls@suse.de>:
On Mon, Sep 03, 2007 at 09:45:30PM -0300, Juan Erbes wrote:
The last days I got more than 5 crashes with the rpmdb, and must rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, in the first case I woluld to install a rpm package. The last case was installing a package compiled in the system and created by checkinstall:
rpmdb: PANIC: Argumento inválido rpmdb: PANIC: fatal region error detected; run recovery [...]
Hmm, a problem with your memory chips? Please run memtest.
I runned for new memtest for about 33 minutes, after changing the memorys voltage (rpmdb crashes again), and not appear any memory error. I tested the 2 cores of the cpu in windows with orthos http://files.extremeoverclocking.com/file.php?f=200 and not apear any cpu error About the memory bandwith with my Athlon64 X2 5200, they are: L1 cache 128 21416 MB/s L2 cache 1024 K 5321 MB/s (1024 K per core) Memory 2047 M 2916 MB/s Those values are right? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Juan Erbes -
Michael Schroeder -
Michel Salim