Re: Dell latitude 7490 touchpad support?

2018-10-12 Thread Anton Shterenlikht
On Thu, Oct 11, 2018 at 08:20:13PM -0400, Hyun Hwang wrote: > On Saturday, September 29, 2018, 8:48 PM (UTC+0100), Johannes Lundberg > wrote: > > Hi > > > > I just got a new work laptop and the touchpad does not work. Some > > information points to that this machine has a Microsoft precision

Re: cannot get touchpad mouse, no psm device, on Dell Precision 3520

2018-06-07 Thread Anton Shterenlikht
On Thu, Jun 07, 2018 at 01:34:31PM -0700, Pete Wright wrote: > > > On 06/07/2018 13:21, Anton Shterenlikht wrote: > > Please help get touchpad mouse on > > Dell Precision 3520. > > The usb mouse works fine. > > > pciconf isn't really applicable h

cannot get touchpad mouse, no psm device, on Dell Precision 3520

2018-06-07 Thread Anton Shterenlikht
Please help get touchpad mouse on Dell Precision 3520. The usb mouse works fine. z> pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x07a91028 chip=0x19108086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host

intel graphics regression? between r332432 and r333982

2018-06-05 Thread Anton Shterenlikht
I'm looking for help to make graphics work on Dell Precision 3520. This did work in r332432: http://freebsd.1045724.x6.nabble.com/Dell-Precision-3520-laptop-help-with-dual-graphics-card-td6249818.html I now updated to: # uname -a FreeBSD z.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r333982: Thu

Re: webcamd panic - is it just me?

2016-12-07 Thread Anton Shterenlikht
>From s...@freebsd.org Wed Dec 7 03:31:16 2016 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215000 >> >> I think this started after moving from 10.3 to 11.0. >> >> Does nobody else see this panic? > >I do not see that panic, however, I do suspect it is the specific cuse >module you are

Thank you for iwm(4)!

2016-06-02 Thread Anton Shterenlikht
Found out only today that Intel Wireless 7260 is supported in -current. Rui, Adrian, (and others?) - many thanks for this. Anton ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe,

Re: em(4) regression between r289975 and r300212

2016-05-23 Thread Anton Shterenlikht
>From benjamin.vill...@gmail.com Mon May 23 10:22:53 2016 > >Hi Anton, > >I have the same behavior on my workstation. I just applied K. Macy's patch >and it seems to work for now. Looks like it's been committed already: r300372 | avg | 2016-05-21 15:51:49 +0100 (Sat, 21 May 2016) | 5 lines

em(4) regression between r289975 and r300212

2016-05-23 Thread Anton Shterenlikht
This is an amd64 laptop, Dell Latitude 3340. I updated from: 11.0-CURRENT #1 r298975: Tue May 3 15:18:03 BST 2016 /usr/obj/usr/src/sys/GENERIC amd64 to: 11.0-CURRENT #2 r300212: Fri May 20 09:50:53 BST 2016 /usr/obj/usr/src/sys/GENERIC amd64 Now em(4) stops working 2-5 min after boot, or,

Re: WIFI urtwn possibly broken on 297561

2016-04-11 Thread Anton Shterenlikht
> >Hi! > >this is because we don't have A-MPDU RX aging on by default. So, if >there are holes in the sequence number space, FreeBSD's reordering >logic doesn't flush frames up until it's received /all/ the traffic. > >I've just enabled it by default in -HEAD now. That should fix it. >Otacilio,

urtwn regression(?) from 10.2 to current r291431

2015-12-06 Thread Anton Shterenlikht
I posted this about a week ago: http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html The problem is that urtwn stopped working in current r291431. I did more testing with the same revision, and sometimes it would work, but extremely slowly, and sometimes seemingly

Re: urtwn regression(?) from 10.2 to current r291431

2015-12-06 Thread Anton Shterenlikht
>From h...@selasky.org Sun Dec 6 14:41:27 2015 > >On 12/06/15 15:14, Anton Shterenlikht wrote: >> I posted this about a week ago: >> >> http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html >> >> The problem is that urtwn stopped >

seems to be solved in r291907: WAS: Re: urtwn regression(?) from 10.2 to current r291431

2015-12-06 Thread Anton Shterenlikht
e.3090...@selasky.org> > >>From h...@selasky.org Sun Dec 6 14:41:27 2015 >> >>On 12/06/15 15:14, Anton Shterenlikht wrote: >>> I posted this about a week ago: >>> >>> http://lists.freebsd.org/pipermail/freebsd-current/2015-November/058683.html

r291431 urtwn usb errors, cannot allocate device

2015-11-29 Thread Anton Shterenlikht
Updated to r291431 from about a month ago. USB wireless stopped working: ugen0.2: at usbus0 urtwn0: on usbus0 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R ugen1.2: at usbus1 uhub2: on usbus1 uhub2: 8 ports with 8 removable, self powered ugen1.3: at usbus1 wlan0: Ethernet address:

