Re: FreeBSD Core Team Response to Controversial Social Media Posts

[Adam]

On Sun, May 19, 2019, 12:42 PM Igor Mozolevsky 
wrote:

> On Sun, 19 May 2019 at 17:54, Warner Losh wrote:
> >
> > On Sun, May 19, 2019, 10:25 AM Graham Perrin wrote:
> >
> > > I know, it's not appropriate to find fun in a serious discussion, but
> > > these six words did make me chuckle:
> > >
> > >  > … freedom of expression … End of discussion.
> > >
> > > No offence intended. I was speed-reading (waiting for a browser to
> > > launch) and those six words leapt out at me :-)
> > >
> >
> > Yes. There will always be limits, just like in real life. You can't tell
> > fire in a theater, and claim freedom of expression, for example.
>
> 
>
> While that is an often cited example, it is rather tenuous as far as
> "freedom of expression" is concerned: yelling "Fire!" in a crowded
> theatre is by no measure an expression of one's views, thoughts, or
> opinions.
>

Additionally, the ruling from which that quote came was used to suppress
dissent and imprison people for just that.  It is a very shaking foundation
on which to launch a censorship campaign. The main group was sentenced for
yelling fire when there really was one.

>
___
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: FreeBSD Core Team Response to Controversial Social Media Posts

[Adam]

On Sat, May 18, 2019 at 4:12 AM Igor Mozolevsky 
wrote:

> This is a typical example of reframing a problem in one side's
> favourable terms. Freedom of expression is a fundamental freedom as
> recognised by the United Nations, and is guaranteed by the highest
> courts of any civilised society. Attacking one's freedom of expression
> under whatever auspices makes one an EXCEPTIONALLY terrible person
> that should go and re-thing their life purpose! End of discussion.
>

I'd go a bit further and say its also every individuals right to be exposed
to such things, and make judgements for themselves.  The voices who are the
most different deserve the most protection.  Without these, any "freedom of
speech" is illusion.  One wonders where these advocates of censorship will
turn when the tool they helped create is eventually turned back on them.

-- 
Adam
___
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: Long waits for Firefox and SeaMonkey to respond to links from other applications

[Adam]

On Sun, Mar 24, 2019 at 6:22 PM Graham Perrin 
wrote:

> When I open a web address in (for example) Thunderbird, there's a wait
> of around fifteen seconds before the web browser, already open, handles
> the address.
>
> Affected browsers:
>
> - Firefox
> - SeaMonkey
> - Waterfox.
>
> Not affected:
>
> - New Moon (Pale Moon) – the waiting period is a split-second
> - Chromium – split-second
> - Falkon – less than two seconds.
>
> Any ideas?
>
>
Start thunderbird from a terminal so you can see an messages.  Sounds like
a tcp or dns timeout, so perhaps some addon.

-- 
Adam
___
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: ZFS no longer mounted in alphanumerical order

[Adam]

On Tue, Mar 12, 2019 at 4:56 PM Andriy Gapon  wrote:

> > Valid point.  So how do I control the order of mounts of zfs?
>
> If you really want / need / have to do it, then disable ZFS auto mounting
> in one
> of multiple ways (zfs_enable="NO", canmount=noauto, mountpoint=legacy) and
> use
> your own script or fstab to mount ZFS filesystems.
>
> Personally, I do not see any reason to do that as long as all my ZFS
> filesystems
> are properly mounted at expected mount points.
>

Maybe there some method of disabling the parallel mounting for those of us
who prefer and expect a bit more symmetry from the output and who don't
find much value in that feature.

-- 
Adam
___
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: bectl slow

[Adam]

On Mon, Feb 18, 2019 at 8:35 PM Graham Perrin 
wrote:

> Preparing to update the OS, I created a new boot environment. Creation
> took a long time, subsequent bectl commands are extraordinarily slow.
>
> Whilst composing this e-mail I'm awaiting completion of a simple list.
>
> Any ideas?
>
> zpool status shows no problem. Last scrubbed 27th December, I'll begin a
> scrub after the current 'bectl list' command completes …
>

What happens if you try it without fuse loaded?

-- 
Adam
___
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: Can't seem to use 5GHz APs with Intel wireless

[Adam]

On Sun, Jun 3, 2018 at 9:50 PM, Dhananjay Balan  wrote:

> On Sun, Jun 03, 2018 at 07:33:30PM +0200, Christoph Moench-Tegeder wrote:
>
> > Is the regdomain/country setting correct for your area and matches your
> > AP? Especially in the 5GHz band there are some "gaps" - not all channels
> > may be used in all countries (because of possible interference with
> > radar equipment and other stuff). See:
> > https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(
> 802.11a/h/j/n/ac/ax)
> >
>
> Thanks for taking time to explain.
>
> Turns out PEBKAC. I had this offending line burried in rc.conf
>
> create_args_wlan0="country DE regdomain FCC4"
>
> According to regdomain(5) 
>
> So I was forcing my card to do 2.4Ghz it seems, removed it - everything
> worked like charm. I can see and connect to 5GHz 11a aps.
>
> wlan0: flags=8843 metric 0 mtu
> 1500
> ether 
> inet 192.168.1.13 netmask 0xff00 broadcast 192.168.1.255
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet MCS mode 11na
> status: associated
> ssid  channel 36 (5180 MHz 11a ht/40+) bssid 
> regdomain FCC country US authmode WPA2/802.11i privacy ON
> deftxkey UNDEF TKIP 2:128-bit txpower 17 bmiss 10 mcastrate 6
> mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 4 -amsdutx
> amsdurx
> shortgi -stbc -ldpc wme roaming MANUAL
>
>
Thanks for the posting.  It appears I made some errors in my previous
response.  I'm using an iwm, not iwn.  And after your pointer I changed my
country to NO which then allows me to see, but not associate to 5gz.

Good yours is working.

-- 
Adam
___
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: Can't seem to use 5GHz APs with Intel wireless

[Adam]

On Sun, Jun 3, 2018 at 9:53 AM, Dhananjay Balan  wrote:

> On Sat, Jun 02, 2018 at 12:37:12AM +0200, Christoph Moench-Tegeder wrote:
> > Did you try adding "mode 11a" to select 5GHz band? (This might be
> > out-of-date, as my WiFi stuff is all on 11) (currently I'm also
> > using 2.4GHz only, for compatibility with some devices and the fact
> > that I have quite some trouble running 2.4GHz and 5GHz from the same
> > interface at the same time).
>
> I did a bit more testing, I have to admit that I am not well versed in
> wifi internals.
>
> 1. ifconfig wlan0 list aps shows my aps having rate 54M (Im not entirely
> sure what this means).
>But however when I connect to it, it shows up as 11g
>
> wlan0: flags=8843 metric 0 mtu
> 1500
> ether a4:4e:31:02:70:3c
> inet 192.168.23.111 netmask 0xff00 broadcast 192.168.23.255
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
> status: associated
> ssid LA03 channel 6 (2437 MHz 11g ht/20) bssid 52:d9:e7:47:c0:c2
> regdomain FCC4 country DE authmode WPA2/802.11i privacy ON
> deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
> protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi
> -stbc -ldpc wme roaming MANUAL
> groups: wlan
>

I do not believe the response you are replying to actually addressed 5gz
which is different than mode.  You may be able to achieve better speeds
using channel parameters.  man ifconfig.

A simple test is to have your AP present SSID of 2.4 and 5 as different
names.  If the 5 doesn't show in the above command, 5 isn't working.


> 2. Adding mode 11a to rc.conf didn't change anything. Still connects to
> 2.4Ghz band.
>

Yup


> 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some
> I tested)
>

I don't believe the iwn driver is capable of 5gz.  At least mine doesn't
work on CURRENT.


> Also, what does 11a mean? shouldn't it be 11n?
> -
> dbalan
> ___
> 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"
>



-- 
Adam
___
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: ZFS RAIDZ1: resilvering at <17.3M/s => abyssal slow ...

[Adam Vande More]

On Thu, Dec 14, 2017 at 8:52 AM, O. Hartmann <ohartm...@walstatt.org> wrote:

> Am Thu, 14 Dec 2017 15:46:17 +0100
> Dimitry Andric <d...@freebsd.org> schrieb:
>
> > On 14 Dec 2017, at 14:43, O. Hartmann <ohartm...@walstatt.org> wrote:
> > >
> > > Am Thu, 14 Dec 2017 14:09:39 +0100
> > > Daniel Nebdal <dneb...@gmail.com> schrieb:
> > >> On Thu, Dec 14, 2017 at 12:48 PM, O. Hartmann <ohartm...@walstatt.org>
> wrote:
> > >>> I just started the rebuild/resilvering process and watch the pool
> crwaling at ~ 18
> > >>> MB/s. At the moment, there is no load on the array, the host is a
> IvyBridge XEON
> > >>> with 4 core/8 threads and 3,4 GHz and 16 GB of RAM. The HDDs are
> attached to a
> > >>> on-board SATA II (300 MB/s max) Intel chip - this just for the
> record.
> > >>>
> > >>> Recently, I switch on the "sync" attribute on most of the defined
> pools's zfs
> > >>> filesystems
> > >>> - I also use a SSD for ZIL/L2ARC caching, but it seems to be unused
> recently in
> > >>> FreeBSD CURRENT's ZFS - this from a observers perspective only.
> > >>>
> > >>> When scrubbing, I see recently also reduced performance on the pool,
> so I'm
> > >>> wondering about the low throughput at the very moment when
> resilvering is in
> > >>> progress.
> > >>>
> > >>> If the "perspective" of "zpool status" is correct, then I have to
> wait after two
> > >>> hours for another 100 hours - ~ 4 days? Ups ... I think there is
> something badly
> > >>> misconfigured or missing.
> > ...
> > >> This is kind of to be expected - for whatever reason, resilvers seem
> > >> to go super slow at first and then speed up significantly. Just don't
> > >> ask me how long "at first" is - I'd give it several (more) hours.
> >
> > Hopefully this will get better in the future, please read:
> >
> > http://open-zfs.org/wiki/Scrub/Resilver_Performance
> >
> > -Dimitry
> >
>
> It has already been started to become better ;-)
>
> After a while now, the throughput is at 128 MBytes/s and the estimated
> time decreased to
> ~ 8 h now - that is much more appreciable than 4 days ;-)
>

If you are viewing the rate with zpool status, I don't think that is a
close to realtime rate.  I don't know of a way to check that either.

-- 
Adam
___
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: Extra Clang Tools

[Adam Weinberger]

> On 15 Sep, 2017, at 20:29, blubee blubeeme <gurenc...@gmail.com> wrote:
> 
> FreeBSD switched to clang as it's compiler some time ago; was clang extra
> tools: http://clang.llvm.org/extra/index.html ever ported over?
> 
> If yes, where is it located?
> Best
> ___
> freebsd-po...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Put WITH_CLANG_EXTRAS=yes in src.conf, and rebuild world.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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"

Re: recent change to vim defaults?

[Adam Weinberger]

