Re: Bus Error on Development Server

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTEdIVAAoJELMiOgVOfjkQeDUH/2elRgHth6uaPqOwUWGCJX93
e8U5RGkQ9+dqcGyi/5gTMWG1xQDVpH3/abRquAvqNiGrlLPR3QlsTDQBi5w7XYDr
JHE9PJcwHYPjnEnHVs/B9ZIgwTRin51mkBF3pN8YH0Pa/mpbcXP3oUODRuKZuvrM
wGNpd7zV4x7QoDn3YZuWrR1mS0sVAebcy4OxKzlq5B7IdK88N7GlyK6y0dkX796t
Z+ZajBDeFdcuvDNVpsy4hGRAQB2fJX7pgBjlAfe+r+3NJGHlG+b+4yy/6Z/SXSf2
XUPkT+ewPa/KoNExc0j3tfl8GK3sqevncJ2xHvxJV0IGDqLCQXSEdnQxaaoCd6g=
=GU56
-----END PGP SIGNATURE-----
Looks like you have a bad disc drive too, sda is throwing IO errors.

François

On Feb 28, 2014, at 10:03 PM, Thomas Lockhart <tlockhart1976@gmail.com> wrote:

> On 2/28/14 6:16 PM, Gkpetrak wrote:
>> Hello,
>>
>> I was trying to process Images with some python scripts, when I receive bus error. After that I had many bus errors on different programs.
>> Finally I tried to start django' development server, and I received the same error.
> The "after that I had many bus errors on different programs" is the clue that perhaps your physical memory has a bad spot.
>
> Your image processing might have used more physical memory than your typical computer load uses, and ended up in a bad part of memory.
>
> I would recommend running an intensive memory test (e.g. memtest86+) to isolate which memory chip is at fault, and either yank it or replace it.
>
> hth
>
> - Tom
>
>> I know that this error happens when a process is trying to access memory
>> that the CPU cannot physically address.
>>
>> I checked my log files and the output of the error is the following:
>>
>>
>> T02:13:26.879355+02:00 suse-pc kernel: [ 9976.488797] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
>>
>>
>> 2014-03-01T02:13:26.879402+02:00 suse-pc kernel: [ 9976.488806] ata1.00: irq_stat 0x40000008
>>
>>
>> 2014-03-01T02:13:26.879413+02:00 suse-pc kernel: [ 9976.488813] ata1.00: failed command: READ FPDMA QUEUED
>>
>>
>> 2014-03-01T02:13:26.879419+02:00 suse-pc kernel: [
>> 9976.488826] ata1.00: cmd 60/08:00:50:8d:75/00:00:39:00:00/40 tag 0 ncq
>> 4096 in
>>
>>
>> 2014-03-01T02:13:26.879428+02:00 suse-pc kernel: [
>> 9976.488826] res 41/40:08:51:8d:75/00:00:39:00:00/00 Emask
>> 0x409 (media
>> error) <F>
>> 2014-03-01T02:13:26.879434+02:00 suse-pc kernel: [ 9976.488832] ata1.00: status: { DRDY ERR }
>>
>>
>> 2014-03-01T02:13:26.879437+02:00 suse-pc kernel: [ 9976.488836] ata1.00: error
>> : { UNC }
>>
>>
>> 2014-03-01T02:13:26.948294+02:00 suse-pc kernel: [ 9976.557999] ata1.00: configured for UDMA/133
>>
>>
>> 2014-03-01T02:13:26.948313+02:00 suse-pc kernel: [ 9976.558034] sd 0:0:0:0: [sda] Unhandled sense code
>>
>>
>> 2014-03-01T02:13:26.948315+02:00 suse-pc kernel: [ 9976.558040] sd 0:0:0:0: [sda]
>>
>>
>> 2014-03-01T02:13:26.948316+02:00 suse-pc kernel: [ 9976.558044] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>>
>>
>> 2014-03-01T02:13:26.948317+02:00 suse-pc kernel: [ 9976.558048] sd 0:0:0:0: [sda]
>>
>>
>> 2014-03-01T02:13:26.948318+02:00 suse-pc kernel: [ 9976.558052] Sense Key : Medium Error
>> [current] [descriptor]
>>
>>
>> 2014-03-01T02:13:26.948320+02:00 suse-pc kernel: [ 9976.558059] Descriptor sense data with sense descriptors (in hex):
>>
>>
>> 2014-03-01T02:13:26.948321+02:00 suse-pc kernel: [ 9976.558062] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
>>
>>
>> 2014-03-01T02:13:26.948321+02:00 suse-pc kernel: [ 9976.558081] 39 75 8d 51
>>
>>
>> 2014-03-01T02:13:26.948335+02:00 suse-pc kernel: [ 9976.558090] sd 0:0:0:0: [sda]
>>
>>
>> 2014-03-01T02:13:26.948338+02:00 suse-pc kernel: [ 9976.558095] Add. Sense: Unrecovered read error
>> - auto reallocate failed
>>
>>
>> 2014-03-01T02:13:26.948339+02:00 suse-pc kernel: [ 9976.558099] sd 0:0:0:0: [sda] CDB:
>>
>>
>> 2014-03-01T02:13:26.948340+02:00 suse-pc kernel: [ 9976.558102] Read(10): 28 00 39 75 8d 50 00 00 08 00
>>
>>
>> 2014-03-01T02:13:26.948341+02:00 suse-pc kernel: [ 9976.558119] end_request: I/O error
>> , dev sda, sector 964005201
>>
>>
>> 2014-03-01T02:13:26.948342+02:00 suse-pc kernel: [ 9976.558207] ata1: EH complete
>>
>>
>>
>>
>>
>> Any ideas ?
>>
>> How can I fix it ?
>>
>> Regards,
>> George
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
>> To post to this group, send email to django-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/33d3ed3a-fd7a-49a4-a897-b0a80ee7c77e%40googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>
>
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/53114E0B.2090606%40gmail.com.
> For more options, visit https://groups.google.com/groups/opt_out.