Re: panic: devfs_fsync: vop_stdfsync failed.

[Fabian Keil]

Fabian Keil  wrote:

> I got the following panic by impatiently unplugging a device while a
> msdosfs partition on it was in the process of getting unmounted:
> 
> Unread portion of the kernel message buffer:
> [368] Device IPOD went missing before all of the data could be written to it; 
> expect data loss.
> [368] fsync: giving up on dirty
> [368] 0xf80011b24760: tag devfs, type VCHR
> [368] usecount 1, writecount 0, refcount 4770 mountedhere 
> 0xf800061eb200
> [368] flags (VI_DOOMED|VI_ACTIVE)
> [368] v_object 0xf80011a4c500 ref 0 pages 4782 cleanbuf 4766 dirtybuf 
> 1
> [368] lock type devfs: EXCL by thread 0xf80010c424d0 (pid 40394, 
> sudo, tid 101528)
> [368] dev msdosfs/IPOD
> [368] panic: devfs_fsync: vop_stdfsync failed.

Filed as bug #205515: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205515

Fabian


pgpz42ZqSWP1P.pgp
Description: OpenPGP digital signature

Re: Build from 9.3-RELEASE to 11.0-CURRENT fails for i386 (-Wsign-compare issues with gcc)

[Garrett Cooper]

> On Dec 22, 2015, at 08:23, John Baldwin  wrote:
> 
>> On Monday, December 21, 2015 11:01:36 AM John Baldwin wrote:
>>> On Saturday, December 19, 2015 01:05:36 PM NGie Cooper wrote:
>>> Hi John,
>>>I tried bootstrapping 9.3-RELEASE to 11.0-CURRENT with i386 and ran into 
>>> the -Wsign-compare issue below when running make libraries with buildworld, 
>>> because it’s building libkvm with gcc 4.2.1 :/… I’ve tried bootstrapping 
>>> with clang/clang37, but haven’t been able to yet. I’ll try installing 
>>> 10.2-RELEASE via freebsd-update so I can use clang instead of gcc.
>>> Thanks!
>>> -NGie
>> 
>> We don't actually support going from 9 to 11.  However, these constants
>> should probably be explicitly unsigned anyway.  I haven't tested this at
>> all, but something like this:
>> 
>> Index: head/lib/libkvm/kvm_i386.h
>> ===
>> --- head/lib/libkvm/kvm_i386.h  (revision 292553)
>> +++ head/lib/libkvm/kvm_i386.h  (working copy)
>> @@ -57,8 +57,8 @@
>> #defineI386_PG_PS  0x080
>> #defineI386_PG_FRAME_PAE   (0x000ff000ull)
>> #defineI386_PG_PS_FRAME_PAE(0x000fffe0ull)
>> -#defineI386_PG_FRAME   (0xf000)
>> -#defineI386_PG_PS_FRAME(0xffc0)
>> +#defineI386_PG_FRAME   (0xf000u)
>> +#defineI386_PG_PS_FRAME(0xffc0u)
>> 
>> #ifdef __i386__
>> _Static_assert(PAGE_SHIFT == I386_PAGE_SHIFT, "PAGE_SHIFT mismatch");
> 
> This passed a universe build on HEAD.  If you can test that it fixes the 9.3 
> -> 11.0
> bootstrap I will commit it.

I'll fire up a 9.3 VM and give it a shot.
Thanks :)!!
-NGie
___
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: Need help with New Build -- Skylake

[Vijay Rjah]

On 12/19/15 4:23 PM, Vijay Rjah wrote:

Hello,

I'm planning to build a file server for my home.

I'm planning on using the B150 Intel chipset (specifically this MoBo: 
http://www.msi.com/product/motherboard/B150M-PRO-VDH.html#hero-overview)


This has Realtek RTL8111H Gigabit LAN controller, Does FreeBSD support 
this? (the man page for mentions support for 8111)


