iwn crashes in current (r282269)

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:

Re: iwn crashes in current (r282269)

Hi, On 2 May 2015 at 00:02, Poul-Henning Kamp p...@phk.freebsd.dk 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:

Re: 2 crashes.... (today's -CURRENT)

On Sat, Aug 24, 2013 at 6:47 PM, Larry Rosenman l...@lerctr.org wrote: Both full core.txt's are available at: http://www.lerctr.org/~ler/**FreeBSD/http://www.lerctr.org/~ler/FreeBSD/ Larry, I am not certain I can be of much help but i am curious what hardware you have. do you have a full

Re: 2 crashes.... (today's -CURRENT)

On Mon, 26 Aug 2013, Sam Fourman Jr. wrote: On Sat, Aug 24, 2013 at 6:47 PM, Larry Rosenman l...@lerctr.org wrote: Both full core.txt's are available at: http://www.lerctr.org/~ler/**FreeBSD/http://www.lerctr.org/~ler/FreeBSD/ Larry, I am not certain I can be of much help but i am curious

Re: 2 crashes.... (today's -CURRENT)

And a 4th: borg.lerctr.org dumped core - see /var/crash/vmcore.3 Sun Aug 25 01:52:10 CDT 2013 FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r254807: Sat Aug 24 16:52:42 CDT 2013 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 panic: page fault GNU gdb 6.1.1

Re: 2 crashes.... (today's -CURRENT)

On Sun, Aug 25, 2013 at 01:56:55AM -0500, Larry Rosenman wrote: And a 4th: borg.lerctr.org dumped core - see /var/crash/vmcore.3 All the traces have little in common except a feel of the random memory corruption. Note that you are the only reporter of such mass panics, so the problem

2 crashes.... (today's -CURRENT)

Both full core.txt's are available at: http://www.lerctr.org/~ler/FreeBSD/ borg.lerctr.org dumped core - see /var/crash/vmcore.0 Sat Aug 24 17:35:31 CDT 2013 FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r254807: Sat Aug 24 16:52:42 CDT 2013

Re: 2 crashes.... (today's -CURRENT)

And another: borg.lerctr.org dumped core - see /var/crash/vmcore.2 Sat Aug 24 20:29:48 CDT 2013 FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r254807: Sat Aug 24 16:52:42 CDT 2013 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 panic: sorele GNU gdb 6.1.1

Re: Crashes with current on X220

Hi, On Sat, 06 Jul 2013 21:20:03 -0700 matt sendtom...@gmail.com wrote: On 07/06/13 19:40, Super Bisquit wrote: Look in the mailing list for Fixing X220 Video the right way. Did I miss something? I'm not sure it's related at all...? you are right. But it did not crash anymore since

Re: Crashes with current on X220

Hi, On Sat, 6 Jul 2013 21:50:20 -0700 Adrian Chadd adr...@freebsd.org wrote: Can you try installing some 10-amd64 snapshots between then and now, and see roughly when it was introduced? I tried to upgrade my machine since March with the same result. But .. There's been a lot of ACPI

Re: Crashes with current on X220

Look in the mailing list for Fixing X220 Video the right way. On Fri, Jul 5, 2013 at 8:14 PM, Erich Dollansky er...@alogt.com wrote: Hi, I updated my rock solid FreeBSD 10 installation from what was current this January to FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2

Re: Crashes with current on X220

On 07/06/13 19:40, Super Bisquit wrote: Look in the mailing list for Fixing X220 Video the right way. Did I miss something? I'm not sure it's related at all...? Matt ___ freebsd-current@freebsd.org mailing list

Re: Crashes with current on X220

Hi, Can you try installing some 10-amd64 snapshots between then and now, and see roughly when it was introduced? There's been a lot of ACPI changes over the last 6 months. It wouldn't surprise me to find one or more of those messed things up. -adrian On 5 July 2013 17:14, Erich Dollansky

Crashes with current on X220

Hi, I updated my rock solid FreeBSD 10 installation from what was current this January to FreeBSD X220.ovitrap.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r252491M: Wed Jul 3 08:45:23 CIT 2013 r...@x220.ovitrap.com:/usr/obj/usr/src/sys/X220 amd64 I have since then frequent crashes. Nothing is

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

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

md(4) crashes in current

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

Re: ATTN: people who were getting CVSup crashes under -current

On 2002-10-09 20:37, John Polstra [EMAIL PROTECTED] wrote: I am trying to understand the CVSup crashes that were reported by some -current users during the past week or two. I realize the crashes had to do with changes in the ucontext structure, but I am trying to understand why those

Re: ATTN: people who were getting CVSup crashes under -current

John Polstra writes: I am trying to understand the CVSup crashes that were reported by some -current users during the past week or two. I realize the crashes had to do with changes in the ucontext structure, but I am trying to understand why those changes mattered. My theory is that the

ATTN: people who were getting CVSup crashes under -current

Folks, I am trying to understand the CVSup crashes that were reported by some -current users during the past week or two. I realize the crashes had to do with changes in the ucontext structure, but I am trying to understand why those changes mattered. My theory is that the changes would matter

Re: ATTN: people who were getting CVSup crashes under -current

On Wed, Oct 09, 2002 at 20:37:39 -0700, John Polstra wrote: understand why those changes mattered. My theory is that the changes would matter to the old pm3 port, but not to the newer ezm3 port. If you experienced the crashes, please check which Modula-3 version you have using pkg_info and

crashes in -current

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

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

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 me, and two users running breakwidgets binary testing script, which

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

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

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

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 me, and two users running breakwidgets binary testing