Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#24560 - [kernel26] Kernel bug at fs/jbd2/transaction.c:2155
Attached to Project:
Arch Linux
Opened by Dominik Köppl (dominikk) - Friday, 03 June 2011, 13:48 GMT
Last edited by Eric Belanger (Snowman) - Monday, 01 August 2011, 16:29 GMT
Opened by Dominik Köppl (dominikk) - Friday, 03 June 2011, 13:48 GMT
Last edited by Eric Belanger (Snowman) - Monday, 01 August 2011, 16:29 GMT
|
DetailsDescription:
Performing tasks, which change the file system (like a system update with pacman) results frequently in a kernel crash, leaving the following message on screen. After the crash, the system is completely frozen, but I can use the PageUp/PageDown-Buttons of my keyboard to read the entire Bug Report. Thus I cannot submit any further information like dmesg, etc. ssh goes also down. Additional info: I'm using the same configuration as in https://bugs.archlinux.org/task/24538 It is likely that Bug 24538 is a result of this bug. As I was installing the system, pacman frequently downloaded corrupted packages showing something like :: File foobar.xz is corrupted. Do you want to delete it? [Y/n] Changing the mirror was no remedy, but trying to download the same package several times worked. Thus I assume it is likely a bug in the filesystem. Another interesting information shown in the bug report of the kernel is the appearance of my mouse as the "last sysfs file". The mouse is part of the Microsoft Wired Desktop 400. I'm using the same type of mouse on an ubuntu desktop without problems. 
SDC10480.JPG
(908.4 KiB)
SDC10481.JPG
(973.7 KiB)
SDC10482.JPG
(916.8 KiB)
SDC10483.JPG
(890.2 KiB)
SDC10484.JPG
(958 KiB)
|
This task depends upon
Closed by Eric Belanger (Snowman)
Monday, 01 August 2011, 16:29 GMT
Reason for closing: Not a bug
Additional comments about closing: Bug was a hardware bug. The SDRAM-Module was misconfigured by the BIOS to use a frequency of 133 MHz which was probably too high. Scaling down to 100 MHz resolves the problem.
Monday, 01 August 2011, 16:29 GMT
Reason for closing: Not a bug
Additional comments about closing: Bug was a hardware bug. The SDRAM-Module was misconfigured by the BIOS to use a frequency of 133 MHz which was probably too high. Scaling down to 100 MHz resolves the problem.
Example:
cp /home/gcc-4.6.0-5-i686.pkg.tar.xz /home/a
md5sum /home/gcc-4.6.0-5-i686.pkg.tar.xz
953b06e81d82c391ecc1d0a01b3e0aa3 /home/gcc-4.6.0-5-i686.pkg.tar.xz
md5sum /home/a
acf078186e4085714759327261f13c05 /home/a
It is not a harddrive error. I've tested this also with a usb-drive (fat32). Seems the filesystem-driver is corrupted.
I've reinstalled Arch Linux again - but this time it even stopped at the partitioning of my harddrive.
The '/arch/setup'-guide was trying to create an ext4-volume and suddenly stopped showing DSCF1718.JPG.
I've also tried to install Debian Lenny. Again, creating an ext4-partition fails giving a nice output: DSCF1742.JPG