from:"Michael Schmiedgen"





Port is devel/apr1 and platform is amd64.

Works fine on my side. It would be helpful if you could build a kernel with
debug symbols, reproduce the problem and provide a stack strace.


Unfortunately I cannot. It is a production machine without debug that does not
like to run on 11.1 OR 11.2 for some strange reason [1]. And I really do not

I'm not referring to 11.1 or 11.2. Just the kernel you use with debug symbols.


I know, this was only some background information.



want to run it on 11.0 anymore. Perhaps it is some crappy hardware from our
hoster, I don't know. Anyway, after minimal-updating SVN to very-latest and
removing SCTP it behaves just fine under load.

Removing SCTP means removing it from the kernel or disabling it in the port?


From the kernel. I commented out 'options SCTP' and recompiled.



Since you said that it crashed multiple times makes me wonder if this problem
is related to SCTP in particular or if there is some other generic issue...


The mentioned commit [2] lies exactly in my SVN update delta. So this could
be the reason, too(?)

Sadly I am to busy right now to investigate further, sorry.

OK. If you have some spare time, enable SCTP again and see if the problem
is related to it...


Yes, if time and point in time permits, because that's a production server
and I can only mess around with it late night.


Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 12.0-ALPHA6 dumps with 'Fatal double fault'


Hi Michael,

many thanks for your help.


On 20.09.2018 18:15, Michael Tuexen wrote:

On 20. Sep 2018, at 17:12, Michael Schmiedgen  wrote:



Can you elaborate which port was triggering the fault and which platform you 
are using?
I would like to reproduce the issue and fix it.


Port is devel/apr1 and platform is amd64.

Works fine on my side. It would be helpful if you could build a kernel with
debug symbols, reproduce the problem and provide a stack strace.


Unfortunately I cannot. It is a production machine without debug that does not
like to run on 11.1 OR 11.2 for some strange reason [1]. And I really do not
want to run it on 11.0 anymore. Perhaps it is some crappy hardware from our
hoster, I don't know. Anyway, after minimal-updating SVN to very-latest and
removing SCTP it behaves just fine under load.



Since you said that it crashed multiple times makes me wonder if this problem
is related to SCTP in particular or if there is some other generic issue...


The mentioned commit [2] lies exactly in my SVN update delta. So this could
be the reason, too(?)

Sadly I am to busy right now to investigate further, sorry.

Thanks again,
  Michael



[1]
https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html
https://lists.freebsd.org/pipermail/freebsd-stable/2014-December/081192.html

[2]
https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071283.html
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 12.0-ALPHA6 dumps with 'Fatal double fault'





Can you elaborate which port was triggering the fault and which platform you 
are using?
I would like to reproduce the issue and fix it.


Port is devel/apr1 and platform is amd64.

CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.10-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
  
Features=0xbfebfbff
Features2=0x1fbae3ff
  AMD Features=0x28100800
  AMD Features2=0x1
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics

It crashed multiple times randomly under heavy load when compiling ports. But I
observed a crash two times exactly in the same place: configure script SCTP test
in devel/apr1.

Thanks,
  Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 12.0-ALPHA6 dumps with 'Fatal double fault'


I removed SCTP from kernel and updated from r338797 to r338827
and the problem seems to be gone.

Michael



On 20.09.2018 14:18, Michael Schmiedgen wrote:

Hi List,

if compiling ports and configure script checks for SCTP with

'checking whether SCTP is supported...'

12.0-ALPHA6 dumps core with message:

Fatal double fault
rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
rax 0x1 rdx 0x3 rbx 0x7fffd198
rcx 0x80b9620b rsi 0xf8029eeb0368 rdi 0x4
r8 0xf801c925c580 r9 0xfe00be2456d4 r10 0x4
r11 0xfe00be245b80 r12 0x7fffd190 r13 0
r14 0x1 r15 0x7fffd1a8 rflags 0x10293
cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b
fsbase 0x8002318d0 gsbase 0x81648a00 kgsbase 0
cpuid = 0; apic id = 00
panic: double fault
cpuid = 0