This is going to be a headless setup, hence I'm not concerned with 
lack of x11 support. (I'm assuming console works)


Does any one in the list have any experiences with this 
Chipset/Motherboard.


-Thanks in advance
Vijay
___
freebsd-questi...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"freebsd-questions-unsubscr...@freebsd.org"

Hi,

I actually went ahead and bought the system. Here is my config

CPU: Intel I3-6100
Mobo: MSI B150M-PRO-VDH
NIC: RTL8111H (on-Board)
RAM: Hyperx DDR4 8 GB

I initially tried to use UEFI-10.2 Release image. But the system was 
repeatedly crashing just after the loader prompt... (PANICS)
I tried installing with 10.2-Release (with BIOS).. But, NIC wasn't 
detected.


It seems the NIC driver was added around September' 15 to the FreeBSD 
tree in github  ( 
https://github.com/freebsd/freebsd/commit/c1d4644cbc1efd41f962e4979caf367c93d3c5f0 
)


I tried installing with 11.0-Current ( Legacy BIOS boot ), NIC works. 
got it installed..


The only issue i have is that the boot process takes a lot of time..  
(similar to 
https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/ 
). the system ultimately boots, but boot times are around 4 - 5 Mins..


How do I debug it? any suggestions?

-Thanks
Vijay

PS: Here is the output of pciconf -lv

root@vrajah-bsd:~ # pciconf -lv
hostb0@pci0:0:0:0:class=0x06 card=0x79821462 chip=0x190f8086 
rev=0x07 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sky Lake Host Bridge/DRAM Registers'
class  = bridge
subclass   = HOST-PCI
vgapci0@pci0:0:2:0:class=0x03 card=0x79821462 chip=0x19128086 
rev=0x06 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sky Lake Integrated Graphics'
class  = display
subclass   = VGA
none0@pci0:0:8:0:class=0x088000 card=0x79821462 chip=0x19118086 
rev=0x00 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sky Lake Gaussian Mixture Model'
class  = base peripheral
xhci0@pci0:0:20:0:class=0x0c0330 card=0x79821462 chip=0xa12f8086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H USB 3.0 xHCI Controller'
class  = serial bus
subclass   = USB
none1@pci0:0:20:2:class=0x118000 card=0x79821462 chip=0xa1318086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H Thermal subsystem'
class  = dasp
none2@pci0:0:21:0:class=0x118000 card=0x79821462 chip=0xa1608086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H LPSS I2C Controller'
class  = dasp
none3@pci0:0:21:1:class=0x118000 card=0x79821462 chip=0xa1618086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H LPSS I2C Controller'
class  = dasp
none4@pci0:0:22:0:class=0x078000 card=0x79821462 chip=0xa13a8086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H CSME HECI'
class  = simple comms
ahci0@pci0:0:23:0:class=0x010601 card=0x79821462 chip=0xa1028086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
class  = mass storage
subclass   = SATA
pcib1@pci0:0:28:0:class=0x060400 card=0x79821462 chip=0xa1148086 
rev=0xf1 hdr=0x01

vendor = 'Intel Corporation'
device = 'Sunrise Point-H PCI Express Root Port'
class  = bridge
subclass   = PCI-PCI
none5@pci0:0:30:0:class=0x118000 card=0x79821462 chip=0xa1278086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H LPSS UART'
class  = dasp
isab0@pci0:0:31:0:class=0x060100 card=0x79821462 chip=0xa1488086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H LPC Controller'
class  = bridge
subclass   = PCI-ISA
none6@pci0:0:31:2:class=0x058000 card=0x79821462 chip=0xa1218086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H PMC'
class  = memory
hdac0@pci0:0:31:3:class=0x040300 card=0xf9821462 chip=0xa1708086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H HD Audio'
class  = multimedia
subclass   = HDA
none7@pci0:0:31:4:class=0x0c0500 card=0x79821462 chip=0xa1238086 
rev=0x31 hdr=0x00

vendor = 'Intel Corporation'
device = 'Sunrise Point-H SMBus'
class  = serial bus
subclass   = 

Re: Need help with New Build -- Skylake

[Ed Maste]

On 22 December 2015 at 12:39, Vijay Rjah  wrote:
>
> The only issue i have is that the boot process takes a lot of time..
> (similar to
> https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/
> ). the system ultimately boots, but boot times are around 4 - 5 Mins..
>
> How do I debug it? any suggestions?

A useful first step is to get a verbose boot ("boot -v" from the
loader prompt) and note where there are any large or unexpected
delays. The "memory test" that was responsible for many reports of
slow FreeBSD boots has been disabled in 11.x for quite some time, so
it won't be that.
___
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"

BZ 205527: can someone look?

[Larry Rosenman]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205527

Can someone take a look at this?  I can get more info, but not sure what 
all y'all need.




--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
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"

Q about fsck_ffs usage detail...

[Jeffrey Bouquet]

After trial and error ( not easily crafted from the man page)
crafting the "mount" command below...

I've on a todo list a  once-in-a-while fsck_ffs  ( in single user mode
or init 1), each filesystem ( eventually ) so that journalling is double checked
as accurate (ufs2)