Re: Depreciate and remove gbde

2015-10-20 Thread Anton Shterenlikht
>GBDE is for when the user is in danger. In danger of what? Please elaborate. >From the handbook, it is not clear at all that the two encryption methods are designed to defend against different threats. Maybe I'm using the wrong one... Thank you Anton

Re: Depreciate and remove gbde

2015-10-20 Thread Anton Shterenlikht
>From p...@phk.freebsd.dk Tue Oct 20 10:08:55 2015 > >>Am I correct that the papers are from 2003 and 2004 >>respectively. Has much changed in gbde since then? > >Nope. One thing that puzzled me about the way gbde is integrated with the FreeBSD boot sequence is that it's not possible to boot

Re: Depreciate and remove gbde

2015-10-20 Thread Anton Shterenlikht
>> In message <201510200645.t9k6jaam004...@mech-as222.men.bris.ac.uk>, Anton >> Shterenlikht writes: >>>> GBDE is for when the user is in danger. >>> >>> In danger of what? >>> Please elaborate. >> >> Read the paper: >>

Re: Depreciate and remove gbde

2015-10-19 Thread Anton Shterenlikht
I use gbde. Can switch to geli, if required, but please provide detailed instructions for switching before removing gbde. Anton ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: urtwn: ioctl[SIOCS80211, op=16, arg_len=0]: Invalid argument

2015-08-18 Thread Anton Shterenlikht
From ke...@ns.kevlo.org Tue Aug 18 10:30:41 2015 Shouldn't it be urtwn-rtl8188eufw_load=YES? Nope. Your device is RTL8188CU not RTL8188EU. Thank you, now works fine. Anton ___ freebsd-current@freebsd.org mailing list

Re: urtwn: ioctl[SIOCS80211, op=16, arg_len=0]: Invalid argument

2015-08-18 Thread Anton Shterenlikht
From ke...@ns.kevlo.org Tue Aug 18 09:59:59 2015 A urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R You need to create a wlan(4) interface and run wpa_supplicant on it. ok, my bad, sorry. You also have to run kldload urtwn-rtl8192cfwT or add this to /boot/loader.conf: urtwn-rtl8192cfwT_load=YES

urtwn: ioctl[SIOCS80211, op=16, arg_len=0]: Invalid argument

2015-08-18 Thread Anton Shterenlikht
I'm trying to setup Asus USB-N10 nano wireless adapter. I get: urtwn0: vendor 0x0b05 product 0x17ba, class 0/0, rev 2.00/2.00, addr 1 on usbus0 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R urtwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 1c:87:2c:c7:c2:6e nd6

old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Anton Shterenlikht
This bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167105 is a show stopper for me. The path/name length is beyond my control, so I cannot make it shorter. This discussion seems inconclusive: http://lists.freebsd.org/pipermail/freebsd-hackers/2012-April/038543.html Is there no easy

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Anton Shterenlikht
From rmack...@uoguelph.ca Mon Jan 19 15:37:25 2015 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167105 is a show stopper for me. The path/name length is beyond my control, so I cannot make it shorter. This discussion seems inconclusive:

isp(4) Qlogic ISP 2422 PCI-X on amd64 or sparc64?

2014-06-02 Thread Anton Shterenlikht
I've a storage array accessed with an isp(4) device from ia64/FreeBSD box. I'm looking for a better supported alternative to ia64, e.g. amd64 or sparc64 to house this isp(4) device: isp0@pci0:192:1:0: class=0x0c0400 card=0x12d6103c chip=0x24221077 rev=0x02 hdr=0x00 vendor = 'QLogic

Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-28 Thread Anton Shterenlikht
I'm not sure it's the same issue. I use neither vmimage nor pf. Also, as I mentioned in http://lists.freebsd.org/pipermail/freebsd-current/2014-March/048939.html r258000, from 11 Nov 2013, works fine. I haven't received any hint as to what might have caused this panic between 258000 and 260689.

r262690 ia64: fatal kernel trap: Page Not Present: comm = automoc4

2014-03-21 Thread Anton Shterenlikht
Got the same trap twice in a row. Both times triggered by building one of these moc related ports in poudriere: 02 www/webkit-qt4 configure 03 www/webkit-gtk2 build 04 sysutils/qzeitgeist build 01 www/webkit-qt4 configure 02 www/webkit-gtk2 configure 03

Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-18 Thread Anton Shterenlikht
I've spent a lot of time on this. At some point I started suspecting disk failures, based on dd errors and smartmontools reports. So I replaced the disks, and then replaced the whole box for another nominally identical SunBlade 1500. The panics persisted. I now think that multiple cold reboots

r263096 sparc64: casperd: Unable to receive message from client: Cannot allocate memory.

