FS#25752 - [libx11]

Attached to Project: Arch Linux
Opened by Hector Urbina (ajendrex) - Thursday, 25 August 2011, 12:24 GMT
Last edited by Jan de Groot (JGC) - Monday, 17 October 2011, 14:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
kernel panic when installing this package, installation is unsuccsessfull.

Additional info:
* package version: 1.4.4-1
attached a picture of the error


Steps to reproduce:
(as root)
pacman -S libx11
   libx11-kernel-panic.png (1.08 MiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 17 October 2011, 14:34 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Corruption issue in filesystem.
Comment by Jan de Groot (JGC) - Thursday, 25 August 2011, 14:39 GMT
Not a bug in libx11. Please boot from a livecd and run reiserfsck on your filesystem, your filesystem looks broken.
Comment by Hector Urbina (ajendrex) - Thursday, 25 August 2011, 15:54 GMT
No corruptions found in any of my reiserfs file systems. Installation of libx11 (try of) keeps giving kernel panic.
Do you have some other ideas?

Thanks for your help,

Héctor.
Comment by Hector Urbina (ajendrex) - Thursday, 25 August 2011, 16:46 GMT
Comment by Jan de Groot (JGC) - Friday, 26 August 2011, 07:48 GMT
Installing libx11 panics your kernel because reiserfs is doing something wrong with the files affected by upgrading libx11. This is either a filesystem bug, or a bug in the reiserfs filesystem driver.

So far I've googled for your vs-6030 message, lots of hits on google, but besides checking your hardware and filesystems for errors, there's not much detailed information about how to solve this problem. You should forward this to the reiserfs mailinglist to get it solved.
Comment by Jelle van der Waa (jelly) - Monday, 17 October 2011, 08:09 GMT
Any update?
Comment by Hector Urbina (ajendrex) - Monday, 17 October 2011, 14:17 GMT
Yep,

Sorry I didn't report it before. The command reiserfsck --check wasn't reporting any error. However, reiserfsck --rebuild-tree (which takes a long time) did found errors and fixed them. This kernel panic error was gone after that.

Loading...