"mount -t ufs -o rw /dev/gtp/root /  "
( ^^ that, not easily crafted from the man page examples, unless it works
sometimes and does not work other times, or needs some precise
order.  This command worked today...)

So much for documentation.
On to the question.

The 'task' would be to run fsck_ffs -y on each filesystem once in a while.
However, after remounting root or some other filesystem rw, the
(NO_WRITE) still appears in fsck_ffs ... appearing to make the effort
moot.   (Since it also answers (No) to its resulting ?repair? questions...)

Fault of "init 1" rather than safe mode at boot, or some unintended 
not-working-yet
fault of fsck_ffs, or some easier way to accomplish the stated task?  

Apologies for not asking it elsewhere... seems like one or two persons reading
this list may know more than others and/or sometimes do the same
commands, every once in a while or after a crash to the debugger instance.

Thanks.
( Not really urgent that anyone answers.  More of an inquiry than a problem... 
at least at
r288246...  )
___
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: Q about fsck_ffs usage detail...

[Ian Lepore]

On Tue, 2015-12-22 at 17:37 -0800, Jeffrey Bouquet wrote:
> After trial and error ( not easily crafted from the man page)
> crafting the "mount" command below...
> 
> I've on a todo list a  once-in-a-while fsck_ffs  ( in single user
> mode
> or init 1), each filesystem ( eventually ) so that journalling is
> double checked
> as accurate (ufs2)
> 
> "mount -t ufs -o rw /dev/gtp/root /  "
> ( ^^ that, not easily crafted from the man page examples, unless it
> works
> sometimes and does not work other times, or needs some precise
> order.  This command worked today...)
> 
> So much for documentation.
> On to the question.
> 
> The 'task' would be to run fsck_ffs -y on each filesystem once in a
> while.
> However, after remounting root or some other filesystem rw, the
> (NO_WRITE) still appears in fsck_ffs ... appearing to make the effort
> moot.   (Since it also answers (No) to its resulting ?repair?
> questions...)
> 
> Fault of "init 1" rather than safe mode at boot, or some unintended
> not-working-yet
> fault of fsck_ffs, or some easier way to accomplish the stated task? 
> 
> Apologies for not asking it elsewhere... seems like one or two
> persons reading
> this list may know more than others and/or sometimes do the same
> commands, every once in a while or after a crash to the debugger
> instance.
> 
> Thanks.
> ( Not really urgent that anyone answers.  More of an inquiry than a
> problem... at least at
> r288246...  )

If I've understood your question correctly, I think the sequence you're
looking for is something like this:

  init 1
  mount -r /
  fsck -y /
  mount -w /
  exit

When the NO_WRITE message appears, fsck is saying it will not write
because others can write.

-- Ian
___
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: Pardon the interruption.

[Joe Nosay]

Okay. Somebody needs to get a board and start building the actual laptop.
www.nxp.com
Since this is a crowd funding effort, it should be easy to have support.


