Re: aliasing (or renaming) kern.geom.debugflags

2011-10-25 Thread Poul-Henning Kamp
In message alpine.gso.1.10.1110242118020@multics.mit.edu, Benjamin Kaduk 
writes:
On Mon, 24 Oct 2011, Andrey V. Elsukov wrote:

 This is stale message. boot0cfg might work without this.

On a *mounted* disk? Surely that qualifies as an open for the purposes 
of the check.

The way this used to work before gpart, is that boot0cfg would send
a GEOM ctl-message to the MBR-geom asking Would you please write this
boot code ?

Since the MBR-geom was the owner of the whole disk, and the one
who had it open for writing, it could obviously do so, if  it saw fit,
and after it had edited its idea about the mbr-partition table into
that boot-code.

Gpart appearantly does not implement such a ctl message.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
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: aliasing (or renaming) kern.geom.debugflags

2011-10-25 Thread Andrey V. Elsukov
On 25.10.2011 10:08, Poul-Henning Kamp wrote:
 The way this used to work before gpart, is that boot0cfg would send
 a GEOM ctl-message to the MBR-geom asking Would you please write this
 boot code ?
 
 Since the MBR-geom was the owner of the whole disk, and the one
 who had it open for writing, it could obviously do so, if  it saw fit,
 and after it had edited its idea about the mbr-partition table into
 that boot-code.
 
 Gpart appearantly does not implement such a ctl message.

gpart does it in the same way.

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature


Re: aliasing (or renaming) kern.geom.debugflags

2011-10-25 Thread Poul-Henning Kamp
In message 4ea654f6.1060...@yandex.ru, Andrey V. Elsukov writes:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig1B092FDF9A756BE78BC74C01
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: quoted-printable

On 25.10.2011 10:08, Poul-Henning Kamp wrote:
 The way this used to work before gpart, is that boot0cfg would send
 a GEOM ctl-message to the MBR-geom asking Would you please write this
 boot code ?
=20
 Since the MBR-geom was the owner of the whole disk, and the one
 who had it open for writing, it could obviously do so, if  it saw fit,
 and after it had edited its idea about the mbr-partition table into
 that boot-code.
=20
 Gpart appearantly does not implement such a ctl message.

gpart does it in the same way.


So why doesn't boot0cfg work ?

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
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: FreeBSD 9.0 RC1 USB Mouse and Keyboard

2011-10-25 Thread Mehmet Erol Sanliturk
On Mon, Oct 24, 2011 at 6:24 PM, Benjamin Kaduk ka...@mit.edu wrote:

 On Sun, 23 Oct 2011, Mehmet Erol Sanliturk wrote:

  I have installed FreeBSD 9.0 RC1 .

 During installation and boots , and ( as root ) console mode , both USB
 keyboard and mouse are working .

 When a graphical desktop ( Fluxbox , Gnome , or KDE ) is started , both of
 them are becoming frozen .
 Detach and attach of mouse are detected , but input is not possible .
 PS/2 mouse is also not working .
 I did not check PS/2 keyboard .
 Only Ctrl-Alt-F1 is discontinuing graphical display , and Ctrl-C is
 returning to root prompt .

 KDE is staying as it is after displaying of hard disk symbol and then it
 is
 waiting there .
 Gnome is displaying all the parts , but no input possibility .
 Fluxbox is displaying its window , but no input possibility .

 It seems that X is NOT able to register dbus related parts ( understood
 from
 messages left on the screen after discontinuation ) .

 On the same computer , I have installed Fedora 15 and everything is
 working
 as expected , means there is no any hardware problem .


 Has this computer successfully run other versions of FreeBSD with X?
 I seem to recall there can be odd interactions with hald, xorg.conf, and
 others.  Some googling brings up
 http://www.wonkity.com/~wblock/docs/html/aei.html which seems to cover
 many of the relevant issues.

 -Ben Kaduk



The above problem has occurred in 9.0 RC1 amd64 .

In the same computer , I have installed 9.0 i386 .
USB Mouse and Keyboard are working very well in console mode and in Fluxbox
.

In both ( amd64 and i386 ) of the installations , /etc/rc.conf contain the
following statements :

moused_type = auto
moused_enable = YES
hald_enable = YES
dbus_enable = YES


There are no any generated X configuration file .


Both of them listed starting of hald and dbus without error during booting .

Thank you very much .


Mehmet Erol Sanliturk
___
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-update not checking disk space?

2011-10-25 Thread René Ladan
Hi,

I tried to upgrade a server at work from 8.2-RELEASE-i386 to 9.0-RC1-i386
using freebsd-update.When running 'freebsd-update install' to install the new
kernel, but that failed because there was insufficient disk space. This resulted
in freebsd-update thinking everything is ok but left the kernel unbootable.

From the screen capture:
 10G# freebsd-update install
 Installing updates...
 /: write failed, filesystem is full
 install: ///boot/kernel/INS@SmmC: No space left on device
 install: ///boot/kernel/INS@lMJN: No space left on device
 install: ///boot/kernel/INS@ez1L: No space left on device
 install: ///boot/kernel/INS@D78d: No space left on device
[... more patch files ..]
 install: ///boot/kernel/ng_bt3c.ko.symbols: No space left on device
 install: ///boot/kernel/ng_btsocket.ko: No space left on device
[.. more destination files ..]
These two types of messages are interleaved.

It ends with:
 install: ///boot/INS@yqYd: No space left on device
 rmdir: ///boot/kernel: Directory not empty

 Kernel updates have been installed.  Please reboot and run
 /usr/sbin/freebsd-update install again to finish installing updates.
 10G# df
 Filesystem  1K-blocksUsed Avail Capacity  Mounted on
 /dev/ad0s1a507630  502860-35840   108%/

So in reality the update never finished properly.

More logs on request.

Regards,
René
--
http://www.rene-ladan.nl/

GPG fingerprint = E738 5471 D185 7013 0EE0  4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
___
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: freebsd-update not checking disk space?

2011-10-25 Thread Colin Percival
On 10/25/11 00:52, René Ladan wrote:
 I tried to upgrade a server at work from 8.2-RELEASE-i386 to 9.0-RC1-i386
 using freebsd-update.When running 'freebsd-update install' to install the new
 kernel, but that failed because there was insufficient disk space. This 
 resulted
 in freebsd-update thinking everything is ok but left the kernel unbootable.

