Re: [osol-discuss] AHCI errors

2010-06-04 Thread Brandon High
On Wed, Jun 2, 2010 at 4:44 AM, Bruno Damour wrote: > I scrubbed all my zfs pools, no problem detected. Everything seems to be > working. > > Any idea of what is happening ? Check your cabling. -B -- Brandon High : bh...@freaks.com ___ opensolaris-d

[osol-discuss] AHCI errors

2010-06-02 Thread Bruno Damour
Hello, Since some time, I'm getting repeted (every 2mn or so) transient errors on AHCI : Jun 2 10:01:09 amber ahci: [ID 777486 kern.warning] WARNING: ahci0: ahci port 0 has interface fatal error Jun 2 10:01:09 amber ahci: [ID 687168 kern.warning] WARNING: ahci0: ahci port 0 is trying to do e

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-10-27 Thread Tim
Sorry if I am a little off topic here... I don't know what's happened to my server, I've noted these time out errors are only appearing on port 1. I'm going to try a few things to see if they make a difference like: 1) remove the new sil3114 card from the server 2) update the motherboard bios (I

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-10-27 Thread Tim
I am seeing these satapkt time outs on snv_111b, 2009.06 release.. I am using a ASUS M2N68-CM and used all 4 SATA ports in a RAIDZ... Today I just added a sil3114 card for more ports (only SATA150 ports) and when I added a single drive to this card and got a new pool going on it, I came across th

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-09-25 Thread Travis Tabbal
> Alternatively if you manage to access the disk in > some other way (e.g. booting the standard non xVM > kernel), add this line to /etc/system: > > set ahci:ahci_msi_enabled = 0 > > then run bootadm update-archive (-R > /relative-root-mountpoint) > to get the new /etc/system in the miniroot and

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-09-25 Thread Dan Reiland
I filed a bug. You may workaround the issue by using the following procedure: This applies also if you jumpstart/cdrom-boot/whatever your box and it hangs in ahci/sata and you don't want to edit the miniroot to set the variable. 1) Grub menu: highlight the Solaris line you want, press "e" then "

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-09-24 Thread Travis Tabbal
snv_111b, 2009.06 release version. I also reverted to this version. This is the first time I've tried the dev releases, so I'm not sure if other versions have this issue or not. -- This message posted from opensolaris.org ___ opensolaris-discuss mailin

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-09-24 Thread Dan Reiland
What build were you running before the move to b123? I have a feeling this may be a regression introduced by: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6451665 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-09-24 Thread Travis Tabbal
I am using the xVM kernel, so perhaps that's why I see it as well. I didn't try the regular one as I updated specifically for the xVM updates. Hopefully the next release fixes the issue. I rolled back to 2009.06 + whatever updates are available in that repo and everything is working fine again.

Re: [osol-discuss] AHCI errors after updating to dev b123

2009-09-23 Thread Dan Reiland
I have a similar issue, however, mine presents when booting the xVM kernel -- non xVM kernel does not exhibit the issue. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

[osol-discuss] AHCI errors after updating to dev b123

2009-09-23 Thread Travis Tabbal
I updated to b123 to test out the xVM updates, which seem to work fine. However, when I boot under the new BE I start getting errors like this: Sep 24 19:23:35 nas ahci: [ID 517647 kern.warning] WARNING: ahci0: watchdog port 0 satapkt 0xff01dfa81448 timed out Sep 24 19:23:35 nas ahci: [ID