On Mon, Dec 21, 2015 at 12:30 PM, Joe Nosay  wrote:

> Let's find out exactly what the laptop project needs and work from there.
> I have some ideas on using it for accessibility and creativity. There needs
> to be a working prototype - a few actually - for developers to build the
> systems.
> Have someone put together a model and we can work from there.
>
___
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"

Pardon the interruption.

[Joe Nosay]

Let's find out exactly what the laptop project needs and work from there. I
have some ideas on using it for accessibility and creativity. There needs
to be a working prototype - a few actually - for developers to build the
systems.
Have someone put together a model and we can work from there.
___
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: Need help with New Build -- Skylake

[Anton Sayetsky]

22 дек. 2015 г. 23:00 пользователь "Ed Maste"  написал:
>
> On 22 December 2015 at 12:39, Vijay Rjah  wrote:
> >
> > The only issue i have is that the boot process takes a lot of time..
> > (similar to
> >
https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/
> > ). the system ultimately boots, but boot times are around 4 - 5 Mins..
> >
> > How do I debug it? any suggestions?
>
> A useful first step is to get a verbose boot ("boot -v" from the
> loader prompt) and note where there are any large or unexpected
> delays. The "memory test" that was responsible for many reports of
> slow FreeBSD boots has been disabled in 11.x for quite some time, so
> it won't be that.
AFAIK, memory test disabling is already in 10-STABLE & 10.2R too.
___
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: Build from 9.3-RELEASE to 11.0-CURRENT fails for i386 (-Wsign-compare issues with gcc)

[John Baldwin]

On Monday, December 21, 2015 11:01:36 AM John Baldwin wrote:
> On Saturday, December 19, 2015 01:05:36 PM NGie Cooper wrote:
> > Hi John,
> > I tried bootstrapping 9.3-RELEASE to 11.0-CURRENT with i386 and ran 
> > into the -Wsign-compare issue below when running make libraries with 
> > buildworld, because it’s building libkvm with gcc 4.2.1 :/… I’ve tried 
> > bootstrapping with clang/clang37, but haven’t been able to yet. I’ll try 
> > installing 10.2-RELEASE via freebsd-update so I can use clang instead of 
> > gcc.
> > Thanks!
> > -NGie
> 
> We don't actually support going from 9 to 11.  However, these constants
> should probably be explicitly unsigned anyway.  I haven't tested this at
> all, but something like this:
> 
> Index: head/lib/libkvm/kvm_i386.h
> ===
> --- head/lib/libkvm/kvm_i386.h  (revision 292553)
> +++ head/lib/libkvm/kvm_i386.h  (working copy)
> @@ -57,8 +57,8 @@
>  #defineI386_PG_PS  0x080
>  #defineI386_PG_FRAME_PAE   (0x000ff000ull)
>  #defineI386_PG_PS_FRAME_PAE(0x000fffe0ull)
> -#defineI386_PG_FRAME   (0xf000)
> -#defineI386_PG_PS_FRAME(0xffc0)
> +#defineI386_PG_FRAME   (0xf000u)
> +#defineI386_PG_PS_FRAME(0xffc0u)
>  
>  #ifdef __i386__
>  _Static_assert(PAGE_SHIFT == I386_PAGE_SHIFT, "PAGE_SHIFT mismatch");

This passed a universe build on HEAD.  If you can test that it fixes the 9.3 -> 
11.0
bootstrap I will commit it.

-- 
John Baldwin
___
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: This igb change makes my igb not working anymore - Re: regression in igb/clang?

[Alan Somers]

I'm experiencing the same problem, and I can confirm that Alexander's
workaround fixes it.  Here is some more information:

* I see the exact same problem on two different systems, both with
S5520HC motherboards.
* Both systems have two igb ports, and igb1 works on both.  Only igb0 is broken.
* Disabling tso, lro, rxcsum, and txcsum has no effect.
* tcpdump reveals that igb0 transmits successfully, but fails to receive
* Curiously, "netstat -I igb0" shows nonzero values for Ipkts, even
though "tcpdump  -i igb0" shows no inbound packets at all.
* I can't really tell if IPv4 or IPv6 are working, because even ARP
doesn't work.
* SVN revisions 291495 and 292570 are both bad.  I don't know any
recent good revision.