Yes, this is a known issue in freebsd-update -- it needs to be much smarter
about detecting and handling errors.  Unfortunately I haven't had time to
deal with this (and it's a lot of work).

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
___
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: /usr/src/sys/conf/kern.mk, line 10: Malformed conditional (${FREEBSD_GCC}), /usr/src/sys/conf/kern.mk, line 14: if-less endif

2011-10-25 Thread O. Hartmann

On 10/25/11 04:48, Arnaud Lacombe wrote:

Hi,

On Mon, Oct 24, 2011 at 6:23 PM, Hartmann, O.
ohart...@zedat.fu-berlin.de  wrote:

On 10/24/11 00:38, Garrett Cooper wrote:

On Oct 23, 2011, at 3:31 PM, Hartmann, O. wrote:


   Kernel building fails since today when kernel gets compiled via CLANG:
   --

stage 2.1: cleaning up the object tree

   --
   cd /usr/obj/usr/src/sys/THOR; MAKEOBJDIRPREFIX=/usr/obj
   MACHINE_ARCH=amd64  MACHINE=amd64  CPUTYPE=native
   GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
   GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
   GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
   _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp  VERSION=FreeBSD 10.0-CURRENT
   amd64 100  INSTALL=sh /usr/src/tools/install.sh
   PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/
   usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr
   /sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbi
   n:/bin:/usr/sbin:/usr/bin /usr/obj/usr/src/make.amd64/make
   KERNEL=kernel cleandir
   /usr/src/sys/conf/kern.mk, line 10: Malformed conditional
   (${FREEBSD_GCC})
   /usr/src/sys/conf/kern.mk, line 14: if-less endif
   make: fatal errors encountered -- cannot continue
   *** Error code 1
   Stop in /usr/src.
   *** Error code 1
   Stop in /usr/src.

It was noted not too long ago on the commit list as well; r226665 caused the 
breakage.
-Garrett___



So, this is by intention?
When does the problem disappear, so folks building FreeBSD with CLANG
are again capable of building a world and kernel?


seemed to have been fixed by dim@:

commit 2286e401073a60babb3cc8efce52657f6fa92f7e
Author: dimd...@freebsd.org
Date:   Mon Oct 24 18:35:16 2011 +

 Put in a temporary band-aid to fix kernel builds when CC=clang, after
 r226665.


Thanks dim@!

  - Arnaud


I was yesterday too fast. After a couple of minutes after I posted, the 
patch rushed in and everything ran smooth as before and expected. Thanks!


Regards,
Oliver
___
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


can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Claude Buisson

Hi,

When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
atapicam (and reverting from cdN to acdN of course), vlc was OK again.

It seems that I am not the only one having this kind of problem, as I found (for
example) this message on questions@ (for releng9):

http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html

Is this a known problem ? Is somebody working on it ?

Thanks,

Claude Buisson
___
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


The future of FreeBSD at Yahoo!

2011-10-25 Thread O. Hartmann
The press in Germania is full of some statements, that Google is about 
to overtake Yahoo!. As far as I know, Yahoo! is one of the more popular 
and bigger, if not the biggest and last stronghold of a FreeBSD driven 
infrastructure. Despite the fact that even Google funded lots of coding 
for FreeBSD, I had the impression that Yahoo! might be one of the 
biggest contributor. And not to mention the psychological effect of 
hearing that such a company is utilizing a project like FreeBSD for 
potential newcomers in the business.


So, what is about the future of FreeBSD? Does FreeBSD have a site where 
all the goods that has been first invented by the FreeBSD/BSD folks or 
all the things that are thought about to come in future are 
shown/listed? Crawling the mailing lists is a really nasty work.


Thanks for having patience,

Oliver
___
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: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Daniel O'Connor

On 25/10/2011, at 20:45, Claude Buisson wrote:
 When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
 ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
 atapicam (and reverting from cdN to acdN of course), vlc was OK again.
 
 It seems that I am not the only one having this kind of problem, as I found 
 (for
 example) this message on questions@ (for releng9):
 
 http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html
 
 Is this a known problem ? Is somebody working on it ?

Have you tried pointing VLC at /dev/cd0 when using ATA_CAM?

It may be trying old style ATA ioctls based on the device name.

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C






___
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: Panics after AHCI timeouts

2011-10-25 Thread Alexey Shuvaev
On Mon, Oct 24, 2011 at 08:27:49PM +0200, C. P. Ghost wrote:
 On Tue, Oct 18, 2011 at 3:13 PM, Alexey Shuvaev
 shuv...@physik.uni-wuerzburg.de wrote:
  On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote:
  On 18 October 2011 03:00, Alexey Shuvaev
  shuv...@physik.uni-wuerzburg.de wrote:
   On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alexey Shuvaev wrote:
   Hello list!
  
   Errr... Replying to myself... Ping? Should I file a PR and put it
   in the back burner? :)
 
  I think filing a PR is a good move. Then just be proactive and poke
  people about it. It'd be good to get this fixed. :)
 
  Done, kern/161768.
 
  Question to the list: does anybody see successful recovery from AHCI
  timeout an a recent CURRENT? Recent means June 2011 or newer, so 9.0
  branch counts also. That is, there are some kernel messages like this:
 
  ahcich0: Timeout on slot 29 port 0
  ahcich0: is  cs  ss  rs  tfd 40 serr 
   cmd fc17
 
  but then AHCI recovers and the system does not panic?
 
 I'm seeing these timeouts too on an 8.2-STABLE amd64 r222832
 from June 7. The system hangs partially -- or, more precisely, all
 processes that attempt to access the disk on this channel hang,
 everything else continues as normal.
 
 I suspect a faulty cable, but I don't have physical access to the system
 to replace parts right now. A panic would be a regression, so I'm holding
 off updates on that server until AHCI becomes more tolerant and somewhat
 self-healing. :(
 
In a communication not on the list mav has said he has done some tests
not so long ago by injecting artificial failures in the AHCI code.
He has not observed any panics and it is not clear if the problem is
generic / hardware related / or purely local. I would not have any time
to investigate further till November.

So, Your Mileage May Vary :)

0.02$,
Alexey.
___
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: Fresh installed Freebsd 9 don't boot from hd

2011-10-25 Thread Pavel Timofeev
2011/10/24 Dimitry Andric d...@freebsd.org

 On 2011-10-23 21:56, Dennis Koegel wrote:

 On Sun, Oct 23, 2011 at 08:57:59PM +0300, Andriy Gapon wrote:

 I found a document that suggests a possibility of BIOS writing more bytes
 to the
 array than its current size of 0x42: [...]
 Could you please test this hypothesis by trying the following patch?


 With -O1 and this patch, it boots. Thank you!


 If you have some time, can you also re-check the other cases you listed
 before?  E.g.:


 gcc -Os -fno-guess-branch-probability -fomit-frame-pointer
 -fno-unit-at-a-time \
-mno-align-long-strings -mrtd [from before r225530]:
 gcc -Os -mrtd:
 gcc -O1 -mrtd:
 gcc -O1:
 gcc -O0:
 gcc -Os:

 clang -O1:
 clang -Os:
 clang -Oz:


My 5 cents:
tested on my HP Proliant DL360 G5 with Andriy's patch
clang -O1: ok (VirtualBox with ahci boots too)
clang -Os: ok
clang -Oz: ok



 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: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Claude Buisson

On 10/25/2011 12:52, Daniel O'Connor wrote:


On 25/10/2011, at 20:45, Claude Buisson wrote:

When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
atapicam (and reverting from cdN to acdN of course), vlc was OK again.

It seems that I am not the only one having this kind of problem, as I found (for
example) this message on questions@ (for releng9):

http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html

Is this a known problem ? Is somebody working on it ?


Have you tried pointing VLC at /dev/cd0 when using ATA_CAM?



Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC)



It may be trying old style ATA ioctls based on the device name.



VLC recognize the tracks and jump quickly from one to the following, without
playing it, and with a flow of messages:

[0x2caf2a3c] cdda access error: Could not set block size
[0x2caf2a3c] cdda access error: cannot read sector n

where the sector number is incremented, and then emit (2 times if I remenber):

[0x2af28bc] es demux error: cannot peek

Sorry for having ommited these messages in the previous mail.

I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a
proposal by avg@ related to libxine:

http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html

These may not be the same problem, but I think they are related (a not so well
documented change in the kerm interface).


--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
   -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C









Claude Buisson
___
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: Fresh installed Freebsd 9 don't boot from hd

2011-10-25 Thread Andriy Gapon
on 24/10/2011 21:23 John Baldwin said the following:
 On Monday, October 24, 2011 12:25:09 pm Andriy Gapon wrote:
 Also, perhaps edd_params_v3 and edd_params_v4 should inherit edd_params in 
 some
 smarter way to avoid verbatim duplicates.
 
 Yeah, probably so.  We will probably never even use them anyway (just as we 
 don't
 use edd_packet_v3 even though we could probably make use of it to avoid some
 bounce buffering in the loader).
 
 Other than these issues the patch looks great!
 Perhaps later we could do detailed definitions for things like interface 
 paths for
 various cases, etc.
 
 I doubt we will ever use them.

In theory we could pass that information from loader to kernel, so that in a
booted system we could try to build a mapping between kernel disks and bios 
disks,
with the boot disk potentially being of the most interest.

-- 
Andriy Gapon
___
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: Slow load time to /boot/loader (3rd stage loader)

