From bugmaster at FreeBSD.org Mon Aug 3 11:06:56 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 3 11:08:14 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200908031106.n73B6twI088569@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From bugmaster at FreeBSD.org Mon Aug 10 11:06:54 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 10 11:07:53 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200908101106.n7AB6rnS025116@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From eldar at djangohosting.ru Fri Aug 14 00:32:56 2009 From: eldar at djangohosting.ru (Eldar T. Zaitov) Date: Fri Aug 14 00:33:02 2009 Subject: kernel panic on CURRENT Message-ID: <4A84E484.5020002@djangohosting.ru> Hi after removing firewire from kernel and using it as module i receive kernel panic in BUS reset. how to reproduce: # kldload firewire.ko commenting out code -- cut -- if (!kdb_active) taskqueue_enqueue(sc->fc.taskqueue, &sc->fwohci_task_busreset); -- cut -- in function static void fwohci_intr_core preverts kernel panic, but I'm sure it's not a solution. kldstat: Id Refs Address Size Name 1 45 0xc0400000 7e8bd4 kernel 3 1 0xc0c0b000 1b778 snd_hda.ko 4 2 0xc0c27000 702b4 acpi.ko 5 1 0xc0c98000 5030 acpi_ibm.ko 6 1 0xc0c9e000 c1d4 uhci.ko 7 1 0xc0cab000 eaf4 ehci.ko 8 1 0xc44ba000 b000 ntfs.ko 9 1 0xc467e000 2f000 pf.ko 10 1 0xc4730000 f000 nfslockd.ko if it matter - kernel was build without kdb. Thank you. From sean.bruno at dsl-only.net Fri Aug 14 02:41:34 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Fri Aug 14 02:41:40 2009 Subject: kernel panic on CURRENT In-Reply-To: <4A84E484.5020002@djangohosting.ru> References: <4A84E484.5020002@djangohosting.ru> Message-ID: <1250217692.8589.15.camel@Lappy> On Fri, 2009-08-14 at 04:13 +0000, Eldar T. Zaitov wrote: > Hi > > after removing firewire from kernel and using it as module i receive > kernel panic in BUS reset. > how to reproduce: > # kldload firewire.ko > > commenting out code > -- cut -- > if (!kdb_active) > taskqueue_enqueue(sc->fc.taskqueue, &sc->fwohci_task_busreset); > -- cut -- > in function > static void fwohci_intr_core > preverts kernel panic, but I'm sure it's not a solution. > > kldstat: > Id Refs Address Size Name > 1 45 0xc0400000 7e8bd4 kernel > 3 1 0xc0c0b000 1b778 snd_hda.ko > 4 2 0xc0c27000 702b4 acpi.ko > 5 1 0xc0c98000 5030 acpi_ibm.ko > 6 1 0xc0c9e000 c1d4 uhci.ko > 7 1 0xc0cab000 eaf4 ehci.ko > 8 1 0xc44ba000 b000 ntfs.ko > 9 1 0xc467e000 2f000 pf.ko > 10 1 0xc4730000 f000 nfslockd.ko > > if it matter - kernel was build without kdb. > > Thank you. > Interesting. Please post the full panic trace when you load firewire as a module. Sean From eldar at djangohosting.ru Fri Aug 14 16:30:41 2009 From: eldar at djangohosting.ru (Eldar T. Zaitov) Date: Fri Aug 14 16:30:49 2009 Subject: kernel panic on CURRENT Message-ID: <4A85C963.8000201@djangohosting.ru> Hi fwohci0: <1394 Open Host Controller Interface> mem 0xe4301000-0xe43017ff,0xe4304000-0xe4307fff irq 17 at device 0.1 on pci21 fwohci0: latency timer 0 -> 32. fwohci0: cache size 0 -> 8. fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 0a:00:06:e4:20:45:7b:15 fwohci0: resetting OHCI...done (loop=0) fwohci0: fwphy_rddata:: 0x2 loop=0, retry=0 fwohci0: fwphy_rddata:: 0x3 loop=0, retry=0 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: fwphy_rddata:: 0x5 loop=0, retry=0 fwohci0: Enable 1394a Enhancements fwohci0: fwphy_rddata:: 0x5 loop=0, retry=0 fwohci0: fwphy_rddata:: 0x2 loop=0, retry=0 fwohci0: fwphy_rddata:: 0x4 loop=0, retry=0 fwohci0: fwphy_rddata:: 0x4 loop=0, retry=0 fwohci0: fwphy_rddata:: 0x4 loop=0, retry=0 fwohci0: Link S400, max_rec 2048 bytes. fwohci0: BUS_OPT 0xa002 -> 0xf800a002 fwohci0: fwohci_set_intr: 1 fwohci0: phy int firewire0: on fwohci0 fwohci0: fwohci_intr_core: BUS reset Fatal trap 12: page fault while in kernel mode fault virtual address = 0x18 fault code = supervisor write, page not present instruction pointer = 0x20:0xc6aebe80 stack pointer = 0x28:0xe69fbc50 frame pointer = 0x28:0xe69fbc78 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (fw0_taskq) panic: from debugger ddb said: stopped at fw_busreset+0x140 here is backtrace: #0 doadump () at pcpu.h:246 #1 0xc070f373 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xc070f5ad in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:579 #3 0xc046e7a7 in db_panic (addr=Could not find the frame base for "db_panic". ) at /usr/src/sys/ddb/db_command.c:478 #4 0xc046ed31 in db_command (last_cmdp=0xc0a93d9c, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:445 #5 0xc046ee8a in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #6 0xc0470cfd in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:229 #7 0xc07386d4 in kdb_trap (type=12, code=0, tf=0xe69fbc10) at /usr/src/sys/kern/subr_kdb.c:535 #8 0xc08f952f in trap_fatal (frame=0xe69fbc10, eva=24) at /usr/src/sys/i386/i386/trap.c:922 #9 0xc08f97d0 in trap_pfault (frame=0xe69fbc10, usermode=0, eva=24) at /usr/src/sys/i386/i386/trap.c:844 #10 0xc08fa162 in trap (frame=0xe69fbc10) at /usr/src/sys/i386/i386/trap.c:526 #11 0xc08df96b in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #12 0xc6aebe80 in fw_busreset () from /boot/kernel/firewire.ko #13 0xc6aef358 in fwohci_task_busreset () from /boot/kernel/firewire.ko #14 0xc0743a92 in taskqueue_run (queue=0xc65fba00) at /usr/src/sys/kern/subr_taskqueue.c:282 #15 0xc0743e2f in taskqueue_thread_loop (arg=0xc627449c) at /usr/src/sys/kern/subr_taskqueue.c:403 #16 0xc06e66e0 in fork_exit (callout=0xc0743db0 , ---Type to continue, or q to quit--- arg=0xc627449c, frame=0xe69fbd38) at /usr/src/sys/kern/kern_fork.c:838 #17 0xc08df9e0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 Hope it help. Do you need any additional info? From bugmaster at FreeBSD.org Mon Aug 17 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 17 11:07:52 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200908171106.n7HB6qF8075759@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From sean.bruno at dsl-only.net Thu Aug 20 08:15:16 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Thu Aug 20 08:15:22 2009 Subject: Have *you* disabled Firewire? Message-ID: <1250756114.23644.8.camel@Lappy> I'm seeing evidence that the Firewire stack has been problematic for a small, but growing set of users out there. I see from a perusal of the mailing lists, that some users are disabling their Firewire stack after they cannot boot or install FreeBSD. This usually is due to a panic preceded by the message:" "run_interrupt_driven_hooks - waiting for xpt_config" This log message was added in the past to provide a diagnostic indication of a failure. If you are one of these folks who have disabled their Firewire driver, please let me know. Also get me the following: Full boot dmesg output (bootverbose) Can you load "firewire"?(in kernel? after boot via module?) Can you load "sbp"?(in kernel? after boot via module?) *anything* else you might thing is relevant? Sean From js at alien8.de Thu Aug 20 21:51:49 2009 From: js at alien8.de (Julian Stecklina) Date: Thu Aug 20 21:51:55 2009 Subject: Have *you* disabled Firewire? References: <1250756114.23644.8.camel@Lappy> Message-ID: <87hbw2gnn3.fsf@tabernacle.localhost> Sean Bruno writes: > I'm seeing evidence that the Firewire stack has been problematic for a > small, but growing set of users out there. I see from a perusal of the > mailing lists, that some users are disabling their Firewire stack after > they cannot boot or install FreeBSD. This usually is due to a panic > preceded by the message:" > "run_interrupt_driven_hooks - waiting for xpt_config" Panic? Most people reported hangs, haven't they? > This log message was added in the past to provide a diagnostic > indication of a failure. > > If you are one of these folks who have disabled their Firewire driver, > please let me know. Also get me the following: > Full boot dmesg output (bootverbose) > Can you load "firewire"?(in kernel? after boot via module?) > Can you load "sbp"?(in kernel? after boot via module?) > *anything* else you might thing is relevant? I did provide this some months ago for my AMD 780G-based board. Was there anything that looked suspicious? Is it worth retrying? Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge From sean.bruno at dsl-only.net Thu Aug 20 23:55:45 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Thu Aug 20 23:56:01 2009 Subject: Have *you* disabled Firewire? In-Reply-To: <87hbw2gnn3.fsf@tabernacle.localhost> References: <1250756114.23644.8.camel@Lappy> <87hbw2gnn3.fsf@tabernacle.localhost> Message-ID: <1250812543.2680.21.camel@Lappy> [ removing -current ] On Thu, 2009-08-20 at 23:51 +0200, Julian Stecklina wrote: > Sean Bruno writes: > > > I'm seeing evidence that the Firewire stack has been problematic for a > > small, but growing set of users out there. I see from a perusal of the > > mailing lists, that some users are disabling their Firewire stack after > > they cannot boot or install FreeBSD. This usually is due to a panic > > preceded by the message:" > > "run_interrupt_driven_hooks - waiting for xpt_config" > > Panic? Most people reported hangs, haven't they? > Hangs yes. If one waits long enough(2 minutes I think), it will panic. > > This log message was added in the past to provide a diagnostic > > indication of a failure. > > > > If you are one of these folks who have disabled their Firewire driver, > > please let me know. Also get me the following: > > Full boot dmesg output (bootverbose) > > Can you load "firewire"?(in kernel? after boot via module?) > > Can you load "sbp"?(in kernel? after boot via module?) > > *anything* else you might thing is relevant? > > I did provide this some months ago for my AMD 780G-based board. Was > there anything that looked suspicious? Is it worth retrying? > > Regards, I'm trying to gather information, thanks for the reminder about your specific hardware. (JMicron based) I've got the same failures reported with JMicron and NVidia based controllers. I will peruse the logs of all the failures and try to come up with something soon. :) Sean From js at alien8.de Sun Aug 23 17:35:58 2009 From: js at alien8.de (Julian Stecklina) Date: Sun Aug 23 17:36:10 2009 Subject: Have *you* disabled Firewire? References: <1250756114.23644.8.camel@Lappy> <87hbw2gnn3.fsf@tabernacle.localhost> <1250812543.2680.21.camel@Lappy> Message-ID: <87fxbiph5m.fsf@tabernacle.localhost> Sean Bruno writes: > I'm trying to gather information, thanks for the reminder about your > specific hardware. (JMicron based) > > I've got the same failures reported with JMicron and NVidia based > controllers. I will peruse the logs of all the failures and try to come > up with something soon. :) This would be much appreciated! If there is any way to support you on this, just say so. Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge From andrew-freebsd at areilly.bpc-users.org Mon Aug 24 02:53:26 2009 From: andrew-freebsd at areilly.bpc-users.org (Andrew Reilly) Date: Mon Aug 24 02:53:32 2009 Subject: Have *you* disabled Firewire? In-Reply-To: <1250756114.23644.8.camel@Lappy> References: <1250756114.23644.8.camel@Lappy> Message-ID: <20090824014933.GA52180@duncan.reilly.home> On Thu, Aug 20, 2009 at 01:15:14AM -0700, Sean Bruno wrote: > I'm seeing evidence that the Firewire stack has been problematic for a > small, but growing set of users out there. I see from a perusal of the > mailing lists, that some users are disabling their Firewire stack after > they cannot boot or install FreeBSD. This usually is due to a panic > preceded by the message:" > "run_interrupt_driven_hooks - waiting for xpt_config" > > This log message was added in the past to provide a diagnostic > indication of a failure. > > If you are one of these folks who have disabled their Firewire driver, > please let me know. Also get me the following: > Full boot dmesg output (bootverbose) > Can you load "firewire"?(in kernel? after boot via module?) > Can you load "sbp"?(in kernel? after boot via module?) > *anything* else you might thing is relevant? I get the xpt_config waits, but I have not disabled firewire: I just work around the problem by manually disconnecting the external drive in question and re-attaching it after the boot has failed and falled into single-user mode. It seems to work fine for post-boot arrival. Want my bootverbose logs? (I think that I posted them before, the first time around, but can probably make a new set.) Also: this does seem to be a race condition kind of thing, because in the intervening time I *have* had at least one successful, hands-off boot. Cheers, -- Andrew From bugmaster at FreeBSD.org Mon Aug 24 11:06:54 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 24 11:07:57 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200908241106.n7OB6r2b048541@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From sean.bruno at dsl-only.net Mon Aug 24 19:35:37 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Mon Aug 24 19:35:43 2009 Subject: Have *you* disabled Firewire? In-Reply-To: <20090824014933.GA52180@duncan.reilly.home> References: <1250756114.23644.8.camel@Lappy> <20090824014933.GA52180@duncan.reilly.home> Message-ID: <1251142535.2682.6.camel@Lappy> > I get the xpt_config waits, but I have not disabled firewire: I > just work around the problem by manually disconnecting the > external drive in question and re-attaching it after the boot > has failed and falled into single-user mode. It seems to work > fine for post-boot arrival. > > Want my bootverbose logs? (I think that I posted them before, > the first time around, but can probably make a new set.) > > Also: this does seem to be a race condition kind of thing, > because in the intervening time I *have* had at least one > successful, hands-off boot. > > Cheers, > If you can send me your bootverbose dmesg output, that would be great. Sean From sean.bruno at dsl-only.net Wed Aug 26 05:12:42 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Wed Aug 26 05:12:47 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <4A9412ED.6080309@freebsd.org> References: <4A9412ED.6080309@freebsd.org> Message-ID: <1251263560.2682.35.camel@Lappy> I just hijacked your email, so I can document your motherboard ieee1394 controller. [See below] On Tue, 2009-08-25 at 19:35 +0300, Andriy Gapon wrote: > I have become to own Gigabyte GA-MA780G-UD3H motherboard: > http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ClassValue=Motherboard&ProductID=3004&ProductName=GA-MA780G-UD3H > It is based on AMD 780G + SB700. > BTW, CPU I am using is Athlon II X2 250. > > Sorry for the broadcast announcement, but this is my first AMD-based system in > many years, so I eagerly started exploring it and hacking for it. > > For this reason please expect a number of questions from me as well as some > reports and hopefully code related to this motherboard. I am going to post them as > follow-ups to this email. > > Meanwhile, if you interested in any information about this motherboard - data > dumps, outputs from tools, etc - please let me know, I will try my best to provide > that. > I'd like to see the output of a dmesg after bootup with 8.0 BETA 3 if possible along with the output of the following: fwcontrol -p fwcontrol -t pciconf -lv Sean (sbruno@freebsd.org) From avg at freebsd.org Wed Aug 26 09:14:46 2009 From: avg at freebsd.org (Andriy Gapon) Date: Wed Aug 26 09:14:51 2009 Subject: GA-MA780G-UD3H motherboard In-Reply-To: <1251263560.2682.35.camel@Lappy> References: <4A9412ED.6080309@freebsd.org> <1251263560.2682.35.camel@Lappy> Message-ID: <4A94F86B.8060108@freebsd.org> on 26/08/2009 08:12 Sean Bruno said the following: > > I'd like to see the output of a dmesg after bootup with 8.0 BETA 3 if > possible along with the output of the following: > > fwcontrol -p > fwcontrol -t > > pciconf -lv Please see http://people.freebsd.org/~avg/ga-ma780g-ud3h/ dmesg is from today's head actually. Let me know if I can provide anything else. -- Andriy Gapon From bugmaster at FreeBSD.org Mon Aug 31 11:07:04 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 31 11:07:56 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200908311107.n7VB74N9070526@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total.