I can provide crash dumps if desired, but without debug information.

Thanks,
   Michael



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

12.0-ALPHA6 dumps with 'Fatal double fault'


Hi List,

if compiling ports and configure script checks for SCTP with

'checking whether SCTP is supported...'

12.0-ALPHA6 dumps core with message:

Fatal double fault
rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
rax 0x1 rdx 0x3 rbx 0x7fffd198
rcx 0x80b9620b rsi 0xf8029eeb0368 rdi 0x4
r8 0xf801c925c580 r9 0xfe00be2456d4 r10 0x4
r11 0xfe00be245b80 r12 0x7fffd190 r13 0
r14 0x1 r15 0x7fffd1a8 rflags 0x10293
cs 0x20 ss 0x28 ds 0x3b es 0x3b fs 0x13 gs 0x1b
fsbase 0x8002318d0 gsbase 0x81648a00 kgsbase 0
cpuid = 0; apic id = 00
panic: double fault
cpuid = 0

I can provide crash dumps if desired, but without debug information.

Thanks,
  Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Mounting ZFS with error 5 failed, since r271963 callout convert

2014-10-28 Thread Michael Schmiedgen




In previous months I had already the same problem with ZFS if
nvidia driver was loaded via /boot/loader.conf. It triggered
the same error. So I loaded the driver on demand with kldload
after login and everything (X + stuff) worked fine.

Very strange...

Does anyone have a clue what is going on here?


So not loading the nvidia driver during boot fixed it?  That seems odd indeed.
Did you recompile the driver after updating?



The nvidia driver problem started long before r271963. If
I update my CURRENT, non base stuff will be deleted and
ports will be completly new installed. The nvidia problem
persisted some of these cycles before I gave up. I can
test if the problem still exists.

But now there is a similar problem with applying kern_cons.c
in r271963. I do not know whether these two are related.

Please let me know if you want to see some configuration
or logs or anything.

Thanks,
  Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Mounting ZFS with error 5 failed, since r271963 callout convert

2014-10-27 Thread Michael Schmiedgen


Hi List,

my ZFS does not mount. I bifurcated to r271963 that
does not work anymore. The commit seems not directly
related to ZFS, but is rather a conversion from timeout(9)
to callout(9).

After booting the kernel it drops to the mount prompt,
stating that ZFS cannot be mounted because of 'error 5'.

Any hints? Can I provide some more information?

Thanks,
  Michael
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Mounting ZFS with error 5 failed, since r271963 callout convert

2014-10-27 Thread Michael Schmiedgen

On 10/27/2014 22:29, Ryan Stone wrote:

On Mon, Oct 27, 2014 at 4:21 PM, Michael Schmiedgen schmied...@gmx.net wrote:

Hi List,

my ZFS does not mount. I bifurcated to r271963 that
does not work anymore. The commit seems not directly
related to ZFS, but is rather a conversion from timeout(9)
to callout(9).

After booting the kernel it drops to the mount prompt,
stating that ZFS cannot be mounted because of 'error 5'.

Any hints? Can I provide some more information?

Thanks,
Michael

The changes to the 3 files there look to be independent, so can you
narrow this down further by applying the patch to only a single file?
Of those three only ACPI looks like it could affect ZFS or disks, so
this will be the patch to try first:

https://svnweb.freebsd.org/base/head/sys/dev/acpica/acpi.c?view=patchr1=271889r2=271963pathrev=271963

If you can get a verbose boot log from the machine that would be
helpful, but you'd need a serial console to capture that.

I applied first acpi.c, then atkbd.c and at last kern_cons.c that
triggered the error.

https://svnweb.freebsd.org/base/head/sys/kern/kern_cons.c?r1=271963r2=271962pathrev=271963

In previous months I had already the same problem with ZFS if
nvidia driver was loaded via /boot/loader.conf. It triggered
the same error. So I loaded the driver on demand with kldload
after login and everything (X + stuff) worked fine.