2014-03-13 Thread Anton Shterenlikht
FreeBSD 11.0-CURRENT #1 r263096 Is casperd started by default? I haven't enabled it in /etc/rc.conf I think I get this error when trying to use ping, e.g.: # ping localhost Broken pipe # ping freebsd.org Broken pipe # Mar 13 12:08:48 casperd[1313]: [ERROR] (casperd) Unable to receive message

Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-12 Thread Anton Shterenlikht
From b...@0x20.net Thu Mar 6 22:02:56 2014 On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote: In my initial PR (sparc64 r261798), http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 I said that rsync was triggering this panic. While true, I now see that there's more

reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-06 Thread Anton Shterenlikht
In my initial PR (sparc64 r261798), http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 I said that rsync was triggering this panic. While true, I now see that there's more to it. I disabled the rsync, and the cron jobs. Still I get exactly the same panic every night at 03:02: # grep Dumptime

Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-06 Thread Anton Shterenlikht
From: Mark Felder f...@freebsd.org On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote: In my initial PR (sparc64 r261798), http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 I said that rsync was triggering this panic. While true, I now see that there's more to it. I disabled

Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-06 Thread Anton Shterenlikht
From g...@freebsd.org Thu Mar 6 15:58:51 2014 On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: Can you go into /etc/periodic/daily and execute those scripts one by one? You should be able to narrow down which one is the culprit. =20 unfortunately I cannot reproduce

Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help

2014-03-06 Thread Anton Shterenlikht
From b...@0x20.net Thu Mar 6 22:02:56 2014 On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote: In my initial PR (sparc64 r261798), http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 I said that rsync was triggering this panic. While true, I now see that there's more

close my resolved and obsolete PR

2014-03-04 Thread Anton Shterenlikht
Please close this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/158542 I can no longer reproduce the problem. Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe,

Re: ia64 r260914 GENERIC kernel: /usr/src/sys/dev/vt/vt_core.c:261: undefined reference to kbd_get_keyboard and so on

2014-03-02 Thread Anton Shterenlikht
From j...@freebsd.org Fri Feb 28 20:57:59 2014 On Friday, February 28, 2014 9:23:28 am Anton Shterenlikht wrote: ia64 r260914 GENERIC kernel contains: device kbdmux # keyboard multiplexer device vt # Virtual terminals device vt_vga

ia64 r260914 GENERIC kernel: /usr/src/sys/dev/vt/vt_core.c:261: undefined reference to kbd_get_keyboard and so on

2014-02-28 Thread Anton Shterenlikht
ia64 r260914 GENERIC kernel contains: device kbdmux # keyboard multiplexer device vt # Virtual terminals device vt_vga # VGA terminal device Trying to build it, I get: linking kernel.debug vt_core.o: In function `vt_window_switch':

Re: kern/187080: panic: sparc64 r261798: Panic String: vm_page_alloc: page 0xfffff8003feea008 is wired

2014-02-26 Thread Anton Shterenlikht
Not sure if this is sparc64 or a kernel issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

option PROCDESC is gone?

2014-02-07 Thread Anton Shterenlikht
/usr/src/UPDATING: 20130905: The PROCDESC kernel option is now part of the GENERIC kernel configuration and is required for the rwhod(8) to work. If you are using custom kernel configuration, you should include 'options PROCDESC'. There is no later entry advising

svn0.eu.freebsd.org timed out - temporary problems?

2014-02-06 Thread Anton Shterenlikht
Something wrong with the svn0.eu.freebsd.org mirror: svn: E60: Unable to connect to a repository at URL 'https://svn0.eu.freebsd.org/base/head' svn: E60: Error running context: Operation timed out I hope it's temprorary problem, but please advise if the mirror address has changed.

Re: svn0.eu.freebsd.org timed out - temporary problems?

2014-02-06 Thread Anton Shterenlikht
From g...@freebsd.org Thu Feb 6 15:34:12 2014 On Thu, Feb 06, 2014 at 01:07:50AM -0800, Anton Shterenlikht wrote: Something wrong with the svn0.eu.freebsd.org mirror: =20 svn: E60: Unable to connect to a repository at URL 'https://svn0.eu.f= reebsd.org/base/head' svn: E60: Error

Re: ata0: FAILURE - zero length DMA transfer attempted

2013-12-29 Thread Anton Shterenlikht
From s...@freebsd.org Sun Dec 29 09:11:31 2013 Am 28.12.2013 22:01, schrieb Anton Shterenlikht: Hello I updated to r257910 amd64. I now get lots of: ata0: FAILURE - zero length DMA transfer attempted ata0: setting up DMA failed Please advise Hi Anton, this is generally caused

ata0: FAILURE - zero length DMA transfer attempted

