trying to track down UFS "dup alloc" message on iSCSI
I am playing with an iSCSI device on FreeBSD client running UFS2 on the device over a LAN. Everything works well until I reboot the iSCSI server - the client pauses for a minute or so then continues working after iSCSI server comes back. No I/O errors are reported. Everything seems to work fine for a little while! But shortly afterwards, I get a panic with the message panic: ffs_valloc: dup alloc It seems related to the length of the delay the iSCSI device is paused - restarting the iSCSI target daemon process doesn't cause the problem but rebooting the whole target box does cause it. 1. Could this be related to the patch Matt Dillon created years ago which I found here? http://leaf.dragonflybsd.org/mailarchive/bugs/2005-01/msg00093.html 2. Can anyone think of any other reason this might happen? I know I am stretching UFS to the limits here, expecting it to pause and restart after more than a minute of locked disk :-) However, since all I/O eventually complete successfully and no errors are reported, I find it suspicious. Cheers - Andrew ps. running latest iSCSI code 2.1 on latest 7-STABLE box. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What has happened to the FreeBSD Forums?
On October 2, 2008 02:51 pm Ron Wingfield wrote: >My apologies in advance if this is an inappropriate "list question", >but . . . >What has happened to the FreeBSD Forum at >[1]"http://www.freebsdforums.com/forums/";. I am/was an infrequent >user/contributor to the forum . . .haven't been there in months, but >WOW! what has happened to the moderation. Why is there so much >filth and pornography posted there now? >The site server response is also abysmal. >Thanks for any info., >Ron W. The forums admin disappeared. We lowly moderators (there were only two of us) had no ability to change anything in the forum setup. We did the best we could for as long as we could to delete the spam entries every day. Several of the users joined together to start a new forum, with multiple admins, and better anti-spam setup. freebsdforums/bsdforums is all but dead. http://www.daemonforums.org is where we all hang out now. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system hangup - I'm lost
On Thu, Oct 02, 2008 at 06:51:06PM +0200, Oliver Lehmann wrote: > > today I'd a crash again - I was not able to get a crash dump (thought a > > "panic" at the end of the kdb would do it but didn't - should have called > > dumpon before ;)) - so here now the information I was able to retrieve: > > > > Ok, what I've got so far is wrinting stuff out to the console when the > > system hangs up: > > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > > ... > > > > and now the debugger stuff: > > > > [snipped] > > > > So.. no idea? anyone? If it's PATA, check the cabling, then check it again, and just to make sure, replace the cable even if the system used to work flawlessly in the past. I've had this on a few servers, but replacing the cables always fixed the problem for me. Oh, btw, you can reproduce this exact behavior on diskless workstations with an NFS-mounted swap. IIRC, it even happened on VERY slow hardware with GBDE or GELI-encrypted swap partitions; but I'm not 100% sure it was due to slowness (it could have been a bad cabling issue as well). > -- > Oliver Lehmann > http://www.pofo.de/ > http://wishlist.ans-netz.de/ -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What has happened to the FreeBSD Forums?
Ron Wingfield wrote: My apologies in advance if this is an inappropriate "list question", but . . . What has happened to the FreeBSD Forum at [1]"http://www.freebsdforums.com/forums/";. I am/was an infrequent user/contributor to the forum . . .haven't been there in months, but WOW! what has happened to the moderation. Why is there so much filth and pornography posted there now? The forums were abandoned. Everyone moved to http://www.daemonforums.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
What has happened to the FreeBSD Forums?
My apologies in advance if this is an inappropriate "list question", but . . . What has happened to the FreeBSD Forum at [1]"http://www.freebsdforums.com/forums/";. I am/was an infrequent user/contributor to the forum . . .haven't been there in months, but WOW! what has happened to the moderation. Why is there so much filth and pornography posted there now? The site server response is also abysmal. Thanks for any info., Ron W. [EMAIL PROTECTED] 501-920-7860 cell (best way) 501-228-4798 home References 1. http://www.freebsdforums.com/forums/ 2. mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pf rules not being loaded during boot on 7.1-PRERELEASE
I recently upgraded my i386 router from 7.0 to 7.1-PRERELEASE. I rebooted it today but despite pf_enable="YES" being in /etc/rc.conf no rules got loaded during boot, despite pf itself having been enabled: router# pfctl -s rules router# pfctl -e -f /etc/pf.conf pfctl: pf already enabled [connection is closed due to new rules being loaded] router# pfctl -s rules scrub in all fragment reassemble [... lots of rules listed] Has anyone else seen this problem, or have I just missed something that's changed between 7.0 and 7.1 in the way pf works? -- Bruce Cran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.5-prerelease and if_re - patches needed?
On Mon, 22 Sep 2008 11:10:23 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > Due to lack of time and energy the change made in HEAD wasn't MFCed > to RELENG_6 so you may still need some patch. stable/7 should have > no such problems though. Does anybody happen to know which patch? > Maybe the issue you're seeing comes from misuse of bus_dma(9) which > was corrected in stable/7. But not MFC'ed to RELENG_6 I guess? Is therer a patch for RELENG_6 somewhere? -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system hangup - I'm lost
John Baldwin wrote: > Sounds like your disk has died, or perhaps the controller is hung and not > completing disk I/O requests anymore. Hm - the 3ware eventlog does not shed any light on this - no events occured. So I can just guess that the controller and the disks are fine (I had once a hard failing disk and the controller detected it correctly) Do you have an idea how to debug this further? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system hangup - I'm lost
On Wednesday 01 October 2008 11:29:43 am Oliver Lehmann wrote: > Hi, > > today I'd a crash again - I was not able to get a crash dump (thought a > "panic" at the end of the kdb would do it but didn't - should have called > dumpon before ;)) - so here now the information I was able to retrieve: > > Ok, what I've got so far is wrinting stuff out to the console when the > system hangs up: > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 Sounds like your disk has died, or perhaps the controller is hung and not completing disk I/O requests anymore. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipfw: install_state: entry already present, done
Hi, I've just updated my 7-STABLE box to 7.1-PRERELEASE, and I'm seeing a quite a few ipfw kernel messages: ipfw: install_state: entry already present, done What is this mean? Has some regression occurred with ipfw? Cheers. -- Jonathan Chen <[EMAIL PROTECTED]> -- Do not take life too seriously. You will never get out of it alive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system hangup - I'm lost
Oliver Lehmann wrote: > Hi, > > today I'd a crash again - I was not able to get a crash dump (thought a > "panic" at the end of the kdb would do it but didn't - should have called > dumpon before ;)) - so here now the information I was able to retrieve: > > Ok, what I've got so far is wrinting stuff out to the console when the > system hangs up: > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 > ... > > and now the debugger stuff: > > [snipped] > So.. no idea? anyone? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb data xfer problem with to/from nokia smartphones
I have difficulties transferring data from or to nokia smartphones in mass storage mode, specially nokia N80 and N95. The files are coming with missing parts, accessing a photo which s stored ont the phone is beeing seen cut somewhere in half, mp3 files are transferred but there are missing parts within, same with other binaries from the same computer (dual boot) with windows xp and fedora 8 txferring the exact same file the thing runs fine happens on i386 and amd64 some idea what might be wrong? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: recommended setup for amd64 7-STABLE with ZFS, Samba 3.2 and possibly ACLs?
On 1 okt 2008, at 12:12, Jeremy Chadwick wrote: On Wed, Oct 01, 2008 at 10:42:32AM +0200, Ben Stuyts wrote: I had to disable mmap access in dovecot, or it would coredump periodically. (mmap_disable = yes in dovecot.conf) Have you tried re-enabling mmap in dovecot on a system with a kernel build after those dates? It's been running for a day now wit mmap enabled, and it works fine now. Again thanks for pointing this out. Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: resource leak
On Wed, 1 Oct 2008, Stephen Clark wrote: A big part of problem is this seems to take about 100 days of uptime to occur. We have some inhouse test boxes but have never seen the problem, probably because non of them have been up more than about 45 days. The units in the field, of which there is about 300, are headless and none are physically close. When the boxes are rebooted there are no error messages in any of the log files, only the absence of information that would normally be logged by new processes that would be spawned. We are getting ready to install a patch that will try to gather more information. I thought about writing an app the would try to fork a child periodically and record in a log file if there was an error. But EAGAIN is nonspecific as to the real reason the fork failed. I was looking for some way to periodically log the resources that would cause the fork failure. The narrowness of the UNIX errno space is, at times, fairly unhelpful. As far as I'm aware, the two main causes of EAGAIN out of fork() are an exhaustion of maxprocs or an exhaustion of per-user process limits. This suggests one or more run-away applications or services, or a gradual leak of processes from a service (perhaps a failure to GC dead children, or a gradual increase but never decrease of worker processes?). Robert N M Watson Computer Laboratory University of Cambridge procstat -k looks like it would have been a good candidate but unfortunately we are running 6.1. Thanks for the response. Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: if_re is broken on RELENG_7 ?
On Thu, Oct 02, 2008 at 12:01:57PM +0300, Sergey V. Dyatko wrote: > В Thu, 2 Oct 2008 17:44:25 +0900 > Pyun YongHyeon <[EMAIL PROTECTED]> пишет: > > > On Thu, Oct 02, 2008 at 10:26:00AM +0300, Sergey V. Dyatko wrote: > > > Hi list, > > > I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit > > > Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used > > > it. Than I started to enjoy BCM43XX wi-fi adapter and now I > > > recently decided to revert to the use of realtek adapter. But it > > > doesn't work. I'm just not running a network card or at all does > > > not work? > > > > > > some additional information: > > > ifconfig shows such information, regardless of whether the cable is > > > connected: > > > > > > %ifconfig re0 > > > re0: flags=8802 metric 0 mtu 1500 > > > > > options=389b > > > ether 00:1a:92:ca:b3:bc > > > media: Ethernet autoselect (10baseT/UTP ) > > > status: no carrier > > > > I don't see what's wrong in the output above. Because there is no > > "RUNNING" in flags field I guess you didn't up the interface. > > (e.g. either assign an IP address to the interface or run > > 'dhclient re0' if you want to get an IP address over DHCP). > > > Hmm, after command 'ifconfig re0 up' status changed to 'active', > media to '100baseTX ' and everything work fine (dhclient > re0). What time have I had to type "up" explicitly to make it work > since? You don't have to, just configure re0 interface(e.g. rc.conf) > > On my desktop with age(4): > without cable: > age0: flags=8802 metric 0 mtu 1500 > > options=319b > ether 00:1b:fc:d4:7d:b3 > media: Ethernet autoselect (none) > status: no carrier > Now I'll plug cable into NIC: > > age0: flags=8802 metric 0 mtu 1500 > > options=319b > ether 00:1b:fc:d4:7d:b3 > media: Ethernet autoselect (100baseTX ) > status: active > in that case I haven't "RUNNING" in flags field too, that flag and flag > 'UP' appeared after I assing IP to age0 > > age0: flags=8843 metric 0 > mtu1500 > > options=319b > ether 00:1b:fc:d4:7d:b3 > inet 192.168.9.240 netmask 0xff00 broadcast 192.168.9.255 That depends on PHY driver, rgephy(4) for re(4). Some PHY hardware requires special mode/initialization to establish a valid link with link partner. It seems that atphy(4) doesn't require any special PHY hardware configuration to establish a link. Also you can say the link status is valid only after interface up. Normally PHY drivers will have to restart auto-negotiation to choose the highest common denominator ability in interface up time. The established link after auto-negotiation may/may not agree on the speed/duplex of the link you've seen before the initialization. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system hangup - I'm lost
Jeremy Chadwick wrote: > - Maxim MAX211ECA1, no idea but doesn't interest me Just for completeness, this is a serial port driver IC. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "[...] one observation we can make here is that Python makes an excellent pseudocoding language, with the wonderful attribute that it can actually be executed." -- Bruce Eckel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: if_re is broken on RELENG_7 ?
В Thu, 2 Oct 2008 17:44:25 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> пишет: > On Thu, Oct 02, 2008 at 10:26:00AM +0300, Sergey V. Dyatko wrote: > > Hi list, > > I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit > > Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used > > it. Than I started to enjoy BCM43XX wi-fi adapter and now I > > recently decided to revert to the use of realtek adapter. But it > > doesn't work. I'm just not running a network card or at all does > > not work? > > > > some additional information: > > ifconfig shows such information, regardless of whether the cable is > > connected: > > > > %ifconfig re0 > > re0: flags=8802 metric 0 mtu 1500 > > > options=389b > > ether 00:1a:92:ca:b3:bc > > media: Ethernet autoselect (10baseT/UTP ) > > status: no carrier > > I don't see what's wrong in the output above. Because there is no > "RUNNING" in flags field I guess you didn't up the interface. > (e.g. either assign an IP address to the interface or run > 'dhclient re0' if you want to get an IP address over DHCP). > Hmm, after command 'ifconfig re0 up' status changed to 'active', media to '100baseTX ' and everything work fine (dhclient re0). What time have I had to type "up" explicitly to make it work since? On my desktop with age(4): without cable: age0: flags=8802 metric 0 mtu 1500 options=319b ether 00:1b:fc:d4:7d:b3 media: Ethernet autoselect (none) status: no carrier Now I'll plug cable into NIC: age0: flags=8802 metric 0 mtu 1500 options=319b ether 00:1b:fc:d4:7d:b3 media: Ethernet autoselect (100baseTX ) status: active in that case I haven't "RUNNING" in flags field too, that flag and flag 'UP' appeared after I assing IP to age0 age0: flags=8843 metric 0 mtu1500 options=319b ether 00:1b:fc:d4:7d:b3 inet 192.168.9.240 netmask 0xff00 broadcast 192.168.9.255 > > > > [EMAIL PROTECTED] -lv | grep re0 -A 4 > > [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x11f51043 chip=0x816810ec > > rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > > dmesg output: http://tiger.byfly.by/files/dmesg.boot > > kernel config: http://tiger.byfly.by/files/tiger-asus-a6m > > > -- -- С уважением, Сергей Дятко системный администратор АГАВА-Минск [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: if_re is broken on RELENG_7 ?
В Thu, 2 Oct 2008 01:08:27 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Thu, Oct 02, 2008 at 10:26:00AM +0300, Sergey V. Dyatko wrote: > > Hi list, > > I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit > > Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used > > it. Than I started to enjoy BCM43XX wi-fi adapter and now I recently > > decided to revert to the use of realtek adapter. But it doesn't > > work. I'm just not running a network card or at all does not work? > > > > some additional information: > > ifconfig shows such information, regardless of whether the cable is > > connected: > > > > %ifconfig re0 > > re0: flags=8802 metric 0 mtu 1500 > > > > options=389b > > ether 00:1a:92:ca:b3:bc > > media: Ethernet autoselect (10baseT/UTP ) > > status: no carrier > > > > [EMAIL PROTECTED] -lv | grep re0 -A 4 > > [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x11f51043 chip=0x816810ec > > rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > > dmesg output: http://tiger.byfly.by/files/dmesg.boot > > kernel config: http://tiger.byfly.by/files/tiger-asus-a6m > > > > p.s.: Excuse me for my English :) > > Looks like link isn't being established, and autoselect is resorting > to 10BT/half. > > Can you provide pciconf -lv output? > sure, http://tiger.byfly.by/files/pciconf.txt > CC'ing PYUN Yong-Hyeon (surname Pyun), who helps maintain this driver. > He might have some patches for you. > -- wbr, tiger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: if_re is broken on RELENG_7 ?
On Thu, Oct 02, 2008 at 10:26:00AM +0300, Sergey V. Dyatko wrote: > Hi list, > I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit > Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used it. > Than I started to enjoy BCM43XX wi-fi adapter and now I recently > decided to revert to the use of realtek adapter. But it doesn't work. > I'm just not running a network card or at all does not work? > > some additional information: > ifconfig shows such information, regardless of whether the cable is > connected: > > %ifconfig re0 > re0: flags=8802 metric 0 mtu 1500 > > options=389b > ether 00:1a:92:ca:b3:bc > media: Ethernet autoselect (10baseT/UTP ) > status: no carrier I don't see what's wrong in the output above. Because there is no "RUNNING" in flags field I guess you didn't up the interface. (e.g. either assign an IP address to the interface or run 'dhclient re0' if you want to get an IP address over DHCP). > > [EMAIL PROTECTED] -lv | grep re0 -A 4 > [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x11f51043 chip=0x816810ec > rev=0x01 > hdr=0x00 vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > dmesg output: http://tiger.byfly.by/files/dmesg.boot > kernel config: http://tiger.byfly.by/files/tiger-asus-a6m > -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: if_re is broken on RELENG_7 ?
On Thu, Oct 02, 2008 at 10:26:00AM +0300, Sergey V. Dyatko wrote: > Hi list, > I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit > Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used it. > Than I started to enjoy BCM43XX wi-fi adapter and now I recently > decided to revert to the use of realtek adapter. But it doesn't work. > I'm just not running a network card or at all does not work? > > some additional information: > ifconfig shows such information, regardless of whether the cable is > connected: > > %ifconfig re0 > re0: flags=8802 metric 0 mtu 1500 > > options=389b > ether 00:1a:92:ca:b3:bc > media: Ethernet autoselect (10baseT/UTP ) > status: no carrier > > [EMAIL PROTECTED] -lv | grep re0 -A 4 > [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x11f51043 chip=0x816810ec > rev=0x01 > hdr=0x00 vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > dmesg output: http://tiger.byfly.by/files/dmesg.boot > kernel config: http://tiger.byfly.by/files/tiger-asus-a6m > > p.s.: Excuse me for my English :) Looks like link isn't being established, and autoselect is resorting to 10BT/half. Can you provide pciconf -lv output? CC'ing PYUN Yong-Hyeon (surname Pyun), who helps maintain this driver. He might have some patches for you. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
if_re is broken on RELENG_7 ?
Hi list, I have ASUS a6m laptop with integrated RTL8168/8111 PCI-E Gigabit Ethernet NIC, long time ago (7.0-CURRENT - 7.0-prerelease) I used it. Than I started to enjoy BCM43XX wi-fi adapter and now I recently decided to revert to the use of realtek adapter. But it doesn't work. I'm just not running a network card or at all does not work? some additional information: ifconfig shows such information, regardless of whether the cable is connected: %ifconfig re0 re0: flags=8802 metric 0 mtu 1500 options=389b ether 00:1a:92:ca:b3:bc media: Ethernet autoselect (10baseT/UTP ) status: no carrier [EMAIL PROTECTED] -lv | grep re0 -A 4 [EMAIL PROTECTED]:2:0:0: class=0x02 card=0x11f51043 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet dmesg output: http://tiger.byfly.by/files/dmesg.boot kernel config: http://tiger.byfly.by/files/tiger-asus-a6m p.s.: Excuse me for my English :) -- wbr, tiger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: resource leak
On Wed, 2008-10-01 at 16:36 -0400, Stephen Clark wrote: > Robert Watson wrote: > > On Wed, 1 Oct 2008, Gary Palmer wrote: > > > >> "ps alxw" may be of interest in addition to "ps auxw" as it displays > >> what the processes are waiting on. It could conceivably be a problem > >> of some kind at the filesystem level. I've seen situations before > >> where a problem escalates to the point where "ls /" hangs, and at that > >> point you're stuck with an unresponsive box. > > > > If you want an even greater level of detail than ps -l, you can use > > procstat -k to generate kernel stack traces for all user/kernel > > threads. Wait channels are very useful, but they only tell you what the > > code that invoked the wait thinks it is for, not how that code was > > reached. A classic example is waiting on an exhausted UMA zone -- you > > get a uma wait channel, but no indication of what subsystem performed > > the memory allocation... This required FreeBSD 7.1 and higher, > > however. (Obviously, the same can be done easily using DDB, but that's > > hard on a box without a serial console, and requires interrupting the > > flow of the operating system, compiling with DDB, etc). > > > > Robert N M Watson > > Computer Laboratory > > University of Cambridge > > > A big part of problem is this seems to take about 100 days of uptime to > occur. > We have some inhouse test boxes but have never seen the problem, probably > because non of them have been up more than about 45 days. The units in the > field, of which there is about 300, are headless and none are physically > close. > > When the boxes are rebooted there are no error messages in any of the log > files, > only the absence of information that would normally be logged by new > processes > that would be spawned. We are getting ready to install a patch that will try > to > gather more information. > > I thought about writing an app the would try to fork a child periodically and > record in a log file if there was an error. But EAGAIN is nonspecific as to > the > real reason the fork failed. I was looking for some way to periodically log > the > resources that would cause the fork failure. > > procstat -k looks like it would have been a good candidate but unfortunately > we > are running 6.1. > > Thanks for the response. > Steve I have a VIA EPIA-based system that was rebooting and not leaving behind any diagnosable evidence that I could find. Attaching a serial console revealed a kernel-trap which was double-faulting as it went to write the kernel dump. I've not yet had the opportunity to investigate further except that out of desperation I threw in an additional 64M of RAM - all I had to hand - adding to its 256M and I haven't seen it fault again in the 37 days since (it would often stay up for less than a day before that). I wonder whether it would be worth your while running a bench unit with limited RAM, either physically or via the hw.physmem tunable. I would probably try to identify the amount of RAM that just allows it to run "normally", ideally subjecting it to a typical workload if possible. If it bombs after running for a reasonable length of time, add back a fraction of the unused memory and see if it then stays up proportionally longer which could be indicative of a memory starvation issue. If you can get it to bomb in the above scenario then you can probably get some insight into where it's failing. Having said that, I should point out that I've not actually used the above technique so I may well be overlooking something which might prevent it from being useful or indeed from "working" at all. Wayne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
