Mailinglist Archive: opensuse-bugs (7951 mails)

< Previous Next >
[Bug 241334] New: Failure to start SATA device on an Athlon 64 X2 (HP dc5750)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 1 Feb 2007 15:46:23 -0700 (MST)
  • Message-id: <bug-241334-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=241334

Summary: Failure to start SATA device on an Athlon 64 X2 (HP
dc5750)
Product: openSUSE 10.2
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Blocker
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: pablomme@xxxxxxxxxxxxxx
QAContact: qa@xxxxxxx


I installed the x86_64 version of openSUSE 10.2, not without issues, alongside
the 32-bit version of windows xp in my computer. After a couple of days using
it, I started getting the following during boot-up (typos are possible; I had
to copy it by hand):

ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: configured for UDMA/100
ata2: EH complete
ata2.00: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x2
ata2.00: irq_stat 0x40000001
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x25 data 8 in
ata2.00: res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x40 (internal error)
ata2: soft resetting port

This is repeated indefinitely, about once per second. The problem seems to
appear somewhat at random --sometimes the system still boots without whingeing
at all.

I'm using the kernel distributed with openSUSE 10.2, recompiled after adding a
patch from AMD to make the kernel detect and use the second CPU (the original
kernel didn't, although it was meant to include SMP support). I didn't get the
problem before patching the kernel, but it may have appeared if I had given it
time (I suppose).

My computer is an HP dc5750 (Athlon 64 X2, 1.5GB RAM), whose hard drive is a
Samsung HD160JJ/P. The SATA controller has vendor/device no. 1002/4380,
corresponding to ATI's 'SB600 Non-Raid-5 SATA'.

Is there any way of, at least, bypassing this problem by issuing appropriate
kernel boot options? Like '-choke-on-sata=no', but with a flag that the kernel
would understand?


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >