Arch Linux

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!
Tasklist

FS#19791 - Segmentation fault on boot of amd64 rc.sysinit?

Attached to Project: Arch Linux
Opened by chris_debian (chris_debian) - Monday, 14 June 2010, 15:38 GMT
Last edited by Angel Velasquez (angvp) - Wednesday, 07 July 2010, 02:50 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When I boot my amd64 box, about 30% of the time, I get a Segmentation Fault that mentions last sysfile /sys/module/mbcache/initstate

and

/etc/rc.sysinit line 291 1725 segmentation fault. It also mentions /bin/mount -a -t $NETFS -O no_netdev

I am unable to capture the output, as I have to reboot my machine to get a succesful boot.

Steps to reproduce:

Boot machine.

Sorry I can't help more. Happy to provide any info you ask for.

Thanks,

Chris.
This task depends upon

Closed by  Angel Velasquez (angvp)
Wednesday, 07 July 2010, 02:50 GMT
Reason for closing:  Implemented
Additional comments about closing:  Seems that updates fixed it, open it again in case that you can replicate the bug.
Comment by Jan de Groot (JGC) - Monday, 14 June 2010, 21:45 GMT
Since you mention segmentation faults and general protection faults, I would advise you to check your hardware using tools like memtest86.
Comment by chris_debian (chris_debian) - Tuesday, 15 June 2010, 15:19 GMT
Fair comment, Jan.

I ran memtest for 12 hours today, without any errors. Additionally, I wasn't seeing this problem before I migrated to Arch, so I'm guessing if it is a fault with a package, it is something that has been introduced with a recent version of a package, as most other distros contain older versions of the software.

Thanks,

Chris.
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 03 July 2010, 19:29 GMT
  • Field changed: Status (Unconfirmed → Waiting on Response)
all your kernel modules related to filesystem are compiled with the exact same compiler version?
Comment by chris_debian (chris_debian) - Sunday, 04 July 2010, 11:46 GMT
Gerardo,

As far as I know. All my software has been installed the same way. Is there anyway I can check?

For the last couple of boots, the problem hasn't occurred, so perhaps a software update has fixed it. Too early to say, though.

Chris.
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 04 July 2010, 17:41 GMT
Lots of packages have been update since your report so maybe, thisd is fixed by some of these...
If you do not use any external (custom) modules related to filesystem, you can ensure that all modules are compiled with the same compiler version.
Please request closure if the problem is not triggered within the next days. Thanks.
Comment by chris_debian (chris_debian) - Tuesday, 06 July 2010, 18:26 GMT
Following Gerardo's comment, I have been unable to replicate this bug, so can only assume that recent updates have fixed my problem. I am happy for this to be CLOSED and am requesting closure.

Thanks to Gerardo and Jan for the help.

Chris.

Loading...