Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
for MSI Z77 MPOWER motherboard: re0@pci0:2:0:0: class=0x02 card=0x77511462 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet ifconfig re0 shows re0: flags=8802 metric 0 mtu 1500 options=8209b ether d4:3d:7e:97:17:e2 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active dhclient re0 produces DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 12 DHCPOFFER from 192.168.1.1 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 192.168.1.1 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPREQUEST on re0 to 255.255.255.255 port 67 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received. No working leases in persistent database - sleeping. Ethernet chip data for older motherboard, MSI Z68MA-ED55(B3), is re0@pci0:3:0:0: class=0x02 card=0x76761462 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet So I still can not connect on the newer motherboard as I can with the older motherboard, despite the same chip; card has a different ID. Tom ___ 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: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)
On Mon, Sep 23, 2013 at 8:30 PM, Harald Schmalzbauer < h.schmalzba...@omnilan.de> wrote: > Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime): > > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer > > mailto:h.schmalzba...@omnilan.de>> wrote: > > > > Hello, > > > > unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to > this > > panic: > > > > > > > > > > wcb4xxp0: <6>Did not do the highestorder stuff > > <6>dahdi: Detected time shift. > > <5>dahdi_echocan_mg2: Registered echo canceler 'MG2' > > > > Starting asterisk afterwards also leads to panic. > > I guess dahdi development stalled, but I wanted to try it because I'd > > prefer freeswitch and need BRI support... > > Is somebody familiar with dahdi and interested in making it work with > > FreeBSD 9.2? > > > > Thanks, > > > > -Harry (not subscribed to isdn@) > > > > > > > > Have you been able to solve the problem? I am running Freeswitch (from > > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line > > (Digium 8 span and single span) without any problems on 9.1. Will test > > it on 9.2 and get back to you if I see a panic . > Hello Amitabh, > > couldn't solve my problem. > First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2 ports > in NT mode, so trying anything else with dahdi before my settings get > correctly recognized is probably not worth the time. > Also I have to investigate if it is still true that libpri doesn't support > ptmp in NT mode!?! > In general, the freebsd dahdi port doesn't seem to be in good shape; > Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d' shows > nothing :-( ), no man page – hard to find out anything about dahdi in > FreeBSD, not even the supported hardwhere seems to be documentend > anywhere... > > Any hints highly appreciated, although I think the better way was to teach > FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN > hardware supported by i4b (ISDN4BSD)! > Or to make chan_capi work with asterisk11 – the lesser evil than fighting > dahid... > > Thanks, > > -Harry > > > Hello Harry Sadly, there is not much help while installing/using dahdi on FreeBSD. There does not seem to by any sysctls defined for dahdi which are needed to set for certain cards. Infact, for the 8 span card, to change the default T1 to E1, I had to make changes in the code directly. Amitabh ___ 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: Possible kqueue related issue on STABLE/RC.
On Mon, Sep 23, 2013 at 03:37:08PM +0200, Patrick Lamaiziere wrote: > Le Fri, 20 Sep 2013 15:17:05 +0200, > Patrick Lamaiziere a ?crit : > > > Le Thu, 12 Sep 2013 10:36:43 +0300, > > Konstantin Belousov a ?crit : > > > > Hello, > > > > > Might be, your issue is that some filesystems do not care about > > > proper locking mode for the fifos. UFS carefully disables shared > > > locking for VFIFO, but it seems ZFS is not. I can propose the > > > following band-aid, which could help you. > > > > > > I have no idea is it the same issue as the kqueue panic. > > > > > > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > > > index c53030a..00bd998 100644 > > > --- a/sys/kern/vfs_vnops.c > > > +++ b/sys/kern/vfs_vnops.c > > > @@ -267,6 +267,8 @@ vn_open_vnode(struct vnode *vp, int fmode, > > > struct ucred *cred, return (error); > > > } > > > } > > > + if (vp->v_type == VFIFO && VOP_ISLOCKED(vp) != > > > LK_EXCLUSIVE) > > > + vn_lock(vp, LK_UPGRADE | LK_RETRY); > > > if ((error = VOP_OPEN(vp, fmode, cred, td, fp)) != 0) > > > return (error); > > > > > > @@ -358,7 +360,7 @@ vn_close(vp, flags, file_cred, td) > > > struct mount *mp; > > > int error, lock_flags; > > > > > > - if (!(flags & FWRITE) && vp->v_mount != NULL && > > > + if (vp->v_type != VFIFO && !(flags & FWRITE) && > > > vp->v_mount != NULL && vp->v_mount->mnt_kern_flag & > > > MNTK_EXTENDED_SHARED) lock_flags = LK_SHARED; > > > else > > > > Ok This has been mfced to 9.2-STABLE. But I still see this panic with > 9-2/STABLE of today (Revision : 255811). This may be better because > before the box paniced within minutes and now within hours (still using > poudriere). > > panic: > fault code = supervisor read data, page not present > instruction pointer = 0x20:0x808ebfcd > stack pointer = 0x28:0xff824c2e0630 > frame pointer = 0x28:0xff824c2e06a0 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 54243 (gvfsd-trash) > trap number = 12 > panic: page fault > cpuid = 2 > KDB: stack backtrace: > #0 0x80939ad6 at kdb_backtrace+0x66 > #1 0x808ffacd at panic+0x1cd > #2 0x80cdfbe9 at trap_fatal+0x289 > #3 0x80cdff4f at trap_pfault+0x20f > #4 0x80ce0504 at trap+0x344 > #5 0x80cc9b43 at calltrap+0x8 > #6 0x8099d043 at filt_vfsvnode+0xf3 > #7 0x808c4793 at kqueue_register+0x3e3 > #8 0x808c4de8 at kern_kevent+0x108 > #9 0x808c5950 at sys_kevent+0x90 > #10 0x80cdf3a8 at amd64_syscall+0x5d8 > #11 0x80cc9e27 at Xfast_syscall+0xf7 > > Full core.txt : > http://user.lamaiziere.net/patrick/public/vfs_vnode-core.txt.0 For start, please load the core into kgdb and for frame 8 p *kn Also, please follow http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html to recompile kernel with the debugging options and try to recreate the panic. pgpNUT12ewyWc.pgp Description: PGP signature
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
On Sun, 22 Sep 2013 20:28:08 + "Thomas Mueller" wrote: > I've been unable to establish Internet connection from a new computer with > Realtek 811E Ethernet despite this Ethernet chip working on another computer > with another MSI motherboard. In additiin to the information you have already provided, you should also provide relevant output from pciconf, like so: root@kg-core1# pciconf -lv | grep -A 4 re0 re0@pci0:2:0:0: class=0x02 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet (substitute the name of your interface for "re0") and also ifconfig output like this: root@kg-core1# ifconfig re0 re0: flags=8843 metric 0 mtu 1500 options=8209b ether 50:46:5d:8b:a2:ea inet 10.1.150.50 netmask 0x broadcast 10.1.255.255 media: Ethernet autoselect (1000baseT ) status: active (again, substitute the name of your interface for "re0") As far as fault-finding "tricks" go, here is one that have helped me on several occasions in the past: before doing anything with a network interface (in other words, before starting DHCP), try doing a 'ifconfig up' for example ifconfig re0 up After that, use the interface normally. If it works, you have found a bug related to the driver and the specific hardware revsion of you card. Create a PR for it. HTH -- Torfinn Ingolfsen ___ 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: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)
Bezüglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime): > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer > mailto:h.schmalzba...@omnilan.de>> wrote: > > Hello, > > unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to this > panic: > > > > > wcb4xxp0: <6>Did not do the highestorder stuff > <6>dahdi: Detected time shift. > <5>dahdi_echocan_mg2: Registered echo canceler 'MG2' > > Starting asterisk afterwards also leads to panic. > I guess dahdi development stalled, but I wanted to try it because I'd > prefer freeswitch and need BRI support... > Is somebody familiar with dahdi and interested in making it work with > FreeBSD 9.2? > > Thanks, > > -Harry (not subscribed to isdn@) > > > > Have you been able to solve the problem? I am running Freeswitch (from > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line > (Digium 8 span and single span) without any problems on 9.1. Will test > it on 9.2 and get back to you if I see a panic . Hello Amitabh, couldn't solve my problem. First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2 ports in NT mode, so trying anything else with dahdi before my settings get correctly recognized is probably not worth the time. Also I have to investigate if it is still true that libpri doesn't support ptmp in NT mode!?! In general, the freebsd dahdi port doesn't seem to be in good shape; Couldn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d' shows nothing :-( ), no man page – hard to find out anything about dahdi in FreeBSD, not even the supported hardwhere seems to be documentend anywhere... Any hints highly appreciated, although I think the better way was to teach FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN hardware supported by i4b (ISDN4BSD)! Or to make chan_capi work with asterisk11 – the lesser evil than fighting dahid... Thanks, -Harry signature.asc Description: OpenPGP digital signature
Re: Possible kqueue related issue on STABLE/RC.
Le Fri, 20 Sep 2013 15:17:05 +0200, Patrick Lamaiziere a écrit : > Le Thu, 12 Sep 2013 10:36:43 +0300, > Konstantin Belousov a écrit : > > Hello, > > > Might be, your issue is that some filesystems do not care about > > proper locking mode for the fifos. UFS carefully disables shared > > locking for VFIFO, but it seems ZFS is not. I can propose the > > following band-aid, which could help you. > > > > I have no idea is it the same issue as the kqueue panic. > > > > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > > index c53030a..00bd998 100644 > > --- a/sys/kern/vfs_vnops.c > > +++ b/sys/kern/vfs_vnops.c > > @@ -267,6 +267,8 @@ vn_open_vnode(struct vnode *vp, int fmode, > > struct ucred *cred, return (error); > > } > > } > > + if (vp->v_type == VFIFO && VOP_ISLOCKED(vp) != > > LK_EXCLUSIVE) > > + vn_lock(vp, LK_UPGRADE | LK_RETRY); > > if ((error = VOP_OPEN(vp, fmode, cred, td, fp)) != 0) > > return (error); > > > > @@ -358,7 +360,7 @@ vn_close(vp, flags, file_cred, td) > > struct mount *mp; > > int error, lock_flags; > > > > - if (!(flags & FWRITE) && vp->v_mount != NULL && > > + if (vp->v_type != VFIFO && !(flags & FWRITE) && > > vp->v_mount != NULL && vp->v_mount->mnt_kern_flag & > > MNTK_EXTENDED_SHARED) lock_flags = LK_SHARED; > > else > Ok This has been mfced to 9.2-STABLE. But I still see this panic with 9-2/STABLE of today (Revision : 255811). This may be better because before the box paniced within minutes and now within hours (still using poudriere). panic: fault code = supervisor read data, page not present instruction pointer = 0x20:0x808ebfcd stack pointer = 0x28:0xff824c2e0630 frame pointer = 0x28:0xff824c2e06a0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 54243 (gvfsd-trash) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: #0 0x80939ad6 at kdb_backtrace+0x66 #1 0x808ffacd at panic+0x1cd #2 0x80cdfbe9 at trap_fatal+0x289 #3 0x80cdff4f at trap_pfault+0x20f #4 0x80ce0504 at trap+0x344 #5 0x80cc9b43 at calltrap+0x8 #6 0x8099d043 at filt_vfsvnode+0xf3 #7 0x808c4793 at kqueue_register+0x3e3 #8 0x808c4de8 at kern_kevent+0x108 #9 0x808c5950 at sys_kevent+0x90 #10 0x80cdf3a8 at amd64_syscall+0x5d8 #11 0x80cc9e27 at Xfast_syscall+0xf7 Full core.txt : http://user.lamaiziere.net/patrick/public/vfs_vnode-core.txt.0 Thanks, regards. ___ 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: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
> Related part of /var/run/dmesg.boot is > > re0: port > 0xe000-0xe0f f mem 0xf7d04000-0xf7d04fff,0xf7d0-0xf7d03fff irq 17 at > device 0.0 on pci2 re0: Using 1 MSI-X message re0: Chip rev. 0x2c80 re0: > MAC rev. 0x miibus0: on re0 rgephy0: 1000BASE-T media interface> PHY 1 on miibus0 rgephy0: none, 10baseT, > 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX , 100baseTX-FDX-flow, > 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX- master, > 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet > address: d4:3d:7e:97:17:e2 > Thomas: That NIC chip works for me and gets it's address information using DHCP. Aug 31 16:09:13 mail kernel: FreeBSD 9.2-PRERELEASE #1: Sat Aug 31 12:13:51 EDT 2013 Aug 31 16:09:13 mail kernel: re0: port 0x2000-0x20ff mem 0xf0004000-0xf0004fff,0xf000-0xf0003fff irq 16 at device 0.0 on pci1 Aug 31 16:09:13 mail kernel: re0: Using 1 MSI-X message Aug 31 16:09:13 mail kernel: re0: Chip rev. 0x2800 Aug 31 16:09:13 mail kernel: re0: MAC rev. 0x Aug 31 16:09:13 mail kernel: miibus0: on re0 Aug 31 16:09:13 mail kernel: rgephy0: PHY 1 on miibus0 Aug 31 16:09:13 mail kernel: rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow Aug 31 16:09:13 mail kernel: re0: Ethernet address: 70:71:bc:18:1b:97 Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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"