2011-10-25 Thread Vinícius Zavam
2011/10/25 J. Kuczewski jkuczew...@bnl.gov:
 Hi all,

 I have recently installed 9.0-RC1 on my Thinkpad X201 and have noticed
 severe (~20 mins) latency to get to the third stage bootloader
 (/boot/loader). This is system triple booted with Windows 7 and Arch Linux
 using the GRUB 2 bootmanager. FreeBSD is not on a extended partition, if it
 matters. I have tested two BIOS disk configurations, one with AHCI and the
 other with IDE compatibility mode. IDE mode is comparatively faster, but
 still slower than expected (~3 mins). To see if this was a regression, I
 installed 8.2, and it has the same exact effect. Booting off of USB stick
 loads fine (e.g. the installer). The following is my notes with the
 different BIOS configurations with a link to the verbose dmesgs for each...

 With AHCI enabled:
    o  dmesg output:
 http://dl.dropbox.com/u/45307545/dmesg_logs/dmesg_ahci.log
    o  Timeline:
        ~05 mins - Loading /boot/default/loader.conf appears.
        ~16 mins - /boot/kernel/kernel args displayed.
        ~20 mins - Welcome to FreeBSD boot prompt.

 With IDE compatibility enabled:
    o  dmesg output:
 http://dl.dropbox.com/u/45307545/dmesg_logs/dmesg_ide.log
    o  Timeline:
        ~02 mins - Loading /boot/default/loader.conf and /boot/kernel/kernel
 args is displayed at once.
        ~03 mins - Welcome to FreeBSD boot prompt is displayed.

 After the boot prompt, startup is normal with no slowdowns to the login
 prompt.

 ---
 Current BIOS and ECP versions (output from Linux):
 ---
 # dmidecode -s bios-version
 6QET52WW (1.22)
 # dmidecode -t 11
 # dmidecode 2.11
 SMBIOS 2.6 present.

 Handle 0x0027, DMI type 11, 5 bytes
 OEM Strings
        String 1: IBM ThinkPad Embedded Controller -[6QHT30WW-1.11    ]-

 ---
 FreeBSD GRUB2 entry:
 ---
 menuentry FreeBSD 9.0-RC1 {
    insmod ufs2
    set root=(hd0,3)
    chainloader +1
 }

 Any guidance to determine the slow down of this loading problem would be
 great.

 Thank you for your time...

 Cheers,
    -John Kuczewski

i've got something like this. check it out:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/054551.html

i remembered this issue when reading your e-mail this morning.
unfortunately i couldn't fix the issue.
just saw the answer from Paulo[1] today (LOL).. but you, John, are
using the same entry with grub2.. so sadness ;-(

nowadays i'm using 10.0current with my asus 1005pe (eeepc) and
everything runs like a charm. i still have the same pavilion; maybe
one day it will run freebsd again (even if it needs 30min to boot) 3

[1] http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055733.html


-- 
Vinícius Zavam
profiles.google.com/egypcio
___
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: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Daniel O'Connor

On 25/10/2011, at 23:24, Jeremy Chadwick wrote:
 These may not be the same problem, but I think they are related (a not so 
 well
 documented change in the kerm interface).
 
 You want atapicam(4).  This is not the same thing as options ATA_CAM.
 See /sys/conf/NOTES.
 
 Whether or not it works with audio CDs is unknown to me.

atapicam is a bridge for the old ATA code to put ATAPI devices _only_ on CAM 
(as well as the ATA infrastructure). Hence they appear as /dev/cd0 and so on.

ATA_CAM puts _all_ ATA devices on CAM, so you should be able to access your 
audio CD that way. 

I just tried and it ripped a CD fine using cdparanoia and cdcontrol seemed to 
play it OK (although I don't have the analogue output of this drive hooked up 
to the audio system).

This is not to say that there isn't a bug in the ATA_CAM code :)

--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C






___
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: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Claude Buisson

On 10/25/2011 14:54, Jeremy Chadwick wrote:

On Tue, Oct 25, 2011 at 01:18:47PM +0200, Claude Buisson wrote:

On 10/25/2011 12:52, Daniel O'Connor wrote:


On 25/10/2011, at 20:45, Claude Buisson wrote:

When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
atapicam (and reverting from cdN to acdN of course), vlc was OK again.

It seems that I am not the only one having this kind of problem, as I found (for
example) this message on questions@ (for releng9):

http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html

Is this a known problem ? Is somebody working on it ?


Have you tried pointing VLC at /dev/cd0 when using ATA_CAM?



Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC)



It may be trying old style ATA ioctls based on the device name.



VLC recognize the tracks and jump quickly from one to the following, without
playing it, and with a flow of messages:

[0x2caf2a3c] cdda access error: Could not set block size
[0x2caf2a3c] cdda access error: cannot read sector n

where the sector number is incremented, and then emit (2 times if I remenber):

[0x2af28bc] es demux error: cannot peek

Sorry for having ommited these messages in the previous mail.

I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a
proposal by avg@ related to libxine:

http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html

These may not be the same problem, but I think they are related (a not so well
documented change in the kerm interface).


You want atapicam(4).  This is not the same thing as options ATA_CAM.
See /sys/conf/NOTES.

Whether or not it works with audio CDs is unknown to me.



I *know* the difference between atapicam and ATA_CAM ;-)

I have done other tests on 8.X and 7.X, and found that audio CDs cannot be
played with atapicam.

BUT, I understood (wrongly ?) that ATA_CAM was the way to go starting with 9.X,
which imply that the traditionnal acdN interface will disappear.

A valid answer to my question may be: we - kernel developpers - know about it,
but we don't care, and the problem must be solved by the userland/applications
developpers.

With some obvious consequences on the upgrading or not upgrading of end users
systems.

Claude Buisson

___
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: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Jeremy Chadwick
On Tue, Oct 25, 2011 at 01:18:47PM +0200, Claude Buisson wrote:
 On 10/25/2011 12:52, Daniel O'Connor wrote:
 
 On 25/10/2011, at 20:45, Claude Buisson wrote:
 When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
 ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
 atapicam (and reverting from cdN to acdN of course), vlc was OK again.
 
 It seems that I am not the only one having this kind of problem, as I found 
 (for
 example) this message on questions@ (for releng9):
 
 http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html
 
 Is this a known problem ? Is somebody working on it ?
 
 Have you tried pointing VLC at /dev/cd0 when using ATA_CAM?
 
 
 Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building 
 VLC)
 
 
 It may be trying old style ATA ioctls based on the device name.
 
 
 VLC recognize the tracks and jump quickly from one to the following, without
 playing it, and with a flow of messages:
 
 [0x2caf2a3c] cdda access error: Could not set block size
 [0x2caf2a3c] cdda access error: cannot read sector n
 
 where the sector number is incremented, and then emit (2 times if I remenber):
 
 [0x2af28bc] es demux error: cannot peek
 
 Sorry for having ommited these messages in the previous mail.
 
 I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a
 proposal by avg@ related to libxine:
 
 http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html
 
 These may not be the same problem, but I think they are related (a not so well
 documented change in the kerm interface).

You want atapicam(4).  This is not the same thing as options ATA_CAM.
See /sys/conf/NOTES.

Whether or not it works with audio CDs is unknown to me.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator   Mountain View, CA, US |
| Making life hard for others since 1977.   PGP 4BD6C0CB |

___
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: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread David Wolfskill
On Fri, Oct 21, 2011 at 04:36:05PM -0400, John Baldwin wrote:
 ...
   Well, as of subversion-1.7, we don't have a .svn directory in
   ${SYSDIR} any more -- it's only at the root of the working copy
   (/usr/src, in this case).  So svnversion is never invoked.
   
   So I've just hacked my copy to parallel the git stanza  look for
   ${SYSDIR}/../.svn,  Not sure that's ideal, but there appears to be
   precedent :-}
   
   It might be handy to resolve this prior to 9.0-RELEASE, I think.
   ...
 ...

 Hmm, that won't always work, the problem is if someone just checks out a 
 kernel tree then .svn will be in SYSDIR.  Alternatively, if you have a tree 
 like mine which has work/freebsd/svn/ with various subdirs (head/, stable/ 
 with subdirs for 7, 8, 9) but all rooted at the upperlevel, just looking two 
 levels up won't work.

