5.4-RC3 Kernel Panic: vinvalbuf: dirty bufs (backtrace included)

2005-04-23 Thread Viktor Rosendahl
Hi, Last night when I was asleep my FreeBSD workstation suffered a kernel panic and did a coredump. The panic occurred at 3.02 AM, that is one minute after the start of the daily script (coincidence?). The only unusual thing I have been doing before the panic was that I was playing with a 1GB

Cypress Semiconductor USB2.0 Storage Device problems on 5.4-RC3

2005-04-23 Thread Domi
Hi guys. I hooked up a new USB2 case (MyBOX Sarotech black/silver) with a 120GB Hitachi Deskstar in it to my Compaq AP550 workstation running FreeBSD 5.4-RC3. $ uname -a FreeBSD canis.local 5.4-RC3 FreeBSD 5.4-RC3 #1: Fri Apr 22 22:03:02 CEST 2005 [EMAIL

Re: Cypress Semiconductor USB2.0 Storage Device problems on 5.4-RC3

2005-04-23 Thread Domi
i googled and found this link: http://lists.freebsd.org/pipermail/freebsd-usb/2004-December/000377.html is this still current or is there anything else I should do? Thanks Domi On Sat, 23 Apr 2005 16:44:53 +0200 Domi [EMAIL PROTECTED] wrote: Hi guys. I hooked up a new USB2 case (MyBOX

[releng_5 tinderbox] failure on alpha/alpha

2005-04-23 Thread FreeBSD Tinderbox
TB --- 2005-04-23 15:22:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-23 15:22:00 - starting RELENG_5 tinderbox run for alpha/alpha TB --- 2005-04-23 15:22:01 - checking out the source tree TB --- 2005-04-23 15:22:01 - cd /home/tinderbox/RELENG_5/alpha/alpha TB ---

panic: mutex tty owned at ../../../kern/kern_event.c:1487

2005-04-23 Thread Dan Nelson
Got the following on a 2004-04-21 -stable kernel: panic messages: --- panic: mutex tty owned at ../../../kern/kern_event.c:1487 cpuid = 0 KDB: stack backtrace: kdb_backtrace(c07c93fb,0,c07aed2c,e97b799c,c3d05780) at kdb_backtrace+0x2e panic(c07aed2c,c07a955e,c07acb39,5cf,c383c800) at panic+0x139

[releng_5 tinderbox] failure on amd64/amd64

2005-04-23 Thread FreeBSD Tinderbox
TB --- 2005-04-23 16:30:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-23 16:30:14 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-04-23 16:30:14 - checking out the source tree TB --- 2005-04-23 16:30:14 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB ---

[releng_5 tinderbox] failure on i386/i386

2005-04-23 Thread FreeBSD Tinderbox
TB --- 2005-04-23 17:50:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-04-23 17:50:56 - starting RELENG_5 tinderbox run for i386/i386 TB --- 2005-04-23 17:50:56 - checking out the source tree TB --- 2005-04-23 17:50:56 - cd /home/tinderbox/RELENG_5/i386/i386 TB --- 2005-04-23

Re: 5.4-RC3 hung - DDB trace/ps provided [possible cause found]

2005-04-23 Thread Ash
Ash wrote: Ash wrote: I've included copies of ddb's ps output and a dmesg as attachments. Here is a trace (pid 95 is bufdaemon): Replying to myself because I just noticed that the ddb ps output wasn't attached as promised. Computers are hard, let me try this again... :) Apologies for replying

Re: panic: mutex tty owned at ../../../kern/kern_event.c:1487

2005-04-23 Thread John-Mark Gurney
Dan Nelson wrote this message on Sat, Apr 23, 2005 at 12:28 -0500: Got the following on a 2004-04-21 -stable kernel: panic messages: --- panic: mutex tty owned at ../../../kern/kern_event.c:1487 cpuid = 0 [...] #0 doadump () at pcpu.h:159 #1 0xc05b44aa in boot (howto=260) at

NEC uPD 720100 USB 2.0 controller () not working on FreeBSD 5.4-STABLE i386 (2005-04-23)

2005-04-23 Thread Raphael H. Becker
Hello *, The NEC uPD 720100 USB 2.0 controller doesn's seem to work. This controller is on a Longshine LCS-8033H PCI USB Card and is a low cost standard-USB2-controller at my local electronics store. [EMAIL PROTECTED]:~# dmesg | egrep (^usb3|^uhub3) usb3: EHCI version 1.0 usb3: companion

Re: panic: mutex tty owned at ../../../kern/kern_event.c:1487

2005-04-23 Thread Dan Nelson
In the last episode (Apr 23), John-Mark Gurney said: Dan Nelson wrote this message on Sat, Apr 23, 2005 at 12:28 -0500: Got the following on a 2004-04-21 -stable kernel: panic messages: --- panic: mutex tty owned at ../../../kern/kern_event.c:1487 cpuid = 0 I can whip up a patch