2013-12-28 Thread Anton Shterenlikht
Hello I updated to r257910 amd64. I now get lots of: ata0: FAILURE - zero length DMA transfer attempted ata0: setting up DMA failed Please advise Below are dmesg.boot and pciconf -lv Many thanks Anton *** Rebooting... cpu_reset: Stopping other CPUs

ia64 r255488: spontaneous reboots, no panic, no trace in logs

2013-11-02 Thread Anton Shterenlikht
On r255488 ia64 I get spontaneous reboots, which are more or less reproducible. These are triggered by nginx serving poudriere built packages. The is no panic, and no traces in the logs. The system just reboots. A similar issue was seen in about 2011, when we tried to build is64 packages on

Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks

2013-10-24 Thread Anton Shterenlikht
From j...@freebsd.org Wed Oct 23 21:10:30 2013 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 Hmm, unfortunately it seems like all the stack traces did not work. There are lots of threads blocked on VM-related locks, and CPU 0 is running vm_daemon. Probably would need a stack

ia64 r255488: panic: uma_zfree: Freeing to non free bucket index. - textdump provided

2013-10-23 Thread Anton Shterenlikht
After updating to r256624, the system is very unresponsive, and really unusable - any command (ps, df, top, ls, etc.) might take up to 1 min to return. However, I could not get it to panic. So I reverted back to r255488. This time I managed to obtain a textdump:

Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks

2013-10-23 Thread Anton Shterenlikht
This time alllocks has lots of info. I updated the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: ia64 r255488: panic: uma_zfree: Freeing to non free bucket index. - textdump provided

2013-10-23 Thread Anton Shterenlikht
From adrian.ch...@gmail.com Wed Oct 23 14:22:00 2013 On 23 October 2013 02:18, Anton Shterenlikht me...@bris.ac.uk wrote: After updating to r256624, the system is very unresponsive, and really unusable - any command (ps, df, top, ls, etc.) might take up to 1 min to return. However, I could

Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks

2013-10-23 Thread Anton Shterenlikht
From j...@freebsd.org Wed Oct 23 16:54:12 2013 On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote: This time alllocks has lots of info. I updated the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 Hmm, unfortunately it seems like all the stack traces did not work

ia64 r256624: Syncing disks... Giving up on 2 buffers