> On 18 Jan, 2017, at 10:35, Julian Elischer <jul...@freebsd.org> wrote:
> 
> On 17/01/2017 1:23 AM, Adam Weinberger wrote:
>>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin <b...@freebsd.org> wrote:
>>> 
>>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
>>>> I noticed that suddenly vim is grabbing mouse movements, which makes life
>>>> really hard.
>>>> 
>>>> Was there a specific revision that brought in this change, and can it be
>>>> removed?
>>> This change appeared in one of the last patchset of vim 7.4 and was one of 
>>> the
>>> "features" of the vim 8.0 release.
>>> 
>>> I do agree this is just totally painful :(
>>> 
>>> Best regards,
>>> Bapt
>> One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
>> option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
>> touched it.
>> 
>> I have moused disabled in all my boxes so I have no idea about bad mouse 
>> behaviour in Vim. If there is a bad default that is causing grief, let's 
>> just fix it in that default vimrc.
>> 
>> I'm not really understanding what the unexpected behaviour is so I can't 
>> make an intelligent recommendation myself, but I'll go with whatever you 
>> folks suggest.
>> 
>> # Adam
> I'm in iterm on my mac.
> I ssh to a freebsd machine
> I use vim on a file.
> I used to be able to use the mouse on my mac to copy a few lines into the cut 
> buffer.. slide-shift-click etc..
> now suddenly if I try highlight some code in vim to copy it vim drags stuff 
> around, scrolls up and down, deletes stuff and generally makes a mess.
> if click, instead of starting a copy zone it grabs some of the text.
> 
> basically it makes hte mouse useless.
> I can;t copy and paste from a file I'm ediitng. I end up having to exit vim 
> and do it in vi.

There have been a number of recommendations in this thread for you, Julian, 
including "set mouse=a" and "set mouse=v". Test some of them out and let me 
know what works for you.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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"

Re: recent change to vim defaults?

[Adam Weinberger]

> On 16 Jan, 2017, at 9:25, Baptiste Daroussin <b...@freebsd.org> wrote:
> 
> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote:
>> I noticed that suddenly vim is grabbing mouse movements, which makes life
>> really hard.
>> 
>> Was there a specific revision that brought in this change, and can it be
>> removed?
> 
> This change appeared in one of the last patchset of vim 7.4 and was one of the
> "features" of the vim 8.0 release.
> 
> I do agree this is just totally painful :(
> 
> Best regards,
> Bapt

One of the things that I inherited with the Vim port was the DEFAULT_VIMRC 
option (which installs /usr/ports/editors/vim/files/vimrc), and I haven't 
touched it.

I have moused disabled in all my boxes so I have no idea about bad mouse 
behaviour in Vim. If there is a bad default that is causing grief, let's just 
fix it in that default vimrc.

I'm not really understanding what the unexpected behaviour is so I can't make 
an intelligent recommendation myself, but I'll go with whatever you folks 
suggest.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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"

Re: recent change to vim defaults?

[Adam Weinberger]

> On 15 Jan, 2017, at 9:03, Julian Elischer <jul...@freebsd.org> wrote:
> 
> I noticed that suddenly vim is grabbing mouse movements, which makes life 
> really hard.
> 
> Was there a specific revision that brought in this change, and can it be 
> removed?

Which patchlevel are you running?

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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"

iwn wlan connection losses after recent upgrade from 10-stable to head

[Adam Vande More]

Recently I upgraded my system to head from 10-stable:

11.0-CURRENT #0 r293760:
iwn0:  mem 0xe3c0-0xe3c01fff irq 17 at
device 0.0 on pci2
net.wlan.debug: 1
net.wlan.0.debug: 1
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 24:77:03:07:32:b8
inet 192.168.254.21 netmask 0xff00 broadcast 192.168.254.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid SSID channel 1 (2412 MHz 11g ht/20) bssid 28:c6:8e:e6:04:7c
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
AES-CCM 2:128-bit AES-CCM 3:128-bit powersavemode CAM
powersavesleep 100 txpower 13 bmiss 10 scanvalid 60 protmode CTS
ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme
roaming MANUAL
groups: wlan


While the 10-STABLE setup was never a pillar of reliability, HEAD seems to
have made things worse for my wifi setup.  Now my connections drops out
several times a day at least resulting in logs such as this:

wpa_supplicant[81975]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=28:c6:8e:e6:04:7c reason=0
kernel: wlan0: link state changed to DOWN
wpa_supplicant[81975]: wlan0: Trying to associate with 28:c6:8e:e6:04:7c
(SSID='SSID' freq=2412 MHz)
wpa_supplicant[81975]: wlan0: Authentication with 28:c6:8e:e6:04:7c timed
out.
wpa_supplicant[81975]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=28:c6:8e:e6:04:7c reason=3 locally_generated=1
wpa_supplicant[81975]: wlan0: Trying to associate with 28:c6:8e:e6:04:7c
(SSID='SSID' freq=2412 MHz)
wpa_supplicant[81975]: wlan0: Authentication with 28:c6:8e:e6:04:7c timed
out.
wpa_supplicant[81975]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=28:c6:8e:e6:04:7c reason=3 locally_generated=1
wpa_supplicant[81975]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1
ssid="SSID" auth_failures=1 duration=10 reason=CONN_FAILED
wpa_supplicant[81975]: wlan0: CTRL-EVENT-SSID-REENABLED id=1 ssid="SSID"
wpa_supplicant[81975]: wlan0: Trying to associate with 28:c6:8e:e6:04:7c
(SSID='SSID' freq=2412 MHz)
wpa_supplicant[81975]: wlan0: Authentication with 28:c6:8e:e6:04:7c timed
out.
wpa_supplicant[81975]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=28:c6:8e:e6:04:7c reason=3 locally_generated=1
wpa_supplicant[81975]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1
ssid="SSID" auth_failures=2 duration=23 reason=CONN_FAILED
wpa_supplicant[81975]: wlan0: CTRL-EVENT-SSID-REENABLED id=1 ssid="SSID"
wpa_supplicant[81975]: wlan0: Trying to associate with 28:c6:8e:e6:04:7c
(SSID='SSID' freq=2412 MHz)
wpa_supplicant[81975]: wlan0: Authentication with 28:c6:8e:e6:04:7c timed
out.

Under 10-STABLE, such events were usually only a few times a week.

I've just disabled N to see if that helps, but is the decreased reliability
expected?  Is there anything I can do to improve stability and preserve N?

Thanks,

-- 
Adam
___
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: Intel Haswell support - Any updates?

[Adam McDougall]

On Thu, Sep 17, 2015 at 12:43:59PM +0100, David Chisnall wrote:

  On 17 Sep 2015, at 11:31, Lundberg, Johannes 
 wrote:
  > 
  > Anyway, I wish the foundation would support the graphics team by sponsoring 
this development…
  
  The Foundation did fund a lot of this work, and likely will again.  The 
problem is not 
  willingness of the Foundation to fund it, nor availability of funds.

I was not aware of this and am happy to hear it!
  
  Long term, the real solution is to convince GPU vendors to put as much effort 
into 
  funding FreeBSD driver development as they do into funding Linux and Windows 
driver 
  development.  The Foundation has been reaching out in this direction,

Glad to hear this too.  It is more comforting to hear.

  but it’s far more compelling if people can document cases where lack of 
FreeBSD support 
  has cost a vendor sales.  If you’ve bought a system with an nVidia or AMD GPU 
(or, 
  ideally, if your company has bought a few thousand) because of lack of 
FreeBSD support
  from Intel, then let Intel know.
  
  David

In all seriousness, do you have a suggested contact for us?  I can't offer bulk 
sales 
avoidance but on a personal level I am clinging to a 4.5 year old laptop and 
would 
replace it tomorrow with another higher end model if I had any practical 
choices for 
FreeBSD graphics support.  Even nVidia is not a checkbox solution on laptops 
because as 
far as I understand it you still have to deal with Optimus which cannot simply 
be 
disabled as in the past.  I also have considerable stability problems with the 
nVidia 
driver on my desktops and I will be reporting it very soon after some 
debugging.  Thanks.
___
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: Broadwell Support FreeBSD 10.1

[Adam McDougall]

On 03/22/2015 19:49, Glen Barber wrote:
 On Sun, Mar 22, 2015 at 04:32:06PM -0700, Marek Novotny wrote:
 New to this group, and new to FreeBSD via PC-BSD. Really like it so far.
 Sorry if this has been asked to death already. Levono has their new T450
 with the 5th gen intel Broadwell i5 processor. I bought it with the hopes of
 running PC-BSD latest version on it. It uses intel 5500 graphics as well.
 Any potential issues using this??

 
 You won't be able to use accelerated graphics.
 
 I have the T540p which has the i7-4800MQ, and am quite happy with
 running FreeBSD CURRENT on it.  I don't care about accelerated graphics
 too much, though.
 
 One nit with the laptop is I needed to use an external USB flash drive
 to store /boot on an MBR partition, because my hard drives are
 GPT-partitioned using ZFS on '/' on GELI-encrypted providers.
 Otherwise, I have noticed that using the /boot on the GPT disk enforces
 low resolution graphics (640x480 IIRC).
 
 By using a USB flash drive for /boot, I can get 1920x1080 resolution
 (one of the many reasons for choosing this laptop).
 
 (I've been meaning to put this into the FreeBSD Wiki, but EBUSY.)
 
 Glen
 

Glen, in the past I briefly tested the uefi bootloader on a Lenovo T440s
including with scfb and I believe the default resolution would raise to
native if I also disabled CSM mode in the bios.  This affected the
console mode as well as scfb which both inherit the framebuffer from the
uefi GOP as I understand it.  Have you tried that?
You should be able to demonstrate it while booted from a uefi boot
stick, no permanent system changes necessary.

I've also been looking forward to see if this trick works with uefi
since xf86-video-scfb performance was perfectly usable on a uefi booted
mac but not the lenovo:
https://forums.freebsd.org/threads/xorg-vesa-driver-massive-speedup-using-mtrr-write-combine.46723/
___
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: default pager (csh)

[Adam McDougall]

The PAGER was less for about half a year and reverted.  Please see:

https://svnweb.freebsd.org/base?view=revisionrevision=242643
___
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: init(8) diagnostics?

[Adam Vande More]

On Sun, Nov 16, 2014 at 12:37 PM, Steve Kargl 
s...@troutmask.apl.washington.edu wrote:

 On Sun, Nov 16, 2014 at 01:23:00PM -0500, Allan Jude wrote:
  On 2014-11-16 13:07, Steve Kargl wrote:
   In init(8), one finds under DIAGNOSISTICS
  
  some processes would not die; ps axl advised.
  
   So, just how is one to actually run 'ps axl advised' as
   the message appears as init(8) is killing off the system?
  
 
  In this case 'advised' is not a literal part of the command, but rather,
  it is suggesting that running 'ps axl' will show which process(es) are
  still running, and those would be the ones that would not die.
 
  When this message comes up, how far through the shutdown are you? Does
  it stall there for a while? or continue quickly?
 

 Yes, I know that the message means that one should run 'ps axl'.

 The system is well beyond any hope of interactive commands at the
 console.  It appears right after init(8) stops syslogd and before
 the 'stopping vnlru ... done.' message.

 I was hoping that I could put the command in /etc/shutdown.rc, but
 reading that script did not provide the insight needed to automatically
 run the command.

 It is somewhat surprising that init(8) does not give the PID(s) of
 the offending process(es).


Or why doesn't it just run it automatically.

-- 
Adam
___
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: How do I get someone to look at / comment on

[Adam McDougall]

On 11/13/2014 21:07, Larry Rosenman wrote:
 this bug?
 
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194770
 
 It's to stop a constant stream of noise on my 11-CURRENT box.
 
 
 

Doesn't r273962 take care of this?
___
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: Ver 2 of the patch [was: Re: i915 driver update testing]

[Adam McDougall]

On 10/23/2014 15:03, Konstantin Belousov wrote:
 Use https://www.kib.kiev.ua/kib/drm/i915.6.patch.  I already have one
 private report of the patch worked from person who got the same panic
 in iicbb.

Yes, this one works (does not panic) and X works!  I kldloaded it after
boot as I usually do.  For the 3 minutes my computer has been up so far,
it seems the same as 10-stable.  Thanks.

___
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: Ver 2 of the patch [was: Re: i915 driver update testing]

[Adam McDougall]

On 10/22/2014 08:26, Konstantin Belousov wrote:
 On Wed, Oct 08, 2014 at 03:12:08PM -0400, Adam McDougall wrote:
 On 10/08/2014 13:05, Konstantin Belousov wrote:
 There are more occurences of the bug I fixed once in patch version 2.
 Also, since pmap changes were committed in modified form, please try
 the updated patch at https://www.kib.kiev.ua/kib/drm/i915.3.patch .


 No apparent change:
 http://www.egr.msu.edu/~mcdouga9/i915-patch3-1.txt
 cite (kgdb) p *(struct drm_i915_private *)(dev_private)
 cite No symbol dev_private in current context.
 
 This is p *(struct drm_i915_private *)(dev-dev_private)

http://www.egr.msu.edu/~mcdouga9/dev_private.txt

 
 I regenerated patch after recent merges and changes in KPI on HEAD.
 https://www.kib.kiev.ua/kib/drm/i915.4.patch
 
 Please apply it, I think the issue should be there still.  Then apply
 the following debugging patch, and set
   kenv drm.debug=0x3
 before loading i915kms.ko.  I want to see the same debugging information,
 and dmesg from the moment of loading the driver.


 In fact, try
 https://www.kib.kiev.ua/kib/drm/i915.5.patch

http://www.egr.msu.edu/~mcdouga9/dconschat.txt
___
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: Ver 2 of the patch [was: Re: i915 driver update testing]

[Adam McDougall]

On 10/08/2014 13:05, Konstantin Belousov wrote:
 On Tue, Oct 07, 2014 at 04:04:54PM -0400, Adam McDougall wrote:
 On 10/07/2014 14:01, Konstantin Belousov wrote:
 On Tue, Oct 07, 2014 at 07:44:19PM +0300, Konstantin Belousov wrote:
 From the same frame, please do
 p *(struct drm_i915_private *)(dev-private)
 p *(struct drm_i915_private *)(dev-dev_private)
 

 I probably figured out what is wrong, but it is still interesting to
 see this piece of data.

 For everybody who has the issue with blank screen or panic after
 the patch:
 1. please try the updated patch,
 https://www.kib.kiev.ua/kib/drm/i915.2.patch
 2. if you use kldload i915kms to test the patch and get the blank
screen, verify do you get panic or just a black screen.  It is
expected for sc, not so for vt.  For vt, if you do get blank screen
and not a panic, do not load i915kms manually and run the X server.
I am interested if running X server does show proper output.


 Backtrace seems the same, I repeated the prior commands:
 http://www.egr.msu.edu/~mcdouga9/i915-patch2-1.txt
 
 There are more occurences of the bug I fixed once in patch version 2.
 Also, since pmap changes were committed in modified form, please try
 the updated patch at https://www.kib.kiev.ua/kib/drm/i915.3.patch .
 

No apparent change:
http://www.egr.msu.edu/~mcdouga9/i915-patch3-1.txt

I made a log of the source operations and compile to be certain I was
using the right patch properly:
http://www.egr.msu.edu/~mcdouga9/20141008-compile.txt

Are any of these an issue in the patch?  Seem unrelated but hopefully
harmless:
diff --git a/sys/dev/md/md.c b/sys/dev/md/md.c
diff --git a/sys/fs/tmpfs/tmpfs_subr.c b/sys/fs/tmpfs/tmpfs_subr.c
diff --git a/sys/kern/kern_exec.c b/sys/kern/kern_exec.c
diff --git a/sys/kern/uipc_shm.c b/sys/kern/uipc_shm.c
diff --git a/sys/kern/uipc_syscalls.c b/sys/kern/uipc_syscalls.c
diff --git a/sys/vm/default_pager.c b/sys/vm/default_pager.c
diff --git a/sys/vm/device_pager.c b/sys/vm/device_pager.c
diff --git a/sys/vm/phys_pager.c b/sys/vm/phys_pager.c
diff --git a/sys/vm/sg_pager.c b/sys/vm/sg_pager.c
diff --git a/sys/vm/swap_pager.c b/sys/vm/swap_pager.c
diff --git a/sys/vm/vm_fault.c b/sys/vm/vm_fault.c
diff --git a/sys/vm/vm_glue.c b/sys/vm/vm_glue.c
diff --git a/sys/vm/vm_object.c b/sys/vm/vm_object.c
diff --git a/sys/vm/vm_pager.c b/sys/vm/vm_pager.c
diff --git a/sys/vm/vm_pager.h b/sys/vm/vm_pager.h
diff --git a/sys/vm/vnode_pager.c b/sys/vm/vnode_pager.c

Thanks.
___
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: i915 driver update testing

[Adam McDougall]

On 10/7/2014 12:20 AM, Konstantin Belousov wrote:

On Mon, Oct 06, 2014 at 07:30:20PM -0400, Adam McDougall wrote:

On 10/05/2014 13:00, Konstantin Belousov wrote:

On Sun, Oct 05, 2014 at 11:01:14AM -0400, Adam McDougall wrote:

(kgdb) #0  doadump (textdump=1) at pcpu.h:219
#1  0x80661efd in kern_reboot (howto=260)
 at /usr/src/sys/kern/kern_shutdown.c:447
#2  0x80662450 in panic (fmt=value optimized out)
 at /usr/src/sys/kern/kern_shutdown.c:746
#3  0x808fe52f in trap_fatal (frame=value optimized out,
 eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:866
#4  0x808fe87c in trap_pfault (frame=0xfe01fe0b21b0,
 usermode=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:677
#5  0x808fde9e in trap (frame=0xfe01fe0b21b0)
 at /usr/src/sys/amd64/amd64/trap.c:426
#6  0x808e00a2 in calltrap ()
 at /usr/src/sys/amd64/amd64/exception.S:231
#7  0x8166808e in i915_write32 (dev_priv=0xf800031f1c00,
 reg=20736, val=0)
 at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_drv.c:992

In kgdb, from this frame, please do
p *dev_priv
p *(dev_priv-dev)
p *(dev_priv-info)

http://www.egr.msu.edu/~mcdouga9/i915-1b.txt

Sorry for the delay.  I duplicated this on a spare computer of the same
model so I can test easier.

Great, thank you.  Please also do, from the frame 12,
p *dev


http://www.egr.msu.edu/~mcdouga9/i915-2.txt
___
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: i915 driver update testing

[Adam McDougall]

On 10/07/2014 12:44, Konstantin Belousov wrote:
 On Tue, Oct 07, 2014 at 09:00:56AM -0400, Adam McDougall wrote:

 On 10/7/2014 12:20 AM, Konstantin Belousov wrote:
 On Mon, Oct 06, 2014 at 07:30:20PM -0400, Adam McDougall wrote:
 On 10/05/2014 13:00, Konstantin Belousov wrote:
 On Sun, Oct 05, 2014 at 11:01:14AM -0400, Adam McDougall wrote:
 (kgdb) #0  doadump (textdump=1) at pcpu.h:219
 #1  0x80661efd in kern_reboot (howto=260)
  at /usr/src/sys/kern/kern_shutdown.c:447
 #2  0x80662450 in panic (fmt=value optimized out)
  at /usr/src/sys/kern/kern_shutdown.c:746
 #3  0x808fe52f in trap_fatal (frame=value optimized out,
  eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:866
 #4  0x808fe87c in trap_pfault (frame=0xfe01fe0b21b0,
  usermode=value optimized out) at 
 /usr/src/sys/amd64/amd64/trap.c:677
 #5  0x808fde9e in trap (frame=0xfe01fe0b21b0)
  at /usr/src/sys/amd64/amd64/trap.c:426
 #6  0x808e00a2 in calltrap ()
  at /usr/src/sys/amd64/amd64/exception.S:231
 #7  0x8166808e in i915_write32 (dev_priv=0xf800031f1c00,
  reg=20736, val=0)
  at
 /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_drv.c:992
 In kgdb, from this frame, please do
 p *dev_priv
 p *(dev_priv-dev)
 p *(dev_priv-info)
 http://www.egr.msu.edu/~mcdouga9/i915-1b.txt

 Sorry for the delay.  I duplicated this on a spare computer of the same
 model so I can test easier.
 Great, thank you.  Please also do, from the frame 12,
 p *dev

 http://www.egr.msu.edu/~mcdouga9/i915-2.txt
 
 From the same frame, please do
 p *(struct drm_i915_private *)(dev-private)
 

(kgdb) f 12
#12 0x81681bd7 in intel_modeset_init (dev=0xf80003bd9000)
at
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/intel_display.c:6603
6603found = intel_sdvo_init(dev, PCH_SDVOB, true);
Current language:  auto; currently minimal
(kgdb) p *(struct drm_i915_private *)(dev-private)
There is no member named private.

___
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: i915 driver update testing

[Adam McDougall]

On 10/07/2014 14:24, Konstantin Belousov wrote:
 On Tue, Oct 07, 2014 at 02:08:06PM -0400, Adam McDougall wrote:
 On 10/07/2014 12:44, Konstantin Belousov wrote:
 On Tue, Oct 07, 2014 at 09:00:56AM -0400, Adam McDougall wrote:

 On 10/7/2014 12:20 AM, Konstantin Belousov wrote:
 On Mon, Oct 06, 2014 at 07:30:20PM -0400, Adam McDougall wrote:
 On 10/05/2014 13:00, Konstantin Belousov wrote:
 On Sun, Oct 05, 2014 at 11:01:14AM -0400, Adam McDougall wrote:
 (kgdb) #0  doadump (textdump=1) at pcpu.h:219
 #1  0x80661efd in kern_reboot (howto=260)
  at /usr/src/sys/kern/kern_shutdown.c:447
 #2  0x80662450 in panic (fmt=value optimized out)
  at /usr/src/sys/kern/kern_shutdown.c:746
 #3  0x808fe52f in trap_fatal (frame=value optimized out,
  eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:866
 #4  0x808fe87c in trap_pfault (frame=0xfe01fe0b21b0,
  usermode=value optimized out) at 
 /usr/src/sys/amd64/amd64/trap.c:677
 #5  0x808fde9e in trap (frame=0xfe01fe0b21b0)
  at /usr/src/sys/amd64/amd64/trap.c:426
 #6  0x808e00a2 in calltrap ()
  at /usr/src/sys/amd64/amd64/exception.S:231
 #7  0x8166808e in i915_write32 (dev_priv=0xf800031f1c00,
  reg=20736, val=0)
  at
 /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_drv.c:992
 In kgdb, from this frame, please do
 p *dev_priv
 p *(dev_priv-dev)
 p *(dev_priv-info)
 http://www.egr.msu.edu/~mcdouga9/i915-1b.txt

 Sorry for the delay.  I duplicated this on a spare computer of the same
 model so I can test easier.
 Great, thank you.  Please also do, from the frame 12,
 p *dev

 http://www.egr.msu.edu/~mcdouga9/i915-2.txt

 From the same frame, please do
 p *(struct drm_i915_private *)(dev-private)


 (kgdb) f 12
 #12 0x81681bd7 in intel_modeset_init (dev=0xf80003bd9000)
 at
 /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/intel_display.c:6603
 6603 found = intel_sdvo_init(dev, PCH_SDVOB, true);
 Current language:  auto; currently minimal
 (kgdb) p *(struct drm_i915_private *)(dev-private)
 There is no member named private.
 It is dev_private, typo.
 
I actually took a guess at that too, but this didn't look helpful:
(kgdb) p *(struct drm_i915_private *)(dev_private)
No symbol dev_private in current context.

___
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: Ver 2 of the patch [was: Re: i915 driver update testing]

[Adam McDougall]

On 10/07/2014 14:01, Konstantin Belousov wrote:
 On Tue, Oct 07, 2014 at 07:44:19PM +0300, Konstantin Belousov wrote:
 From the same frame, please do
 p *(struct drm_i915_private *)(dev-private)
 
 I probably figured out what is wrong, but it is still interesting to
 see this piece of data.
 
 For everybody who has the issue with blank screen or panic after
 the patch:
 1. please try the updated patch,
   https://www.kib.kiev.ua/kib/drm/i915.2.patch
 2. if you use kldload i915kms to test the patch and get the blank
screen, verify do you get panic or just a black screen.  It is
expected for sc, not so for vt.  For vt, if you do get blank screen
and not a panic, do not load i915kms manually and run the X server.
I am interested if running X server does show proper output.
 

Backtrace seems the same, I repeated the prior commands:
http://www.egr.msu.edu/~mcdouga9/i915-patch2-1.txt
___
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: i915 driver update testing

[Adam McDougall]

On 10/05/2014 13:00, Konstantin Belousov wrote:
 On Sun, Oct 05, 2014 at 11:01:14AM -0400, Adam McDougall wrote:
 (kgdb) #0  doadump (textdump=1) at pcpu.h:219
 #1  0x80661efd in kern_reboot (howto=260)
 at /usr/src/sys/kern/kern_shutdown.c:447
 #2  0x80662450 in panic (fmt=value optimized out)
 at /usr/src/sys/kern/kern_shutdown.c:746
 #3  0x808fe52f in trap_fatal (frame=value optimized out,
 eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:866
 #4  0x808fe87c in trap_pfault (frame=0xfe01fe0b21b0,
 usermode=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:677
 #5  0x808fde9e in trap (frame=0xfe01fe0b21b0)
 at /usr/src/sys/amd64/amd64/trap.c:426
 #6  0x808e00a2 in calltrap ()
 at /usr/src/sys/amd64/amd64/exception.S:231
 #7  0x8166808e in i915_write32 (dev_priv=0xf800031f1c00,
 reg=20736, val=0)
 at
 /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/i915_drv.c:992
 In kgdb, from this frame, please do
 p *dev_priv
 p *(dev_priv-dev)
 p *(dev_priv-info)

http://www.egr.msu.edu/~mcdouga9/i915-1b.txt

Sorry for the delay.  I duplicated this on a spare computer of the same
model so I can test easier.
___
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: i915 driver update testing

[Adam McDougall]