OK...  How about (untested) something like:

Index: sys/conf/newvers.sh
===
--- sys/conf/newvers.sh (revision 226724)
+++ sys/conf/newvers.sh (working copy)
@@ -88,7 +88,7 @@
 i=`${MAKE:-make} -V KERN_IDENT`
 
 for dir in /bin /usr/bin /usr/local/bin; do
-   if [ -d ${SYSDIR}/.svn -a -x ${dir}/svnversion ] ; then
+   if [ ( -d ${SYSDIR}/.svn -o -d ${SYSDIR}/../.svn ) -a -x 
${dir}/svnversion ] ; then
svnversion=${dir}/svnversion
break
fi

then?  That should preserve current behavior for the case you  Jilles
expressed concern about, while repairing the currently-broken default
case.

I believe it's in the interest of the project to have that default
case working again (at least) in time for 9.0-RELEASE.

Please.

 

I'm staying out of the svnversion vs. svn info branch of the thread.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpTVPQPCqGf5.pgp
Description: PGP signature


Problems with ada0: Previously was known as ad6 functionality

2011-10-25 Thread Jason Edwards
Hello list,

I'm working on ZFSguru, a FreeNAS-like distribution based on FreeBSD
that focuses on NAS or Network Attached Storage functionality,
sporting a web-interface et al.

I've been building FreeBSD 9.0-RC1, and put together a LiveCD using my
own scripts. It works, and boots fine in Virtualbox just like the
other LiveCDs. Though I discovered a problem.

It appears that some new functionality was put in 9.x to 'symlink' the
new 'ada' devices using AHCI driver to the old-fashioned 'ad' (ATA)
device names, probably to make migration of ATA to AHCI driver more
convenient for users still using hardcoded devices in /etc/fstab
(shame on you!). However, I suspect this is causing a nasty
side-effect, because after having created a GPT partition with a ZFS
pool on it, I cannot import it once I reboot fresh from the LiveCD,
with 'zpool import' showing a corrupt pool. I've seen this before and
generally it means that ZFS cannot read data or that GEOM does funny
things. In this case, it could be that ad6 and ada0 both contain the
same metadata, which somehow causes ZFS to go beserk.

I would like to debug this issue, but for that I need to disable the
'ada0 to ad6' symlinking functionality. I've searched for a sysctl
variable which can disable this behavior, but have not found it.
Anyone can enlighten me how I can disable this behavior, so that I
only get /dev/ada0 and no ad6? If the zpool import works again after
that change, this would confirm my suspicions that this behavior is
causing the zpool import command to fail.

I'm using FreeBSD 9.0-RC1 fetched this morning as RELENG_9, uname:
# uname -a
FreeBSD zfsguru.bsd 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 25 07:13:52
UTC 2011 ssh@zfsguru:/usr/obj/usr/src/sys/GENERIC  amd64


Relevant command output:

# dmesg | grep ad
(..)
ada0: Previously was known as ad6

# ls -l /dev/ad*
lrwxr-xr-x  1 root  wheel4 Oct 25 13:21 /dev/ad6 - ada0
lrwxr-xr-x  1 root  wheel6 Oct 25 13:21 /dev/ad6p1 - ada0p1
crw-r-  1 root  operator0,  73 Oct 25 13:20 /dev/ada0
crw-r-  1 root  operator0,  75 Oct 25 13:20 /dev/ada0p1

# glabel status
  Name  Status  Components
(..)
  gpt/testdisk N/A  ada0p1

# zpool import
  pool: tank
id: 17935188179790554412
 state: FAULTED
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported using
the '-f' flag.
   see: http://www.sun.com/msg/ZFS-8000-5E
config:

tankFAULTED  corrupted data
  15830803292687600194  UNAVAIL  corrupted data


Regards,
Jason / sub.mesa
___
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: Problems with ada0: Previously was known as ad6 functionality

2011-10-25 Thread Nikolay Denev
On Oct 25, 2011, at 4:38 PM, Jason Edwards wrote:

 Hello list,
 
 I'm working on ZFSguru, a FreeNAS-like distribution based on FreeBSD
 that focuses on NAS or Network Attached Storage functionality,
 sporting a web-interface et al.
 
 I've been building FreeBSD 9.0-RC1, and put together a LiveCD using my
 own scripts. It works, and boots fine in Virtualbox just like the
 other LiveCDs. Though I discovered a problem.
 
 It appears that some new functionality was put in 9.x to 'symlink' the
 new 'ada' devices using AHCI driver to the old-fashioned 'ad' (ATA)
 device names, probably to make migration of ATA to AHCI driver more
 convenient for users still using hardcoded devices in /etc/fstab
 (shame on you!). However, I suspect this is causing a nasty
 side-effect, because after having created a GPT partition with a ZFS
 pool on it, I cannot import it once I reboot fresh from the LiveCD,
 with 'zpool import' showing a corrupt pool. I've seen this before and
 generally it means that ZFS cannot read data or that GEOM does funny
 things. In this case, it could be that ad6 and ada0 both contain the
 same metadata, which somehow causes ZFS to go beserk.
 
 I would like to debug this issue, but for that I need to disable the
 'ada0 to ad6' symlinking functionality. I've searched for a sysctl
 variable which can disable this behavior, but have not found it.
 Anyone can enlighten me how I can disable this behavior, so that I
 only get /dev/ada0 and no ad6? If the zpool import works again after
 that change, this would confirm my suspicions that this behavior is
 causing the zpool import command to fail.
 
 I'm using FreeBSD 9.0-RC1 fetched this morning as RELENG_9, uname:
 # uname -a
 FreeBSD zfsguru.bsd 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 25 07:13:52
 UTC 2011 ssh@zfsguru:/usr/obj/usr/src/sys/GENERIC  amd64
 
 
 Relevant command output:
 
 # dmesg | grep ad
 (..)
 ada0: Previously was known as ad6
 
 # ls -l /dev/ad*
 lrwxr-xr-x  1 root  wheel4 Oct 25 13:21 /dev/ad6 - ada0
 lrwxr-xr-x  1 root  wheel6 Oct 25 13:21 /dev/ad6p1 - ada0p1
 crw-r-  1 root  operator0,  73 Oct 25 13:20 /dev/ada0
 crw-r-  1 root  operator0,  75 Oct 25 13:20 /dev/ada0p1
 
 # glabel status
  Name  Status  Components
 (..)
  gpt/testdisk N/A  ada0p1
 
 # zpool import
  pool: tank
id: 17935188179790554412
 state: FAULTED
 status: One or more devices contains corrupted data.
 action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported using
the '-f' flag.
   see: http://www.sun.com/msg/ZFS-8000-5E
 config:
 
tankFAULTED  corrupted data
  15830803292687600194  UNAVAIL  corrupted data
 
 
 Regards,
 Jason / sub.mesa


Hello Jason,

I was struck with this problem too yesterday.
I was able to import the pool by specifying the directory where zpool should 
look for devices.
Like : zpool import -d /dev/gptid
Alternatively you can try putting kern.cam.ada.legacy_aliases=0 in your 
/boot/loader.conf

Regards,
Nikolay

___
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: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Claude Buisson

On 10/25/2011 15:08, Daniel O'Connor wrote:


On 25/10/2011, at 23:24, Jeremy Chadwick wrote:

These may not be the same problem, but I think they are related (a not so well
documented change in the kerm interface).


You want atapicam(4).  This is not the same thing as options ATA_CAM.
See /sys/conf/NOTES.

Whether or not it works with audio CDs is unknown to me.


atapicam is a bridge for the old ATA code to put ATAPI devices _only_ on CAM 
(as well as the ATA infrastructure). Hence they appear as /dev/cd0 and so on.