2013-10-21 Thread Anton Shterenlikht
Issuing reboot: Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1: buf:0xa0009e10e200, vnode:0, flags:0, blkno:0, lblkno:0, buflock:lock type bufwait: EXCL by thread 0xe00012741680 (pid

Re: panic: wrong page state m 0xe00000027a9adb40 + savecore deadlock

2013-10-16 Thread Anton Shterenlikht
panic: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/182999 deadlock: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: panic: wrong page state m 0xe00000027a9adb40 + savecore deadlock

2013-10-16 Thread Anton Shterenlikht
From kostik...@gmail.com Wed Oct 16 13:02:51 2013 On Wed, Oct 16, 2013 at 02:55:26PM +0300, Konstantin Belousov wrote: On Wed, Oct 16, 2013 at 09:02:19AM +0100, Anton Shterenlikht wrote: panic: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/182999 =20 db show pginfo 0xe0027d352600

Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

2013-10-15 Thread Anton Shterenlikht
From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013 If you're not able to get a full dump, a textdump would be enough. In your DDB scripts just remove the 'call doadump' step and you should be done, unless I'm missing something. Please adjust the script as well to include all the informations

panic: wrong page state m 0xe00000027a9adb40 + savecore deadlock

2013-10-15 Thread Anton Shterenlikht
From davide.itali...@gmail.com Mon Oct 14 12:50:44 2013 This is fair enough -- If you're still at the ddb prompt, please print the whole panic message (or at least the address of the lock reported as deadlocked by DEADLKRES), so that we can at least have a candidate. Here's another one,

Re: panic: wrong page state m 0xe00000027a9adb40 + savecore deadlock

2013-10-15 Thread Anton Shterenlikht
From davide.itali...@gmail.com Tue Oct 15 11:30:07 2013 On Tue, Oct 15, 2013 at 10:43 AM, Anton Shterenlikht me...@bris.ac.uk wrote: Anyway, savecore eventually deadlocks: panic: deadlkres: possible deadlock detected for 0xe000127b7b00, blocked for 901401 ticks [trim] Tracing

WITNESS: unable to allocate a new witness object

2013-10-15 Thread Anton Shterenlikht
I'm trying to set up textdump(4). On boot I see: WITNESS: unable to allocate a new witness object also Expensive timeout(9) function: 0x9ffc00e222e0(0xa09ed320) 0.002434387 s kickstart. Does the first indicate I haven't set up WITNESS correctly? What does the second tell me?

Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

2013-10-14 Thread Anton Shterenlikht
From davide.itali...@gmail.com Fri Oct 11 15:39:49 2013 If you're not able to get a full dump, a textdump would be enough. In your DDB scripts just remove the 'call doadump' step and you should be done, unless I'm missing something. Please adjust the script as well to include all the informations

panic: uma_zfree: Freeing to non free bucket index.

2013-10-14 Thread Anton Shterenlikht
BTW, I see in dmesg: Starting ddb. ddb: sysctl: debug.ddb.scripting.scripts: Invalid argument /etc/rc: WARNING: failed to start ddb What is that about? panic: uma_zfree: Freeing to non free bucket index. cpuid = 0 KDB: stack backtrace: db_trace_self(0x9ffc00158380) at db_trace_self+0x40

Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

2013-10-11 Thread Anton Shterenlikht
From davide.itali...@gmail.com Thu Sep 26 13:12:30 2013 On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht me...@bris.ac.uk wrote: Regarding textdump(4), I'm not clear where the following scripts should be located and used: [snip] Are these ddb(8) commands? Or do I set these in /etc

Re: poudriere jail building error: make[4]: /pdr/jails/ia64/usr/src/etc/periodic/daily/Makefile line 27: Malformed conditional (${MK_BIND_NAMED} != no)

2013-10-02 Thread Anton Shterenlikht
I asked in ports@ and was told this is a current@ issue. Please help. Anton Date: Tue, 1 Oct 2013 16:37:26 -0500 From: Bryan Drewery br...@shatow.net To: Anton Shterenlikht me...@bris.ac.uk Subject: Re: poudriere jail building error: make[4]: /pdr/jails/ia64/usr/src/etc/periodic/daily/Makefile

Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

2013-09-26 Thread Anton Shterenlikht
From davide.itali...@gmail.com Wed Sep 25 19:00:09 2013 On Wed, Sep 25, 2013 at 5:30 PM, Anton Shterenlikht me...@bris.ac.uk wrote: From davide.itali...@gmail.com Wed Sep 25 16:12:47 2013 Can you please paste the output of 'show locks', 'show alllocks', 'show lockedvnods' at least? Ideally you

panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

2013-09-25 Thread Anton Shterenlikht
FreeBSD mech-as221.men.bris.ac.uk 10.0-ALPHA2 FreeBSD 10.0-ALPHA2 #8 r255811: Tue Sep 24 09:04:17 BST 2013 r...@mech-as221.men.bris.ac.uk:/usr/obj/usr/src/sys/UZI ia64 panic: deadlkres: possible deadlock detected for 0xe00012d07b00, blocked for 902743 ticks cpuid = 1 KDB: stack

Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks

2013-09-25 Thread Anton Shterenlikht
From davide.itali...@gmail.com Wed Sep 25 16:12:47 2013 Can you please paste the output of 'show locks', 'show alllocks', 'show lockedvnods' at least? Ideally you should provide all the informations listed here. http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html

panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe0000000129b4d80, blocked for 901858 ticks

2013-09-25 Thread Anton Shterenlikht
This panic was triggered by svn up, while portmaster updates were going on: FreeBSD mech-as221.men.bris.ac.uk 10.0-ALPHA2 FreeBSD 10.0-ALPHA2 #8 r255811: Tue Sep 24 09:04:17 BST 2013 r...@mech-as221.men.bris.ac.uk:/usr/obj/usr/src/sys/UZI ia64 - - - - - - - - - - Prior Console Output - -

ia64 r255472: /usr/src/sys/kern/uipc_syscalls.c:2196: warning: obj_size may be used uninitialized in this function

2013-09-12 Thread Anton Shterenlikht
ia64 r255472 buildkernel gives this error: cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option

Re: GCC withdraw

2013-08-30 Thread Anton Shterenlikht
Subject: Re: GCC withdraw From: Warner Losh i...@bsdimp.com Date: Thu, 29 Aug 2013 10:00:19 -0600 Gcc is still an absolute requirement on all non-x86 platforms (including arm) due to the issues with clang. Some of these issues are bugs in specific things (arm) that keep coming up (and keep

Re: svn error during 'make buildkernel'?

2013-08-03 Thread Anton Shterenlikht
Delivered-To: freebsd-current@freebsd.org Date: Sat, 3 Aug 2013 15:17:02 -0700 From: Steve Kargl s...@troutmask.apl.washington.edu To: Glen Barber g...@freebsd.org Subject: Re: svn error during 'make buildkernel'? svn repository. The change to use svnlite in newvers.sh should have an entry in

ia64 r252055: panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ /usr/src/sys/ia64/ia64/trap.c:562

2013-08-02 Thread Anton Shterenlikht
This happened when exiting from cssh session: panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ /usr/src/ sys/ia64/ia64/trap.c:562 cpuid = 1 KDB: enter: panic [ thread pid 52881 tid 100409 ] Stopped at kdb_enter+0x92: [I2]addl r14=0xffe29320,gp ;; db show

https://svn0.us-east.freebsd.org/base/head is not on 1.8 yet?

2013-06-20 Thread Anton Shterenlikht
svn --version svn, version 1.8.0 (r1490375) compiled Jun 20 2013, 09:21:02 on amd64-portbld-freebsd10.0 # svn up Updating '.': svn: E17: Unrecognized URL scheme for 'https://svn0.us-east.freebsd.org/base/head' Anton ___

Re: https://svn0.us-east.freebsd.org/base/head is not on 1.8 yet?

2013-06-20 Thread Anton Shterenlikht
On 06/20/13 10:32, Anton Shterenlikht wrote: svn --version svn, version 1.8.0 (r1490375) compiled Jun 20 2013, 09:21:02 on amd64-portbld-freebsd10.0 # svn up Updating '.': svn: E17: Unrecognized URL scheme

Re: Cannot startx on FreeBSD10 Current

2013-06-16 Thread Anton Shterenlikht
From: Walter Hurry walterhu...@gmail.com Subject: Re: Cannot startx on FreeBSD10 Current Date: Fri, 14 Jun 2013 20:50:59 + (UTC) On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote: On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry

Re: Cannot startx on FreeBSD10 Current

2013-06-16 Thread Anton Shterenlikht
From: Walter Hurry walterhu...@gmail.com Subject: Re: Cannot startx on FreeBSD10 Current Date: Sun, 16 Jun 2013 17:53:53 + (UTC) On Sun, 16 Jun 2013 11:27:36 +0100, Anton Shterenlikht wrote: From: Walter Hurry walterhu...@gmail.com

graphics cards do not work: sparc64/machbf r251648, amd64/nvidia r249781

2013-06-14 Thread Anton Shterenlikht
In addition to what I wrote already for sparc64, I now get this failure on amd64 r249781: (EE) Jun 14 18:17:27 NVIDIA(0): Failed to initialize default colormap (EE) NVIDIA(0): *** Aborting *** Maybe my portmaster -r perl didn't go well? Or do I need to rebuild some other ports? Thanks Anton

r250633: make -j buildkernel: ports module: illegal option -- J

2013-05-24 Thread Anton Shterenlikht
amd64 r250633 buildworld fine, but on make -j4 buildkernel got this error: === Ports module net/bwn-firmware-kmod (all) *skip* Extracting v4/b0g0initvals5.fw /usr/bin/touch /usr/obj/usr/src/sys/BUZI/usr/ports/net/bwn-firmware-kmod/work/bg /v4/ucode.fw make: illegal option -- J usage: make

r250609: error: use of undeclared identifier 'CLOCK_PROCESS_CPUTIME_ID'

2013-05-13 Thread Anton Shterenlikht
# uname -a FreeBSD mech-aslap239.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r2463 70M: Tue Feb 19 09:04:48 GMT 2013 r...@mech-aslap239.men.bris.ac.uk:/usr/obj /usr/src/sys/BUZI amd64 make buildworld: c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include

Re: svn: E175002: Unable to connect to a repository at URL 'https://svn.freebsd.org/base/head'

2013-04-22 Thread Anton Shterenlikht
From g...@freebsd.org Mon Apr 22 22:57:51 2013 On Mon, Apr 22, 2013 at 05:28:15PM -0400, Glen Barber wrote: # svn up /usr/src/ Updating '/usr/src': svn: E175002: Unable to connect to a repository at URL 'https://svn.fre= ebsd.org/base/head'

Re: ipfilter(4) needs maintainer

2013-04-14 Thread Anton Shterenlikht
A migration *guide*, yes. Tools to convert one syntax to another: no. ok, so what is the brief migraiton advice? The Handbook mentions PF and IPFW. I gather from your mails that PF is the recommended choice. Is that so? If I choose PF, can I just follow the Handbook PF section, and once

Re: troubles with buildworld/sendmail/sasl/clang

2013-03-21 Thread Anton Shterenlikht
Kimmo Paasiala writes: =buildworld=== /usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/usersmtp.c:1864:8: error: incompatible pointer types passing 'void ()' to parameter of type 'void (*)(char *,

Re: PathScale EKO Path 5 not for FreeBSD anymore?

2013-02-20 Thread Anton Shterenlikht
Oliver I try to use FreeBSD for day-to-day numerical work, as far as possible. I have to complement it with linux cluster systems, largely due to a range of compilers available there. Anyway, keep me posted if you get anywhere with this. Anton ___

Re: daily otput: rejected mail hosts?

2013-02-20 Thread Anton Shterenlikht
From mexas Thu Feb 14 09:51:50 2013 To: freebsd-questi...@freebsd.org Subject: daily otput: rejected mail hosts? Reply-To: me...@bristol.ac.uk I see in the daily output: Checking for rejected mail hosts: 172 553 check_mail system.mail

panic: Assertion t-t_cursor.tp_row = t-t_winsize.tp_row failed at /usr/src/sys/teken/teken_subr.h:94

2013-02-18 Thread Anton Shterenlikht
I got this panic when playing with the docking station for lenovo T61p. I tried to attach/detach it. I got a complete crash dump, but don't know what to do with it. root@zzz:/var/crash # cat info.1 Dump header from device /dev/ada0p3 Architecture: amd64 Architecture Version: 2 Dump Length:

Re: 7+ days of dogfood

2013-02-12 Thread Anton Shterenlikht
From s...@troutmask.apl.washington.edu Sun Feb 10 19:06:10 2013 On Sun, Feb 10, 2013 at 06:51:23PM +, Anton Shterenlikht wrote: Date: Sun, 10 Feb 2013 08:44:24 -0800 From: Steve Kargl s...@troutmask.apl.washington.edu To: Boris

Re: 7+ days of dogfood

2013-02-12 Thread Anton Shterenlikht
Date: Tue, 12 Feb 2013 02:48:49 -0800 (PST) From: Jakub Lach jakub_l...@mailplus.pl To: freebsd-current@freebsd.org Hi Anton, I recognize you from your usual struggle with ia64 :) Hope your work/environment really have a good

on amd64 r246552: iwn0: Intel Wireless WiFi Link 4965: fatal firmware error

2013-02-11 Thread Anton Shterenlikht
This is a T61p 6459 laptop with (from pciconf -lv): iwn0@pci0:3:0:0:class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' class = network or (from dmesg):

Re: on amd64 r246552: iwn0: Intel Wireless WiFi Link 4965: fatal firmware error

2013-02-11 Thread Anton Shterenlikht
From tomek.ce...@gmail.com Mon Feb 11 11:11:23 2013 Yesterday I had something similar - it was cause by a radio switch flip: iwn0: RF switch: radio disabled ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0:

Re: 7+ days of dogfood

2013-02-10 Thread Anton Shterenlikht
Date: Sun, 10 Feb 2013 08:44:24 -0800 From: Steve Kargl s...@troutmask.apl.washington.edu To: Boris Samorodov b...@passap.ru Subject: Re: 7+ days of dogfood FFLAGS = -O2 -pipe -march=native -mtune=native I don't like using = for FLAGS

Re: 7+ days of dogfood

2013-02-10 Thread Anton Shterenlikht
From s...@troutmask.apl.washington.edu Sun Feb 10 19:06:10 2013 On Sun, Feb 10, 2013 at 06:51:23PM +, Anton Shterenlikht wrote: Date: Sun, 10 Feb 2013 08:44:24 -0800 From: Steve Kargl s...@troutmask.apl.washington.edu To: Boris

building custom kernel on -current: unknown option COMPAT_LINUX

2013-02-09 Thread Anton Shterenlikht
This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32 to the kernel config, following sys/amd64/conf/NOTES On buildkernel I get: unknown option COMPAT_LINUX What am I missing? Thanks Anton ___

Re: 7+ days of dogfood

2013-02-09 Thread Anton Shterenlikht
Date: Sat, 9 Feb 2013 16:07:23 -0800 From: Steve Kargl s...@troutmask.apl.washington.edu To: freebsd-current@freebsd.org Subject: 7+ days of dogfood In a long thread started by Peter Wemm on developers@, he described the move/upgrade of the

Re: building custom kernel on -current: unknown option COMPAT_LINUX

2013-02-09 Thread Anton Shterenlikht
From free...@edvax.de Sun Feb 10 00:29:36 2013 On Sun, 10 Feb 2013 00:18:06 GMT, Anton Shterenlikht wrote: This is on amd64 r246552 I added options COMPAT_43 options COMPAT_LINUX options COMPAT_LINUX32

Re: building custom kernel on -current: unknown option COMPAT_LINUX

2013-02-09 Thread Anton Shterenlikht
From free...@edvax.de Sun Feb 10 00:42:11 2013 On Sun, 10 Feb 2013 00:31:44 GMT, Anton Shterenlikht wrote: From free...@edvax.de Sun Feb 10 00:29:36 2013 On Sun, 10 Feb 2013 00:18:06 GMT, Anton Shterenlikht wrote

installworld error: ad0: FAILURE - READ_DMA status=51READY, DSC, ERROR error=40UNCORRECTABLE LBA=28071584

2013-01-04 Thread Anton Shterenlikht
I got this error on make installworld: === sbin/dhclient (install) install -s -o root -g wheel -m 555 dhclient /sbin ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=40UNCORRECTABLE LBA=28071584 g_vfs_done():ad0a[READ(offset=14372651008, length=16384)]error = 5 vnode_pager_getpages: I/O

Re: installworld error: ad0: FAILURE - READ_DMA status=51READY, DSC, ERROR error=40UNCORRECTABLE LBA=28071584

2013-01-04 Thread Anton Shterenlikht
Date: Fri, 4 Jan 2013 11:09:07 GMT From: Anton Shterenlikht me...@bristol.ac.uk I got this error on make installworld: === sbin/dhclient (install) install -s -o root -g wheel -m 555 dhclient /sbin ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR

r244114 ia64: make check-old-libs says /lib/libz.so.5 can be removed, but it is still needed by /usr/sbin/dtrace and /usr/sbin/lockstat

2012-12-12 Thread Anton Shterenlikht
I updated to r244114 on ia64 following the standard procedure. I then get: # make check-old-libs Checking for old libraries /lib/libz.so.5 # while sysutils/libchk shows: Binaries that are linked with: /lib/libz.so.5 /usr/sbin/dtrace /usr/sbin/lockstat and indeed these two

Re: r244114 ia64: make check-old-libs says /lib/libz.so.5 can be removed, but it is still needed by /usr/sbin/dtrace and /usr/sbin/lockstat

2012-12-12 Thread Anton Shterenlikht
From swhet...@gmail.com Wed Dec 12 17:55:00 2012 On Wed, Dec 12, 2012 at 10:52 AM, Scot Hetzel swhet...@gmail.com wrote: On Wed, Dec 12, 2012 at 4:07 AM, Anton Shterenlikht me...@bristol.ac.uk wrote: I updated to r244114 on ia64 following the standard

Re: r244114 ia64: make check-old-libs says /lib/libz.so.5 can be removed, but it is still needed by /usr/sbin/dtrace and /usr/sbin/lockstat

2012-12-12 Thread Anton Shterenlikht
From swhet...@gmail.com Wed Dec 12 17:54:59 2012 On Wed, Dec 12, 2012 at 4:07 AM, Anton Shterenlikht me...@bristol.ac.uk wrote: I updated to r244114 on ia64 following the standard procedure. I then get: # make check-old-libs Checking

from 5-NOV WITH_CLANG_IS_CC in /etc/src.conf is no longer needed, right?

2012-11-09 Thread Anton Shterenlikht
Hi I'm on 242801 amd64. I understand from [1] that WITH_CLANG_IS_CC is no longer needed in /etc/src.conf. Yet I somehow still get cc,c++,cpp all GCC binaries, e.g. # /usr/bin/cc --version cc (GCC) 4.2.1 20070831 patched [FreeBSD] I'm missing something else. Please advise Thanks Anton [1]

Re: from 5-NOV WITH_CLANG_IS_CC in /etc/src.conf is no longer needed, right?

2012-11-09 Thread Anton Shterenlikht
From d...@freebsd.org Fri Nov 9 14:11:18 2012 On 2012-11-09 09:27, Anton Shterenlikht wrote: I'm on 242801 amd64. I understand from [1] that WITH_CLANG_IS_CC is no longer needed in /etc/src.conf. Yet I somehow still get cc,c++,cpp all GCC

Re: from 5-NOV WITH_CLANG_IS_CC in /etc/src.conf is no longer needed, right?

2012-11-09 Thread Anton Shterenlikht
From christer.solsko...@gmail.com Fri Nov 9 20:40:46 2012 On 2012-11-09 09:27, Anton Shterenlikht wrote: I'm on 242801 amd64. I understand from [1] that WITH_CLANG_IS_CC is no longer needed in /etc/src.conf

Re: FORTRAN vs. Fortran (was: November 5th is Clang-Day)

2012-11-02 Thread Anton Shterenlikht
Date: Fri, 2 Nov 2012 17:08:18 +1100 From: Greg 'groggy' Lehey g...@freebsd.org To: Erich Dollansky erichfreebsdl...@ovitrap.com Subject: FORTRAN vs. Fortran (was: November 5th is Clang-Day) On Friday, 2 November 2012 at 12:21:03 +0700, Erich Dollansky

Re: FORTRAN vs. Fortran (was: November 5th is Clang-Day)

2012-11-02 Thread Anton Shterenlikht
From thera...@theravensnest.org Fri Nov 2 10:54:08 2012 On 2 Nov 2012, at 10:21, Anton Shterenlikht wrote: further development of FreeBSD/ia64 and FreeBSD/sparc64 will probably suffer and then stop altogether There is a SPARC64 back end

Re: ia64 panic: make_dev_credv: bad si_name (error=17, si_name=pass3)

2012-09-21 Thread Anton Shterenlikht
From j...@freebsd.org Thu Sep 20 20:30:06 2012 On Thursday, September 20, 2012 4:53:30 am Anton Shterenlikht wrote: On ia64 r235474 I added another disk and did camcontrol rescan all to see it. I got this panic: panic: make_dev_credv

  1   2   3   >