Bus Error on Development Server

[Gkpetrak]

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.

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 

[Thomas Lockhart]

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

--
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...@googlegroups.com.
To post to this group, send email to django...@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.

[François Schiettecatte]

Looks like you have a bad disc drive too, sda is throwing IO errors.

François

> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/53114E0B.2090606%40gmail.com.

[Gkpetrak]

Hello, thank you for your quick replies.

I tried to start the development server with the GNU debugger gdb to check the error and I had the following output:

Starting program: /home/george/venv/bin/python
Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
Try: zypper install -C "debuginfo(build-id)=0a23c4e8300b31613d800697d835b384e921407e"
Missing separate debuginfo for /usr/lib64/libpython2.7.so.1.0
Try: zypper install -C "debuginfo(build-id)=296d71f2934f9c2d3ba886de2800eec20e7c962b"
Missing separate debuginfo for /lib64/libpthread.so.0
Try: zypper install -C "debuginfo(build-id)=ef5f5dbcb2398c608fef7884e1bfb65be3b5f0ef"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libc.so.6
Try: zypper install -C "debuginfo(build-id)=837f2459b5923578eb82a4b75b1f98a5faa08532"
Missing separate debuginfo for /lib64/libdl.so.2
Try: zypper install -C "debuginfo(build-id)=da368634ea211229f45d2f8d32e7da61800b4c75"
Missing separate debuginfo for /lib64/libutil.so.1
Try: zypper install -C "debuginfo(build-id)=80aa68689cd052a407891ec71329f565261589cc"
Missing separate debuginfo for /lib64/libm.so.6
Try: zypper install -C "debuginfo(build-id)=24fba01931c773fd5b4688b34c4acde47ea77cb9"
Python 2.7.3 (default, Apr 14 2012, 08:58:41) [GCC] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Missing separate debuginfo for /home/george/venv/lib64/python2.7/lib-dynload/readline.so
Try: zypper install -C "debuginfo(build-id)=5bb968f04d3f29f9101606204af80c47b2ccd318"
Missing separate debuginfo for /lib64/libreadline.so.6
Try: zypper install -C "debuginfo(build-id)=8c2147faeda30880a1e7ced012fe68264afd22d0"
Missing separate debuginfo for /lib64/libtinfo.so.5
Try: zypper install -C "debuginfo(build-id)=e6b19dfd986236e90c926ddc6d8e300034392f75"

Some info for my system:
Architecture: x86_64
CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz  (*4)
Disk: ST9500325AS (/dev/sda)
Os: OpenSuse 12.3

I think that my disk is going to die, but until then, how can I fix it ?
Any ideas ?

Thank you in advance,
George