-Alan

On Thu, Nov 19, 2015 at 11:21 PM, Alexander Leidinger
 wrote:
> Dual stack.
> Ping was on ipv4, no answer. Without the line I get the answer.
> I have not tried a ping6.
> --
> Send from a mobile device, please forgive brevity and misspelling.
>
>
> Gesendet mit AquaMail für Android
> http://www.aqua-mail.com
>
>
> Am 20. November 2015 02:07:11 schrieb Eric Joyner :
>
>> Are you using IPv6?
>>
>> On Thu, Nov 19, 2015 at 12:42 PM Alexander Leidinger <
>> alexan...@leidinger.net> wrote:
>>
>>> On Wed, 11 Nov 2015 11:45:32 +0100
>>> Alexander Leidinger  wrote:
>>>
>>> > Hi,
>>> >
>>> > I' updated a system with -current as of r287323 (end August) to
>>> > r290633 (yesterday).
>>> >
>>> > Result: no network connection (not even ping) on igb.
>>> > Ping internally (local addresses) works, anything outgoing/incoming
>>> > doesn't.
>>>
>>> And this is the function which causes it:
>>> e1000_rx_fifo_flush_82575(>hw);
>>>
>>> If I comment it out in if_igb.c, the network card works again.
>>>
>>> Full quote below for the PCI ID of my card in case it helps for fixing
>>> the issue.
>>>
>>> Bye,
>>> Alexander.
>>>
>>> > I disabled HW support (tso4, lro, rxcsum, txcsum): doesn't help.
>>> >
>>> > Did I miss some known defect/workaround?
>>> >
>>> > Anything I should test/provide besides what is below?
>>> >
>>> > The igb device is a:
>>> > ---snip---
>>> > igb0@pci0:1:0:0: class=0x02 card=0x34e28086 chip=0x10a78086
>>> > rev=0x02 hdr=0x00 ---snip---
>>> >
>>> > My src.conf:
>>> > ---snip---
>>> > WITH_IDEA=yes
>>> > WITHOUT_PROFILE=yes
>>> > CFLAGS+=-DFTP_COMBINE_CWDS
>>> > MALLOC_PRODUCTION=yes
>>> > LOADER_FIREWIRE_SUPPORT=yes
>>> > #WITH_FAST_DEPEND=yes
>>> > ---snip---
>>> >
>>> > My buildworld related config in make.conf:
>>> > ---snip---
>>> > CFLAGS+= -O2 -pipe
>>> > COPTFLAGS= -O2 -pipe
>>> > #CPUTYPE?=core2
>>> > #WITH_CCACHE_BUILD=yes
>>> > #.if (!empty(.CURDIR:M/usr/src*)
>>> > || !empty(.CURDIR:M/usr/obj*)|| !empty(.CURDIR:M/space/system/usr_obj*))
>>> > #.if !defined(NOCCACHE) && exists(/usr/local/libexec/ccache/world/cc)
>>> > #CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/cc,1}
>>> > #CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/c++,1} #.endif
>>> > #.endif
>>> > ---snip---
>>> >
>>> > The commented out parts were active initially, but then I commented
>>> > them out, cleaned out /usr/obj (rm -r) and rebuild/reinstall to make
>>> > sure it's not due to them (CPUTYPE commented out due to the fact that
>>> > there's a new compiler, and I use zsh and there was a commit talking
>>> > about zsh and CPUTYPE workaround).
>>> >
>>> > Bye,
>>> > Alexander.
>>> >
>>>
>>>
>>> --
>>> http://www.Leidinger.net alexan...@leidinger.net: PGP 0xC773696B3BAC17DC
>>> http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0xC773696B3BAC17DC
>>> ___
>>> 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"
>>>
>
>
> ___
> 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"
___
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"