Very strange...

Does anyone have a clue what is going on here?

Thanks,
Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: r259580 breaks radeonkms

2014-08-06 Thread Michael Schmiedgen


Something is wrong with Intel hardware too on CURRENT from yesterday. I
have not looked deeper into it.

Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Status of llvm/clang 3.4?

2014-03-04 Thread Michael Schmiedgen


On 04.03.2014 13:17, Thomas Mueller wrote:

What is the current status of clang, regarding known bugs, on FreeBSD-current?

There were reports of www/firefox failing to build because of bug in llvm.

Can I currently build ports normally on FreeBSD-current amd64 and i386, or do I 
need to wait?

Or update system and build ports on my FreeBSD 10-stable amd64 and i386 
installations while I wait for bug fix?


Recently I had problems with building py-sqlite3 while building firefox,
something like unknown clang arguments ('-R' or something) are errors
now. Yesterday I built (via ssh) fresh kernel/world/ports and
everything worked fine (the build). Today I will try the binaries with
direct access to the machine.

Cheers
  Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [OT] ta-spring


On 29.01.2014 15:45, Dmitry Marakasov wrote:

* Dimitry Andric (d...@freebsd.org) wrote:



Hm, which port is having problems with this?  I have built quite a large
set, and never encountered this issue.

In any case: yes, it is quite long overdue for a libc++ update. :-)  I
will have a look tonight.


New version of games/spring (not in ports yet).



Can we expect a current version of spring in ports soon? That would
be nice! AFAIK newer versions require OpenMP. Will this compile with
our (new 3.4 soon) base clang?

Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [OT] ta-spring


On 29.01.2014 16:16, David Chisnall wrote:

On 29 Jan 2014, at 15:08, Michael Schmiedgen schmied...@gmx.net wrote:


Can we expect a current version of spring in ports soon? That would
be nice! AFAIK newer versions require OpenMP. Will this compile with
our (new 3.4 soon) base clang?


Base clang doesn't support OpenMP.  We should probably import Intel's Clang 
fork into ports:

http://clang-omp.github.io

This can then be used to compile things that need both libc++ and OpenMP.  
Intel's OpenMP runtime is permissively licensed now, but will likely require a 
small amount of porting to get it to work on FreeBSD (it supports Linux and OS 
X).



I thought OpenMP will be an integral part of LLVM/clang in near future,
at least the front-end part? It seems there are plans to even integrate
the runtime in the llvm project source tree:

http://openmp.llvm.org/

Ok, so llvm/clang 3.4 obviously will not ship with OpenMP, but maybe
later versions.

Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [OT] ta-spring


On 29.01.2014 16:42, David Chisnall wrote:

On 29 Jan 2014, at 15:37, Michael Schmiedgen schmied...@gmx.net wrote:

On 29.01.2014 16:16, David Chisnall wrote:

On 29 Jan 2014, at 15:08, Michael Schmiedgen schmied...@gmx.net wrote:


I thought OpenMP will be an integral part of LLVM/clang in near future,
at least the front-end part? It seems there are plans to even integrate
the runtime in the llvm project source tree:

http://openmp.llvm.org/

Ok, so llvm/clang 3.4 obviously will not ship with OpenMP, but maybe
later versions.


Active development happens in Intel's tree, and is slowly being merged 
upstream.  Eventually, Clang will have full OpenMP 4 support, but Intel's tree 
will have it first and there is likely to be a lag before it makes it into 
mainline clang.

As such, it would make sense to have a port as a stop-gap until it is ready.



Ah, ok, that makes sense. Thanks for explanation.

BTW very amusing *and* very informative bsdtalk/vBSDCon2013 talk a while
ago, thanks for that! :)

Cheers
  Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [OT] ta-spring


On 29.01.2014 17:34, Dmitry Marakasov wrote:

* Michael Schmiedgen (schmied...@gmx.net) wrote:


Can we expect a current version of spring in ports soon? That would
be nice!


Yes and no. The port is ready, however it's unstable - it crashes on
start in most cases, however if it doesn't crash on start, it'll work
without problems. I don't think that's suitable for ports, but since
94.1 which is currently in ports has build problems, it may be least
of two evils.

For now, the port is available for testing here:

https://github.com/AMDmi3/freebsd-ports/tree/master/games/spring


AFAIK newer versions require OpenMP. Will this compile with
our (new 3.4 soon) base clang?


It compiles fine, so either they doesn't use OpenMP or it's
optional, haven't investigated.

The cause for clang 3.4 experiments is the instability mentioned
above. Disassembly shows that it crashes on thread-local storage
access because a null pointer is used as TLS location for some
reason. I though that it may be a clang 3.3 miscompilation and
tried 3.4, but there's that libc++ problem.

We can't also build it with GCC, as it depends on boost which is
built with clang and is thus incompatible with GCC-generated code.
GCC has another problem, see my following forwarded mail, but that
can be circumvented in spring code.

My current plans are:

1) Try to patch system libc++ and try 3.4 again to check if that's
clang 3.3 specific, however that won't help the port anyway as I
libc++ can't be patched on all 10.0 systems.
2) Try to debug TLS access further. That'd be quite painstaking.
3) Write to clang maillist, maybe it's a known problem


Great! Many thanks for your efforts, much appreciated! Let me know if
you need some testing, I run CURRENT on both desktop and laptop,
usually not more than few weeks old. I stay tuned.

Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: undefined reference to xenpci_alloc_space

2013-10-11 Thread Michael Schmiedgen


On 10/11/13 05:39, Justin T. Gibbs wrote:

On Oct 10, 2013, at 12:40 PM, Michael Schmiedgen schmied...@gmx.net wrote:


is it intended that kernel does not build if

device xenpci

is omitted in the kernel config? I get the following error:

linking kernel
gnttab.o: In function `gnttab_resume':
/usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to 
`xenpci_alloc_space'

Thanks,
  Michael


XENHVM depends on xenpci, so you must remove XENHVM if you remove
xenpci.  Perhaps we should make a change similar to the attached
patch in order to make this clear?



Arghh, my fault. I did not inspect changes to kernel config
carefully enough. Thanks for the hint.

  Michael


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

undefined reference to xenpci_alloc_space

2013-10-10 Thread Michael Schmiedgen


Hi List,

is it intended that kernel does not build if

device xenpci

is omitted in the kernel config? I get the following error:

linking kernel
gnttab.o: In function `gnttab_resume':
/usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to 
`xenpci_alloc_space'


Thanks,
  Michael
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Lenovo x220 - hangs on shutdown

2013-07-17 Thread Michael Schmiedgen


On 16.07.2013 22:48, Joel Dahl wrote:

Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it 
hangs when I do a shutdown from an xterm. The screen just goes black and the 
fan never spins down. It doesn't respond to ping.


My build is from Sunday. I never type 'shutdown', but it is configured
to shutdown when I close the display. Everything works fine.
I can investigate revision and shutdown from xterm at home if you
like.

Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Lenovo x220 - hangs on shutdown

2013-07-17 Thread Michael Schmiedgen


On 07/16/13 22:48, Joel Dahl wrote:

Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it 
hangs when I do a shutdown from an xterm. The screen just goes black and the 
fan never spins down. It doesn't respond to ping.


X220, 10.0-CURRENT #0 r253368 amd, powerd running. In xterm I type
'shutdown -p now' and everything works fine. But the kernel is
compiled without INVARIANTS and without WITNESS and malloc runs
in production mode.

Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Audio Hints, T520?

2013-05-06 Thread Michael Schmiedgen


On 05/06/13 04:49, Kevin Oberman wrote:

On Sun, May 5, 2013 at 7:43 PM, Sean Bruno sean_br...@yahoo.com wrote:

On Mon, 2013-05-06 at 03:25 +0200, Michael Schmiedgen wrote:


Was trying to get the microphone working, but it seems to not quite be
working.


I got the same problem with my X220. Before the last Lenovo
HDA quirk commits everything worked fine, but I had to set
the default sound unit to 1.
Now I do not need to set the sound unit, audio output works
out of the box but recording does not work anymore. I fiddled
with nid config but got bored after the fifth reboot.



Ok, this smells like a recent regression.



Could be. I'm running 9-STABLE, not current, on my T520. I can only say
that the hints I provided work fine on my T520 on 9-stable.


Sorry for making noise. Now it works for me. Only thing is I
booted Windows in between, nothing else. Now Skype test call
works, before it did not.

Cheers
  Michael


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Audio Hints, T520?

2013-05-05 Thread Michael Schmiedgen


On 04.05.2013 06:14, Sean Bruno wrote:

Speaker/headphones working great on Current.

Was trying to get the microphone working, but it seems to not quite be
working.


I got the same problem with my X220. Before the last Lenovo
HDA quirk commits everything worked fine, but I had to set
the default sound unit to 1.
Now I do not need to set the sound unit, audio output works
out of the box but recording does not work anymore. I fiddled
with nid config but got bored after the fifth reboot.

The behaviour changed at my last world build a month ago.

I can supply dmesg or sysctl output if you want.

Thanks
  Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: ZFS cache devs UNAVAIL

Hi Andriy,

my dmesg is listed below.

Thanks,
  Michael


FreeBSD 10.0-CURRENT #0: Tue Oct 23 00:14:32 CEST 2012
root@gizeh.smoke:/usr/obj/usr/src/sys/GIZEH amd64
CPU: Intel(R) Xeon(R) CPU   E3110  @ 3.00GHz (2992.57-MHz
K8-class CPU)
  Origin = GenuineIntel  Id = 0x10676  Family = 0x6  Model = 0x17
Stepping = 6

Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE

Features2=0x8e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1
  AMD Features=0x20100800SYSCALL,NX,LM
  AMD Features2=0x1LAHF
  TSC: P-state invariant, performance statistics
