Date: Fri, 23 Apr 2010 19:29:31 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= <olivier@cochard.me> Cc: Bernhard Schmidt <bschmidt@techwires.net>, freebsd-stable@freebsd.org Subject: Re: iwn firmware instability with an up-to-date stable kernel Message-ID: <v2w7d6fde3d1004231929yb5b54ac6rc3a90276014176b0@mail.gmail.com> In-Reply-To: <r2q3131aa531004180456w49eea301t526d305c8e7a980a@mail.gmail.com> References: <w2s3131aa531004171849i12348bdbt12dfbb18c1f71bc2@mail.gmail.com> <20100418081400.GA40496@mx.techwires.net> <r2q3131aa531004180456w49eea301t526d305c8e7a980a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/4/18 Olivier Cochard-Labbé <olivier@cochard.me>: > 2010/4/18 Bernhard Schmidt <bschmidt@techwires.net>: >> Are you able to reproduce this on demand? As in type a few commands and >> the firmware error occurs? >> > > No, I'm not able to reproduce on demand this problem. I'm seeing similar issues on occasion with my Lenovo as well: Apr 23 19:25:24 garrcoop-fbsd kernel: firmware error log: Apr 23 19:25:24 garrcoop-fbsd kernel: error type = "NMI_INTERRUPT_WDG" (0x00000004) Apr 23 19:25:24 garrcoop-fbsd kernel: program counter = 0x0000046C Apr 23 19:25:24 garrcoop-fbsd kernel: source line = 0x000000D0 Apr 23 19:25:24 garrcoop-fbsd kernel: error data = 0x0000000207030000 Apr 23 19:25:24 garrcoop-fbsd kernel: branch link = 0x00008370000004C2 Apr 23 19:25:24 garrcoop-fbsd kernel: interrupt link = 0x000006DA000018B8 Apr 23 19:25:24 garrcoop-fbsd kernel: time = 4287402440 Apr 23 19:25:24 garrcoop-fbsd kernel: driver status: Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 0: qid=0 cur=1 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 1: qid=1 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 2: qid=2 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 3: qid=3 cur=36 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 4: qid=4 cur=123 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 5: qid=5 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 6: qid=6 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 7: qid=7 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 8: qid=8 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 9: qid=9 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 10: qid=10 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 11: qid=11 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 12: qid=12 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 13: qid=13 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 14: qid=14 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 15: qid=15 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: rx ring: cur=8 This may be because the system was under load (I was installing a port shortly before the connection dropped). I'll try poking at this further because it's going to be an annoying productivity loss :/. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v2w7d6fde3d1004231929yb5b54ac6rc3a90276014176b0>