As I said: I know it (after 16 years of FreeBSD use ...)


ATA_CAM puts _all_ ATA devices on CAM, so you should be able to access your 
audio CD that way.

I just tried and it ripped a CD fine using cdparanoia and cdcontrol seemed to 
play it OK (although I don't have the analogue output of this drive hooked up 
to the audio system).



I just played a CD with cdcontrol on a ATA_CAMed 9.0 system from Sept 25 (hooked
to the audio), but do not know what is proven that way: VLC see the tracks of
the audio CD and may even identifiy them with cddb, but cannot play them (see
the error messages). So my current conclusion (?) is that the problem lies with
the userland librairies (cdda, ..)


This is not to say that there isn't a bug in the ATA_CAM code :)



I will do another test on 9.0 (after rebuilding the ports), and eventually get
rid of ATA_CAM and wait (im)patiently for a knowledgeable one to have a look at
the problem. If this is a real problem, I may hope that it will appear after the
release of 9.0 and its use in the real world.


--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
   -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C



Claude Buisson
___
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: Problems with ada0: Previously was known as ad6 functionality

2011-10-25 Thread Jason Edwards
On Tue, Oct 25, 2011 at 4:35 PM, Nikolay Denev nde...@gmail.com wrote:
 I was struck with this problem too yesterday.
 I was able to import the pool by specifying the directory where zpool should 
 look for devices.
 Like : zpool import -d /dev/gptid
 Alternatively you can try putting kern.cam.ada.legacy_aliases=0 in your 
 /boot/loader.conf

Hello Nikolay,

Thanks for your reply!

The kern.cam.ada.legacy_aliases=0 indeed makes the /dev/ad6 device go
away. However, unlike I suspected, it did not solve the zpool import
problem. It still lists my pool as corrupted. If I use the zpool
import -d /dev/gpt as you suggested, the pool displays as ONLINE and I
can import it just fine. Using -d /dev works too, so I guess this
works fine as a workaround.

Still, can I assume this is a bug that will be fixed in time before
9.0-RELEASE ?

Regards,
Jason
___
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


getting the cpuid for a userspace process ?

2011-10-25 Thread Luigi Rizzo
as the subject says... is there any way to get the current
CPU id for a userspace process (of course,
valid only at the time the function is called as the
process might be arbitrarily moved while it runs)

thanks
luigi
___
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: The future of FreeBSD at Yahoo!

2011-10-25 Thread Julian H. Stacey
Hi,
Reference:
 From: O. Hartmann ohart...@zedat.fu-berlin.de 
 Date: Tue, 25 Oct 2011 12:48:12 +0200 
 Message-id:   4ea693ec.1070...@zedat.fu-berlin.de 

O. Hartmann wrote:
 The press in Germania is full of some statements, that Google is about 
 to overtake Yahoo!. As far as I know, Yahoo! is one of the more popular 
 and bigger, if not the biggest and last stronghold of a FreeBSD driven 
 infrastructure. Despite the fact that even Google funded lots of coding 
 for FreeBSD, I had the impression that Yahoo! might be one of the 
 biggest contributor. And not to mention the psychological effect of 
 hearing that such a company is utilizing a project like FreeBSD for 
 potential newcomers in the business.
 
 So, what is about the future of FreeBSD? Does FreeBSD have a site where 
 all the goods that has been first invented by the FreeBSD/BSD folks or 
 all the things that are thought about to come in future are 
 shown/listed? Crawling the mailing lists is a really nasty work.
 
 Thanks for having patience,

Try advoc...@freebsd.org

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Reply below, not above;  Indent with  ;  Cumulative like a play script.
 Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
___
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


LSI 9240-8i (IBM M1015) MegaRaid support

2011-10-25 Thread Roberto de Iriarte

Hi,

Is there any expectancy of getting this piece of hardware (or it's IBM 
silbing, the M1015) working in MegaRaid mode, without having to reflash 
the card to IT mode.


The reason of this request is that the UEFI Bios on the IBM XSeries 
3550M3 refuses to properly initialize the controller if reflashed with 
the IT mode firmware, thus making it unusable.


A search on LSI's website for a driver that supports 8-Stable or 9 did 
not produce any results


Many thanks and best regards,
Roberto
___
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: getting the cpuid for a userspace process ?

2011-10-25 Thread John Baldwin
On Tuesday, October 25, 2011 11:06:22 am Luigi Rizzo wrote:
 as the subject says... is there any way to get the current
 CPU id for a userspace process (of course,
 valid only at the time the function is called as the
 process might be arbitrarily moved while it runs)

Not from userland, no.  On x86 you can use cpuid to fetch the APIC ID, but 
that does not map 1:1 to FreeBSD cpu IDs.

-- 
John Baldwin
___
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: getting the cpuid for a userspace process ?

2011-10-25 Thread Poul-Henning Kamp
In message 201110251342.45194@freebsd.org, John Baldwin writes:
On Tuesday, October 25, 2011 11:06:22 am Luigi Rizzo wrote:
 as the subject says... is there any way to get the current
 CPU id for a userspace process (of course,
 valid only at the time the function is called as the
 process might be arbitrarily moved while it runs)

Not from userland, no.  On x86 you can use cpuid to fetch the APIC ID, but 
that does not map 1:1 to FreeBSD cpu IDs.

How does JEmalloc do it ?


-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
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: getting the cpuid for a userspace process ?

2011-10-25 Thread Kostik Belousov
On Tue, Oct 25, 2011 at 01:42:45PM -0400, John Baldwin wrote:
 On Tuesday, October 25, 2011 11:06:22 am Luigi Rizzo wrote:
  as the subject says... is there any way to get the current
  CPU id for a userspace process (of course,
  valid only at the time the function is called as the
  process might be arbitrarily moved while it runs)
 
 Not from userland, no.  On x86 you can use cpuid to fetch the APIC ID, but 
 that does not map 1:1 to FreeBSD cpu IDs.
Not quite so. The kern.proc sysctls do provide oncpu and lastcpu
information, which, I believe, is used by top. But this is very slow way
to get cpu id.


pgpjMU1cp088f.pgp
Description: PGP signature


gmirror failed with error 19.

2011-10-25 Thread Martin Wilke
Hi,

I face the same error since upgrade from 8.2 to 9.0RC1, is there any way to fix 
that?

thx Martin___
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: getting the cpuid for a userspace process ?

2011-10-25 Thread Dan Nelson
In the last episode (Oct 25), Poul-Henning Kamp said:
 In message 201110251342.45194@freebsd.org, John Baldwin writes:
 On Tuesday, October 25, 2011 11:06:22 am Luigi Rizzo wrote:
  as the subject says... is there any way to get the current CPU id for a
  userspace process (of course, valid only at the time the function is
  called as the process might be arbitrarily moved while it runs)
 
 Not from userland, no.  On x86 you can use cpuid to fetch the APIC ID,
 but that does not map 1:1 to FreeBSD cpu IDs.
 
 How does JEmalloc do it ?