real memory  = 6442450944 (6144 MB)
avail memory = 6145687552 (5860 MB)
Event timer LAPIC quality 400
ACPI APIC Table: PTLTD  APIC  
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0 Version 2.0 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: PTLTDXSDT on motherboard
acpi0: Power Button (fixed)
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff irq 0,8
on acpi0
Timecounter HPET frequency 14318180 Hz quality 950
Event timer HPET frequency 14318180 Hz quality 450
Event timer HPET1 frequency 14318180 Hz quality 440
Event timer HPET2 frequency 14318180 Hz quality 440
Event timer HPET3 frequency 14318180 Hz quality 440
atrtc0: AT realtime clock port 0x70-0x71 on acpi0
Event timer RTC frequency 32768 Hz quality 0
attimer0: AT timer port 0x40-0x43,0x50-0x53 on acpi0
Timecounter i8254 frequency 1193182 Hz quality 0
Event timer i8254 frequency 1193182 Hz quality 100
Timecounter ACPI-safe frequency 3579545 Hz quality 850
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
vgapci0: VGA-compatible display port 0x2000-0x207f mem
0xd200-0xd2ff,0xc000-0xcfff,0xd000-0xd1ff irq 16
at device 0.0 on pci1
nvidia0: GeForce 8600 GT on vgapci0
vgapci0: child nvidia0 requested pci_enable_io
vgapci0: child nvidia0 requested pci_enable_io
em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0x1820-0x183f mem
0xd330-0xd331,0xd3324000-0xd3324fff irq 16 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: 00:30:48:93:f0:06
uhci0: Intel 82801I (ICH9) USB controller port 0x1840-0x185f irq 16 at
device 26.0 on pci0
usbus0 on uhci0
uhci1: Intel 82801I (ICH9) USB controller port 0x1860-0x187f irq 17 at
device 26.1 on pci0
usbus1 on uhci1
uhci2: Intel 82801I (ICH9) USB controller port 0x1880-0x189f irq 18 at
device 26.2 on pci0
usbus2 on uhci2
ehci0: Intel 82801I (ICH9) USB 2.0 controller mem
0xd3326800-0xd3326bff irq 18 at device 26.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
hdac0: Intel 82801I HDA Controller mem 0xd332-0xd3323fff irq 16 at
device 27.0 on pci0
pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0
pci5: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0
pci13: ACPI PCI bus on pcib3
ahci0: Marvell 88SE912x AHCI SATA controller port
0x3030-0x3037,0x3024-0x3027,0x3028-0x302f,0x3020-0x3023,0x3000-0x300f
mem 0xd300-0xd30007ff irq 16 at device 0.0 on pci13
ahci0: AHCI v1.20 with 8 6Gbps ports, Port Multiplier not supported
ahcich0: AHCI channel at channel 0 on ahci0
ahcich1: AHCI channel at channel 1 on ahci0
ahcich2: AHCI channel at channel 2 on ahci0
ahcich3: AHCI channel at channel 3 on ahci0
ahcich4: AHCI channel at channel 4 on ahci0
ahcich5: AHCI channel at channel 5 on ahci0
ahcich6: AHCI channel at channel 6 on ahci0
ahcich7: AHCI channel at channel 7 on ahci0
atapci0: Marvell 88SE912x UDMA133 controller port
0x3048-0x304f,0x303c-0x303f,0x3040-0x3047,0x3038-0x303b,0x3010-0x301f
mem 0xd3000800-0xd300080f irq 17 at device 0.1 on pci13
uhci3: Intel 82801I (ICH9) USB controller port 0x18a0-0x18bf irq 23 at
device 29.0 on pci0
usbus4 on uhci3
uhci4: Intel 82801I (ICH9) USB controller port 0x18c0-0x18df irq 22 at
device 29.1 on pci0
usbus5 on uhci4
uhci5: Intel 82801I (ICH9) USB controller port 0x18e0-0x18ff irq 18 at
device 29.2 on pci0
usbus6 on uhci5
ehci1: Intel 82801I (ICH9) USB 2.0 controller mem
0xd3326c00-0xd3326fff irq 23 at device 29.7 on pci0
usbus7: EHCI version 1.0
usbus7 on ehci1
pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0
pci17: ACPI PCI bus on pcib4
atapci1: ITE IT8212F UDMA133 controller port
0x4020-0x4027,0x4014-0x4017,0x4018-0x401f,0x4010-0x4013,0x4000-0x400f
irq 23 at device 4.0 on pci17
ata2: ATA channel at channel 0 on atapci1
ata3: ATA channel at channel 1 on atapci1
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
ahci1: Intel ICH9 AHCI SATA controller port
0x1c70-0x1c77,0x1c64-0x1c67,0x1c68-0x1c6f,0x1c60-0x1c63,0x1c00-0x1c1f
mem 0xd3326000-0xd33267ff irq 17 at device 31.2 on pci0

Re: ZFS cache devs UNAVAIL

Hi Andy,

thank you for your reply. I will test your patch right now
and give you feedback.

On 10/23/12 22:08, Andriy Gapon wrote:
 on 23/10/2012 20:56 Michael Schmiedgen said the following:
 ...
 vdev_geom_open_by_path:519[1]: guid mismatch for provider /dev/ada0p1:
 5267967234359339128 != 0.
 
 Thank you for this valuable information.
 
 Do you have a rough estimate of when you started to experience this issue?

I experienced this since my 2012-10-17 build. I build every
3-5 weeks.

 Could you please also provide output of the following command captured right
 after a reboot and then after you re-add the cache disks?
 $ zdb -lll /dev/ada0p



Here the data in UNAVAIL state:

# zdb -lll /dev/ada0p1

LABEL 0

version: 5000
state: 4
guid: 5267967234359339128

