Re: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
It works fine. When I grep the dmesg, I can find this message. -- Best regards, Yanhui ___ 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: em0 with latest driver hangs again and again (without "Watchdog timeout" message!)
Hello, Brandon. You wrote 3 марта 2011 г., 17:08:26: > I see that you have CRC errors: > dev.em.0.mac_stats.crc_errs: 156 > and receive errors: > dev.em.0.mac_stats.recv_errs: 147 It (almost) doesn't change. And it hangs again. It seems, that 7.2.2 hangs more often than 7.1.9 on my hardware :( -- // Black Lion AKA Lev Serebryakov ___ 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: em0 with latest driver hangs again and again (without "Watchdog timeout" message!)
Hello, Brandon. You wrote 3 марта 2011 г., 17:08:26: > I see that you have CRC errors: > dev.em.0.mac_stats.crc_errs: 156 > and receive errors: > dev.em.0.mac_stats.recv_errs: 147 > You probably have a hardware problem. Is this the only machine on > which you're experiencing the problem? It is only machine with Intel NIC in my network. I'll try to replace patchcord... -- // Black Lion AKA Lev Serebryakov ___ 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: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
On Wednesday, March 02, 2011 7:39:56 pm Yanhui Shen wrote: > `CPU0: local APIC error 0x40" > > I get this error on my ThinkPad R400(Intel Core2 T6570). Do you get a hang or does the machine keep working fine? -- John Baldwin ___ 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: em0 with latest driver hangs again and again (without "Watchdog timeout" message!)
On Thu, Mar 3, 2011 at 2:10 AM, Lev Serebryakov wrote: > Hello, Arnaud. > You wrote 2 марта 2011 г., 9:55:50: > I have been running with 7.2.2 and so far so good. However, its hard to say in my case as the box I would only periodically see the issue. >>> As I wrote to Jack, my NIC hangs today with 7.2.2 >> Do you have any detailed error ? What the output of sysctl "dev.em.X" >> where X is the index of the hung interface ? > One more hang. Two logs are attached. > > -- > // Black Lion AKA Lev Serebryakov I see that you have CRC errors: dev.em.0.mac_stats.crc_errs: 156 and receive errors: dev.em.0.mac_stats.recv_errs: 147 You probably have a hardware problem. Is this the only machine on which you're experiencing the problem? -Brandon ___ 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: NFS client over udp
--- On Wed, 2/23/11, Rick Macklem wrote: > From: Rick Macklem > Subject: Re: NFS client over udp > To: "Kirill Yelizarov" > Cc: freebsd-stable@freebsd.org > Date: Wednesday, February 23, 2011, 1:35 AM > > --- On Tue, 2/22/11, Rick > Macklem > wrote: > > > > > From: Rick Macklem > > > Subject: Re: NFS client over udp > > > To: "Kirill Yelizarov" > > > Cc: freebsd-stable@freebsd.org > > > Date: Tuesday, February 22, 2011, 2:10 AM > > > > --- On Sun, 2/20/11, Rick > > > Macklem > > > wrote: > > > > > > > > > From: Rick Macklem > > > > > Subject: Re: NFS client over udp > > > > > To: "Kirill Yelizarov" > > > > > Cc: freebsd-stable@freebsd.org > > > > > Date: Sunday, February 20, 2011, 9:02 > PM > > > > > > --- On Fri, 2/18/11, Kirill > > > > > Yelizarov > > > > > > > > On Fri, Feb 18, 2011 at > > > 05:27:00AM > > > > > > > > -0800, Kirill Yelizarov > wrote: > > > > > > > > > I have a > reproducible memory > > > leak when > > > > > using nfs > > > > > > > > client with an old > > > > > > > > > nfs server > > > > > > > > > > > > and mbufs used > > > > > > 8193/1722/9915 mbufs in use > > > (current/cache/total) > > > > > > 8192/1264/9456/25600 mbuf clusters > in use > > > > > (current/cache/total/max) > > > > > > 8192/605 mbuf+clusters out of > packet > > > secondary zone in > > > > > use > > > > > > (current/cache) > > > > > > 0/768/768/12800 4k (page size) > jumbo > > > clusters in use > > > > > > (current/cache/total/max) > > > > > > 0/0/0/6400 9k jumbo clusters in > use > > > > > (current/cache/total/max) > > > > > > 0/0/0/3200 16k jumbo clusters in > use > > > > > (current/cache/total/max) > > > > > > 18432K/6030K/24462K bytes > allocated to > > > network > > > > > (current/cache/total) > > > > > > 0/0/0 requests for mbufs denied > > > > > (mbufs/clusters/mbuf+clusters) > > > > > > 0/0/0 requests for jumbo clusters > denied > > > (4k/9k/16k) > > > > > > 0/0/0 sfbufs in use > (current/peak/max) > > > > > > 0 requests for sfbufs denied > > > > > > 0 requests for sfbufs delayed > > > > > > 0 requests for I/O initiated by > sendfile > > > > > > 0 calls to protocol drain > routines > > > > > > > > > > > > Kirill > > > > > > > > > > > You could try the attached patch. It > fixes the > > > only places > > > > > in the > > > > > client side krpc over udp that seems > mights cause > > > a leak. I > > > > > have no > > > > > idea if it will help, since these cases > should > > > rarely, if > > > > > ever, > > > > > happen in practice. > > > > > > > > > > Please let us know if you have the > chance to try > > > the patch > > > > > and > > > > > whether or not it helped. > > > > > > > > > > rick > > > > > > > > > Rick, i tried your patch. Fortunately it > didn't help > > > me. There are no > > > > warnings on console and memory is climbing > up during > > > syncs and not > > > > freed later. I'll try to switch to tcp this > evening. > > > Thanks for help > > > > > > > I'll assume that's unfortunately;-) Since the two > cases > > > patched probably > > > never happen, I'm not surprised. > > > > > > The only other thing I can think of that you > could try is > > > switching to > > > the experimental client. This would identify if > the bug is > > > in the regular > > > client or somewhere further down in the rpc > transport. > > > > > > The mount command would look something like: > > > # mount -t newnfs -o nfsv3,udp > : > > > > > > > > I added options NFSCL to my kernel and tried to mount. > mount shows > > everything is ok: > > 192.168.0.35:/home on /mnt (newnfs) > > but when i try to cd /mnt i get permission denied > > my export allow root and everything is done as root. > What am i doing > > wrong? > > > Try adding the "resvport" option. I don't think it's a > default for > the experimental client at this time. (I have a series of > patches > for the client that will go into head in April that brings > it in > line with the regular client, including same default mount > options.) Rick, I have good news. I upgraded to 8.2-stable and i ran all four different tests (nfs client new and old and over udp and tcp) and found that there is no leak in either. ALl of them behave almost the same, i couldn't find any difference. The speed i achieved on 1Gb link is 52Mb/s. The only difference is that i can't umount new nfs client even if there are no processes using this mount point. Thanks for help Kirill ___ 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: em0 with latest driver hangs again and again (without "Watchdog timeout" message!)
Hello, Arnaud. You wrote 2 марта 2011 г., 9:55:50: >>> I have been running with 7.2.2 and so far so good. However, its hard to >>> say in my case as the box I would only periodically see the issue. >> As I wrote to Jack, my NIC hangs today with 7.2.2 > Do you have any detailed error ? What the output of sysctl "dev.em.X" > where X is the index of the hung interface ? One more hang. Two logs are attached. -- // Black Lion AKA Lev Serebryakov em0.7.2.2.hang1.log Description: Binary data em0.7.2.2.hang2.log Description: Binary data ___ 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: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
On 3 Mar, 2011, at 02:39 , Yanhui Shen wrote: > `CPU0: local APIC error 0x40" > > I get this error on my ThinkPad R400(Intel Core2 T6570). > > > -- > Best regards, > Yanhui > ___ > 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" I saw this error too a few days ago, it was wen I plugged a USB keyboard to a HP EX470 machine. ___ 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"