On 10/03/2014 13:02, Konstantin Belousov wrote:
 Please find at the
 https://kib.kiev.ua/kib/drm/i915.1.patch
 a patch which provides some updates to the i915 driver. At large, this
 is import of the batch of Linux commits, and as such, it is interesting
 mostly as attempt to restart the race to get us more up to date Linux code
 imported. It might provide some bug fixes, most likely for IvyBridge.
 Interesting from the development PoV is the update of the GEM i/o ioctl
 code path to mimic Linux code structure.
 
 I am asking _only_ for reports of regressions with the patch applied,
 comparing with the code which is currently in HEAD. I will not debug
 any existing bugs, my goal right now is to commit this update, which is
 needed for further work. I.e., only when you get an issue with the patch
 applied, but cannot reproduce the problem without the patch, please
 prepare a bug report.
 
 FYI, the driver will attach to haswell gfx, but I am not interested in
 reports about this (see above paragraph). On my test box, which is Core
 i7 4770S, the mode-setting and front-buffer rendering works, but Mesa
 immediately cause renderer to bug out.
 
 Work was sponsored by The FreeBSD Foundation, both by time and hardware,
 and Intel provided access to the documentation.

I receive a Fatal trap 12: page fault while in kernel mode.

I was previously loading i915kms in rc.conf on 10-stable where the
screen would blank out for a short time then switch to native
resolution.  Last night I compiled a fresh kernel from -head so I could
test recent ZFS code (userland still from 10).  It behaved like 10.
After applying i915.1.patch, the screen blanks in the same place then
invisibly panics with a page fault.  I hastily replaced the broken
kernel so I didn't accidentally boot it, but I would be happy to compile
a new one (FYI since info below may not match a new compile).  Please
tell me if or how you would like me to help.  Thanks.

FreeBSD colfax 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r272549M: Sun Oct  5
10:32:28 EDT 2014 mcdouga9@colfax:/usr/obj/usr/src/sys/AMD64-11  amd64

panic: page fault

CPU: Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz (3325.07-MHz
K8-class CPU)

[11] Loading kernel modules:
[11] info: [drm] Initialized drm 1.1.0 20060810
[11] drmn0: Intel IronLake on vgapci0
[11] info: [drm] MSI enabled 1 message(s)
[11] info: [drm] AGP at 0xd000 256MB
[11] iicbus0: Philips I2C bus on iicbb0 addr 0xff
[11] iic0: I2C generic I/O on iicbus0
[11] iic1: I2C generic I/O on iicbus1
[11] iicbus2: Philips I2C bus on iicbb1 addr 0x0
[11] iic2: I2C generic I/O on iicbus2
[11] iic3: I2C generic I/O on iicbus3
[11] iicbus4: Philips I2C bus on iicbb2 addr 0x0
[11] iic4: I2C generic I/O on iicbus4
[11] iic5: I2C generic I/O on iicbus5
[11] iicbus6: Philips I2C bus on iicbb3 addr 0x0
[11] iic6: I2C generic I/O on iicbus6
[11] iic7: I2C generic I/O on iicbus7
[11] iicbus8: Philips I2C bus on iicbb4 addr 0x0
[11] iic8: I2C generic I/O on iicbus8
[11] iic9: I2C generic I/O on iicbus9
[11] iicbus10: Philips I2C bus on iicbb5 addr 0x0
[11] iic10: I2C generic I/O on iicbus10
[11] iic11: I2C generic I/O on iicbus11
[11] info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[11] info: [drm] Driver supports precise vblank timestamp query.
[11]
[11]
[11] Fatal trap 12: page fault while in kernel mode
[11] cpuid = 0; apic id = 00
[11] fault virtual address  = 0x0
[11] fault code = supervisor read data, page not present
[11] instruction pointer= 0x20:0x8166808e
[11] stack pointer  = 0x28:0xfe01fe0b2260
[11] frame pointer  = 0x28:0xfe01fe0b22a0
[11] code segment   = base 0x0, limit 0xf, type 0x1b
[11]= DPL 0, pres 1, long 1, def32 0, gran 1
[11] processor eflags   = interrupt enabled, resume, IOPL = 0
[11] current process= 124 (kldload)
[11] trap number= 12
[11] panic: page fault
[11] cpuid = 0
[11] Uptime: 11s
[11] Dumping 252 out of 3874
MB:..7%..13%..26%..32%..45%..51%..64%..76%..83%..95%

Reading symbols from /boot/kernel/zfs.ko.symbols...done.
Loaded symbols for /boot/kernel/zfs.ko.symbols
Reading symbols from /boot/kernel/opensolaris.ko.symbols...done.
Loaded symbols for /boot/kernel/opensolaris.ko.symbols
Reading symbols from /boot/kernel/linprocfs.ko.symbols...done.
Loaded symbols for /boot/kernel/linprocfs.ko.symbols
Reading symbols from /boot/kernel/linux.ko.symbols...done.
Loaded symbols for /boot/kernel/linux.ko.symbols
Reading symbols from /boot/kernel/i915kms.ko.symbols...done.
Loaded symbols for /boot/kernel/i915kms.ko.symbols
Reading symbols from /boot/kernel/drm2.ko.symbols...done.
Loaded symbols for /boot/kernel/drm2.ko.symbols
Reading symbols from /boot/kernel/iicbus.ko.symbols...done.
Loaded symbols for /boot/kernel/iicbus.ko.symbols
Reading symbols from /boot/kernel/iic.ko.symbols...done.
Loaded symbols for /boot/kernel/iic.ko.symbols
Reading symbols from 

Re: UEFI display frozen on Retina MacBook Pro

[Adam McDougall]

On 09/10/2014 02:08, Rui Paulo wrote:
 On Sep 8, 2014, at 06:21, Anders Bolt Evensen andersb...@icloud.com wrote:

 To see the FreeBSD (U)EFI boot loader on the Mac, you need to install an EFI 
 shell like rEFIt on either your hard drive or a HFS formatted memory stick:
 
 I think this is just a problem with our EFI implementation, though.  We 
 should be able to switch to text mode like rEFIt does.
 
 --
 Rui Paulo
 
 
 
 ___
 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
 

Please see
http://www.mail-archive.com/freebsd-current@freebsd.org/msg155044.html
for a patch.
___
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: UEFI display frozen on Retina MacBook Pro

[Adam McDougall]

On 09/10/2014 11:09, John Baldwin wrote:
 On Wednesday, September 10, 2014 08:03:47 AM Adrian Chadd wrote:
 Would you or someone else please file a PR with that patch? That way
 it doesn't get lost.

 https://bugs.freebsd.org/submit/

 Thanks!
 
 Please assign it to emaste@ as he had volunteered to commit the patch 
 previously.
 
 Also, Ed, regarding the earlier thread about this, I think instead of hacking 
 up the EFI headers, we should use the stock headers and adjust our code to 
 use 
 whatever naming contentions (CamelCase, etc.) those use.  This is what we do 
 with ACPICA for example.
 

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193524
___
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: nscd not caching

[Adam McDougall]

On 08/17/2014 09:09, Eggert, Lars wrote:
 Nobody using nscd? Really?
 

I would test for you, but we retired our NIS infrastructure at least a
year ago.  I did have it working on a test client at some point, but I
didn't push it into production because I found a couple issues (below).

We were using +: type entries in the local password and group
tables and I believe we used an unmodified /etc/nsswitch.conf (excluding
cache lines while testing nscd):

group: compat
group_compat: nis
hosts: files dns
networks: files
passwd: compat
passwd_compat: nis
shells: files
services: compat
services_compat: nis
protocols: files
rpc: files

The two main problems I recall were nscd making java crash, and nscd
holding on to negative cache lookups too long, causing failures while
installing ports that depend on adding users/groups for a following file
permission change.  I can't remember if the latter issue was fixed at
some point.  I also can't remember if I was receiving perfectly accurate
results from the cache either.

At our site, we never had enough load to outright require nscd on
FreeBSD, although there were some areas where caching had a usability
benefit.  top was slow to open since it would load the whole passwd
table first, but top -u was a workaround.  Our Samba servers allowed
users to connect a few seconds quicker if it didn't have to pull down
the entire group table to check group membership of the connecting user.
 As a workaround until we retired NIS, I wrote a hack of a script to
merge NIS groups into my local /etc/group files periodically from cron.
 Aside from bugs in my script, that worked well.

I dabbled with nscd a bit after we switched from NIS to LDAP.  I think I
recall lookups being slightly slower WITH the cache, plus I would get
some duplicated group entries returned on all but the first getent
group.  The short version is we in no way seem to benefit or require a
cache of LDAP with our site size, so I'm just not using nscd.  I didn't
make bug reports for these issues, I had to prioritize towards more
pressing issues.  I'm trying to do better about reporting bugs.


___
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: android bsd connectivity tools etc ?

[Adam Vande More]

On Wed, Aug 13, 2014 at 6:47 PM, Julian H. Stacey j...@berklix.com wrote:

 Hi,
 Any tips for Android / FreeBSD BSD tools for connectivity etc ?

 I just got a Samsung Galaxy Note 3, with Android 4.4.2 kernel 3.4.0

 It directs me to
 https://www.android.com/filetransfer/
 which seems binary for mac

 I recall I will need current for IP tethering

 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-usb-tethering.html

 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html#networking-lagg-wired-and-wireless

 I'll build a current from a 10.0-RELEASE partition,
 but now looking with 9.2-RELEASE I see:

 /dev/
 lrwxr-xr-x  1 root  wheel9 Aug 14 00:01 ugen1.5@ - usb/1.5.0
 crw---  1 root  operator  0x7a Aug 14 00:00 usb/1.5.0
 crw---  1 root  operator  0x8f Aug 14 00:00 usb/1.5.1
 crw---  1 root  operator  0x90 Aug 14 00:00 usb/1.5.2

 devd .conf will need:
match   vendor0x04e8;
match   product   0x6860;
match   devclass  0x00;
match   devsubclass   0x00;
match   sernum6758498c;
match   release   0x0400;
 I've no idea what to do for attach

 http://www.freebsd.org/cgi/ports.cgi?query=androidstype=all
 has just
 /usr/ports/devel/android-tools-adb/pkg-descr
  these for cross compiling later:
 /usr/ports/lang/*gnatdroid*/pkg-descr

 I also found
 ports/
 deskutils/tine20
 net/crtmpserver
 net/linphone
 https://source.android.com/source/index.html

 Any URLs, tips, comments welcome, Thanks


Android can run an sshd server as well as a socks proxy.


-- 
Adam
___
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: uefi boot on Apple Mac

[Adam McDougall]

I could boot from USB but the console stops after printing the
resolution.  I tried on a macbookpro of unknown age (not brand new, not
very old) and a newer Air.  I could tell by the way my USB key blinked
that it actually finished booting and went to the installer, and would
shut down properly when I hit the power button.  I modified my USB key
to enable a vt100 serial console on /dev/cuaU0 in /etc/ttys and used a
USB serial console where I could login and run bsdinstall if I wanted.
I was able to finish a bootable uefi install to a second USB key but
the console on all of these installs stops after printing the
resolution.  It was not clear to me if it that means it just doesn't
support the screen or what.  X claimed it could not find a console.

