How get SCSI working after ACPI malfunction?

Asked by markling on 2016-02-07

My SCSI failed without warning and for no apparent reason.

How can I recover it?

Having previously been fine, my machine now fails to boot when I switch it on with my scsi device connected.

It reports some boot messages (edited):

ACPI PCC Probe Failed
Starting Version 219

Worker[139] /devices/pci000:00 ... etc
SCSI timing out command, waited 82s
... devices/pci .... timeout kill it
... seq 987 /devices/pci killed
... INFO: task systemd-udevd:139 blocked for more than 120 seconds
module len 27812 truncated
INFO: task sh blocked for more than 120 seconds
INFO: task alsactl:468 blocked for more than 120 seconds
INFO: task apparmor: 474 blocked for more than 120 seconds

and so on.

Here's what looks like a relevant section from kern.log:

Feb 7 22:08:58 zammo kernel: [ 10.846041] scsi host4: Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
Feb 7 22:08:58 zammo kernel: [ 10.846041] <Adaptec aic7850 SCSI adapter>
Feb 7 22:08:58 zammo kernel: [ 10.846041] aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs
Feb 7 22:08:58 zammo kernel: [ 10.846041]
Feb 7 22:08:58 zammo kernel: [ 60.535354] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
Feb 7 22:08:58 zammo kernel: [ 64.555112] lp: driver loaded but no devices found
Feb 7 22:08:58 zammo kernel: [ 64.638863] ppdev: user-space parallel port driver
Feb 7 22:08:58 zammo kernel: [ 64.724900] parport_pc 00:03: reported by Plug and Play ACPI
Feb 7 22:08:58 zammo kernel: [ 64.724948] parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]
Feb 7 22:08:58 zammo kernel: [ 64.807286] lp0: using parport0 (interrupt-driven).
Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: Firmware space is locked read-only. If you can't or
Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: don't want to disable this in firmware setup, and if
Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: you are certain that your system has a functional
Feb 7 22:08:58 zammo kernel: [ 70.374056] intel_rng: RNG, try using the 'no_fwh_detect' option.
Feb 7 22:08:58 zammo kernel: [ 70.387710] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Feb 7 22:08:58 zammo kernel: [ 70.505366] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082f conflicts with OpRegion 0x000000000000082a-0x000000000000082a (\GIC3) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505380] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082f conflicts with OpRegion 0x000000000000082b-0x000000000000082b (\GIC2) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505389] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082f conflicts with OpRegion 0x0000000000000828-0x000000000000082d (\GLBC) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505398] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082f conflicts with OpRegion 0x000000000000082a-0x000000000000082a (\SACT) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505405] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082f conflicts with OpRegion 0x0000000000000828-0x0000000000000828 (\SSTS) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505413] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 7 22:08:58 zammo kernel: [ 70.505419] ACPI Warning: SystemIO range 0x00000000000008b0-0x00000000000008bf conflicts with OpRegion 0x00000000000008b8-0x00000000000008b8 (\GHI0) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505427] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 7 22:08:58 zammo kernel: [ 70.505432] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008af conflicts with OpRegion 0x000000000000088e-0x000000000000088e (\GIC1) (20141107/utaddress-258)
Feb 7 22:08:58 zammo kernel: [ 70.505441] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Feb 7 22:08:58 zammo kernel: [ 70.505445] lpc_ich: Resource conflict(s) found affecting gpio_ich

--------------------------------------
Description: Ubuntu 15.04
Release: 15.04
--------------------------------------

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu boost-defaults Edit question
Assignee:
No assignee Edit question
Last query:
2016-02-20
Last reply:
2016-02-21

Ubuntu 15.04 is EOL and no longer supported in any way. I suggest you upgrade to Wily.

markling (markling) said : #2

Agh. Dreaded upgrade. I try to avoid it.

Would that necessarily account for scsi ceasing to work? And would an upgrade necessarily fix it?

I do now see, however, that 15.04 being EOL explains why Software Updater has been telling me that it can't find any repositories. I've been meaning to look into that. But linux is like a three-year-old child. It has no conception that its users have their own minds and so don't know everything it knows.

What does that mean in relation to my problem, though? I still get updates. Are they essentially incompatible and is my system integrity therefore being slowly eroded with every update?

And short of an upgrade (which is a sizeable undertaking that requires some preparation and advanced warning), is there an easy way to resolve this problem with scsi, which is a pressing and relatively immediate priority?

Manfred Hampl (m-hampl) said : #3

What is the disk setup of your system?
And what is the issue? No access to a SCSI-connected hard disk or what?

Remark:
Messages like

ACPI PCC Probe Failed
Starting Version 219
ACPI Warning: SystemIO range 0x0...-0x0... conflicts with OpRegion 0x0...-0x0...
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Are just warnings or informational and do not necessarily indicate a problem.

markling (markling) said : #4

The scsi device is a scanner. It was working fine. Now since when I turn the scanner on the system won't boot, it's not working fine. I assumed an update created the problem. But I wasn't alert enough to catch it.

Regarding your remark on the messages:

Yes, yes. But the fact remains that there is a problem.

Moreover, the messages occur when I switch the scsi device on, and accompany the boot failure. When I switch the scsi off, the messages disappear and the system boots.

The ACPI PCC probe message occurs at all times. It is apparently redundant. But it is on a related topic and hasn't been happening very long, so I thought I might report it.

Manfred Hampl (m-hampl) said : #5

For the "ACPI PCC" message see also
FAQ #1163: “ACPI PCC probe failed”.

Manfred Hampl (m-hampl) said : #6

If you have the scanner switched off and boot the system, and later switch it on, do you get any additional messages in the system log (dmesg | tail)?

markling (markling) said : #7

No, no such error messages when the scanner is off.

re. the 'PCC probe' message:

thank you, I had read the report you've noted. I included the message here because, though it is said to be redundant, it was on a related topic and might seem relevant to someone.

The other messages, which occur when the scanner is switched on, but not when it is switched off, and accompany a boot failure, indicate a scsi failure.

Manfred Hampl (m-hampl) said : #8

Just as an additional trivial step: try removing ad re-attaching all SCSI cables. Physical connection problems might result in weird error messages. And if you have spare ones, you might try replacing cable(s).

Can you help with this problem?

Provide an answer of your own, or ask markling for more information if necessary.

To post a message you must log in.