Re: gptzfsboot: error 4 lba 30

2013-04-03 Thread Sergey V. Dyatko
On Tue, 2 Apr 2013 17:07:14 -0400 John Baldwin j...@freebsd.org wrote: On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote: Hi. On one of my fresh installed servers I am seeing the following output during boot: gptzfsboot: error 4 lba 30 ... gptzfsboot: error 4 lba 31

Re: gptzfsboot: error 4 lba 30

2013-04-03 Thread Andriy Gapon
on 03/04/2013 09:12 Sergey V. Dyatko said the following: On Tue, 2 Apr 2013 17:07:14 -0400 John Baldwin j...@freebsd.org wrote: On Monday, March 25, 2013 7:52:04 am Kai Gallasch wrote: Hi. On one of my fresh installed servers I am seeing the following output during boot: gptzfsboot:

Why tzdata2013b has not be merged to stable/8 ?

2013-04-03 Thread Claude Buisson
Hi, On March 15, tzdata2013b has been merged to head (r248307), to stable/6 (r248308), to stable/7 (r248309) and to stable/9 (r248310). But not to stable/8. I dare think than having an up to date zoneinfo could be a must for the incoming 8.4 release.. Claude Buisson

Re: Any objections/comments on axing out old ATA stack?

2013-04-03 Thread Alexander Motin
On 02.04.2013 21:39, Matthias Andree wrote: Am 31.03.2013 23:02, schrieb Scott Long: So what I hear you and Matthias saying, I believe, is that it should be easier to force disks to fall back to non-NCQ mode, and/or have a more responsive black-list for problematic controllers. Would this

Re: gptzfsboot: error 4 lba 30

2013-04-03 Thread Andrey V. Elsukov
On 03.04.2013 01:07, John Baldwin wrote: gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 Humm, do you have disks that the BIOS sees that are small? An error code of 4 means 'sector not found' or 'read error'. It would be interesting to see the output of 'lsdev -v' from the loader

Re: 9.1-REL Supermicro H8DCL-iF kernel panic

2013-04-03 Thread John Baldwin
On Monday, April 01, 2013 12:29:46 pm Xin Li wrote: Yes, this is a bandaid and the right fix should be refactor the code a little bit to make sure that no interrupt handler is installed before the driver have done other initializations but I don't have hardware that can reproduce this issue

Re: Any objections/comments on axing out old ATA stack?

2013-04-03 Thread Matthias Andree
I have just sent more information to the PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=157397 The short summary (more info in the PR) is: - limiting tags to 31 does not help - disabling NCQ appears to help in initial testing, but warrants more testing - error happens during

Re: Any objections/comments on axing out old ATA stack?

2013-04-03 Thread Jeremy Chadwick
On Thu, Apr 04, 2013 at 12:15:32AM +0200, Matthias Andree wrote: I have just sent more information to the PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=157397 The short summary (more info in the PR) is: - limiting tags to 31 does not help - disabling NCQ appears to help in initial

Re: Any objections/comments on axing out old ATA stack?

2013-04-03 Thread Matthias Andree
Am 04.04.2013 01:38, schrieb Jeremy Chadwick: ... While skimming Linux libata code and commits in the past, the only glaringly obvious bug/issue I see is with SB600/SB700 chipsets (the hardware revision apparently matters) and port multiplier (PMP) support and soft resets. Are you using a

Re: Any objections/comments on axing out old ATA stack?

2013-04-03 Thread Jeremy Chadwick
On Thu, Apr 04, 2013 at 02:19:16AM +0200, Matthias Andree wrote: Am 04.04.2013 01:38, schrieb Jeremy Chadwick: ... While skimming Linux libata code and commits in the past, the only glaringly obvious bug/issue I see is with SB600/SB700 chipsets (the hardware revision apparently