On 07/12/2014 10:24, Huang Wen Hui wrote:
 As loader.efi and kernel not change at all from USB to CD, I am confuse why
 you can boot from CD.
 Anyway, I try to boot from CD as you suggest, but I got the same result as
 before:(
 
 
 2014-07-12 18:09 GMT+08:00 Anders Bolt-Evensen andersb...@icloud.com:
 
 I also got a message like that when I booted from a USB stick on a
 MacBookPro8,3 (17 inch, late 2011).

 I fixed it by creating a custom ISO image and burned that onto a DVD using
 an external DVD drive.
 The UEFI installer boots fine from this external DVD drive.

 Here is how I did it:

 Genereste an ISO with the FreeBSD-CURRENT kernel, mount the ISO and copy
 all files from the root directory in the ISO and unmount
  cd /usr/src/release
  sh ./generate-release.sh # You may have to run “make buildworld” and
 be connected to the internet to install required ports.
  mount -t cd9660 /scratch/R/release/FreeBSD-something-disc1.iso /mnt
  mkdir freebsd_generic_installer
 #Files copied to the directory in the next command will be copied to a
 new ISO in step 3
  cp -R /mnt/ freebsd_generic_installer/
  umount /mnt
 2. Create a FAT filesystem image and place the loader in it in the default
 path that UEFI will look for (the following steps are copied from
 https://wiki.freebsd.org/UEFI#CD.2FDVD_Boot_under_UEFI):
  dd if=/dev/zero of=efiboot.img bs=4k count=100
  mdconfig -a -t vnode -f efiboot.img
  newfs_msdos -F 12 -m 0xf8 /dev/md0
  mount -t msdosfs /dev/md0 /mnt
  mkdir -p /mnt/efi/boot
  cp loader.efi /mnt/efi/boot/bootx64.efi
  umount /mnt
  mdconfig -d -u 0

 3. Create the custom ISO image. Please make sure that the entry in
 freebsd_generic_installer/etc/fstab matches the label you choose in the
 command below.
  makefs -t cd9660 -o bootimage='i386;efiboot.img' -o no-emul-boot -o
 rockridge -o label=“FREEBSD_UEFI_INSTALL -o publisher=test uefi-test.iso
 freebsd_generic_installer/

 To get the example in the command above to work, please make sure that the
 entry in freebsd_generic_installer/etc/fstab reads
 /dev/iso9660/FREEBSD_UEFI_INSTALL/cd9660ro0 0

 4. Burn the image to DVD, reboot your system and choose “EFI Boot”. Note
 that unless you are using a EFI console like rEFIt or rEFInd, you may have
 to kind of wait a couple of minutes while the kernel is loading before
 anything appears on the screen.



 On 04/07/14 16:34, Huang Wen Hui wrote:

 Hi,
 On my MacbookPro11,3, I got this error message:

 http://sw.gddsn.org.cn/freebsd/uefi.jpg

 cheers,

 Huang WenHui

 2014-07-04 22:13 GMT+08:00 Ed Maste ema...@freebsd.org:

  On 24 May 2014 19:39, Rafael Espíndola rafael.espind...@gmail.com
 wrote:

 Yes, I got that in the mac laptops I tried, it worked on a Mac Pro. It
 might be the frame buffer corruption that Ed Maste was mentioning.

 I purchased a new MacBook Air yesterday (model identifier
 MacBookAir6,2).  UEFI boot and vt(4) worked correctly.  (My image
 included Rafael's patch; I haven't tried a boot without.)

 I also committed a change to display the framebuffer parameters
 (address, dimensions, etc.) on boot, in order to help identify the
 source of this issue.  If you have a moment can you build a new USB
 stick image and give it a try?

 -Ed

  ___
 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
 



 ___
 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
 

___
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: diskid documentation

[Adam McDougall]

On 06/01/2014 10:17, Sean Bruno wrote:
 On Sun, 2014-06-01 at 09:41 -0400, Michael W. Lucas wrote:
 Hi,

 I'm trying to track down the documentation for the /dev/diskid/blah
 device nodes. Is there a man page?

 It appears that this is a current-only thing, so I'm asking here? (At
 least, none of my 9.x or 10.x machines have /dev/diskid.)

 Thanks,
 ==ml



 
 
 I'm afraid not.  In this case sys/geom/label/g_label_disk_ident.c *is*
 the documentation.
 
 sean
 
 bcc current@
 cc  geom@
 

Also, I believe it is only in 10.0-RELEASE and higher.  Even if your
kernel supports it, /dev/diskid will not exist if no hardware is found
with supported strings (tested in a VM just now).
___
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

Should we make WITHOUT_LIB32=yes the default for 11-RELEASE?

[Adam McDougall]

On most amd64 systems I run, I usually set WITHOUT_LIB32=yes in /etc/src.conf
because I don't need them.  This weekend I did a stock install on an older
AMD64 Core 2 Duo minipc and a buildworld of 10-STABLE took almost two hours 
with LIB32 and CLANG since much of it gets compiled twice.

Is it time to deprecate LIB32 in -current for 11-RELEASE?  I realize some
ports may need it, but I hope that need is waning and we are just spending
a lot of compile time by default for little gain.  We could save a lot of
compile time for a lot of users, and they could still opt-in if needed.
Putting it up for discussion, not insisting it should be done.  Thanks.
___
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: What on earth is all this %20 crap at the end of the GUID? (newfs?)

[Adam McDougall]

On 04/29/2014 19:51, Sean Bruno wrote:
 Created a simple partition:
 
  root@:~ # gpart create -s gpt da11
 da11 created
 root@:~ # gpart add -t freebsd-ufs da11
 da11p1 added
 root@:~ # gpart show da11
 =40  7814037088  da11  GPT  (3.6T)
   40  7814037088 1  freebsd-ufs  (3.6T)
 
 root@:~ # 
 
 Then run a newfs and reboot the system.  Upon reboot this is what I get?
 
 =40  7814037088  da11  GPT  (3.6T)
   40  7814037088 1  freebsd-ufs  (3.6T)
 =40  7814037088  diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20%
 20%20%20%20  GPT  (3.6T)
   40  7814037088
 1  freebsd-ufs  (3.6T)
 
 
 What is going on here?
 
 sean
 

I'm guessing it is picking up spaces from a physical ID on your disk
from /sys/geom/label/g_label_disk_ident.c

kern.geom.label.disk_ident.enable=0 in /boot/loader.conf will ignore
that class.  It was added in 10 and only shows up with certain devices.
___
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 command can block the whole ZFS subsystem!

[Adam Vande More]

On Sun, Jan 5, 2014 at 2:11 AM, O. Hartmann ohart...@zedat.fu-berlin.dewrote:

 On Sun, 5 Jan 2014 10:14:26 +1100
 Peter Jeremy pe...@rulingia.com wrote:

  On 2014-Jan-04 23:26:42 +0100, O. Hartmann
  ohart...@zedat.fu-berlin.de wrote:
  zfs list -r BACKUP00
  NAME  USED  AVAIL  REFER  MOUNTPOINT
  BACKUP00 1.48T  1.19T   144K  /BACKUP00
  BACKUP00/backup  1.47T  1.19T  1.47T  /backup
 
  Well, that at least shows it's making progress - it's gone from 2.5T
  to 1.47T used (though I gather that has taken several days).  Can you
  pleas post the result of
  zfs get all BACKUP00/backup
 

 Here we go:


 NAME PROPERTY  VALUE SOURCE
 BACKUP00/backup  type  filesystem-
 BACKUP00/backup  creation  Fr Dez 20 23:17 2013  -
 BACKUP00/backup  used  1.47T -
 BACKUP00/backup  available 1.19T -
 BACKUP00/backup  referenced1.47T -
 BACKUP00/backup  compressratio 1.00x -
 BACKUP00/backup  mounted   no-
 BACKUP00/backup  quota none  default
 BACKUP00/backup  reservation   none  default
 BACKUP00/backup  recordsize128K  default
 BACKUP00/backup  mountpoint/backup   local
 BACKUP00/backup  sharenfs  off   default
 BACKUP00/backup  checksum  sha256local
 BACKUP00/backup  compression   lz4   local
 BACKUP00/backup  atime ondefault
 BACKUP00/backup  devices   ondefault
 BACKUP00/backup  exec  ondefault
 BACKUP00/backup  setuidondefault
 BACKUP00/backup  readonly  off   default
 BACKUP00/backup  jailedoff   default
 BACKUP00/backup  snapdir   hiddendefault
 BACKUP00/backup  aclmode   discard   default
 BACKUP00/backup  aclinheritrestricteddefault
 BACKUP00/backup  canmount  ondefault
 BACKUP00/backup  xattr ondefault
 BACKUP00/backup  copies1 default
 BACKUP00/backup  version   5 -
 BACKUP00/backup  utf8only  off   -
 BACKUP00/backup  normalization none  -
 BACKUP00/backup  casesensitivity   sensitive -
 BACKUP00/backup  vscan off   default
 BACKUP00/backup  nbmandoff   default
 BACKUP00/backup  sharesmb  onlocal
 BACKUP00/backup  refquota  none  default
 BACKUP00/backup  refreservationnone  default
 BACKUP00/backup  primarycache  all   default
 BACKUP00/backup  secondarycacheall   default
 BACKUP00/backup  usedbysnapshots   0 -
 BACKUP00/backup  usedbydataset 1.47T -
 BACKUP00/backup  usedbychildren0 -
 BACKUP00/backup  usedbyrefreservation  0 -
 BACKUP00/backup  logbias   latency   default
 BACKUP00/backup  dedup onlocal


As already described by Dan and perhaps not followed up on:  dedup requires
at very large amount of memory.  Assuming 32GB is sufficient is most likely
wrong.

What does zdb -S BACKUP00 say?

Also I will note you were asked if the ZFS FS in question had dedup
enabled.  You replied with a response from an incorrect FS.



-- 
Adam
___
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 command can block the whole ZFS subsystem!

[Adam Vande More]

On Sun, Jan 5, 2014 at 9:41 AM, O. Hartmann ohart...@zedat.fu-berlin.dewrote:

 
  As already described by Dan and perhaps not followed up on:  dedup
  requires at very large amount of memory.  Assuming 32GB is sufficient
  is most likely wrong.
 
  What does zdb -S BACKUP00 say?

 That command is stuck for 2 hours by now ...


That is expected. It is not stuck, it is running.  It's output will
indicate what is the minimum required for your dataset. The command will be
slow if you have large dataset/insufficient ram.  Really slow if both.


-- 
Adam
___
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: RTL8111/8168B not negotiating 1GB

[Adam Vande More]

On Thu, Jan 2, 2014 at 7:39 PM, Sam Fourman Jr. sfour...@gmail.com wrote:

 Hello list,

 I have a Asus Sabertooth 990FXv2 motherboard,  and a run of the mill
 NetGear DGS2205 desktop gig switch

 with linux my Ethernet can negotiate at 1GB but with FreeBSD it can not
 if I force the device to 1000baseT  with ifconfig it does not work.


 uname -a
 FreeBSD NewBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r260188M: Thu Jan  2
 04:27:49 CST 2014 sfourman@NewBSD:/usr/obj/usr/src/sys/GENERIC  amd64



 re0@pci0:10:0:0: class=0x02 card=0x85051043 chip=0x816810ec rev=0x09
 hdr=0x00
 vendor = 'Realtek Semiconductor Co., Ltd.'
 device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
 class  = network
 subclass   = ethernet



 root@NewBSD:/usr/home/sfourman/Desktop # ifconfig
 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE
 ether 60:a4:4c:60:d5:a7
 inet 192.168.1.31 netmask 0xff00 broadcast 192.168.1.255
 inet6 fe80::62a4:4cff:fe60:d5a7%re0 prefixlen 64 scopeid 0x1
 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
 media: Ethernet autoselect (100baseTX full-duplex)
 status: active


/etc/rc.conf is important here as well as the complete steps and output
which provoked this response:

but with FreeBSD it can not
if I force the device to 1000baseT  with ifconfig it does not work.

In the given output, autoselect clearly selects 100Mb connection, the
question is why.



-- 
Adam
___
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: [RFC] libdispatch (aka Grand Central Dispatch) in base

[Adam Vande More]

On Tue, Oct 29, 2013 at 9:04 PM, Teske, Devin devin.te...@fisglobal.comwrote:

 Hi all,

 I'd like to bring up the discussion for topic..

 Importing libdispatch (aka Apple's Grand Central Dispatch) into base
 (contrib?).

 Specifically into HEAD then MFC'd only as far back as stable/10.

 Here's the reason why:
 http://devinteske.com/freebsd-installer-enhancements

 Summary:
 For the purpose of providing a concurrency model better than pthreads for
 the
 expressed desire to bring about concurrent data processing (applicable
 directly
 to distributions, packages, signing and more).

 Multiple people have confirmed with me with respect to the above blog
 article
 that the concurrency model would be most efficient with libdispatch.

 Since the tool mentioned in the blog is
 a. Compiling with clang
 b. Requires newest dialog(3) that is only in stable/10 or higher

 I'd say that it looks like a match made in heaven.

 But of course, there's that one hang-up... dispatch is not available in
 base yet.

 Is anyone working on getting dispatch into base?


FWIW, I say +1 to your proposition and +1 to your contribs. However I say
prove it works.
,


-- 
Adam
___
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: Buying recommendation for silent router/fileserver

[Adam McDougall]

Finally got around to it, kern/182818. Thanks for the encouragement.

On 10/12/12 11:14, Adam McDougall wrote:

I did not, but I put it on my list to try to accomplish.

On 10/11/12 13:41, Adrian Chadd wrote:

Did you ever file a PR for the slow SATA behaviour?



Adrian


On 11 October 2012 09:52, Adam McDougall mcdou...@egr.msu.edu wrote:


Be wary of the Soekris net6501, I bought three of the 1.6Ghz net6501-70
model which has an Atom E-680 cpu (E series) and it compiles more 
than twice
as slow as a 1.6Ghz Atom N270 in an older netbook.  Someone else 
running

Linux reported similar CPU slowness.  As far as practical network
throughput, I could only get 100Mbit/sec with a simple HTTP download 
of a

file full of zeros, and OpenVPN could only push about 25Mbit/sec.  As a
practical example of the CPU slowness, it takes about 1.5 minutes to 
compile
pkg on the N270 netbook and 5 minutes on the 6501 (around 4.5 if I 
use -j2).

A kernel compile took an hour. Unfortunately I had no idea this CPU
(possibly implementation?) was so slow before I purchased it, and I 
could
scarcely find evidence of it on google after hours of searching when 
I had

already discovered the issue.  I was hoping to find some comparative
benchmarks between various Atom series but manufacturers generally 
don't do

that.

Additionally, the total AHCI SATA write speed on the net6501 (in BSD 
only?)
has a strange 20MB/sec limitation but reads can go over 100MB/sec.  
If I

write to one disk I get 20MB/sec, if I write to both SATA disks I get
10MB/sec each.  Write is equally slow on a SSD.  Both someone running
OpenBSD and I running FreeBSD reported the same symptoms to the 
soekris-tech
mailing list and received no useful replies towards getting that 
problem
solved.  I tested the write speed briefly with Linux and it did not 
appear
to have the 20MB/sec limitation.  I did confirm it was using 
MSI(-X?) with
boot -v.  I think this hardware would need to fall into Alexander 
Motin's
hands to get anywhere with debugging the SATA speed issue. Since it 
seems
fine in Linux, maybe some day it can be fixed in BSD but I have no 
clue how
that limitation could happen.  The disks I tested with are fine in 
normal

computers.

___
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




___
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: rcs is gone?

[Adam Vande More]

On Mon, Oct 7, 2013 at 8:16 PM, Julian Elischer jul...@freebsd.org wrote:

 On 10/8/13 9:05 AM, Lyndon Nerenberg wrote:

 On 2013-10-07, at 5:58 PM, Ian Lepore i...@freebsd.org wrote:

  I have not re-read those threads to see just how much of the discussion
 involved rcs, I just spot-checked a few and confirmed my memory that it
 showed up in some of the messages there.

 I don't see any discussion as to why the code (CVS, in this case) *needs*
 to be removed.

 What, in the current builds of 10.x, is broken by leaving RCS/CVS in
 place?  And what, as 10.x moves forward towards a public release, will be
 broken by leaving this code in the base?

 I have less of a problem with replacing CVS with svnlite than I have with
 removing RCS.
 After all CVS's main reason for being in the system has switched to
 svnlite.
 And if you are using CVS yourself for other developement, you are probbaly
 further
 on with installing a system and are already installing other packages.
 that's not the case with RCS. I know that people use it as part of their
 install
 procedure. Plus RCS is used within other tools. e.g. patch etc. It's also
 a REALLY SMALL
 utility, suitable for embedding into scripts etc. (the Unix way(TM)) I
 consider it a base utility.
 It does a simple operation on a file.

 the discussion in arch was A YEAR AGO, was hidden under a differnet title,
 and DID NOT RESULT
 in a clear mandate to remove RCS.

 Please put it back, and inthe mena while while we discuss it properly this
 time, please revert the commit
 (official request.. as described in the group rules).


I would like to see RCS remain in base as well.  Many enterprise distro
still ship it by default too.  There is no compelling reason to remove it.



-- 
Adam Vande More
___
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: rcs is gone?

[Adam Vande More]

On Mon, Oct 7, 2013 at 8:30 PM, Adam Vande More amvandem...@gmail.comwrote:


 I would like to see RCS remain in base as well.  Many enterprise distro
 still ship it by default too.  There is no compelling reason to remove it.


I sort of retract that statement.  I thought the base RCS was already
OpenRCS.  I support the inclusion of OpenRCS.  That functionality is very
useful and many admins are used to having it present.



-- 
Adam Vande More
___
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: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]

[Adam McDougall]

On 09/21/13 09:41, Davide Italiano wrote:

On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann
ohart...@zedat.fu-berlin.de wrote:

On Sat, 21 Sep 2013 07:08:25 -0500
Bryan Drewery bdrew...@freebsd.org wrote:


On 9/21/2013 7:06 AM, Bjoern A. Zeeb wrote:

On Sat, 21 Sep 2013, Bryan Drewery wrote:


Unread portion of the kernel message buffer:
panic: Lock lle not exclusively locked @
/usr/src/sys/kern/kern_rwlock.c:140

cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe118aeef820
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0
vpanic() at vpanic+0x126/frame 0xfe118aeef910
panic() at panic+0x43/frame 0xfe118aeef970
__rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980
_callout_stop_safe() at _callout_stop_safe+0x54/frame
0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame
0xfe118aeefa30 softclock_call_cc() at
softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at
softclock+0x47/frame 0xfe118aeefb30
intr_event_execute_handlers() at
intr_event_execute_handlers+0x93/frame 0xfe118aeefb70
ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0
fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0
--- trap 0, rip = 0, rsp = 0xfe118aeefcb0, rbp = 0 ---


+1 from me;  I  guess introduced somwhere between 255569 and 255758,
as these are my edges of kernel.old and kernel.


r255726 was stable for me. r255759 is not.

r255755 converted ipfilter to callout, but I am unsure if that is the
problem.


r255729 is also stable for me - I'm with r255729 again, since r255757
crashed.

Let me know if this fixes the problem for you:
http://people.freebsd.org/~davide/review/lc_calloutfix.diff

Thanks,


Worked for me so far. I generally couldn't stay up more than 30 minutes
before the patch and now my uptime is 90 minutes. Thanks!
___
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: Panic on head (r255759) [_callout_stop_safe()- panic: Lock lle not exclusively locked @ /usr/src/sys/kern/kern_rwlock.c:140]

[Adam McDougall]

On 09/21/13 12:34, Davide Italiano wrote:

On Sat, Sep 21, 2013 at 9:31 AM, Bryan Drewery bdrew...@freebsd.org wrote:

On 9/21/2013 11:18 AM, Adam McDougall wrote:

On 09/21/13 09:41, Davide Italiano wrote:

On Sat, Sep 21, 2013 at 2:51 PM, O. Hartmann
ohart...@zedat.fu-berlin.de wrote:

On Sat, 21 Sep 2013 07:08:25 -0500
Bryan Drewery bdrew...@freebsd.org wrote:


On 9/21/2013 7:06 AM, Bjoern A. Zeeb wrote:

On Sat, 21 Sep 2013, Bryan Drewery wrote:


Unread portion of the kernel message buffer:
panic: Lock lle not exclusively locked @
/usr/src/sys/kern/kern_rwlock.c:140

cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe118aeef820
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe118aeef8d0
vpanic() at vpanic+0x126/frame 0xfe118aeef910
panic() at panic+0x43/frame 0xfe118aeef970
__rw_assert() at __rw_assert+0xa3/frame 0xfe118aeef980
_callout_stop_safe() at _callout_stop_safe+0x54/frame
0xfe118aeef9f0 arptimer() at arptimer+0x14e/frame
0xfe118aeefa30 softclock_call_cc() at
softclock_call_cc+0x188/frame 0xfe118aeefb10 softclock() at
softclock+0x47/frame 0xfe118aeefb30
intr_event_execute_handlers() at
intr_event_execute_handlers+0x93/frame 0xfe118aeefb70
ithread_loop() at ithread_loop+0xa6/frame 0xfe118aeefbb0
fork_exit() at fork_exit+0x84/frame 0xfe118aeefbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe118aeefbf0
--- trap 0, rip = 0, rsp = 0xfe118aeefcb0, rbp = 0 ---

+1 from me;  I  guess introduced somwhere between 255569 and 255758,
as these are my edges of kernel.old and kernel.


r255726 was stable for me. r255759 is not.

r255755 converted ipfilter to callout, but I am unsure if that is the
problem.


r255729 is also stable for me - I'm with r255729 again, since r255757
crashed.

Let me know if this fixes the problem for you:
http://people.freebsd.org/~davide/review/lc_calloutfix.diff

Thanks,


Worked for me so far. I generally couldn't stay up more than 30 minutes
before the patch and now my uptime is 90 minutes. Thanks!

Same here.


--
Regards,
Bryan Drewery


I would wait another couple of hours before the commit, but still I'm
confident this fixed the problem.


 7:05PM  up  8:18, 1 user, load averages: 0.08, 0.18, 0.21

___
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: Kernel panic on FreeBSD 10.0-CURRENT amd64

[Adam Kirchhoff]

On Tue, Mar 5, 2013 at 9:04 PM, Ryan Stone ryst...@gmail.com wrote:

 On Tue, Mar 5, 2013 at 8:03 PM, Adam Kirchhoff adam.k.kirchh...@gmail.com
  wrote:

 I have recently installed 9.1 and attempted to upgrade to 10.0-CURRENT
 yesterday (largely in an effort to test the new radeon DRM code).
 Unfortunately, upon rebooting, I am left at kernel debugger prompt:

 cd0 at ata0 bus 0 scbus0 target 1 lun 0
 cd0: TSSTcorp CD-ROM  TS-H192C DE00 Removable CD-ROM SCSI-0 device
 cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
 cd0: Attempt to query device size failed: NOT READY, Medium not
 present - tray closed
 panic: g_read_data(): invalid length 0
 cpuid = 0
 KDB: enter: panic
 [ thread pid 13 tid 100014 ]
 Stopped at  kdb_enter+0x3e: movq$0,kdb_why
 db bt
 Tracing pid 13 tid 100014 td 0xfe0002957490
 kdb_enter() at kdb_enter+0x3e/frame 0xff800026a960
 vpanic() at vpanic+0x147/frame 0xff800026a9a0
 kassert_panic() at kassert_panic+0x136/frame 0xff800026aa10
 g_read_data() at g_read_data+0x45/frame 0xff800026aa50
 g_label_ntfs_taste() at g_label_ntfs_taste+0xde/frame 0xff800026aa90
 g_label_taste() at g_label_taste+0x37b/frame 0xff800026ab60
 g_new_provider_event() at g_new_provider_event+0xda/frame
 0xff800026ab80
 g_run_events() at g_run_events+0x167/frame 0xff800026abb0
 fork_exit() at fork_exit+0x84/frame 0xff800026abf0
 fork_trampoline() at fork_trampoline+0xe/frame 0xff800026abf0
 --- trap 0, rip = 0, rsp = 0xff800026acb0, rbp = 0 ---

 I'm no expert, but it appears to be  related to the NTFS partition I
 have on a separate hard drive.

 Any ideas what the problem might be or how to debug this further?

 Adam
 ___
 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
 


 This sounds like something that was just fixed today.  Do you have r247837?

 http://svnweb.freebsd.org/changeset/base/247837



No, I did not.  I do now, and my computer is booting up.  Thanks.

Adam
___
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

Kernel panic on FreeBSD 10.0-CURRENT amd64

[Adam Kirchhoff]

I have recently installed 9.1 and attempted to upgrade to 10.0-CURRENT
yesterday (largely in an effort to test the new radeon DRM code).
Unfortunately, upon rebooting, I am left at kernel debugger prompt:

cd0 at ata0 bus 0 scbus0 target 1 lun 0
cd0: TSSTcorp CD-ROM  TS-H192C DE00 Removable CD-ROM SCSI-0 device
cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not
present - tray closed
panic: g_read_data(): invalid length 0
cpuid = 0
KDB: enter: panic
[ thread pid 13 tid 100014 ]
Stopped at  kdb_enter+0x3e: movq$0,kdb_why
db bt
Tracing pid 13 tid 100014 td 0xfe0002957490
kdb_enter() at kdb_enter+0x3e/frame 0xff800026a960
vpanic() at vpanic+0x147/frame 0xff800026a9a0
kassert_panic() at kassert_panic+0x136/frame 0xff800026aa10
g_read_data() at g_read_data+0x45/frame 0xff800026aa50
g_label_ntfs_taste() at g_label_ntfs_taste+0xde/frame 0xff800026aa90
g_label_taste() at g_label_taste+0x37b/frame 0xff800026ab60
g_new_provider_event() at g_new_provider_event+0xda/frame 0xff800026ab80
g_run_events() at g_run_events+0x167/frame 0xff800026abb0
fork_exit() at fork_exit+0x84/frame 0xff800026abf0
fork_trampoline() at fork_trampoline+0xe/frame 0xff800026abf0
--- trap 0, rip = 0, rsp = 0xff800026acb0, rbp = 0 ---

I'm no expert, but it appears to be  related to the NTFS partition I
have on a separate hard drive.

Any ideas what the problem might be or how to debug this further?

Adam
___
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: kmem_map auto-sizing and size dependencies

[Adam McDougall]

On 1/22/2013 6:22 PM, Artem Belevich wrote:

On Mon, Jan 21, 2013 at 1:06 PM, Pawel Jakub Dawidek p...@freebsd.org wrote:

On Fri, Jan 18, 2013 at 08:26:04AM -0800, m...@freebsd.org wrote:

  Should it be set to a larger initial value based on min(physical,KVM) space
  available?

It needs to be smaller than the physical space, [...]

Or larger, as the address space can get fragmented and you might not be
able to allocate memory even if you have physical pages available.

+1 for relaxing upper limit.

I routinely patch all my systems that use ZFS to allow kmem_map size
to be larger than physical memory. Otherwise on a system where most of
RAM goes towards ZFS ARC I used to eventually run into dreaded
kmem_map too small panic.

--Artem
___

Ever since related code has been patched to properly permit kmem=2x physmem
out of the box, I've been using that guideline for my systems and
I've not had an out of kmem panic in years.  I've previously ran into weird
temporary deadlocks with strong IO if I set the kmem too high, as if the ARC
caused something important to be overwritten; that is just my theory.  I 
agree

with the fragmentation principle here.  YMMV regarding the kmem size.
___
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: 9.1-RC3 LiveCD missing features

[Adam Vande More]

On Fri, Dec 7, 2012 at 5:05 PM, Tomek CEDRO tomek.ce...@gmail.com wrote:

 As I get ffs_valloc kernel panic on my / I want to check for badblocks but
 cannot do that from the system itself so I need another FreeBSD instance to
 run badblocks on unmounted /. There are no badblocks on LiveCD and I cannot
 simply download it with pkg_add -r. Installing another system just to test
 existing one seems silly. It would be nice to finally have swiss army knife
 on generic LiveCD FreeBSD install, not using linux windows hirens etc :-)

 I have just started dd if=root of=root from LiveCD, Ill let you know if
 that worked :-)