Looking at the source, it just determines the number of CPUs, creates a
number of arenas proportional to that, and assigns threads to an arena.  If
contention on a particular arena gets bad, the thread gets moved to another
areana (see everything inside #ifdef MALLOC_BALANCE blocks).

-- 
Dan Nelson
dnel...@allantgroup.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: gmirror failed with error 19.

2011-10-25 Thread Garrett Cooper
On Tue, Oct 25, 2011 at 11:15 AM, Martin Wilke m...@freebsd.org wrote:
 Hi,

 I face the same error since upgrade from 8.2 to 9.0RC1, is there any way to 
 fix that?

errno == 19 = ENODEV -- so the question is, what device is missing?
-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


Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread Craig Rodrigues
On Tue, Oct 25, 2011 at 7:00 AM, David Wolfskill da...@catwhisker.org wrote:
 Index: sys/conf/newvers.sh
 ===
 --- sys/conf/newvers.sh (revision 226724)
 +++ sys/conf/newvers.sh (working copy)
 @@ -88,7 +88,7 @@
  i=`${MAKE:-make} -V KERN_IDENT`

  for dir in /bin /usr/bin /usr/local/bin; do
 -       if [ -d ${SYSDIR}/.svn -a -x ${dir}/svnversion ] ; then
 +       if [ ( -d ${SYSDIR}/.svn -o -d ${SYSDIR}/../.svn ) -a -x 
 ${dir}/svnversion ] ; then
                svnversion=${dir}/svnversion
                break
        fi

 then?  That should preserve current behavior for the case you  Jilles
 expressed concern about, while repairing the currently-broken default
 case.

 I believe it's in the interest of the project to have that default
 case working again (at least) in time for 9.0-RELEASE.

 Please.

 

 I'm staying out of the svnversion vs. svn info branch of the thread.

 Peace,
 david
 --
 David H. Wolfskill                              da...@catwhisker.org
 Depriving a girl or boy of an opportunity for education is evil.

 See http://www.catwhisker.org/~david/publickey.gpg for my public key.


Hi,

I know that Doug disagreed with me on this, but I think this would be
easier to implement in the short term:

for dir in /bin /usr/bin /usr/local/bin; do
   if [ -x ${dir}/svnversion -a -x ${dir}/svn  ]; then
   ${dir}/svn info ${SRCDIR}/sys  /dev/null 21
   if [ $? -eq 0 ]; then
svnversion=${dir}/svnversion
   fi
   fi
done


The alternative would be to run ${dir}/svnversion, and check the output
of that command, making sure that the output starts with a number.

-- 
Craig Rodrigues
rodr...@crodrigues.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: FreeBSD 9.0 RC1 USB Mouse and Keyboard

2011-10-25 Thread Mehmet Erol Sanliturk
On Mon, Oct 24, 2011 at 7:46 PM, Warren Block wbl...@wonkity.com wrote:

 On Sun, 23 Oct 2011, Mehmet Erol Sanliturk wrote:

  I have installed FreeBSD 9.0 RC1 .

 During installation and boots , and ( as root ) console mode , both USB
 keyboard and mouse are working .

 When a graphical desktop ( Fluxbox , Gnome , or KDE ) is started , both of
 them are becoming frozen .
 Detach and attach of mouse are detected , but input is not possible .
 PS/2 mouse is also not working .
 I did not check PS/2 keyboard .
 Only Ctrl-Alt-F1 is discontinuing graphical display , and Ctrl-C is
 returning to root prompt .

 KDE is staying as it is after displaying of hard disk symbol and then it
 is
 waiting there .
 Gnome is displaying all the parts , but no input possibility .
 Fluxbox is displaying its window , but no input possibility .

 It seems that X is NOT able to register dbus related parts ( understood
 from
 messages left on the screen after discontinuation ) .

 On the same computer , I have installed Fedora 15 and everything is
 working
 as expected , means there is no any hardware problem .


 The same symptoms happen if X is configured to use hald for input device
 detection but hald is not running.  The easy way to test that is to put
 Option AutoAddDevices Off
 in the ServerLayout section.



Also by Benjamin Kaduk :


Has this computer successfully run other versions of FreeBSD with X?
I seem to recall there can be odd interactions with hald, xorg.conf, and
others. Some googling brings up
http://www.wonkity.com/~wblock/docs/html/aei.html which seems to cover many
of the relevant issues.

-Ben Kaduk


--

After the above messages ,
on the same computer , I have installed the FreeBSD 9.0 RC1 amd64 again .

I have generated an xorg.conf file .

Into the xorg.conf  file and ServerLayout part , I have inserted

 Option AutoAddDevices  Off

The USB Mouse and Keyboard , Fluxbox  started to work as expected in the
graphical mode  under X .


Without the above statement about Option , the error message is :

(EE) config/hal : couldn't initialise context . unknown error (null)


In FreeBSD 9.0 RC1 i386 , such a step is NOT necessary .


Thank you very much .

Mehmet Erol Sanliturk
___
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: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread Doug Barton
On 10/25/2011 12:43, Craig Rodrigues wrote:

 I know that Doug disagreed with me on this,

I didn't disagree with you. I pointed out that there is absolutely no
reason to run 2 separate commands. To put it more bluntly, I pointed out
why your suggestion is a bad idea.

I'm sorry to be so blunt but I'm getting really tired of people who
can't let go of bad ideas even when it's demonstrated conclusively why
they are bad. :)

 The alternative would be to run ${dir}/svnversion, and check the output
 of that command, making sure that the output starts with a number.

The attached implements that, and is almost certainly the right way to
go. It would be nice if someone could test it, and better if someone
else could commit it. I swore after the last time that I'd stay away
from that file precisely because of all the bikeshed stupidity that this
issue creates.


Doug

-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

Index: newvers.sh
===
--- newvers.sh  (revision 226474)
+++ newvers.sh  (working copy)
@@ -88,7 +88,7 @@
 i=`${MAKE:-make} -V KERN_IDENT`
 
 for dir in /bin /usr/bin /usr/local/bin; do
-   if [ -d ${SYSDIR}/.svn -a -x ${dir}/svnversion ] ; then
+   if [ -x ${dir}/svnversion ] ; then
svnversion=${dir}/svnversion
break
fi
@@ -99,8 +99,12 @@
 done
 
 if [ -n $svnversion ] ; then
-echo $svnversion
-   svn= r`cd ${SYSDIR}  $svnversion`
+   echo $svnversion
+   svn=`cd ${SYSDIR}  $svnversion`
+   case $svn in
+   [0-9]*) svn= r${svn} ;;
+   *)  unset svn ;;
+   esac
 fi
 
 if [ -n $git_cmd ] ; then
___
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: Slow load time to /boot/loader (3rd stage loader)

2011-10-25 Thread J. Kuczewski

On 10/25/2011 08:15 AM, Vinícius Zavam wrote:

2011/10/25 J. Kuczewskijkuczew...@bnl.gov:

Hi all,

I have recently installed 9.0-RC1 on my Thinkpad X201 and have noticed
severe (~20 mins) latency to get to the third stage bootloader
(/boot/loader). This is system triple booted with Windows 7 and Arch Linux
using the GRUB 2 bootmanager. FreeBSD is not on a extended partition, if it
matters. I have tested two BIOS disk configurations, one with AHCI and the
other with IDE compatibility mode. IDE mode is comparatively faster, but
still slower than expected (~3 mins). To see if this was a regression, I
installed 8.2, and it has the same exact effect. Booting off of USB stick
loads fine (e.g. the installer). The following is my notes with the
different BIOS configurations with a link to the verbose dmesgs for each...

With AHCI enabled:
o  dmesg output:
http://dl.dropbox.com/u/45307545/dmesg_logs/dmesg_ahci.log
o  Timeline:
~05 mins - Loading /boot/default/loader.conf appears.
~16 mins - /boot/kernel/kernelargs  displayed.
~20 mins - Welcome to FreeBSD boot prompt.

With IDE compatibility enabled:
o  dmesg output:
http://dl.dropbox.com/u/45307545/dmesg_logs/dmesg_ide.log
o  Timeline:
~02 mins - Loading /boot/default/loader.conf and /boot/kernel/kernel
args  is displayed at once.
~03 mins - Welcome to FreeBSD boot prompt is displayed.

After the boot prompt, startup is normal with no slowdowns to the login
prompt.

---
Current BIOS and ECP versions (output from Linux):
---
# dmidecode -s bios-version
6QET52WW (1.22)
# dmidecode -t 11
# dmidecode 2.11
SMBIOS 2.6 present.

Handle 0x0027, DMI type 11, 5 bytes
OEM Strings
String 1: IBM ThinkPad Embedded Controller -[6QHT30WW-1.11]-

---
FreeBSD GRUB2 entry:
---
menuentry FreeBSD 9.0-RC1 {
insmod ufs2
set root=(hd0,3)
chainloader +1
}