LABEL 1

version: 5000
state: 4
guid: 5267967234359339128

LABEL 2

version: 5000
state: 4
guid: 5267967234359339128

LABEL 3

version: 5000
state: 4
guid: 5267967234359339128

# zdb -lll /dev/ada1p1

LABEL 0

version: 5000
state: 4
guid: 5693315451104805234

LABEL 1

version: 5000
state: 4
guid: 5693315451104805234

LABEL 2

version: 5000
state: 4
guid: 5693315451104805234

LABEL 3

version: 5000
state: 4
guid: 5693315451104805234



Here the data after readding the two devs:

zdb -lll /dev/ada0p1

LABEL 0

version: 5000
state: 4
guid: 13019058935211054376

LABEL 1

version: 5000
state: 4
guid: 13019058935211054376

LABEL 2

version: 5000
state: 4
guid: 13019058935211054376

LABEL 3

version: 5000
state: 4
guid: 13019058935211054376


# zdb -lll /dev/ada1p1

LABEL 0

version: 5000
state: 4
guid: 1347428618237802818

LABEL 1

version: 5000
state: 4
guid: 1347428618237802818

LABEL 2

version: 5000
state: 4
guid: 1347428618237802818

LABEL 3

version: 5000
state: 4
guid: 1347428618237802818


I will post the data after build/install/reboot soon.

Thanks,
  Michael

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: ZFS cache devs UNAVAIL

On 10/23/12 22:23, Andriy Gapon wrote:
 on 23/10/2012 23:08 Andriy Gapon said the following:
 on 23/10/2012 20:56 Michael Schmiedgen said the following:
 ...
 vdev_geom_open_by_path:519[1]: guid mismatch for provider /dev/ada0p1:
 5267967234359339128 != 0.

 Thank you for this valuable information.

 Do you have a rough estimate of when you started to experience this issue?

 Could you please also provide output of the following command captured right
 after a reboot and then after you re-add the cache disks?
 $ zdb -lll /dev/ada0p


 
 I still would like to get the above information if possible.
 But here is a patch that you can try:
 
 --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c
 +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c
 @@ -270,14 +270,16 @@ vdev_geom_read_config(struct g_consumer *cp, nvlist_t
 **config)
   continue;
 
   if (nvlist_lookup_uint64(*config, ZPOOL_CONFIG_POOL_STATE,
 - state) != 0 || state = POOL_STATE_DESTROYED) {
 + state) != 0 || state == POOL_STATE_DESTROYED ||
 + state  POOL_STATE_L2CACHE) {
   nvlist_free(*config);
   *config = NULL;
   continue;
   }
 
 - if (nvlist_lookup_uint64(*config, ZPOOL_CONFIG_POOL_TXG,
 - txg) != 0 || txg == 0) {
 + if (state != POOL_STATE_SPARE  state != POOL_STATE_L2CACHE 
 + (nvlist_lookup_uint64(*config, ZPOOL_CONFIG_POOL_TXG,
 + txg) != 0 || txg == 0)) {
   nvlist_free(*config);
   *config = NULL;
   continue;

This works for me. Thank you very much! :) For zdb data see below,
it has not changed since patch-apply/readd/reboot.

  Michael



# zdb -lll /dev/ada0p1

LABEL 0

version: 5000
state: 4
guid: 13019058935211054376

LABEL 1

version: 5000
state: 4
guid: 13019058935211054376

LABEL 2

version: 5000
state: 4
guid: 13019058935211054376

LABEL 3

version: 5000
state: 4
guid: 13019058935211054376

# zdb -lll /dev/ada1p1

LABEL 0

version: 5000
state: 4
guid: 1347428618237802818

LABEL 1

version: 5000
state: 4
guid: 1347428618237802818

LABEL 2

version: 5000
state: 4
guid: 1347428618237802818

LABEL 3

version: 5000
state: 4
guid: 1347428618237802818

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: ZFS cache devs UNAVAIL