You probalby want a filesystem tool but it's impossible to tell since you
didn't include all the relevant info.  Try fsck.

If you did want a badblocks tool from the base system, /sbin/recoverdisk
is the best.  dd is fine, but not as through as it.

-- 
Adam Vande More
___
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: after upgrade, can't restart apache via cron

[Adam Vande More]

On Thu, Nov 22, 2012 at 9:17 PM, Michael W. Lucas mwlu...@michaelwlucas.com
 wrote:



 FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD
 10.0-CURRENT #15: Thu Nov  8 14:02:45 EST 2012
 mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC
  amd64

 I can manually restart apache22 with the following /etc/rc.conf entries:

 apache22_enable=YES
 apache22_fib=0

 I have a cron entry that restarts apache regularly, to compensate for
 some mysql daftness.

 13  *  * * * /usr/local/etc/rc.d/apache22 restart

 When this job runs, I get the following email:

 Performing sanity check on apache22 configuration:
 Syntax OK
 Stopping apache22.
 Waiting for PIDS: 59501.
 Performing sanity check on apache22 configuration:
 Syntax OK
 Starting apache22.
 eval: setfib: not found
 /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22

 If I run /usr/local/etc/rc.d/apache22 restart from the command line, I
 can restart httpd without trouble.

 Any thoughts?


I would guess you need /usr/sbin/ in cron's path.

-- 
Adam Vande More
___
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: after upgrade, can't restart apache via cron

[Adam McDougall]

On 11/22/2012 10:17 PM, Michael W. Lucas wrote:


FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT 
#15: Thu Nov  8 14:02:45 EST 2012 
mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC  amd64

I can manually restart apache22 with the following /etc/rc.conf entries:

apache22_enable=YES
apache22_fib=0

I have a cron entry that restarts apache regularly, to compensate for
some mysql daftness.

13  *  * * * /usr/local/etc/rc.d/apache22 restart

When this job runs, I get the following email:

Performing sanity check on apache22 configuration:
Syntax OK
Stopping apache22.
Waiting for PIDS: 59501.
Performing sanity check on apache22 configuration:
Syntax OK
Starting apache22.
eval: setfib: not found
/usr/local/etc/rc.d/apache22: WARNING: failed to start apache22

If I run /usr/local/etc/rc.d/apache22 restart from the command line, I
can restart httpd without trouble.

Any thoughts?

==ml


Make sure the path to setfib is in PATH in the crontab?

PATH=/blah/blah/blah:/usr/sbin
* *   *   *   *   blah

___
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: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf)

[Adam Vande More]

On Tue, Nov 20, 2012 at 12:22 PM, Chuck Burns brea...@gmail.com wrote:

 The ones who want the old pf can maintain it.. those who want the new one,
 can maintain *it*.


This is beach front property on Fantasy Island.  There isn't even enough
manpower to sufficiently support one currently.

-- 
Adam Vande More
___
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: Buying recommendation for silent router/fileserver

[Adam McDougall]

I did not, but I put it on my list to try to accomplish.

On 10/11/12 13:41, Adrian Chadd wrote:

Did you ever file a PR for the slow SATA behaviour?



Adrian


On 11 October 2012 09:52, Adam McDougall mcdou...@egr.msu.edu wrote:

On 10/11/12 12:05, Gary Palmer wrote:


On Thu, Oct 11, 2012 at 04:54:53PM +0200, Ulrich Sp??rlein wrote:


Hey guys,

I need to replace an aging Pentium IV system that has been serving as my
router, access point, file- and mediaserver for quite some time now. The
replacement should have:

- amd64 CPU (for ZFS, obviously)
- 2x GigE (igress, egress interfaces)
- some form of wlan interface (I currently use an Atheros based PCI card)
- eSATA for attaching a backup disk where I stream ZFS snapshots to
- serial port is always nice, for when I mess up an upgrade
- fan-less if possible

So far, this here seems to fit the bill perfectly
http://www.fit-pc.com/web/fit-pc/intensepc/
but pricing seems to defy any reality.

It does not state directly which chipsets are used for Wifi and
Ethernet, the block diagram claims Ethernet chips to be Intel 82579 and
RTL8111D, but I don't trust that fully.

For Wifi I can always fall back to sticking in a supported USB stick,
although that's kinda hacky.

So how well is networking going to be supported by FreeBSD? Should I
just bite the bullet and find out?



I'd recommend the Soekris net6501, but it's even more expensive than the
intensepc (I suspect due to low hardware volumes but thats just a guess)

http://soekris.com/products/net6501.html

You also don't specify what kind of storage you need, which is obviously
an important factor for a file/media server.

Gary
___
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



Be wary of the Soekris net6501, I bought three of the 1.6Ghz net6501-70
model which has an Atom E-680 cpu (E series) and it compiles more than twice
as slow as a 1.6Ghz Atom N270 in an older netbook.  Someone else running
Linux reported similar CPU slowness.  As far as practical network
throughput, I could only get 100Mbit/sec with a simple HTTP download of a
file full of zeros, and OpenVPN could only push about 25Mbit/sec.  As a
practical example of the CPU slowness, it takes about 1.5 minutes to compile
pkg on the N270 netbook and 5 minutes on the 6501 (around 4.5 if I use -j2).
A kernel compile took an hour. Unfortunately I had no idea this CPU
(possibly implementation?) was so slow before I purchased it, and I could
scarcely find evidence of it on google after hours of searching when I had
already discovered the issue.  I was hoping to find some comparative
benchmarks between various Atom series but manufacturers generally don't do
that.

Additionally, the total AHCI SATA write speed on the net6501 (in BSD only?)
has a strange 20MB/sec limitation but reads can go over 100MB/sec.  If I
write to one disk I get 20MB/sec, if I write to both SATA disks I get
10MB/sec each.  Write is equally slow on a SSD.  Both someone running
OpenBSD and I running FreeBSD reported the same symptoms to the soekris-tech
mailing list and received no useful replies towards getting that problem
solved.  I tested the write speed briefly with Linux and it did not appear
to have the 20MB/sec limitation.  I did confirm it was using MSI(-X?) with
boot -v.  I think this hardware would need to fall into Alexander Motin's
hands to get anywhere with debugging the SATA speed issue.  Since it seems
fine in Linux, maybe some day it can be fixed in BSD but I have no clue how
that limitation could happen.  The disks I tested with are fine in normal
computers.

___
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


___
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: Buying recommendation for silent router/fileserver

[Adam McDougall]

On 10/11/12 12:05, Gary Palmer wrote:

On Thu, Oct 11, 2012 at 04:54:53PM +0200, Ulrich Sp??rlein wrote:

Hey guys,

I need to replace an aging Pentium IV system that has been serving as my
router, access point, file- and mediaserver for quite some time now. The
replacement should have:

- amd64 CPU (for ZFS, obviously)
- 2x GigE (igress, egress interfaces)
- some form of wlan interface (I currently use an Atheros based PCI card)
- eSATA for attaching a backup disk where I stream ZFS snapshots to
- serial port is always nice, for when I mess up an upgrade
- fan-less if possible

So far, this here seems to fit the bill perfectly
http://www.fit-pc.com/web/fit-pc/intensepc/
but pricing seems to defy any reality.

It does not state directly which chipsets are used for Wifi and
Ethernet, the block diagram claims Ethernet chips to be Intel 82579 and
RTL8111D, but I don't trust that fully.

For Wifi I can always fall back to sticking in a supported USB stick,
although that's kinda hacky.

So how well is networking going to be supported by FreeBSD? Should I
just bite the bullet and find out?


I'd recommend the Soekris net6501, but it's even more expensive than the
intensepc (I suspect due to low hardware volumes but thats just a guess)

http://soekris.com/products/net6501.html

You also don't specify what kind of storage you need, which is obviously
an important factor for a file/media server.

Gary
___
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



Be wary of the Soekris net6501, I bought three of the 1.6Ghz net6501-70 
model which has an Atom E-680 cpu (E series) and it compiles more than 
twice as slow as a 1.6Ghz Atom N270 in an older netbook.  Someone else 
running Linux reported similar CPU slowness.  As far as practical 
network throughput, I could only get 100Mbit/sec with a simple HTTP 
download of a file full of zeros, and OpenVPN could only push about 
25Mbit/sec.  As a practical example of the CPU slowness, it takes about 
1.5 minutes to compile pkg on the N270 netbook and 5 minutes on the 6501 
(around 4.5 if I use -j2).  A kernel compile took an hour. 
Unfortunately I had no idea this CPU (possibly implementation?) was so 
slow before I purchased it, and I could scarcely find evidence of it on 
google after hours of searching when I had already discovered the issue. 
 I was hoping to find some comparative benchmarks between various Atom 
series but manufacturers generally don't do that.


Additionally, the total AHCI SATA write speed on the net6501 (in BSD 
only?) has a strange 20MB/sec limitation but reads can go over 
100MB/sec.  If I write to one disk I get 20MB/sec, if I write to both 
SATA disks I get 10MB/sec each.  Write is equally slow on a SSD.  Both 
someone running OpenBSD and I running FreeBSD reported the same symptoms 
to the soekris-tech mailing list and received no useful replies towards 
getting that problem solved.  I tested the write speed briefly with 
Linux and it did not appear to have the 20MB/sec limitation.  I did 
confirm it was using MSI(-X?) with boot -v.  I think this hardware would 
need to fall into Alexander Motin's hands to get anywhere with debugging 
the SATA speed issue.  Since it seems fine in Linux, maybe some day it 
can be fixed in BSD but I have no clue how that limitation could happen. 
 The disks I tested with are fine in normal computers.

___
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: Clang as default compiler November 4th

[Adam Vande More]

On Tue, Sep 11, 2012 at 12:19 PM, Roman Divacky rdiva...@freebsd.orgwrote:

 Can you please provide a small self contained test case that shows
 that clang is doing worse on accuracy than gcc?

 So that we can analyze it and decide if it's a bug in the code or
 in the compiler. So far we know absolutely nothing.


Not to speak for Steve, but he provided this information in another thread:

http://lists.freebsd.org/pipermail/freebsd-current/2012-September/036410.html


-- 
Adam Vande More
___
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: OpenLDAP/SASL2 problem in FreeBSD 10.0-CURRENT WAS: Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2

[Adam McDougall]

On 8/18/2012 4:07 AM, O. Hartmann wrote:

My setups on all boxes using OpenLDAP, the port
net/opendldap24-client/server has security/cyrus-sasl2 enabled.
I use nsswitch and nascd.

The problem:
I can not anymore install or reinstall (using portmaster, patched for
pkgng) the ports

security/cyrus-sasl2
net/openldap24-client

When performing an update (no matter which one), The installation
process dies when installing the packages (see error for openldap-cleint
below, it is proxy for cyrus-sasl2 also).

After a failed installation, close to all binaries I touch start to
coredump in a mustang way. ls(1) works, but ls -la dumps core (resolving
the ownership-issue?).

The only way to save the box is to copy missing libldap_r-2.4.so.8 or
libsasl2.so.2 to /usr/local/lib/ from another, compatible box or from a
backup.

It is impossible to me to update/reinstall either net/openldap24-client
or security/cyrus-sasl2.

===  Installing for openldap-sasl-client-2.4.32_1
===   Generating temporary packing list
Segmentation fault (core dumped)
*** [install-mtree] Error code 139


What happens if you disable both LDAP and cache support from NSS before
upgrading either of those two packages?  Installing files certainly must
invoke functions that need to translate owners/groups to uid/gid so perhaps
something related to that suddenly fails during an attempt to replace
the library.  It sounds like if your LDAP support becomes corrupt, then
it leaves a gaping hole in the NSS critical path that many parts of the
system must be using.  When you run into this situation and can resolve
it easily by replacing the old ldap library, is the old one corrupt?
Missing?  Can you save a copy for evaluation?  Does your system break in
a similar manner simply by renaming the LDAP library, or does it behave
worse only if there is a faulty LDAP library being used by nss_ldap?

___
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: sysctl filesystem ?

[Adam Vande More]

On Mon, Jun 25, 2012 at 7:03 PM, Arnaud Lacombe lacom...@gmail.com wrote:

 Hi folks,

 I find myself in a situation where I need to directly explore the
 sysctl(8) tree from my program. The tricky part is this:


There is this:

http://svnweb.freebsd.org/base/releng/4.7/sys/miscfs/kernfs/

-- 
Adam Vande More
___
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: Why Are You NOT Using FreeBSD ?

[Adam Strohl]

On 6/9/2012 14:50, O. Hartmann wrote:

Lucky man! We are off from some desktop services (like LibreOffice and
Firefox) for more than a week now!


Why did you update to begin with?  Bug/security fix?

--
Adam Strohl
http://www.ateamsystems.com/
___
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: [CFT] Xorg Upgrade 7.5.2

[Adam K Kirchhoff]

On Mon, 13 Feb 2012 15:39:21 +0200
Volodymyr Kostyrko c.kw...@gmail.com wrote:

 Adam K Kirchhoff wrote:
 
  I've run it for a while now and am actually having a pretty serious
  issue:
 
  http://thorn.visualtech.com/screenshot.jpg
 
  As you can see, that big window on the right monitor (though
  certainly doesn't limit itself to just that screen) is almost
  entirely corrupt. It's an xfce4 Terminal, though this can happen
  with nearly any window, and happens both with compositing enabled
  or disabled.  Getting the window to redraw somehow (either by
  highlighting all the text or resizing it) will fix tha areas that
  are redrawn.
 
  The problem is most often triggered by moving the window around, or
  moving other windows around on top of it.  Unfortunately, it makes X
  barely usable.
 
 I'm not involved with testing new version but I can second this issue 
 with current version in ports. When I managed to add my TV as a
 second screen XFCE draws garbage instead of desktop on the second
 screen. E17 however worked like a charm. I mean... you sure this is
 not an XFCE issue?

Yes, I'm quite sure. This happens with xfce4, kde4 and just plain
openbox. 

I've seen similar distortion (though not quite the same as what's in my
screenshot) from the radeon driver even before testing this new
version.  I will, however, confirm these various corruptions with the
radeon driver happen less with E17.  

I've also seen the same thing on OpenBSD.  The distortion I've seen
with the driver/Xorg from ports I've also seen on Slackware when
disabling KMS, so I'm quite convinced this is a UMS-specific bug.

Adam
___
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: [CFT] Xorg Upgrade 7.5.2

[Adam K Kirchhoff]

I've run it for a while now and am actually having a pretty serious
issue:

http://thorn.visualtech.com/screenshot.jpg

