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#38281 - system freeze (probably ethernet caused)
Attached to Project:
Arch Linux
Opened by yerzhan (yerzhan) - Thursday, 26 December 2013, 11:09 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Friday, 07 February 2014, 00:55 GMT
Opened by yerzhan (yerzhan) - Thursday, 26 December 2013, 11:09 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Friday, 07 February 2014, 00:55 GMT
|
DetailsDescription:
I have installed Archlinux on my lenovo G510 laptop. Everthing was ok but I had to restart installation because of weird problem, when it was downloading the packages (pacstrap), it suddenly started showing lines of text saying something about: atx: fatal error ... resetting It countinued for a while and then everything freezed and the screen was showing the messages (attached a picture of it). After that I reinstalled system successfully but again it happened. No messages just freezed screen (was wrokning using graphical interface). Currently I am using internet through wifi, not ethernet, hope it wont happen again. Also I tried to look at logs at /var/log folder, but I found faillog file containing only one very long line consisting of symbols "@^@^@^...." Steps to reproduce: Can't reproduce, happens at any time. 
20131225_213047.jpg
(1.88 MiB)
|
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Friday, 07 February 2014, 00:55 GMT
Reason for closing: Upstream
Additional comments about closing: Please report to upstream. Nothing to do here. Thanks.
Friday, 07 February 2014, 00:55 GMT
Reason for closing: Upstream
Additional comments about closing: Please report to upstream. Nothing to do here. Thanks.
This seems to be a bug in the driver of the wired interface. I recently experienced roughly the same thing on a SLES server. In that case, as I said, there was a bug in the interface's driver, which caused the watchdog to crash the system. Could you please try to switch back to the wired interface, and, after it crashes again, and you reboot your computer, please paste the contents of "journalctl -xn" (without quotes) in a file, and upload it here. I would be interested in the lines before the --- Reboot --- line
Thanks.