Re: 11.0 and tw_cli fail
From my experience;
I posess one 9650se card 12 ports with a computer build with freeBSD
with a custom kernel build.
i haved this particular error one day (it uses old mmap calls, which have
removed some time ago)
you can see why it fails by invoking the tw_cli after the truss(1) command
# truss tw_cli
readlink("/etc/malloc.conf",0x7fffea50,63) ERR#2 'No such file or
directory'
issetugid() = 0 (0x0)
compat6.mmap(0x0,0x1000,0x3,0x1002,0x,0x0,0x0) = 34366898176
(0x8006d4000)
break(0x78f000) = 0 (0x0)
break(0x79) = 0 (0x0)
break(0x791000) = 0 (0x0)
sysarch(AMD64_SET_FSBASE,0x7fffeb10) = 0 (0x0)
snip
the tw_cli utility worked again with COMPAT_FREEBSD6 compiled in the kernel
and the compat libraries from the same version also installed...
this two things solved this very particular problem; for me at least.
hope it helps you.
Regards.
> Message du 30/05/17 23:34
> De : "Alan Somers"
> A : "CBL"
> Copie à : "FreeBSD"
> Objet : Re: 11.0 and tw_cli fail
>
> Was the tw_cli utility built for FreeBSD 10? If so, you need to
> either rebuilt it, or build your kernel with COMPAT_FREEBSD10 in the
> config file. It's in the GENERIC config file, so you'll have it if
> you don't use a custom kernel.
> -Alan
>
> On Tue, May 30, 2017 at 3:19 PM, CBL wrote:
> > Updated a box to 11.0 with a legacy 3ware 9690SA using the twe driver.
> > Now the tw_cli utility is now throwing "Bad system call (core dumped).
> >
> > Anybody have any suggestions? Was working fine on 10.3.
> >
> > Thanks
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD hangs on boot after kernel upgrade to 9.0-R
On Sun, 22 Jan 2012 14:47:47 +1100 (EST), Ian Smith wrote On Sun, 22 Jan 2012, mato wrote: On Sat, 21 Jan 2012 22:57:05 +0200, Alexander Motin wrote Hi. On 01/21/12 21:34, mato wrote: I've used freebsd-update to upgrade from 8.2-R to 9.0-R and all looked niceuntil the first reboot. Now my FreeBSD always hangs midway through the bootprocess and the last message output is:uhub3:Intel EHCI root HUB...I've tried safe boot option but that does not help at all.When I disable USB support in BIOS the last message before hang is:ata1: reset tp1 mask=03 ostat0=00 ostat1=00(aprobe0:ata0:0:1:0): SIGNATURE: eb14 Any idea what might be wrong and how to fix it please ? The last line is the ATAPI device detection. What ATA controller doyou have there? On one Core2Duo-class Supermicro system alike hangwas caused by ITE PATA controller. In that case it was workaroundedby adding hint.ata.0.mode=PIO4 to /oot/loader.conf. You may tryjust set it from loader prompt with `set` command. I don't know exact controller but this is Pentium M based laptop. Which one? HDD is primary master while DVD drive is primary slave. :-/ And it's been working like this since FreeBSD 5.3. Anyway, I've tried your advice but unfortunately it did not help. Here is longer log (retyped from screen): ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=50 stat1=00 devices=0x20001 (aprobe0:ata0:0:0:0): SIGNATURE: ata1: reset tp1 mask=03 ostat0=00 ostat1=00 (aprobe0:ata0:0:1:0): SIGNATURE: eb14 Then it hangs. And please note it looks differently when USB is not turned off in BIOS. Though I have no idea if / how that matters. So what now please ? Any other things to try ? It's possible this is not an ATA problem; these being the last messages you see may just be the last (maybe) successful thing happening; those messages look about normal to me. I had similar symptoms (ie the last messages before the problem occurring being ATA ones) with a long term error (60 second stall) when resuming my Thinkpad T23, which turned out to be a USB problem, in my case with UHCI. The solution to that was to build a kernel thus: include GENERIC ident NO_UHCI # load on boot, unload/reload around suspend/resume nodeviceuhci# UHCI PCI-USB interface # not used nodeviceohci# OHCI PCI-USB interface # not used, USB 1 only nodeviceehci# EHCI PCI-USB interface (USB 2.0) That's on 8.2-RELEASE, but I haven't heard of this issue being resolved on 9 yet. Of course, if you can't boot you can't build a new kernel on it, but I thought I'd mention USB as a possible 'hidden' issue here. It seems USB is innocent here as upon turning it back on in BIOS USB mesages are intermixed with ATA ones .. here are the last 4 before hang: uhub2: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus2 (aprobe0:ata0:0:1:0): SIGNATURE: eb14 ugen3.1: Intel at usbus3 uhub3: Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus3 I waited several minutes but no progress, it seems stuck. M. PS: This laptop is Asus W1N with following specs: Pentium M, 1GB RAM, 80GB HDD, Pioneer DVD-RW DVR-K14AS, Intel 82801DBM Ultra ATA Storage Controller - 24CA, Intel 82801DB/DBM USB2 Enhanced Host Controller - 24CD. Freehosting PIPNI - http://www.pipni.cz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD hangs on boot after kernel upgrade to 9.0-R
Hi, I've used freebsd-update to upgrade from 8.2-R to 9.0-R and all looked nice until the first reboot. Now my FreeBSD always hangs midway through the boot process and the last message output is: uhub3: Intel EHCI root HUB... I've tried safe boot option but that does not help at all. When I disable USB support in BIOS the last message before hang is: ata1: reset tp1 mask=03 ostat0=00 ostat1=00 (aprobe0:ata0:0:1:0): SIGNATURE: eb14 Any idea what might be wrong and how to fix it please ? Thanks, Martin Freehosting PIPNI - http://www.pipni.cz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD hangs on boot after kernel upgrade to 9.0-R
On Sat, 21 Jan 2012 22:57:05 +0200, Alexander Motin wrote Hi. On 01/21/12 21:34, mato wrote: I've used freebsd-update to upgrade from 8.2-R to 9.0-R and all looked nice until the first reboot. Now my FreeBSD always hangs midway through the boot process and the last message output is: uhub3:Intel EHCI root HUB... I've tried safe boot option but that does not help at all. When I disable USB support in BIOS the last message before hang is: ata1: reset tp1 mask=03 ostat0=00 ostat1=00 (aprobe0:ata0:0:1:0): SIGNATURE: eb14 Any idea what might be wrong and how to fix it please ? The last line is the ATAPI device detection. What ATA controller do you have there? On one Core2Duo-class Supermicro system alike hang was caused by ITE PATA controller. In that case it was workarounded by adding hint.ata.0.mode=PIO4 to /oot/loader.conf. You may try just set it from loader prompt with `set` command. I don't know exact controller but this is Pentium M based laptop. HDD is primary master while DVD drive is primary slave. :-/ And it's been working like this since FreeBSD 5.3. Anyway, I've tried your advice but unfortunately it did not help. Here is longer log (retyped from screen): ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: reset tp2 stat0=50 stat1=00 devices=0x20001 (aprobe0:ata0:0:0:0): SIGNATURE: ata1: reset tp1 mask=03 ostat0=00 ostat1=00 (aprobe0:ata0:0:1:0): SIGNATURE: eb14 Then it hangs. And please note it looks differently when USB is not turned off in BIOS. Though I have no idea if / how that matters. So what now please ? Any other things to try ? Thanks, Martin Freehosting PIPNI - http://www.pipni.cz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Recent PAM changes worth an UPDATING entry?
Doug Barton wrote: On Fri, 24 Aug 2007, martinko wrote: Doug Barton wrote: Howdy, I just rebuilt and installed my world on my 6-stable box, and ran into a snag. Like a lot of users I use -DNO_CLEAN in buildworld since this is a very slow box that I use mostly as a file/dns server. After rebooting I could ssh in ok (probably because I don't use PAM for sshd) but couldn't su, or log in at the console. After looking at the errors, I figured out that I needed to completely recompile stuff related to PAM. Just to be on the safe side I did libpam, login, su, and getty. After that I was able to log in normally from the console, and su from either terminal. IMO this is worth an entry in UPDATING since I probably won't be the only user who stumbles across this. Doug Doug, Could it possibly be related to the following issue of mine ?? : http://lists.freebsd.org/pipermail/freebsd-questions/2007-July/153137.html Sure sounds that way. Have you tried doing clean recompiles of those programs? Doug Doug, I'm not quite sure why after buildworld installworld I would need to recompile some stuff once again (apart from ports, if necessary, of course). Does it have something to do with -DNO_CLEAN and what exactly ? Anyway, I didn't use it while doing my buildworld. Anyway, I may try what you suggest (asap). Meanwhile, could you pls explain where you looked at for errors and what exactly you did afterwards ?? (I was at lost myself) Cheers, Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