As you can see, that big window on the right monitor (though certainly
doesn't limit itself to just that screen) is almost entirely corrupt.
It's an xfce4 Terminal, though this can happen with nearly any window,
and happens both with compositing enabled or disabled.  Getting the
window to redraw somehow (either by highlighting all the text or
resizing it) will fix tha areas that are redrawn.

The problem is most often triggered by moving the window around, or
moving other windows around on top of it.  Unfortunately, it makes X
barely usable.

Adam

On Mon, 06 Feb 2012 10:35:50 -0500
Adam K Kirchhoff akirchhoff135...@comcast.net wrote:

 
 A big thanks to all.
 
 [adamk@memory ~]$ cat /var/log/Xorg.0.log | head -n 10
 [46.127]
 X.Org X Server 1.10.4
 Release Date: 2011-08-19
 [46.128] X Protocol Version 11, Revision 0
 [46.128] Build Operating System: FreeBSD 9.0-STABLE amd64
 [46.128] Current Operating System: FreeBSD memory.visualtech.com 
 9.0-STABLE FreeBSD 9.0-STABLE #5: Thu Jan 26 22:09:39 EST 2012 
 r...@memory.visualtech.com:/usr/obj/usr/src/sys/MEMORY amd64
 [46.128] Build Date: 06 February 2012  09:37:45AM
 [46.128]
 [46.128] Current version of pixman: 0.24.0
 [46.128]Before reporting problems, check http://wiki.x.org
 
 [adamk@memory ~]$ glxinfo | grep -i OpenGL
 IRQ's not enabled, falling back to busy waits: 2 0
 OpenGL vendor string: Advanced Micro Devices, Inc.
 OpenGL renderer string: Mesa DRI R600 (RV710 954F)  TCL
 OpenGL version string: 2.1 Mesa 7.11.2
 OpenGL shading language version string: 1.20
 OpenGL extensions:
 
 3D compositing works with KDE's desktop effects.  compiz works as
 well (though enabling the magnifier plugin crashes X).  xmoto,
 foobillard, neverball and openarena are all (to varying degrees)
 playable.
 
 Adam
 
 
 
 ___
 freebsd-...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-x11
 To unsubscribe, send any mail to freebsd-x11-unsubscr...@freebsd.org
___
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: Enhancing the user experience with tcsh

[Adam Vande More]

On Thu, Feb 9, 2012 at 6:52 PM, Eitan Adler li...@eitanadler.com wrote:

 In conf/160689 (http://www.freebsd.org/cgi/query-pr.cgi?pr=160689)
 there has been some discussion about changing the default cshrc file.

 I'd like to commit something like the following based on Chris's patch
 at the end of the thread. This post is an attempt to open the change
 to wider discussion.

 commit dbe6cb730686dd53af7d06cc9b69b60e6e55549c
 diff --git a/etc/root/dot.cshrc b/etc/root/dot.cshrc
 --- a/etc/root/dot.cshrc
 +++ b/etc/root/dot.cshrc
 @@ -7,9 +7,10 @@

  alias hhistory 25
  alias jjobs -l
 -alias la   ls -a
 +alias la   ls -aF
  alias lf   ls -FA
 -alias ll   ls -lA
 +alias ll   ls -lAF


I don't like the change to alias ll.  I use it frequently and the proposed
change makes it less readable.  Otherwise, these mostly seem overdue.

-- 
Adam Vande More
___
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: [CFT] Xorg Upgrade 7.5.2

[Adam K Kirchhoff]

A big thanks to all.

[adamk@memory ~]$ cat /var/log/Xorg.0.log | head -n 10
[46.127]
X.Org X Server 1.10.4
Release Date: 2011-08-19
[46.128] X Protocol Version 11, Revision 0
[46.128] Build Operating System: FreeBSD 9.0-STABLE amd64
[46.128] Current Operating System: FreeBSD memory.visualtech.com 
9.0-STABLE FreeBSD 9.0-STABLE #5: Thu Jan 26 22:09:39 EST 2012 
r...@memory.visualtech.com:/usr/obj/usr/src/sys/MEMORY amd64

[46.128] Build Date: 06 February 2012  09:37:45AM
[46.128]
[46.128] Current version of pixman: 0.24.0
[46.128]Before reporting problems, check http://wiki.x.org

[adamk@memory ~]$ glxinfo | grep -i OpenGL
IRQ's not enabled, falling back to busy waits: 2 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV710 954F)  TCL
OpenGL version string: 2.1 Mesa 7.11.2
OpenGL shading language version string: 1.20
OpenGL extensions:

3D compositing works with KDE's desktop effects.  compiz works as well 
(though enabling the magnifier plugin crashes X).  xmoto, foobillard, 
neverball and openarena are all (to varying degrees) playable.


Adam



___
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: Trouble getting serial support for Live CD in 9 installer

[Adam McDougall]

On 11/23/11 15:03, Garrett Cooper wrote:

On Wed, Nov 23, 2011 at 11:12 AM, Adam McDougallmcdou...@egr.msu.edu  wrote:

I often use the serial console on my servers through ILOM remote console
access to install FreeBSD because it lets me cut and paste commands into a
live shell from install media.  Back with FreeBSD 8.x and previous, the
console worked as a dual console between the redirected VGA/keyboard console
and serial, all I had to do was drop to the loader prompt at the boot loader
menu to enter:

set console=comconsole
set boot_serial=yes
boot

 From then on, the VGA console was ignored until I rebooted.  But in 9.x
(currently trying 9.0-RC2 from the usb image), I have to interrupt an
earlier loader to use -h or -D to enable serial(dual) console support at
all.  I then enter the two variables above as I usually do, then specify my
terminal type (xterm), then choose Live CD which prints:
Updating motd: /etc/motd is not writable, update failed.
Configuring syscons: blanktime.
Starting cron.
Starting background file system checks in 60 seconds.

Wed Nov 23 19:03:02 UTC 2011

but then it prints the FreeBSD banner and spawns the login: prompt on the
VGA console instead.

Is there something else I can set during the boot process to make this work?
  I could try modifying the configuration on the usb image to suit my site
but this is more modification than I required in the past and surprisingly
different.  Please let me know if I can provide more information or help in
some way.  Thanks.

If I don't hear back in a few days or so, I'll make a PR.


You'll need to change your device.hints and /etc/ttys.
-Garrett
___
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


Thanks.  This lead me to an even easier solution with no editing that 
should work with booting from CD and with previous versions:


1. Boot completely normally
2. Use the installer to drop to Live CD shell
3. execute: /usr/libexec/getty std.9600 ttyu0

This spawns a login prompt on the serial port ttyu0 which is essentially 
all I need.  I didn't seem to need to alter the device hints at all for 
my situation, and on a USB key I can mount -u -o rw / to edit one or 
more of /etc/ttys, /boot/loader.conf, /boot.config if I want to make it 
permanent for next time.

___
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

Trouble getting serial support for Live CD in 9 installer

[Adam McDougall]

I often use the serial console on my servers through ILOM remote console 
access to install FreeBSD because it lets me cut and paste commands into 
a live shell from install media.  Back with FreeBSD 8.x and previous, 
the console worked as a dual console between the redirected VGA/keyboard 
console and serial, all I had to do was drop to the loader prompt at the 
boot loader menu to enter:


set console=comconsole
set boot_serial=yes
boot

From then on, the VGA console was ignored until I rebooted.  But in 9.x 
(currently trying 9.0-RC2 from the usb image), I have to interrupt an 
earlier loader to use -h or -D to enable serial(dual) console support at 
all.  I then enter the two variables above as I usually do, then specify 
my terminal type (xterm), then choose Live CD which prints:

Updating motd: /etc/motd is not writable, update failed.
Configuring syscons: blanktime.
Starting cron.
Starting background file system checks in 60 seconds.

Wed Nov 23 19:03:02 UTC 2011

but then it prints the FreeBSD banner and spawns the login: prompt on 
the VGA console instead.


Is there something else I can set during the boot process to make this 
work?  I could try modifying the configuration on the usb image to suit 
my site but this is more modification than I required in the past and 
surprisingly different.  Please let me know if I can provide more 
information or help in some way.  Thanks.


If I don't hear back in a few days or so, I'll make a PR.
___
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: Need a README to explain items in download directory

[Adam Vande More]

On Sat, Sep 3, 2011 at 6:00 PM, Craig Rodrigues rodr...@crodrigues.orgwrote:

 For this line:

 (1)  FreeBSD-8.2-RELEASE-i386-bootonly.iso - Requires an Internet
 Connection

 Does this mean that this ISO has the minimal stuff to boot, and
 then do an install by downloading packages over the Internet?  I really
 don't
 know, that's why I'm asking. :)


While such wording may be helpful to a new user over completely absent
directions, it's technically flawed.  You don't need an internet connection,
but rather a network connection or some other form of installation media.

/nitpick

-- 
Adam Vande More
___
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: Trying to install current from a memory stick and then a DVD and got a new and strange installer.

[Adam Vande More]

On Mon, Jul 25, 2011 at 11:46 AM, eculp ec...@encontacto.net wrote:

 That makes two of us right now.  I gave up, accepted the automatic
 partition and everything else went as expected, I suppose.  The disk results
 are:

 # df
 Filesystem  1K-blocksUsed Avail Capacity  Mounted on
 /dev/ada0p2 941441086 2150880 863974920 0%/
 devfs   1   1 0   100%/dev

 In my world from the beginning of commercial unix, I have never had a one
 partition disk.  I'm not sure if it is that bad with today's, controllers,
 drives, drivers, etc.  I hope someone chimes in with a I see no major
 problems with gpt.

 My major problem was editing the automatic swap that was set at 4G and the
 menu would not let me change the 4G.  The experienced option would not
 accept a blank value as swap even though there was message that said it
 would.

 I feel like a real idiot and am beginning to believe that it might be true.
 The rest of the install was brain dead.  It was possibly a bit simpler than
 the previous.  Less decisions ;)

 I had the idea the following were available in the new installer.
  1.  Raid configuration
  2.  ZFS
  3.  Regular everyday simple disk partitioning as before.

 I wasn't able to find any functional option except the one mentioned above.

 Now, I have to accept this single partition or upgrade sources to date,
 build a release and reinstall but I don't know if the problem has been
 fixed.  I'll probably give it a try.  It isn't that much of a deal.


Hopefully I add something of value to this thread, but as a workaround you
can use a PCBSD image and installer to install/partion plain vanilla FreeBSD
with the options you mentioned earlier in a graphical enviroment.



-- 
Adam Vande More
___
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: Switch from legacy ata(4) to CAM-based ATA

[Adam Vande More]

On Sun, Apr 24, 2011 at 1:54 PM, Scott Long sco...@samsco.org wrote:

 Indeed, there's nothing wrong with preserving access to the system details
 for the use of administration, troubleshooting, and even mere geeky
 knowledge.  This isn't about taking power away from the superusers, it's
 about making the system smart enough to handle common situations reliably.
 I'm sure that there some among us who pine for the good old days of manually
 configuring and linking a kernel, but it's hard to argue that an
 auto-configured kernel isn't pretty darn convenient most of the time.  What
 I'm proposing is just the next step in that process.


For me, your proposal would make life more difficult as it is on Linux.
I've had to do more deployment/autoconfig setups recently and FreeBSD's
method of device naming makes it much easier for me to deal with.  I like
the fact I easily know what disk is attached to what controller and what NIC
driver is in use.  The NIC specific naming is more useful than disk
controller, but both have their places for me. It makes
tweaking/troubleshooting quicker in some situations.  In fact, I would like
even more of it it, eg /dev/usbda0.

What a disk is called is already different(for me) than what is in fstab
since some(maybe many?) people are already using some of the abstraction
methods currently available.  If a sys-admin makes an effort, a consistent
fstab is pretty easily achieved but it's better done by pre-deployment
planning rather than after.  If one of the new installer proposals handled
this automatically, even better.

My point is that device names are still an important hint to functionality
particularly for auto-deployment/configure settings where specific hardware
isn't always known ahead of time.

-- 
Adam Vande More
___
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: [Call for testers] FreeBSD VirtIO Network Driver

[Adam Vande More]

On Sun, Jan 2, 2011 at 5:02 PM, bv deboomer...@gmail.com wrote:

 Hi.

 I'd like to present the network VirtIO driver I've been working on for
 the last few months in my spare time. It is not based on the NetBSD code
 that is floating around. The attached patch should apply to both recent
 -current and -stable. Early development was done on VirtualBox,
 but most has been done on KVM/QEMU.
 snip
 I'm going to be away from my computer for the next couple of days,
 I'll get to any email after then.


Thanks for this work, I'm sure it will be quite useful.

I'm testing on a FreeBSD Virtualbox Host/Guest.  Guest is CURRENT
kern.osrevision:  199506 virtualbox-ose-3.2.10_2

My particular version of Virtualbox isn't optimized yet for virtio I
believe, but I did see about 1/3 higher peak bandwidth and a definite
reduction in CPU usage.

-- 
Adam Vande More
___
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: Should green_saver.ko shut off a laptop's backlight?

[Adam Vande More]

On Sat, Nov 27, 2010 at 6:39 PM, Doug Barton do...@freebsd.org wrote:

 My recollection is that green_saver should turn off an LCD backlight, but I
 just loaded it up on my laptop and it's not doing so. It does remove the
 text from the screen, but the backlight is still on (i.e., it is doing
 exactly what blank_saver does).

 When running X DPMS works on that same laptop, so I know the hardware is
 capable. This is 9-current amd64 at r214025. Any suggestions are welcome.


It's never worked for me either and this has been around awhile.

http://www.freebsd.org/cgi/query-pr.cgi?pr=114928cat=

-- 
Adam Vande More
___
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: Call for Documentation Contributors

[Adam Vande More]

On Thu, Sep 2, 2010 at 5:54 PM, Daniel Gerzo dan...@rulez.sk wrote:

 I actually think there is some point in this idea. The problem is that many
 times we just leave notes or warnings specific for given releases, which can
 many times lead to confusion (or people just don't notice) and as time goes
 and we cut the support for given releases they get stale (e.g. We had many
 of those for 5.x).

 We could just maintain the handbook in separate branches like we do with
 src, keeping them all built online, and merge relevant things where
 appropriate. This will, however, add quite a lot (for my taste) of
 additional work for us.


Wouldn't it be a lot easier to have a nice article on installing
/usr/ports/misc/freebsd-doc-* from the date of the release of the installed
system?  Or maybe offer archive web access to a handbook snapshot from that
date(Django does something similar)?  Maintaining separate handbook branches
seems unrealistic if there aren't enough doc contributors to maintain one to
expectations, and IME discrepancies aren't very frequent.


-- 
Adam Vande More
___
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: Call for Documentation Contributors

[Adam Vande More]

On Thu, Sep 2, 2010 at 11:10 PM, Adam Vande More amvandem...@gmail.comwrote:

 Wouldn't it be a lot easier to have a nice article on installing
 /usr/ports/misc/freebsd-doc-* from the date of the release of the installed
 system?  Or maybe offer archive web access to a handbook snapshot from that
 date(Django does something similar)?  Maintaining separate handbook branches
 seems unrealistic if there aren't enough doc contributors to maintain one to
 expectations, and IME discrepancies aren't very frequent.


I need to add to that installing release specific handbook/documentation via
sysinstall is the Easy Button.

-- 
Adam Vande More
___
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: CD/DVD ejecting after sysinstall

[Adam Vande More]

On Sat, Aug 21, 2010 at 5:24 PM, Randi Harper sek...@gmail.com wrote:

 On Aug 20, 2010, at 14:21, Rui Paulo rpa...@freebsd.org wrote:
 
  You are correct. We should not be ejecting the CD without a prompt. If
 the commit is reverted, it should be explicitly noted in the code so that we
 don't do this mistake again.
 
  Regards,
  --
  Rui Paulo
 
 

 That's a judgement call, not an absolute. I think what we are doing isn't a
 problem for 99.999% of use cases.


I think 99.999% is a bit high, as couple times during my FreeBSD usage this
would have been a problem for me although is not currently an issue.  I
don't really know what problem this solves as it is unnecessary in 100% of
use cases as far as I can tell.  It's not that I don't appreciate the
thought behind it, but this will be problem for others I imagine as well.
It's a VERY big inconvenience sometimes to visit a datacenter when you
thought you had a rock solid remote setup in place.

In defense of the current behavior, you can get basically the same behavior
by setting up a PXE boot system, but that is not always desirable or
convenient.  Also all KVM's don't give the option to remotely load ISO's.

-- 
Adam Vande More
___
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: Official request: Please make GNU grep the default

[Szilveszter Adam]

On Thu, Aug 19, 2010 at 09:42:01PM +, b. f. wrote:
 Gabor:
 
 One more thing to look into, in addition to the context problems,
 ndisgen breakage, and problems on certain file systems:
 
 At r211506, 'grep -wq' does not seem to work properly (in the very
 least, it is not the same as with GNU grep), and has broken the
 'check-categories' target (and hence builds) of all ports with 'lisp'
 in CATEGORIES.

Seconded. This also breaks the ports using bsd.apache.mk, and what's
worse, it does so silently. I have been bitten by this myself with
www/apache22, several core modules have not been built resulting in a
useless apache installation.

So, I believe there is more to do here than just performance
optimisation.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
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: k3b causing system freeze/panic

[Szilveszter Adam]

On Wed, Jul 28, 2010 at 01:42:30PM +0200, Dag-Erling Sm??rgrav wrote:
 Sorry, I misparsed ATA_CAM as ahci.  Why on earth would anyone want to
 use ATA_CAM these days?

Well, I am not sure if you really meant ATA_CAM and not ATAPICAM? But in
case you meant it, for people who do not use SATA-capable hardware,
ATA_CAM is useful. This laptop may be no longer be the most recent model
these days, but runs -CURRENT just fine most of the time. Also, if I
remember correctly, for people with a bit more recent controllers
ATA_CAM offers other advantages, but those do not affect me. So, for me
ATA_CAM is just a better version of the ata(4) driver...

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
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: Switchover to CAM ATA?

[Szilveszter Adam]

On Fri, Apr 23, 2010 at 09:40:59AM +0300, Andriy Gapon wrote:
 on 23/04/2010 07:48 Szilveszter Adam said the following:
  There is one interesting tidbit though: previously it used to be
  possible to run cdda2wav also as non-root, provided the user running it
  had read access to the /dev/cd0 device. This seems to no longer work.
 
 Probably you also need access to the corresponding passX device, which you can
 find from output of 'camcontrol devlist'.
 You didn't need that with *a*cd0.

That seems to be it, the perms on pass1 needed fixing. Thanks for the
tip! 

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
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: Switchover to CAM ATA?

[Adam Vande More]

On Thu, Apr 22, 2010 at 11:25 AM, Julian Elischer jul...@elischer.orgwrote:

 just one little fly in that ointment...  booting.

 You need to be able to act with the raid in the same way the bios does
 or you can't boot. I don't think geom would easlily do that but I could be
 wrong. Certainly if you treat teh ata raid as just a bunch of striped disks,
 then the bios will not be able to boot off it.

 of course don't take my word too seriosly asn I'm not running an ata raid
 system at the moment.


gmirror booting works great only thing to change is fstab to reflect block
dev changes, gstripe doesn't.  I honestly wasn't aware ataraid could boot a
striped volume, if so it does something geom can't.


-- 
Adam Vande More
___
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: Switchover to CAM ATA?

[Szilveszter Adam]

Dear Alexander, dear collegaues,

On Thu, Apr 22, 2010 at 06:31:37PM +0300, Alexander Motin wrote:
 Can we do switchover now, or some more reasons preventing this?

I have been using ATA_CAM with legacy support for ata(4) for some time,
and have found it to be stable and very useable. I have even removed
atapicam from the kernel, since it is no longer needed, I have the
/dev/cd0 device also without. So, in my opinion it is ready for
prime-time also on legacy hw.

There is one interesting tidbit though: previously it used to be
possible to run cdda2wav also as non-root, provided the user running it
had read access to the /dev/cd0 device. This seems to no longer work.

Has anybody else noticed this?

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
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: ports and PBIs

[Adam Vande More]

On Fri, Apr 9, 2010 at 8:31 PM, Julian Elischer jul...@elischer.org wrote:


 Alfred Perlstein , Matt at ix systems Kris (Mr PBI), some
 others and I, felt that these ideas seemed to make some sense
 and so I put them here for comment.


FWIW, when I see these discussions I'm always left wondering what's the bad
part?  I do think there are problems, but there doesn't seem to be a clear
defined set of what is wrong.   IMO, there should be a defined set of goals
to judge possible implementations against.

In manys ways, simply having a Lastest package archive for RELEASE that is
rebuilt say weekly which would resolve most of the problems I run into and
address some the non-power users desires as well.  Anyways, I'm sure this
will be an entertaining thread.

-- 
Adam Vande More
___
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: iwi problems on -CURRENT (Apr 4. 2010)

[Adam K Kirchhoff]

FYI, this happens with GENERIC, too.

Adam

On Sat, 3 Apr 2010 16:54:47 -0400
Adam K Kirchhoff akirchhoff135...@comcast.net wrote:

 
 I'm having some problems with iwi on -CURRENT.
 
 FreeBSD scroll.ashke.com 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Apr
 3 EDT 2010 r...@scroll.ashke.com:/usr/obj/usr/src/sys/SCROLL  i386
 
 SCROLL is simply GENERIC without INVARIANTS, INVARIANT_SUPPORT,
 WITNESS, and WITNESS_SKIPSPIN.
 
 In loader.conf I have:
 
 if_iwi_load=YES
 iwi_bss_load=YES
 legal.intel_iwi.license_ack=1
 
 In /etc/rc.conf I have:
 
 wlans_iwi0=wlan0
 ifconfig_wlan0=DHCP wpa
 
 Upon bootup, iwi fails to work with:
 
 iwi0: Intel(R) PRO/Wireless 2200BG at device 3.0 on pci3
 iwi0: [ITHREAD]
 iwi0: parity error
 iwi0: timeout waiting for iwi_bss firmware initialization to complete
 iwi0: could not load boot firmware iwi_bss
 iwi0: timeout waiting for master
 
 According to the iwi man page, could not load boot firmware should
 not happen :-)
 
 Any thoughts on how to get this working?  For what it's worth, I
 installed FreeBSD on this machine earlier this week, immediately
 upgraded to -CURRENT (previous installations from the 8-STABLE series
 on this laptop refused to let any wireless driver connect to the APs
 at work, so I specifically wanted to see if this had been fixed in
 -CURRENT), and iwi worked fine for a few days.  Then it stopped,
 though I did not change anything on the system.  I updated -CURRENT
 today to see if doing so would get iwi working again, but it did not.
 
 Adam
 ___
 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
