Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On Thu, Mar 26, 2009 at 11:23:09AM +, John wrote: Weongyo Jeong wrote: Could you please test it with attached patch to fix a page fault? I don't know why bus_dma_tag_create() returns ENOMEM that it looks temporary. Hi, Seems the patch failed to apply: [r...@potato /usr/src/sys/dev/malo]# ls -la total 140 drwxr-xr-x2 root wheel512 Mar 26 11:17 . drwxr-xr-x 199 root wheel 3072 Mar 24 16:58 .. -rw-r--r--1 root wheel 8 May 4 2008 if_malo.c -rw-r--r--1 root wheel 19096 May 4 2008 if_malo.h -rw-r--r--1 root wheel 9625 Mar 26 11:14 if_malo_pci.c -rw-r--r--1 root wheel 22333 May 4 2008 if_malohal.c -rw-r--r--1 root wheel 8266 May 4 2008 if_malohal.h -rw-r--r--1 root wheel 3722 May 4 2008 if_maloioctl.h -rw-r--r--1 root wheel375 Mar 26 11:15 patch_malo_20090326_panic.diff [r...@potato /usr/src/sys/dev/malo]# patch patch_malo_20090326_panic.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: if_malo_pci.c |=== |--- if_malo_pci.c (revision 187939) |+++ if_malo_pci.c (working copy) -- Patching file if_malo_pci.c using Plan A... Hunk #1 failed at 260. 1 out of 1 hunks failed--saving rejects to if_malo_pci.c.rej done It looks something goes wrong so could you please patch if_malo_pci.c manually it's a very simple patch and test? Sorry for inconvenience. regards, Weongyo Jeong ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
amr driver broken since March 12
at least for me :-) [and sorry for the cross posting] old (March 12 , i know need the svn rev number but...) dmesg | grep amr amr0: LSILogic MegaRAID 1.53 mem 0xfbef-0xfbef,0xfe58-0xfe5f irq 27 at device 0.0 on pci4 amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: LSILogic Intel(R) RAID Controller SRCU42X Firmware 414I, BIOS A100, 128MB RAM amr0: delete logical drives supported by controller amrd0: LSILogic MegaRAID logical drive on amr0 amrd0: 34857MB (71387136 sectors) RAID 0 (optimal) amrd1: LSILogic MegaRAID logical drive on amr0 amrd1: 280024MB (573489152 sectors) RAID 5 (optimal) and a resent 7.2 (same host): amr0: LSILogic MegaRAID 1.53 mem 0xfbef-0xfbef,0xfe58-0xfe5f irq 27 at device 0.0 on pci4 amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: LSILogic Intel(R) RAID Controller SRCU42X Firmware 414I, BIOS A100, 128MB RAM amr0: adapter is busy amr0: adapter is busy amr0: delete logical drives supported by controller (probe0:amr0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:amr0:0:6:0): CAM Status: SCSI Status Error (probe0:amr0:0:6:0): SCSI Status: Check Condition (probe0:amr0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe0:amr0:0:6:0): Invalid field in CDB (probe0:amr0:0:6:0): Unretryable error btw, since I also have similar problems with another kind of raid card (iir), I suspect some related changes are the cause. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Is some combination of gmirror, md file systems, snapshots and, maybe, quotas considered harmful?
Hello, On Sun, Mar 22, 2009 at 04:31:56AM -0500, Scott Lambert wrote: I added this machine to our AMANDA setup on March 13, 2009. I noticed that mksnap_ffs was running on /home, cpu time used: 0:00.77, as things began to circle the drain. That was about 30 minutes after the dump attempt had been started by AMANDA. There were many processes waiting in state D. This time I did a reboot -n -q and the box rebooted but was still fscking when I got to the office. # ls -l /home/.snap -r 1 root operator 117285093376 Mar 20 03:18 dump_snapshot Did you compile the Amanda port with the -L option to dump enabled? Don't ;-) Kind regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amr driver broken since March 12
Danny Braniss wrote: at least for me :-) [and sorry for the cross posting] old (March 12 , i know need the svn rev number but...) None of the commit activity on March 12 is jumping out at me as being suspicious. However, you are now the second person who has told me about AMR problems in 7.1 recently. If you have a precise svn change number, it would help greatly. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amr driver broken since March 12
Danny Braniss wrote: at least for me :-) [and sorry for the cross posting] old (March 12 , i know need the svn rev number but...) None of the commit activity on March 12 is jumping out at me as being suspicious. However, you are now the second person who has told me about AMR problems in 7.1 recently. If you have a precise svn change number, it would help greatly. Scott my bad. the last working amr/iir is from March 12. I first detected the problem sometime later, but not later than March 23. So it has to be changes in that time frame. both drivers are showing similar symptoms: waiting for not busy the iir goes on for ever, and it's the cam that eventually panics, run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config (actually not 100% true, depending if WITNESS is on or off, it sometimes just hangs). the amr seems to time out: amr0: adapter is busy thanks for looking into the problem, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amr driver broken since March 12
Danny Braniss wrote: Danny Braniss wrote: at least for me :-) [and sorry for the cross posting] old (March 12 , i know need the svn rev number but...) None of the commit activity on March 12 is jumping out at me as being suspicious. However, you are now the second person who has told me about AMR problems in 7.1 recently. If you have a precise svn change number, it would help greatly. Scott my bad. the last working amr/iir is from March 12. I first detected the problem sometime later, but not later than March 23. So it has to be changes in that time frame. both drivers are showing similar symptoms: waiting for not busy the iir goes on for ever, and it's the cam that eventually panics, run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config (actually not 100% true, depending if WITNESS is on or off, it sometimes just hangs). the amr seems to time out: amr0: adapter is busy thanks for looking into the problem, danny Ok, here are a series of revisions to step through, in forward order. Make sure that you are starting with at least revision 189568. Then, update to exactly the revision numbers below, recompile the kernel, and test: 190087 190091 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amr driver broken since March 12
On Fri, Mar 27, 2009 at 06:52:32PM +0300, Danny Braniss wrote: Danny Braniss wrote: at least for me :-) [and sorry for the cross posting] old (March 12 , i know need the svn rev number but...) None of the commit activity on March 12 is jumping out at me as being suspicious. However, you are now the second person who has told me about AMR problems in 7.1 recently. If you have a precise svn change number, it would help greatly. Scott (Long) my bad. the last working amr/iir is from March 12. I first detected the problem sometime later, but not later than March 23. So it has to be changes in that time frame. I think Scott Long was actually asking if you could try to cvsup (or csup) to a date between those two and see if the problem shows there. If you go for, (23 - 12/2) + 12, something like March 17, it would help to narrow what changes could be causing the problem. If you see the problem with a March 17 kernel, you can split the time between March 12 and 17 and try again. Then just keep cutting the search space in half until you can pretty much say This is the commit that broke things for me. It's not always possible for someone to take the time to do the binary search for the actual commit which broke things for them. But when they can, it really helps the developers. Just cutting it down from 11 days to 5 or 6 days can probably be a big help. -- Scott LambertKC5MLE Unix SysAdmin lamb...@lambertfam.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
Weongyo Jeong wrote: It looks something goes wrong so could you please patch if_malo_pci.c manually it's a very simple patch and test? Sorry for inconvenience. After editing, is it sufficient to just build and install a new kernel? thanks -- John ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: malo causes sig 12 error and panic on Freebsd 7.2-PRERELEASE (7-STABLE)
On 3/27/09, John li...@reiteration.net wrote: Weongyo Jeong wrote: It looks something goes wrong so could you please patch if_malo_pci.c manually it's a very simple patch and test? Sorry for inconvenience. After editing, is it sufficient to just build and install a new kernel? Yes, (or only if_malo module if you plan to use kldload/loader.conf: cd /sys/modules/malo make make install) -- Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE
On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote: Any news about that? http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html I'm sorry, I forgot this issue which was caused by my disk crash happened in the end of Jan, 2009. I've updated age(4) patch in the following URL. http://people.freebsd.org/~yongari/age/age.diff Please test the with 1. shutdown your box 2. remove power cable and wait 5 min. 3. unplug UTP cabble 4. boot and see whether age(4) does not lockup your box 5. plug UTP cable and see whether age(4) can send/receive traffics And please do 1. reboot your box with UTP cable plugged in 2. check whether age(4) works Please also see whether ethernet MAC address is correctly detected in both cases. Thanks for reminder. I tried with the last commited version after updating src with no luck: still hang on boot (actually it hangs when I kldload it, as I removed it from my KERNCONF, so I can boot with the NIC enabled). Then I applied your patch and, as with the previous one you asked me to try, it's working. I did the two tests exactly how you asked and everything seems fine. The MAC address is correct in both cases. The connection is working and I did some huge file transfer with ssh with another pc with performance comparable with my rl0 (I think at the limits of a 100Mbps net, imposed by my router). Here you can find my dmesg -a http://pastebin.com/f4afd50db If you have any other test I can do for you, please ask. Do you have any idea if it will included it 7.2-RELEASE? Thanks Barbara ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
X.org hanging under 7.2-PRERELEASE
I update -STABLE about once a week. On Wednesday I update, and subsequently started getting hangs and lockups. This happens only when DRI is enabled. When DRI is disabled there is no problem. The seriousness can vary. Sometimes I can ssh in from another machine to reboot, other times I can't. The last time it hung, top showed X.org at 100.0% CPU. The previous time it was stuck with in a drmwtq state. The hang always occurs within twenty minutes of starting X. Particulars: FreeBSD 7.2-PRERELEASE #2: Thu Mar 26 19:21:26 xf86-video-ati-6.12.1 (with Radeon X1550) kdelibs-4.2.1_1 Relevant portions of my xorg.conf: Section Module Load extmod Load dbe Load dri Load glx Load xtrap Load freetype EndSection Section Device Identifier Card0 Driver radeon ... Option AGPMode 4 Option RenderAccel on Option AccelMethod EXA EndSection I have had no prior problems with -STABLE. I have an Intel Q45 chipset, so I need to run -STABLE, and don't have the option of going back to -RELEASE. Is there any easy way to go back to an earlier -STABLE? -- David Johnson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ALT_BREAK_TO... + ILO ... missing something in config ...
Due to an issue I'm having with 7.x, and trying to track it down, I spent tonight getting my server setup to allow my to break into the debugger when it hangs, and hopefully dump core ... But, although I *think* I've got it all, I'm obviously missing something, as it isn't breaking ... First ... I'm running a proliant server, and when I connect via SSH to ILO on that machine, and type 'vsp', I get a shell as I expect, I can type, etc ... when I reboot the machine, I get the opening splash screen with the 7(?) options (normal boot, single user mode, etc, etc) ... but I get nothing between that and the login prompt ... first sign of a problem, maybe? Next, the easy question ... what is the key stroke to issue when one has ALT_BREAK_TO_DEBUGGER is set in the kernel? I thought it was CR ~ ^b ... is that correct? I'm using putty to connect via ssh, if that makes a difference ... I've also tried using the browser interface into ilo / vsp, same lack of a result ... Beyond adding sio device driver to my kernel, I've also got: options ALT_BREAK_TO_DEBUGGER options KDB options DDB Missing a kernel option maybe? I have the following in /boot/loader.conf: comconsole_speed=9600 console=vidconsole,comconsole # A comma separated list of console(s) boot_multicons=-D # -D: Use multiple consoles boot_serial=-h # -h: Use serial console So ... eithe rI don't have it enabled like I think, or I'm doing the wrong key stroke ... or ... Thx Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
