|
Bugzilla – Full Text Bug Listing |
| Summary: | "ieee1394: sbp2: aborting sbp2 command" on NFORCE3 chipset with external firewire hdd | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Andreas Gleichmann <gleichmann.andreas> |
| Component: | Kernel | Assignee: | Chris L Mason <mason> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | SUSE Linux 10.1 | ||
| Hardware: | All | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Andreas Gleichmann
2005-09-18 20:23:26 UTC
Chris, anyone in your team who could have a look? Olaf knows the firewire bits the best I think. Olaf, does this error look familiar? write a 1 to /sys/module/sbp2/parameters/serialize_io and see if it goes away. Since there has been no reaction if the proposed serialize_io=1 helped and "ieee1394: sbp2: aborting sbp2 command" is even in the linux1394.org F.A.Q. ( http://www.linux1394.org/faq.php#sbp2abort ), I assume that fixed the issue. The full answer found there is this ------------------------------------------------------------------------------ Possible causes are firmware bugs of the drive, unidentified bugs in Linux, or defective hardware. Make sure the drive and bridge do not overheat, which happens easily in non-ventilated enclosures. Look for a firmware update. Alas, firmware updaters typically run on Windows or Mac OS, and some SBP-2 bridges cannot be updated at all. Try serialized sbp2 operation (see sbp2 module load parameters ). Under Linux 2.6, try the CFQ I/O scheduler: echo cfq > /sys/block/sda/queue/scheduler (Replace sda by the correct device name.) Or make CFQ the default by appending the kernel parameter "elevator=cfq" at the boot prompt or in the boot loader configuration. -------------------------------------------------------------------------------- Since the default for serialize_io has been changed to 1 in mainline since the release of 10.0, we should only see this message in 10.1 if the SBP2 bridge overheats or is defective, so I think there is not much to do for 10.1 regarding this bug. For 10.0, we could create and SDB artcile and optionally, the message could be extended from "ieee1394: sbp2: aborting sbp2 command" to "ieee1394: sbp2: aborting sbp2 command, see linux1394.org/faq.php" but since serialize_io=1 by default in 10.1, I do not account this as neccessary. Since there was no response since >3 months to the needinfo, and the fix from the FAQ is active in 10.1, and I don't see anything left do do, I'm closing this bug. |