___
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

iwi problems on -CURRENT (Apr 4. 2010)

[Adam K Kirchhoff]

I'm having some problems with iwi on -CURRENT.

FreeBSD scroll.ashke.com 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Apr  3 
 EDT 2010 r...@scroll.ashke.com:/usr/obj/usr/src/sys/SCROLL  i386

SCROLL is simply GENERIC without INVARIANTS, INVARIANT_SUPPORT,
WITNESS, and WITNESS_SKIPSPIN.

In loader.conf I have:

if_iwi_load=YES
iwi_bss_load=YES
legal.intel_iwi.license_ack=1

In /etc/rc.conf I have:

wlans_iwi0=wlan0
ifconfig_wlan0=DHCP wpa

Upon bootup, iwi fails to work with:

iwi0: Intel(R) PRO/Wireless 2200BG at device 3.0 on pci3
iwi0: [ITHREAD]
iwi0: parity error
iwi0: timeout waiting for iwi_bss firmware initialization to complete
iwi0: could not load boot firmware iwi_bss
iwi0: timeout waiting for master

According to the iwi man page, could not load boot firmware should
not happen :-)

Any thoughts on how to get this working?  For what it's worth, I
installed FreeBSD on this machine earlier this week, immediately
upgraded to -CURRENT (previous installations from the 8-STABLE series
on this laptop refused to let any wireless driver connect to the APs at
work, so I specifically wanted to see if this had been fixed in
-CURRENT), and iwi worked fine for a few days.  Then it stopped, though
I did not change anything on the system.  I updated -CURRENT today to
see if doing so would get iwi working again, but it did not.

Adam
___
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: Results of BIND RFC

[Adam Vande More]

On Fri, Apr 2, 2010 at 3:08 PM, Freddie Cash fjwc...@gmail.com wrote:

 Maybe I'm just a lowly sysadmin and ex-port maintainer, but ...

 No, no, no, definitely no, no, and no!!

 The greatest thing about FreeBSD is that there is a clear separation
 between
 the base OS and everything else (ports, local installs, etc).  You get a
 nice, clearly defined, base to build on.  You get a stable base that
 changes
 infrequently, that you can add software to on whatever schedule you want.

 The worst thing about Linux distros is the lack of this clear separation
 between the base and third-party apps.  If you want to install an updated
 version of Apache, you either have to update the whole damned distro, go
 searching for some unsupported backports repos, or compile everything by
 hand defeating the whole point of binary packages.

 Making the tools do deal with the base could be interesting, but please,
 please, please don't shove everything into the pkg_tools and turning
 FreeBSD
 into just a random collection of packages that kind of work together.
 IOW, don't go down the distro path.

 Keep the base OS separate from third-party apps.  Keep the tools to deal
 with them separate.


True word, brother!  If we wanted to run linux there are options for it.
debs suck, rpms really suck.  Those types of systems are sometimes faster to
get up and rolling as long as you want vanilla apps, but they are a major
PITA for many types of customizations which are a breeze with the ports
tree.  You'd be killing of one of the more elegant approaches in FreeBSD.
Sure there are problem with it, but IMO adopting more severe problems isn't
a good answer.

Maybe that was a 4/1 too though.  If so, good work.


-- 
Adam Vande More
___
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

bsdtar(1) line_reader.c interesting code part - partial patch

[Adam PAPAI]

Hi,

Bug report sais:

http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/144786

bsdtar(1) doesn't support multi line matching or it is broken.

This patch [1] should solve it but not sure about this line in the 
original code:


if (lr-nullSeparator) {
...
}

This is  constant '\n' so this code part was never reached. This is why 
the '\n' separated lines were handled as one long line.


The line_reader.c header comment sais:

 * Read lines from file and do something with each one.  If option_null
 * is set, lines are terminated with zero bytes; otherwise, they're
 * terminated with newlines.

But where is the switch to change between \n and zero bytes? :)

[1]: http://www.wooh.hu/freebsd/line_reader.c.patch.txt


--
Adam PAPAI
___
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

[PATCH] - ports/144792 (untar.c, Makefile) ports/archivers/untar

[Adam PAPAI]

Hi,

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144792

To remove the compile warnings I've added the required header files. 
(and a small fix for the Makefile NOMAN - NO_MAN warning)


http://www.wooh.hu/freebsd/untar.c.patch.txt
http://www.wooh.hu/freebsd/Makefile.patch.txt

--
Adam PAPAI

___
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: dumb question 'Bad system call' after make world

[Szilveszter Adam]

Hello,

On Fri, Nov 21, 2003 at 09:44:17PM -0500, Barney Wolff wrote:
 Does make world build a kernel?  I didn't think so, and OP's message
 indicates that make world is all he did.  I suspect re-install is the
 best answer now.

Yes, make world does not build or install kernels. I'd also go for
reinstall, provided the OP has not yet put a lot of work into
customising the install...

 Will somebody please tell me when make world is ever correct in the
 environment of the last several years?  I've been unable to understand
 its continued existence as a target.

One of it's last hideouts seems to be the make release target...

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3

[Szilveszter Adam]

Hello,

On Wed, Oct 22, 2003 at 01:21:10AM -0400, Joe Marcus Clarke wrote:
 On Wed, 2003-10-22 at 01:14, Scott W wrote:
  Also, is there a way to pass configure options to portupgrade, or should 
  I run make clean  ./configure for each port in an 'upgrade chain' and 
  then force portupgrade to not make clean prior to building/installing?
 
 Configure arguments?  No.  However, you can use the -m option to pass
 make arguments (e.g. -DWITH_FOO).  To pass configure arguments, you'd
 have to edit the port Makefiles directly.

There is an easier way: you can use CONFIGURE_* variables, which can
also be defined on the command line. For documentation on these and on
the Makefile format for ports, see the Porters Handbook.

There is also pkgtools.conf, as has been noted.

Hope this helps.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: /bin/sh terminated abnormally

[Szilveszter Adam]

On Sat, Oct 04, 2003 at 09:19:45PM -0700, Mike Hunter wrote:

  when I boot into the FreeBSD 5.1 I am getting this error message :
  WARNING: Userland calling deprecated sysctl, please rebuild world.
  
  I tried to world rebuild the  but I can't  It's failing at
  /usr/src/gnu/usr.bin/gperf
  
  I re-cvsuped the src this time I can't buildworld
  
  Stop in /usr/src/include/sys/_type.h : 80
  
  i dont know what to do now
 
 I'm cc'ing current because I'm not sure what the best thing to do is at
 this point.  You could try rm -rf'ing /usr/srclil help?

No need to do that. You have done the following:

buildworld on old system. Worked.
buildkernel on old system. Worked.
installkernel on old system. Worked, but now your kernel is not in sync
with your userland any more.
reboot with new kernel (with manual intervention). Seems it worked. But
now you need to make installworld, to get back in sync. (from single
user mode, of course)

But best would be, for future reference, to first update the src files
to the 5.x you are upgrading to, *then* reading /usr/src/UPDATING, there
is a lenghty section on upgrading from 4.x to 5.x, and following it to
minute detail, because this operation is rather complicated. The section
is titled To upgrade in-place from 4.x-stable to current. It is not
late to read it even now. There are a few things worth noting in there.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: panic on yesterday's -CURRENT: linux emulation and vm (lockmgr: locking against myself)

[Adam Migus]

Alan Cox wrote:

On Thu, Sep 25, 2003 at 11:15:57AM -0400, Robert Watson wrote:
 

...
#6  0xc049f355 in vm_fault (map=0xc6fc1700, vaddr=0, fault_type=1 '\001', 
   fault_flags=0) at /usr/src/sys/vm/vm_fault.c:219
#7  0xc04eddd9 in trap_pfault (frame=0xdd699b18, usermode=0, eva=0)
   at /usr/src/sys/i386/i386/trap.c:709
#8  0xc04eda50 in trap (frame=
 {tf_fs = -1070333928, tf_es = -1067384816, tf_ds = 16, tf_edi = 0,
tf_esi = -1068054086, tf_ebp = -580281484, tf_isp = -580281532, tf_ebx =
441, tf_edx = -968258896, tf_ecx = 0, tf_eax = -968258896, tf_trapno = 12,
tf_err = 0, tf_eip = -1070325008, tf_cs = 8, tf_eflags = 66178, tf_esp =
0, tf_ss = -1068146900})
   at /usr/src/sys/i386/i386/trap.c:418
#9  0xc04dd9e8 in calltrap () at {standard input}:102
#10 0xc04adbde in vm_page_sleep_if_busy (m=0x1b9, also_m_busy=1, msg=0x0)
   at /usr/src/sys/vm/vm_page.c:441
#11 0xc04abcfb in vm_object_split (entry=0xc6eea8ac)
   at /usr/src/sys/vm/vm_object.c:1226
...
   

Based upon the above information, it looks like vm_object_split()
followed a bogus vm page pointer.  This is in frequently executed
code.  So, I would hypothesize a race condition or transient hardware
error is responsible.
When my recent amd64 and i386 pmap changes are replicated on all
platforms that will enable me to introduce additional assertions on
the vm object locking.  That may reveal some unsynchronized vm object
accesses that could lead to the above problem.
Alan
___
 

FWIW, I got this same panic a few days ago, running portinstall shortly 
after gnome2 had fillled my fd table for some unknown reason, on 
5.1-RELEASE-p5.

Adam

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ATA-ng

[Adam K Kirchhoff]

I upgraded to -CURRENT from around 6:00 PM EST (10:00 PM GMT, iirc), a few
hours after your message, Soren, and gave it a shot...  With the atapicam
device.  Unfortunately, it doesn't see my IDE cd drive as either an IDE cd
drive or a SCSI drive.  It's completely missing :-)

But, on the + side, at least I'm not getting a kernel panic any more :-)

On Wed, 27 Aug 2003, Soren Schmidt wrote:

 It seems Chris Petrik wrote:
  Think it would be a wise thing to do is to make a kernel option to use ATAng
  and one to use the old ATAold or something you commited a important part of
  the system without throughly testing it and most people dont use SMP i would
  think to do it this way then when its proven that ATAng is stable and
  working remove the ATAold stuff and make ATAng default but thats just a
  sugestion as im having problems too.

 It sounds to me as if you should not run -current :)

 Anyhow please upgrade to the latest that should fix the problems with
 the probe missing some devices.

 -Søren
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30

[Adam K Kirchhoff]

Thomas,

I tried your patch.  Though I know longer get kernel panics, I
also don't get FreeBSD to see my IDE CD/DVD drive :-) (as either an IDE or
SCSI drive).

Adam

On Thu, 28 Aug 2003, Thomas Quinot wrote:

 Le 2003-08-27, Lee Damon écrivait :

  Removing atapicam from my kernel configuration fixed the problem
  for me as well.

 Please try the patch I posted on -current under HEADS UP! ATAng
 committed.

 Thanks,
 Thomas.

 --
 [EMAIL PROTECTED]
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: IDE DVD playback on 5.1-CURRENT

[Adam K Kirchhoff]

Hmmm...  I'll give that a shot, thanks :-)  Did you ever submit your patch
to the port maintainer?

Adam