Any guidance to determine the slow down of this loading problem would be
great.

Thank you for your time...

Cheers,
-John Kuczewski

i've got something like this. check it out:
http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/054551.html

i remembered this issue when reading your e-mail this morning.
unfortunately i couldn't fix the issue.
just saw the answer from Paulo[1] today (LOL).. but you, John, are
using the same entry with grub2.. so sadness ;-(

nowadays i'm using 10.0current with my asus 1005pe (eeepc) and
everything runs like a charm. i still have the same pavilion; maybe
one day it will run freebsd again (even if it needs 30min to boot)3

[1] http://lists.freebsd.org/pipermail/freebsd-stable/2010-March/055733.html


Thanks for the links. I have a spare disk that I'll make just for 
FreeBSD, just to see if this is a partitioning problem with the BTX 
loader, or something BIOS related. Just to note, it doesn't matter if I 
use GRUB2 or FreeBSD's boot manager, both were tested.


Thanks for the idea.

Cheers,
-John Kuczewski
___
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: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread Craig Rodrigues
On Tue, Oct 25, 2011 at 1:07 PM, Doug Barton do...@freebsd.org wrote:

 I didn't disagree with you. I pointed out that there is absolutely no
 reason to run 2 separate commands. To put it more bluntly, I pointed out
 why your suggestion is a bad idea.

Hmmm, sounds like a disagreement to me.
I have read your concerns, but I don't fully
understand why invoking svn info ${SRCDIR}/sys,
ignoring the output of svn info, and then just
checking its return status is a bad idea.
Using svnversion further down in the script
if svn info succeeds is all that I was recommending.

Anyways, I am fine with the patch which you propose.

The only possible issue could be in future,
if svn switches from using decimal revision numbers
to numbers which are in hexadecimal, base64, etc.

However, that is not currently the case, and if
it does happen in future, we can change the script
accordingly.

-- 
Craig Rodrigues
rodr...@crodrigues.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: FreeBSD 9.0 RC1 USB Mouse and Keyboard

2011-10-25 Thread Warren Block

On Tue, 25 Oct 2011, Mehmet Erol Sanliturk wrote:


Also by Benjamin Kaduk :


Has this computer successfully run other versions of FreeBSD with X?
I seem to recall there can be odd interactions with hald, xorg.conf, and 
others. Some googling brings up 
http://www.wonkity.com/~wblock/docs/html/aei.html which seems to cover many of
the relevant issues.

-Ben Kaduk


--

After the above messages , 
on the same computer , I have installed the FreeBSD 9.0 RC1 amd64 again .

I have generated an xorg.conf file .

Into the xorg.conf  file and ServerLayout part , I have inserted 

 Option AutoAddDevices  Off

The USB Mouse and Keyboard , Fluxbox  started to work as expected in the 
graphical mode  under X .


Without the above statement about Option , the error message is :

(EE) config/hal : couldn't initialise context . unknown error (null)


This line appears if x11-servers/xorg-server was built with the HAL 
option enabled.



In FreeBSD 9.0 RC1 i386 , such a step is NOT necessary .


They should be the same.  On i386, maybe xorg-server was built with the 
HAL option disabled?___
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: getting the cpuid for a userspace process ?

2011-10-25 Thread John Baldwin
On Tuesday, October 25, 2011 2:09:12 pm Poul-Henning Kamp wrote:
 In message 201110251342.45194@freebsd.org, John Baldwin writes:
 On Tuesday, October 25, 2011 11:06:22 am Luigi Rizzo wrote:
  as the subject says... is there any way to get the current
  CPU id for a userspace process (of course,
  valid only at the time the function is called as the
  process might be arbitrarily moved while it runs)
 
 Not from userland, no.  On x86 you can use cpuid to fetch the APIC ID, but 
 that does not map 1:1 to FreeBSD cpu IDs.
 
 How does JEmalloc do it ?

I don't think it does on FreeBSD.  The only thing malloc() knows on FreeBSD is
the total number of CPUs.  I believe Linux has a system call that returns this
though (sched_getcpu() is the public interface which is a wrapper around a
getcpu() system call).  From the manpage it would seem that sched_getcpu() 
uses a per-thread shared page of some sort so that it doesn't actually have to 
enter the kernel to get the CPU ID.  Alternatively, you could imagine it on 
x86 at least exporting a table mapping APIC IDs to CPU IDs and then using 
cpuid and that table to do the lookup purely in userland.  That would only 
necessitate a global shared page and not one per-thread.  You could still fall 
back to a system call for other architectures that simply returned 
curthread-td_oncpu.

-- 
John Baldwin
___
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: Fresh installed Freebsd 9 don't boot from hd

2011-10-25 Thread John Baldwin
On Monday, October 24, 2011 7:21:27 pm Gunnar Schaefer wrote:
 On Oct 24, 2011, at 2:40 PM, Dennis Koegel wrote:
 
  On Mon, Oct 24, 2011 at 11:33:23AM -0400, John Baldwin wrote:
  Perhaps try http://www.freebsd.org/~jhb/patches/edd_params.patch
  
  GCC chokes here in drv.c:{49,50}: cannot convert to a pointer type:
  
 v86.ds = VTOPSEG(params);
 v86.esi = VTOPOFF(params);
  
  Changed this to params. Also changed sector_size to uint16_t as noted
  by Andriy. Boots perfectly! (Tested with gcc and clang)
 
 I'd like to test these patches on my Supermicro machine as well. 
Unfortunately, I don't know how to go about it, but I'm hopeful to be able to 
figure it out with some basic instructions. I'm currently running a fresh RC1 
install, and I'm able to boot the system if I set the BIOS to IDE mode, rather 
than AHCI.
 
 Any help would be much appreciated,

I just committed them to HEAD (226748 along with a cleanup in 226746).  They
should backport to 9.

-- 
John Baldwin
___
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: FreeBSD 9.0 RC1 USB Mouse and Keyboard

2011-10-25 Thread Mehmet Erol Sanliturk
On Tue, Oct 25, 2011 at 4:41 PM, Warren Block wbl...@wonkity.com wrote:

 On Tue, 25 Oct 2011, Mehmet Erol Sanliturk wrote:

  Also by Benjamin Kaduk :


 Has this computer successfully run other versions of FreeBSD with X?
 I seem to recall there can be odd interactions with hald, xorg.conf, and
 others. Some googling brings up
 http://www.wonkity.com/~wblock/docs/html/aei.html which seems to cover
 many of
 the relevant issues.

 -Ben Kaduk


 --

 After the above messages ,
 on the same computer , I have installed the FreeBSD 9.0 RC1 amd64 again .

 I have generated an xorg.conf file .

 Into the xorg.conf  file and ServerLayout part , I have inserted

  Option AutoAddDevices  Off

 The USB Mouse and Keyboard , Fluxbox  started to work as expected in the
 graphical mode  under X .


 Without the above statement about Option , the error message is :

 (EE) config/hal : couldn't initialise context . unknown error (null)


 This line appears if x11-servers/xorg-server was built with the HAL option
 enabled.

  In FreeBSD 9.0 RC1 i386 , such a step is NOT necessary .


 They should be the same.  On i386, maybe xorg-server was built with the HAL
 option disabled?



I do not know because I am using downloaded .iso files as they are supplied
in mirrors without any modification .

Thank you very much .


Mehmet Erol Sanliturk
___
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: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread Doug Barton
On 10/25/2011 13:23, Craig Rodrigues wrote:
 On Tue, Oct 25, 2011 at 1:07 PM, Doug Barton do...@freebsd.org wrote:

 I didn't disagree with you. I pointed out that there is absolutely no
 reason to run 2 separate commands. To put it more bluntly, I pointed out
 why your suggestion is a bad idea.
 
 Hmmm, sounds like a disagreement to me.

Disagreement implies that you and I both have equally valid ideas, and
that we cannot agree on which one to use.

 I have read your concerns, but I don't fully
 understand why invoking svn info ${SRCDIR}/sys,
 ignoring the output of svn info, and then just
 checking its return status is a bad idea.

As I tried to explain previously, running one command, testing the
outcome, and then running another command if the first succeeded is a
bad idea if you can simply run the command you need to run in the first
place and parse *its* output. Obviously running 'svn info' first isn't
overwhelmingly expensive, so this isn't the most horrible idea ever
suggested for FreeBSD. However as a general principle we should be
trying to do the best we can, not only for its own sake, but as an
example to those who read and copy the code.

BTW, the rest of my analysis in my previous post is relevant here too.
If a bare 'svnversion' took a long time to return in a non-svn directory
then obviously we'd have to give your solution a better look. However,
given that it returns nearly instantaneously, there's no point.

 Using svnversion further down in the script
 if svn info succeeds is all that I was recommending.

Yes, I understood what you were suggesting. :)

 Anyways, I am fine with the patch which you propose.

