Re: iwn crashes in current (r282269)

2015-05-02 Thread Adrian Chadd
Hi, On 2 May 2015 at 00:02, Poul-Henning Kamp wrote: > May 2 01:01:34 critter kernel: iwn0: device timeout > May 2 01:01:34 critter kernel: firmware: 'iwn6000g2afw' version 0: 677296 > bytes loaded at 0x81f880c0 > May 2 01:01:34 critter kernel: iwn0: iwn_read_firmware: ucode rev=0x12

iwn crashes in current (r282269)

2015-05-02 Thread Poul-Henning Kamp
May 2 01:01:34 critter kernel: iwn0: device timeout May 2 01:01:34 critter kernel: firmware: 'iwn6000g2afw' version 0: 677296 bytes loaded at 0x81f880c0 May 2 01:01:34 critter kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 May 2 01:01:40 critter kernel: iwn0: iwn_tx_data: m=0xff

Two crashes in CURRENT from October 7th, both mention Xint0x80_syscall()

2003-10-29 Thread Eivind Olsen
Hello. I've experienced some crashes here with FreeBSD 5.1-CURRENT from October 7th. I tried yesterday to upgrade to a more recent CURRENT but it crashed (the 2nd. crash here). Both crashes stop at different places, but they both refer to Xint0x80_syscall - I don't know if this is relevant or no

md(4) crashes in current

2003-03-17 Thread Kevin Oberman
After configuring an md in current (as of last Friday), I will later panic. Unfortunately (or not), the kernel on this system was built without symbols, witness, invariants, or debugger. So I built a new kernel with all of those things and...no more panics. Makes debug a bit difficult. I then bui

crashes in -current

2002-07-02 Thread Seth Hettich
I'm still getting these crashes: Panicstring: bremfree: bp 0xc772a840 not locked and: Panicstring: Most recently used by kqueue On two very different systems (both PC's). I have more info in PR 38438. Is this happening to other people? -Seth To Unsubscribe: send mail to [EMAIL PROTECTED]

Re: repost of procfs crashes in -CURRENT (no html)..

2000-02-18 Thread Luoqi Chen
> Kernel: > === > FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb > 14 23:00:42 GMT 2000 > [EMAIL PROTECTED]:/usr/src/sys/compile/KARMA i386 > > Background: > > 3 users. One with X running , and two users running breakwidgets > , which make use of a

Re: repost of procfs crashes in -CURRENT (no html)..

2000-02-18 Thread Poul-Henning Kamp
The real solution is to make killall(1)s funtionality part of kill(1) and avoid reading /proc so that we don't even have to mount /proc. Poul-Henning In message <[EMAIL PROTECTED]>, Thomas Stromberg writes: >3 users. One with X running , and two users running breakwidgets >, which make use of

repost of procfs crashes in -CURRENT (no html)..

2000-02-18 Thread Thomas Stromberg
Sorry about the html posting, it seems that Mozilla M13 decided to rape my message. I hate html postings just as much as you do (thank god for procmail filters), and will send this one using pine so Mozilla doesn't try to rethink my e-mail for me. Kernel: === FreeBSD karma.afterthought.org