On Thu, 28 Aug 2003, Peter Kostouros wrote:

 Hi

 I had a similar problem when running mplayer with recent kernels. My
 problem was that although I was executing mplayer with -dvd-device
 /dev/acd0, the program was trying to open /dev/racd0. I modified
 main/libmpdvdkit2/dvd_reader.c and sure enough everything is OK. I hope
 the following helps:

 #if defined(SYS_BSD)
 /* FreeBSD /dev/(r)(a)cd0c (a is for atapi), recomended to _not_ use r
OpenBSD /dev/rcd0c, it needs to be the raw device
NetBSD  /dev/rcd0[d|c|..] d for x86, c (for non x86), perhaps others
Darwin  /dev/rdisk0,  it needs to be the raw device
BSD/OS  /dev/sr0c (if not mounted) or /dev/rsr0c ('c' any letter will
 do) */
 static char *bsd_block2char( const char *path )
 {
 char *new_path;

 #if 0
 /* If it doesn't start with /dev/ or does start with /dev/r exit */
 if( strncmp( path, /dev/,  5 ) || !strncmp( path, /dev/r, 6 ) )
   return (char *) strdup( path );

 /* Replace /dev/ with /dev/r */
 new_path = malloc( strlen(path) + 2 );
 strcpy( new_path, /dev/r );
 strcat( new_path, path + strlen( /dev/ ) );
 #endif

 new_path = strdup(path);

 return new_path;
 }
 #endif


 Adam K Kirchhoff wrote:

 Again, no luck.  From vlc:
 
 [0141] main input: playlist item `dvdold:///dev/[EMAIL PROTECTED],1'
 [0141] dvd input error: dvdcss cannot open device
 libdvdread: Using libdvdcss version 1.2.5 for DVD access
 libdvdread: Could not open /dev/acd0 with libdvdcss.
 libdvdread: Can't open /dev/acd0 for reading
 [0141] dvdread input error: libdvdcss cannot open source
 [0141] vcd input error: no movie tracks found
 [0141] main input error: no suitable access module for 
 `/://dvdold:///dev/[EMAIL PROTECTED],1
 
 From mplayer:
 
 Playing DVD title 1
 libdvdread: Could not open device with libdvdcss.
 libdvdread: Can't open /dev/acd0 for reading
 Couldn't open DVD device: /dev/acd0
 
 From ogle:
 
 libdvdread: Using libdvdcss version 1.2.5 for DVD access
 libdvdread: Could not open /dev/acd0c with libdvdcss.
 libdvdread: Can't open /dev/acd0c for reading
 ERROR[ogle_nav]: faild to open/read the DVD
 
 Yet the same DVD in the firewire drive works just fine.
 
 I can certainly try recompiling the applications but, frankly, I'm really
 doubtful that will solve the problem :-(
 
 Adam
 
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
 
 
 
 


 --

 Regards

 Peter

 As always the organisation disavows knowledge of this email


 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to [EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: IDE DVD playback on 5.1-CURRENT

[Adam K Kirchhoff]

And a quick FYI:  After making the changes below, mplayer still refuses to
play back any DVDs. :-)  I'll probably just wait till ATAnp and atapicam
are working together nicely again before I continue fighting with it.

Adam

On Thu, 28 Aug 2003, Adam K Kirchhoff wrote:


 Hmmm...  I'll give that a shot, thanks :-)  Did you ever submit your patch
 to the port maintainer?

 Adam

 On Thu, 28 Aug 2003, Peter Kostouros wrote:

  Hi
 
  I had a similar problem when running mplayer with recent kernels. My
  problem was that although I was executing mplayer with -dvd-device
  /dev/acd0, the program was trying to open /dev/racd0. I modified
  main/libmpdvdkit2/dvd_reader.c and sure enough everything is OK. I hope
  the following helps:
 
  #if defined(SYS_BSD)
  /* FreeBSD /dev/(r)(a)cd0c (a is for atapi), recomended to _not_ use r
 OpenBSD /dev/rcd0c, it needs to be the raw device
 NetBSD  /dev/rcd0[d|c|..] d for x86, c (for non x86), perhaps others
 Darwin  /dev/rdisk0,  it needs to be the raw device
 BSD/OS  /dev/sr0c (if not mounted) or /dev/rsr0c ('c' any letter will
  do) */
  static char *bsd_block2char( const char *path )
  {
  char *new_path;
 
  #if 0
  /* If it doesn't start with /dev/ or does start with /dev/r exit */
  if( strncmp( path, /dev/,  5 ) || !strncmp( path, /dev/r, 6 ) )
return (char *) strdup( path );
 
  /* Replace /dev/ with /dev/r */
  new_path = malloc( strlen(path) + 2 );
  strcpy( new_path, /dev/r );
  strcat( new_path, path + strlen( /dev/ ) );
  #endif
 
  new_path = strdup(path);
 
  return new_path;
  }
  #endif
 
 
  Adam K Kirchhoff wrote:
 
  Again, no luck.  From vlc:
  
  [0141] main input: playlist item `dvdold:///dev/[EMAIL PROTECTED],1'
  [0141] dvd input error: dvdcss cannot open device
  libdvdread: Using libdvdcss version 1.2.5 for DVD access
  libdvdread: Could not open /dev/acd0 with libdvdcss.
  libdvdread: Can't open /dev/acd0 for reading
  [0141] dvdread input error: libdvdcss cannot open source
  [0141] vcd input error: no movie tracks found
  [0141] main input error: no suitable access module for 
  `/://dvdold:///dev/[EMAIL PROTECTED],1
  
  From mplayer:
  
  Playing DVD title 1
  libdvdread: Could not open device with libdvdcss.
  libdvdread: Can't open /dev/acd0 for reading
  Couldn't open DVD device: /dev/acd0
  
  From ogle:
  
  libdvdread: Using libdvdcss version 1.2.5 for DVD access
  libdvdread: Could not open /dev/acd0c with libdvdcss.
  libdvdread: Can't open /dev/acd0c for reading
  ERROR[ogle_nav]: faild to open/read the DVD
  
  Yet the same DVD in the firewire drive works just fine.
  
  I can certainly try recompiling the applications but, frankly, I'm really
  doubtful that will solve the problem :-(
  
  Adam
  
  
  ___
  [EMAIL PROTECTED] mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to [EMAIL PROTECTED]
  
  
  
  
  
 
 
  --
 
  Regards
 
  Peter
 
  As always the organisation disavows knowledge of this email
 
 
  ___
  [EMAIL PROTECTED] mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to [EMAIL PROTECTED]
 



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

IDE DVD playback on 5.1-CURRENT

[Adam K Kirchhoff]

I've asked this same question on freebsd-questions an on #freebsd
(freenode), but haven't gotten any answer, so I thought I'd ask on here.

I'm hoping someone can help me out here.

I recently moved a firewire card and DVD drive that had been in my FreeBSD
box to another computer.  I replaced it with an IDE DVD drive.  The
probelm is that now I can't get mplayer or vlc to play any DVDs that had
previously worked with the firewire drive.

I have, of course, made sure that /dev/dvd is a symbolic link to /dev/acd0
instead of /dev/cd0 (as it used to be).  The only difference that I can
think of is that FreeBSD sees the firewire drive as a scsi drive and sees
the ide drive as an ide drive.

Is DVD playback just not supported on IDE drives on FreeBSD -CURRENT?

I've grabbed the output from mplayer and the dump from ktrace/kdump and
posted them at:

http://memory.visualtech.com/kdump.txt (975 kB)
http://memory.visualtech.com/mplayer.txt (1 kB)

From mplayer.txt, you see that it's complaing:

Couldn't open DVD device: /dev/dvd

Now /dev/dvd is a symlink to /dev/acd0:

[ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/dvd
lrwxr-xr-x  1 root  wheel  3 Aug 25 15:54 /dev/dvd - /dev/acd0

And /dev/acd0 looks like:

[ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/acd0
crw-r--r--  1 root  operator  117,   0 Aug 25 15:36 /dev/acd0

Note:  user 'adamk' is part of the 'operator' group.  In addition, as you
can see from the mplayer.txt file, I've tried this as root just in case
there's some strange permission thing going on.  Still no luck.

Adam


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: IDE DVD playback on 5.1-CURRENT

[Adam K Kirchhoff]

On Wed, 27 Aug 2003, Terry Lambert wrote:

 Adam K Kirchhoff wrote:
  I recently moved a firewire card and DVD drive that had been in my FreeBSD
  box to another computer.  I replaced it with an IDE DVD drive.  The
  probelm is that now I can't get mplayer or vlc to play any DVDs that had
  previously worked with the firewire drive.
 [ ... ]
  Couldn't open DVD device: /dev/dvd
 [ ... ]
  Now /dev/dvd is a symlink to /dev/acd0:
 
  [ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/dvd
  lrwxr-xr-x  1 root  wheel  3 Aug 25 15:54 /dev/dvd - /dev/acd0
 
  And /dev/acd0 looks like:
 
  [ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/acd0
  crw-r--r--  1 root  operator  117,   0 Aug 25 15:36 /dev/acd0
 
  Note:  user 'adamk' is part of the 'operator' group.  In addition, as you
  can see from the mplayer.txt file, I've tried this as root just in case
  there's some strange permission thing going on.  Still no luck.

 A really common problem with DVD and audio-using programs is
 they try to open device read/write, instead of read-only.

 I notice that you don't have write permission.  This might be
 your problem.

No such luck.  I already thought about that and chmod acd0 to 666 just in
case.

 Also, you may want to try a hard link instead of a symbolic
 link; see man devfs and man rc.devfs.

 Finally, try recompiling your DVD player program, whatever it
 is, since it might check at compile time what it's talking to,
 and be too dumb to do the right thing.

 You may also want to pint it directly at the device, instead
 of using a symbolic link and making things more complicated
 than they need to be (one less variable to vary and cause
 breakage).

Again, no luck.  From vlc:

[0141] main input: playlist item `dvdold:///dev/[EMAIL PROTECTED],1'
[0141] dvd input error: dvdcss cannot open device
libdvdread: Using libdvdcss version 1.2.5 for DVD access
libdvdread: Could not open /dev/acd0 with libdvdcss.
libdvdread: Can't open /dev/acd0 for reading
[0141] dvdread input error: libdvdcss cannot open source
[0141] vcd input error: no movie tracks found
[0141] main input error: no suitable access module for `/://dvdold:///dev/[EMAIL 
PROTECTED],1

From mplayer:

Playing DVD title 1
libdvdread: Could not open device with libdvdcss.
libdvdread: Can't open /dev/acd0 for reading
Couldn't open DVD device: /dev/acd0

From ogle:

libdvdread: Using libdvdcss version 1.2.5 for DVD access
libdvdread: Could not open /dev/acd0c with libdvdcss.
libdvdread: Can't open /dev/acd0c for reading
ERROR[ogle_nav]: faild to open/read the DVD

Yet the same DVD in the firewire drive works just fine.

I can certainly try recompiling the applications but, frankly, I'm really
doubtful that will solve the problem :-(

Adam


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: IDE DVD playback on 5.1-CURRENT

[Adam K Kirchhoff]

On Wed, 27 Aug 2003, Adam K Kirchhoff wrote:


 On Wed, 27 Aug 2003, Terry Lambert wrote:

  Adam K Kirchhoff wrote:
   I recently moved a firewire card and DVD drive that had been in my FreeBSD
   box to another computer.  I replaced it with an IDE DVD drive.  The
   probelm is that now I can't get mplayer or vlc to play any DVDs that had
   previously worked with the firewire drive.
  [ ... ]
   Couldn't open DVD device: /dev/dvd
  [ ... ]
   Now /dev/dvd is a symlink to /dev/acd0:
  
   [ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/dvd
   lrwxr-xr-x  1 root  wheel  3 Aug 25 15:54 /dev/dvd - /dev/acd0
  
   And /dev/acd0 looks like:
  
   [ [EMAIL PROTECTED] - /usr/home/adamk ]: ls -l /dev/acd0
   crw-r--r--  1 root  operator  117,   0 Aug 25 15:36 /dev/acd0
  
   Note:  user 'adamk' is part of the 'operator' group.  In addition, as you
   can see from the mplayer.txt file, I've tried this as root just in case
   there's some strange permission thing going on.  Still no luck.
 
  A really common problem with DVD and audio-using programs is
  they try to open device read/write, instead of read-only.
 
  I notice that you don't have write permission.  This might be
  your problem.

 No such luck.  I already thought about that and chmod acd0 to 666 just in
 case.

  Also, you may want to try a hard link instead of a symbolic
  link; see man devfs and man rc.devfs.
 
  Finally, try recompiling your DVD player program, whatever it
  is, since it might check at compile time what it's talking to,
  and be too dumb to do the right thing.
 
  You may also want to pint it directly at the device, instead
  of using a symbolic link and making things more complicated
  than they need to be (one less variable to vary and cause
  breakage).

 Again, no luck.  From vlc:

 [0141] main input: playlist item `dvdold:///dev/[EMAIL PROTECTED],1'
 [0141] dvd input error: dvdcss cannot open device
 libdvdread: Using libdvdcss version 1.2.5 for DVD access
 libdvdread: Could not open /dev/acd0 with libdvdcss.
 libdvdread: Can't open /dev/acd0 for reading
 [0141] dvdread input error: libdvdcss cannot open source
 [0141] vcd input error: no movie tracks found
 [0141] main input error: no suitable access module for `/://dvdold:///dev/[EMAIL 
 PROTECTED],1

 From mplayer:

 Playing DVD title 1
 libdvdread: Could not open device with libdvdcss.
 libdvdread: Can't open /dev/acd0 for reading
 Couldn't open DVD device: /dev/acd0

 From ogle:

 libdvdread: Using libdvdcss version 1.2.5 for DVD access
 libdvdread: Could not open /dev/acd0c with libdvdcss.
 libdvdread: Can't open /dev/acd0c for reading
 ERROR[ogle_nav]: faild to open/read the DVD

 Yet the same DVD in the firewire drive works just fine.

 I can certainly try recompiling the applications but, frankly, I'm really
 doubtful that will solve the problem :-(

 Adam

I rebooted my machine and finally noticed the following error message on
the console:

acd0: FAILURE - FLUSHCACHE status=51READY,DSC,ERROR error=4ABORTED

Could this be part of my problem?

Adam


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30laptop

[Adam K Kirchhoff]

I'm seeing the same thing on my desktop box.  I thought that atapicam
might solve my DVD playback problems so I recompiled the kernel with the
atapicam device and this was the result:

CPU: Intel Pentium III (1002.28-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x68a  Stepping = 10
  
Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE
real memory  = 536805376 (511 MB)
avail memory = 515506176 (491 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00178011, at 0xfec0
bktr_mem: memory holder loaded
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: VIA694 AWRDACPI on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00fdd20
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI-safe frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0
acpi_cpu0: CPU on acpi0
acpi_cpu1: CPU on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 
0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
IOAPIC #0 intpin 11 - irq 2
IOAPIC #0 intpin 10 - irq 5
IOAPIC #0 intpin 5 - irq 10
agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xf000-0xf7ff at device 
0.0 on pci0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
drm0: ATI Radeon QL R200 8500 LE port 0xc000-0xc0ff mem 
0xf900-0xf900,0xe000-0xefff irq 10 at device 0.0 on pci1
info: [drm] AGP at 0xf000 128MB
info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
isab0: PCI-ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: VIA 82C686B UDMA100 controller port 0xd000-0xd00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: serial bus, USB at device 7.2 (no driver attached)
pci0: serial bus, USB at device 7.3 (no driver attached)
pci0: bridge, PCI-unknown at device 7.4 (no driver attached)
fxp0: Intel 82559 Pro/100 Ethernet port 0xdc00-0xdc3f mem 
0xfb00-0xfb0f,0xfb101000-0xfb101fff irq 5 at device 8.0 on pci0
fxp0: Ethernet address 00:d0:b7:90:6c:3e
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ahc0: Adaptec 19160B Ultra160 SCSI adapter port 0xe000-0xe0ff mem 
0xfb10-0xfb100fff irq 2 at device 9.0 on pci0
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
pci0: serial bus, FireWire at device 10.0 (no driver attached)
bktr0: BrookTree 878 mem 0xfb103000-0xfb103fff irq 10 at device 11.0 on pci0
bktr0: Hauppauge Model 44801 D126
bktr0: Hauppauge WinCast/TV, Philips NTSC tuner.
pci0: multimedia at device 11.1 (no driver attached)
pci0: multimedia, audio at device 12.0 (no driver attached)
pci0: input device at device 12.1 (no driver attached)
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 
irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A, console
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0 port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0: Parallel port bus on ppc0
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
orm0: Option ROMs at iomem 0xd-0xd3fff,0xc-0xccfff on isa0
pmtimer0 on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x100
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2

Timecounters tick every 10.000 msec
acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0%
ad0: 39083MB Maxtor 5T040H4 [79408/16/63] at ata0-master UDMA100
acd0: DVDROM Pioneer DVD-ROM ATAPIModel DVD-120 at ata0-slave PIO4
ad2: 117246MB Maxtor 6Y120L0 [238216/16/63] at ata1-master UDMA100
Waiting 3 seconds for SCSI devices to settle


Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 
fault virtual address   = 0x0
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc017d4ae
stack pointer   = 0x10:0xd7142abc
frame pointer   = 0x10:0xd7142ac8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags  

Re: mksnap_ffs, snapshot issues, again

[Adam Migus]

Julian Elischer said:
 Would it not be possible to make the snapshot file not appear in a
 directory until it si finished? (I know that would be 'wierd'
 but it would give a guaranteed solution..


That sounds kinda neat as a compile time option or non-default (or
perhaps even default) tunable if it were possible and not too
difficult.  The problem should likely be addressed given people
might want to create snapshots around the same time they run find
via the maintanence scripts.

-- 
Adam - Migus Dot Org (http://www.migus.org)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: sound card woes

[Szilveszter Adam]

Hello,

On Fri, Aug 22, 2003 at 11:30:45AM -0400, Matt Gostick wrote:
 On Wed, 2003-08-20 at 17:04, Szilveszter Adam wrote:
  What does 'cat /dev/sndstat' say?
 
 # cat /dev/sndstat
 FreeBSD Audio Driver (newpcm)
 Installed devices:
 pcm0: SB16 DSP 4.16 (ViBRA16X) at io 0x220 irq 7 drq 0 bufsz 4096d (1p/1r/0v 
 channels duplex default)

So it's a Vibra. It seems to be detected mostly ok.

 cat test.wav  /dev/dsp makes a sound...  but it isn't exactly what
 test.wav should sound like.

You mean the sound is distorted?

  The issue is probably some resource conflict. Since you have an SB 16,
  I'll have to ask: is it ISA? Or ISAPnP? Or PCI? PCI should just work
  but if it is ISA, you will need some tweaking.
 
 It is an ISA card... very old.  Should I try and dig up a PCI card, or
 is it going to fairly 'painless' tweaking?  Where should I start
 tweaking?

My previous assumption seems to be reinforced, it is probably a resource
conflict. If the card is ISAPnP (I think it is) you could try to extract
a correct configuration from it using the pnpinfo command. Do not be
very surprised if you will see many possible configs. (My old SB 64 AWE
card had at least 6 or something) Pick one that is marked best or
similar and check that the kernel uses that. You should also try and
avoid IRQ sharing for the slot that the card is in if possible. If the
card does not find the proper setting by itself, you may need to use
hints. See them in /usr/src/sys/conf/NOTES, like this:

hints.sbc.0.at=isa
hints.sbc.0.port=0x220
hints.sbc.0.irq=5
hints.sbc.0.drq=1
hints.sbc.0.flags=0x15

Please do not copy these simply, but find the settings that your card
supports and use those! 

If the card is not even ISAPnP, then you need its docs to find the real
config. Possibly there is also a DOS program to set them on the card or
jumpers. 

For your first question, yes, it should be easier to get a PCI card to
work (even an SB 16) and it will cause less problems in any case. ISA
cards can impact the system performance very badly.

Hope this helps somewhat.
-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: sound card woes

[Szilveszter Adam]

Hello,

On Wed, Aug 20, 2003 at 03:20:55PM -0400, Matt Gostick wrote:
 I have a SND Blaster 16 in my computer.  I was using FreeBSD 4.8 and
 'device pcm' in my kernel config file, worked great.  I've completely
 re-installed with 5.1R and recompiled my kernel with 'device pcm'. 
 Unfortunately sound doesn't work.

You also could add 'device sbc' to your kernel config since that is the
SB bridge driver. But the card should work with PCM only. 

What does 'cat /dev/sndstat' say?

The issue is probably some resource conflict. Since you have an SB 16,
I'll have to ask: is it ISA? Or ISAPnP? Or PCI? PCI should just work
but if it is ISA, you will need some tweaking.

 I no longer have a /dev/snd0 device - I think I had one before...  how
 do I make devices in 5.1R???   MAKEDEV is no longer available... and
 section 9.5 of the FreeBSD manual says: If you are running FreeBSD 5.0
 or later you can safely skip this section. These versions use devfs(5)
 to allocate device nodes transparently for the user

You do not need this, devfs will create the device for you when needed.


-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

date/time, standards n' stuff question

[Adam Migus]

Folks,
First of all I'm not sure if this is the right list.  If it isn't
please accept my apologies and divert the thread to the right one so
I'll know for future reference.

I'm using the following little program to generate nano-second
timestamps for performance testing:

int
main(int argc, char **argv)
{
struct timespec ts;

if (clock_gettime(CLOCK_REALTIME, ts) != 0) {
perror(clock_gettime);
return (1);
}
printf(%d.%09lu\n, ts.tv_sec, ts.tv_nsec);

return (0);
}

My question is would it be right/acceptable/agreeable to augment
/usr/bin/date to include an option to generate nanosecond precision
dates?  I'm thinking this might make things icky with regards to
standards, etc. but if it were an option and didn't affect the
existing functionality would it really matter?  Would anyone care? 
Does anyone like or object to the idea?

My motivation for asking is simply to avoid having to distribute/use
this program with the performance testing stuff as previously
(before I cared about nano-second precision) I just used
/usr/bin/date to generate the datestamps.


-- 
Adam - Migus Dot Org (http://www.migus.org)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: make buildkernel hang with SCHED_ULE

[Adam Migus]

Dr. Richard E. Hawkins said:
 On Thu, Aug 14, 2003 at 10:49:42PM -0400, Adam Migus wrote:
 Andrew Gallatin wrote:

 WRT the mime thing.  My apologies.  It never occured to me as
 everyone I
 know personally uses a real mail reader.  I'd attached them
 simply to
 keep the scrolling down and allow order independant viewing.
 Thanks for
 the tip.  I'll just read them in as plain text in the future.

 If it gives mail or mh problems, it doesn't work on *real* mail
 readers.

 :)

 hawk, ignobly usin mutt
 --
 Richard E. Hawkins, Asst. Prof. of Economics/\   ASCII ribbon
 campaign
 [EMAIL PROTECTED]  Smeal 178  (814) 375-4700  \ /   against HTML
 mail
 These opinions will not be those of  Xand postings.
 Penn State until it pays my retainer.   / \


Well, I guess we're back to that whole, what is real thing.  So if
for the sake of argument, if works with mime were the
qualification for a real mail reader and everyone stopped using
mime, would all mail readers become not real?  Gee, that could be
problematic.  There must be something else that makes a mail reader
real.  Otherwise we'd better hope people keep using mime.

If continued, I think this belongs on -chat.  :-)

-- 
Adam - Migus Dot Org (http://www.migus.org)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: make buildkernel hang with SCHED_ULE

[Adam Migus]

Andrew Gallatin wrote:

Adam Migus writes:
 Folks,
 While doing some performance analysis (doing make -j5 buildkernel)
 on a set of 14 kernels I've hit one using the SCHED_ULE scheduler
 that hangs.   It happens every time but not necessarily in the same
 place in the make.
 

...

 The hardware is a dual Xeon box.  The kernel is SMP w/ SCHED_ULE
 instead of SCHED_4BSD, the options required for diskless and the
 following two options:
You have machdep.hlt_logical_cpus: 1 in your sysctl output.  [BTW,
lots of people read this mail via the web archives at
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1073654+0+current/freebsd-current,
where its impossible to view mime; it would be MUCH better for us if
appended things like stack traces and sysctl output rather then
scrambling them for no reason]
SCHED_ULE is incompatible with halting logical CPUs.  Something about
it does't know the core isn't running, so it schedules a job there
which never runs, and then it gets confused.  When I boot a 1 CPU P4
with an SMP kernel and machdep.hlt_logical_cpus=1, it hangs before
making it to multiuser mode..
Try setting machdep.hlt_logical_cpus=0 (via sysctl now, and in
/boot/loader.conf so it doesn't happen again).
Drew
 

Andrew,
WRT the mime thing.  My apologies.  It never occured to me as everyone I 
know personally uses a real mail reader.  I'd attached them simply to 
keep the scrolling down and allow order independant viewing.  Thanks for 
the tip.  I'll just read them in as plain text in the future.

WRT the sysctl value.  Thanks for the tip.  Is this to be considered a 
bug in SCHED_ULE?  If the default is hlt_logical_cpus=1 I would think 
the scheduler should be able to handle it or deal with it 
appropriately.  Perhaps ignoring the value, setting it to 0 internally 
or even just putting a warning message on boot?  After all, not everyone 
RTFM's.  :-)

Thanks again,

--
Adam - Migus Dot Org (http://www.migus.org)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]