Awesome!

 The only possible issue could be in future,
 if svn switches from using decimal revision numbers
 to numbers which are in hexadecimal, base64, etc.
 
 However, that is not currently the case, and if
 it does happen in future, we can change the script
 accordingly.

Actually hex would still work since 0x would match. :)

In any case I just tested the svn case, and it worked. If someone else
could test the non-svn case then we can get this fixed and move on.


Doug

-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.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: FreeBSD 9.0 RC1 USB Mouse and Keyboard

2011-10-25 Thread Garrett Cooper
On Tue, Oct 25, 2011 at 1:52 PM, Mehmet Erol Sanliturk
m.e.sanlit...@gmail.com wrote:
 On Tue, Oct 25, 2011 at 4:41 PM, Warren Block wbl...@wonkity.com wrote:

 On Tue, 25 Oct 2011, Mehmet Erol Sanliturk wrote:

  Also by Benjamin Kaduk :


 Has this computer successfully run other versions of FreeBSD with X?
 I seem to recall there can be odd interactions with hald, xorg.conf, and
 others. Some googling brings up
 http://www.wonkity.com/~wblock/docs/html/aei.html which seems to cover
 many of
 the relevant issues.

 -Ben Kaduk


 --

 After the above messages ,
 on the same computer , I have installed the FreeBSD 9.0 RC1 amd64 again .

 I have generated an xorg.conf file .

 Into the xorg.conf  file and ServerLayout part , I have inserted

  Option AutoAddDevices  Off

 The USB Mouse and Keyboard , Fluxbox  started to work as expected in the
 graphical mode  under X .


 Without the above statement about Option , the error message is :

 (EE) config/hal : couldn't initialise context . unknown error (null)


 This line appears if x11-servers/xorg-server was built with the HAL option
 enabled.

  In FreeBSD 9.0 RC1 i386 , such a step is NOT necessary .


 They should be the same.  On i386, maybe xorg-server was built with the HAL
 option disabled?



 I do not know because I am using downloaded .iso files as they are supplied
 in mirrors without any modification .

The default is WITH_HAL:

OPTIONS+=   HAL Compile with HAL config support on

Why WITHOUT_HAL would be defined with i386 and not amd64, I have no
idea, but if the build environments are consistently then it should be
on for both.
Thanks,
-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


Re: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread Craig Rodrigues
On Tue, Oct 25, 2011 at 1:54 PM, Doug Barton
 Actually hex would still work since 0x would match. :)

Yes, but if in the future, a revision number format is ever chosen
that doesn't include
0x at the beginning, and is something like:
a23728ea7d592acc69b36875a482cdf3fd5c8d

then this check would fail.  However, none of this
exists yet in SVN, so it is not worth worry about
right now.

It would have been nice if svnversion had
a different return status in non-SVN directories.
Checking svnversion output is fine, but
it looks like a lot of things are changing around
in SVN-land, including the output of commands.

-- 
Craig Rodrigues
rodr...@crodrigues.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: sys/conf/newvers.sh vs. subversion-1.7

2011-10-25 Thread Doug Barton
On 10/25/2011 14:45, Craig Rodrigues wrote:
 On Tue, Oct 25, 2011 at 1:54 PM, Doug Barton
 Actually hex would still work since 0x would match. :)
 
 Yes, but if in the future, a revision number format is ever chosen
 that doesn't include
 0x at the beginning, and is something like:
 a23728ea7d592acc69b36875a482cdf3fd5c8d
 
 then this check would fail.  However, none of this
 exists yet in SVN, so it is not worth worry about
 right now.

Yes, that was what the smiley at the end of my sentence above was
intending to convey. Sorry I wasn't more clear. :)


Doug

-- 

Nothin' ever doesn't change, but nothin' changes much.
-- OK Go

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.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: Panics after AHCI timeouts

2011-10-25 Thread Alexander Kabaev
On Tue, 18 Oct 2011 14:28:07 +0100
Steven Hartland kill...@multiplay.co.uk wrote:

 
 - Original Message - 
 From: Alexey Shuvaev shuv...@physik.uni-wuerzburg.de
 To: freebsd-current@freebsd.org
 Sent: Tuesday, October 18, 2011 2:13 PM
 Subject: Re: Panics after AHCI timeouts
 
 
  On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote:
  Done, kern/161768.
  
  Question to the list: does anybody see successful recovery from AHCI
  timeout an a recent CURRENT? Recent means June 2011 or newer, so 9.0
  branch counts also. That is, there are some kernel messages like
  this:
  
  ahcich0: Timeout on slot 29 port 0
  ahcich0: is  cs  ss  rs  tfd 40
  serr  cmd fc17
  
  but then AHCI recovers and the system does not panic?
 
 Not a recent CURRENT but on 8.2-RELEASE we have seen recovery on
 secondary ssd drives without a panic, but it does generally
 drop the disk and need a power off, power on to recover the
 disk properly; although we believe that's a firmware bug on
 the ssds
 
 Regards
 Steve
 
I do see timeouts on one of my Samsung ST3750330A disks and they
definitely do not cause any panics. The weird part in my case is that
disk then immediately reappears as online and mirror zpool can be
rebuilt by just onlining the disk with 'zpool online pool disk'
command.

It seems to be happening once system has accumulated some uptime. If
rebooted, it keeps running for a week or two with no issues, but then
timeouts start to happen more or less reliably every single 24 hours.
 
-- 
Alexander Kabaev


signature.asc
Description: PGP signature


Re: can audio CDs be played with ATA_CAM ?

2011-10-25 Thread Craig Rodrigues
On Tue, Oct 25, 2011 at 3:15 AM, Claude Buisson clbuis...@orange.fr wrote:
 Hi,

 When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to
 ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to
 atapicam (and reverting from cdN to acdN of course), vlc was OK again.

Hi,

Would vlc have worked if, while ATA_CAM was enabled,
there was a symlink so that /dev/acd0 - cd0 ?
-- 
Craig Rodrigues
rodr...@crodrigues.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: LSI 9240-8i (IBM M1015) MegaRaid support

2011-10-25 Thread Roberto de Iriarte

I have to rectify myself

It is possible to install FreeBSD 9-Beta3 amd64 (9-RC1 boots correctly 
as well, i will upgrade in a couple of hours) on the X3550 M3 with a 
reflashed M1015 SAS controller, using the mps driver


It is only extremely tiresome (and not because of FreeBSD!)

I will document the procedure asap, as i've seen in the forums that 
others have had problems with this machine.


Best regards
Roberto

P.S. Many thanks to Scott Long for the mps driver!

Hi,

Is there any expectancy of getting this piece of hardware (or it's IBM 
silbing, the M1015) working in MegaRaid mode, without having to 
reflash the card to IT mode.


The reason of this request is that the UEFI Bios on the IBM XSeries 
3550M3 refuses to properly initialize the controller if reflashed with 
the IT mode firmware, thus making it unusable.


A search on LSI's website for a driver that supports 8-Stable or 9 did 
not produce any results


Many thanks and best regards,
Roberto
___
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