Bug#610851: base: Crash at boot time
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
> Hello,
>
> I got you some log and some images.
> Sadly, all I could get for now are crappy images and empty logs as it
> seems that the logger does not have the time to start...
>
> Well, for the images, I will try to get something better than my phone
> to take pictures. But this might have to wait till tomorrow. And for the
> logs, if you have another idea than using rsyslog, I will take it.
>
> The link for the logs :
> https://documents.epfl.ch/users/h/ho/houdemer/www/kern.log.tar.bz
> The link for the pictures (~10 Mo) :
> https://documents.epfl.ch/users/h/ho/houdemer/www/images.tar
> Those pictures are taken chronologically but not all from the same
> start. There should be three different starts.
>
> Cheers.
>
> On 23/01/11 12:34, Julien Cristau wrote:
>> reassign 610851 linux-2.6
>> severity 610851 important
>> kthxbye
>>
>> On Sun, Jan 23, 2011 at 12:25:10 +0100, Charles-Henry Houdemer wrote:
>>
>>> Package: base
>>> Severity: critical
>>> Justification: breaks the whole system
>>>
>>> Hello,
>>>
>>> I have a rather serious problem here appearing after a fresh install.
>>> It happens that my system crashes at boot time. But it does so intermitently.
>>> First I will (try to) describe the symptoms, then the suspected culprit and
>>> finally an ugly way to fix it.
>>>
>>> So the symptoms :
>>> Sometimes (around 3/4 times) my debian crashes when I try to boot it. To be
>>> more precise, it happens as soon as just after the first fsck and might
>>> happen a bit later. All that I can say is that a segmentation fault appears
>>> along with its trace. And then it is impossible to do anything except a hard
>>> reboot directly on the machine or with a sysrq.
>>>
>>> The suspected culprit :
>>> My ati 4870X2. My suspitions went on it because even updating the whole
>>> system the problem remained. And also because it "could not" have been a
>>> problem coming from the installer as it was used to install the same debian
>>> on my laptop without problem. And also because the problem appeared again
>>> after a second installation.
>>>
>>> An ugly fix :
>>> My suspitions on the graphic card, I wondered if the absence of the
>>> proprietary firmware could be the cause. So I installed them. And the
>>> problem disappeared (~10 reboots without any problem). Just to be sure, I
>>> tried to remove them. And the problem is back.
>>>
>>> So if you want any additional information, I am ready to do (nearly)
>>> anything possible to help you. Have a nice day.
>>>
>> Please capture the kernel logs from this error, and/or the console
>> output (e.g. with a camera).
>>
>> Cheers,
>> Julien
Hello,
I did some pictures of a better quality and a little movie.
You can find them here :
https://documents.epfl.ch/users/h/ho/houdemer/www/photos
Also, I would like to add a little something about the logs. They are
not exactly empty. But in case of a crash, the logging daemon does not
have the time to start. So there are only logs for when the system can
actually start.
Cheers,
Charles-Henry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iF4EAREIAAYFAk09WVAACgkQJ/8FFS1xjYqmnwD/RDHSEp1Iqh9gSaNJS5gaftUV
+sCk4h4XHetR7HzcblgA/0v8J8LwsCi7AiNp2vTk8hLXph6HfNuL1qSV4pr+vskQ
=kNY6
-----END PGP SIGNATURE-----
Reply to: