Re: advice sought: workflow with -CURRENT and amd GPU [Re: -CURRENT hangs since at least 2022-04-04]
On Apr 19, 2022, at 4:49 AM, Michael Schuster wrote: > Hi, > > I'm highjacking and re-purposing the previous thread, I hope that's OK > (I did change the subject ;-)) - I'm keeping some of the previous > contents for reference. > > I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and have > been using a similar approach to keep the machine up to date - or so I > suspect. Still, after a while (several months), I end up with one or > more of these: > - I get some sort of panic in DRM (at startup or, currently, at shutdown) > - when I boot into to a previous BE to attempt a fix and then again > reboot into the current one, I get tons of messages like this > "... kernel: KLD iic.ko: depends on kernel - not available or > version mismatch > ... kernel: linker_load_file: /boot/kernel/iic.ko - unsupported file > type" > and computer refuses to accept input (let alone start X) > > and some others I don't recall right now. > > Before I ask for advice (see below), let me explain the approaches > I've taken so far. I install with ZFS from the beginning, current boot > env is "N". These are outlines, not exact commands: > > I) never touch the current BE, always update a new one: > 1) given current BE N, I create a new BE N+1 and mount it on /mnt, > 2) 'cd /usr/src; git pull; sudo make DESTDIR=/mnt ... (build, install, etc)' > 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make DESTDIR=/mnt install' > 4) beadm activate BE N+1; reboot > > II) keep a "new" BE as backup/fallback, update current BE: > 1) given current BE N, I create a new BE N+1 (mounting not required) > (this is the intended 'fallback') > 2) 'cd /usr/src; git pull"; then "make" as described in the Handbook > "24.6. Updating FreeBSD from Source" > 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make install' > 4) reboot > > in both scenarios(sp?), I do "pkg update; pkg upgrade" from time to > time (also following the resp. approach shown above). > > I suspect that I'm missing something fundamental in my approaches - > does anyone have a (for them) foolproof approach along these lines, or > can someone show me what I'm missing in either of mine (in private, if > you prefer)? I don't know whether you're missing anything, but I wanted to mention I recently found a tool useful in helping my own BE-based source upgrades: /usr/src/tools/build/beinstall.sh I've found it helps with the build/upgrade steps. See man beinstall(8) for details. Cheers, Paul.
advice sought: workflow with -CURRENT and amd GPU [Re: -CURRENT hangs since at least 2022-04-04]
Hi, I'm highjacking and re-purposing the previous thread, I hope that's OK (I did change the subject ;-)) - I'm keeping some of the previous contents for reference. I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and have been using a similar approach to keep the machine up to date - or so I suspect. Still, after a while (several months), I end up with one or more of these: - I get some sort of panic in DRM (at startup or, currently, at shutdown) - when I boot into to a previous BE to attempt a fix and then again reboot into the current one, I get tons of messages like this "... kernel: KLD iic.ko: depends on kernel - not available or version mismatch ... kernel: linker_load_file: /boot/kernel/iic.ko - unsupported file type" and computer refuses to accept input (let alone start X) and some others I don't recall right now. Before I ask for advice (see below), let me explain the approaches I've taken so far. I install with ZFS from the beginning, current boot env is "N". These are outlines, not exact commands: I) never touch the current BE, always update a new one: 1) given current BE N, I create a new BE N+1 and mount it on /mnt, 2) 'cd /usr/src; git pull; sudo make DESTDIR=/mnt ... (build, install, etc)' 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make DESTDIR=/mnt install' 4) beadm activate BE N+1; reboot II) keep a "new" BE as backup/fallback, update current BE: 1) given current BE N, I create a new BE N+1 (mounting not required) (this is the intended 'fallback') 2) 'cd /usr/src; git pull"; then "make" as described in the Handbook "24.6. Updating FreeBSD from Source" 3) 'cd usr/ports/graphics/drm-devel-kmod; sudo make install' 4) reboot in both scenarios(sp?), I do "pkg update; pkg upgrade" from time to time (also following the resp. approach shown above). I suspect that I'm missing something fundamental in my approaches - does anyone have a (for them) foolproof approach along these lines, or can someone show me what I'm missing in either of mine (in private, if you prefer)? TIA for all and any advice Michael On Mon, Apr 18, 2022 at 9:33 PM Pete Wright wrote: > > > > On 4/18/22 12:23, filis+fbsdcurr...@filis.org wrote: > > Hi, > > > > I'm running -CURRENT on this one desktop box which is a "Ryzen 7 4800U > > with Radeon Graphics", since it didn't work on 13R. > > I use Boot environments and on 2022-04-04 I updated it and it started > > to completely freeze under X (I haven't tried letting it run without > > X) after a few dozen minutes. > [...] > > > After updating your CURRENT environment did you rebuild the drm-kmod > package? that's usually required as the LKPI is much more of a moving > target on that branch compared to STABLE or RELEASE. i have a pretty > much identical setup and building/installing drm-devel-kmod has been > working flawlessly for quite a while. > > after building/installing my latest world i do following (this is from a > local script i use when rebuilding): > > cd $PORTS/graphics/drm-devel-kmod > sudo pkg unlock -y drm-devel-kmod > sudo make package > sudo pkg upgrade -y work/pkg/*.pkg > sudo pkg lock -y drm-devel-kmod > > -pete > > -- > Pete Wright > p...@nomadlogic.org > @nomadlogicLA > > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'
Re: -CURRENT hangs since at least 2022-04-04
On dl., abr. 18 2022, Pete Wright wrote: On 4/18/22 12:23, filis+fbsdcurr...@filis.org wrote: Hi, I'm running -CURRENT on this one desktop box which is a "Ryzen 7 4800U with Radeon Graphics", since it didn't work on 13R. I use Boot environments and on 2022-04-04 I updated it and it started to completely freeze under X (I haven't tried letting it run without X) after a few dozen minutes. I went on vacation and came back today and updated it again to see if the issue went away, but it froze again. I went back to the latest BE before 2022-04-04, which is from 2022-03-21 and so far it works fine again. I use a different machine to build and then rsync /usr/src and /usr/obj over and run make installworld, etc locally and also pkg upgrade (I use FreeBSD -latest packages) everything, so I can't quite tell if this is related to base or drm-kmod and I'm not too familiar with changes in the timeframe between 2022-03-21 and 2022-04-04 that would affect my setup. Is there anything I can try and/or find or collect info to shed more light on this? After updating your CURRENT environment did you rebuild the drm-kmod package? that's usually required as the LKPI is much more of a moving target on that branch compared to STABLE or RELEASE. i have a pretty much identical setup and building/installing drm-devel-kmod has been working flawlessly for quite a while. after building/installing my latest world i do following (this is from a local script i use when rebuilding): cd $PORTS/graphics/drm-devel-kmod sudo pkg unlock -y drm-devel-kmod sudo make package sudo pkg upgrade -y work/pkg/*.pkg sudo pkg lock -y drm-devel-kmod -pete I too have recently noticed some freezes after a few hours on -CURRENT that were not happening before. This with a matching drm-devel-kmod package (built with matching source on matching kernel). The hw being: AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx -- Evilham
Re: -CURRENT hangs since at least 2022-04-04
On 4/18/22 12:23, filis+fbsdcurr...@filis.org wrote: Hi, I'm running -CURRENT on this one desktop box which is a "Ryzen 7 4800U with Radeon Graphics", since it didn't work on 13R. I use Boot environments and on 2022-04-04 I updated it and it started to completely freeze under X (I haven't tried letting it run without X) after a few dozen minutes. I went on vacation and came back today and updated it again to see if the issue went away, but it froze again. I went back to the latest BE before 2022-04-04, which is from 2022-03-21 and so far it works fine again. I use a different machine to build and then rsync /usr/src and /usr/obj over and run make installworld, etc locally and also pkg upgrade (I use FreeBSD -latest packages) everything, so I can't quite tell if this is related to base or drm-kmod and I'm not too familiar with changes in the timeframe between 2022-03-21 and 2022-04-04 that would affect my setup. Is there anything I can try and/or find or collect info to shed more light on this? After updating your CURRENT environment did you rebuild the drm-kmod package? that's usually required as the LKPI is much more of a moving target on that branch compared to STABLE or RELEASE. i have a pretty much identical setup and building/installing drm-devel-kmod has been working flawlessly for quite a while. after building/installing my latest world i do following (this is from a local script i use when rebuilding): cd $PORTS/graphics/drm-devel-kmod sudo pkg unlock -y drm-devel-kmod sudo make package sudo pkg upgrade -y work/pkg/*.pkg sudo pkg lock -y drm-devel-kmod -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA
Re: Current hangs in reboot
On Wed, 11 Dec 2002, Taavi Talvik wrote: After testing, it turns out, that 'hang on reboot' problem maybe related to mainboard (Gigabyte GA-8PE667 Ultra) and/or USB driver for Intel 82801DB. After turning off onboard USB rebooting works even if ACPI is enabled. It was necessary to disable only Intel 82801DB (ICH4) devices. kernel: uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xb800-0xb81f irq 14 at device 29.0 on pci0 kernel: usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 kernel: usb0: USB revision 1.0 kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub0: 2 ports with 2 removable, self powered kernel: uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xb000-0xb01f irq 14 at device 29.1 on pci0 kernel: usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 kernel: usb1: USB revision 1.0 kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub1: 2 ports with 2 removable, self powered kernel: uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xb400-0xb41f irq 15 at device 29.2 on pci0 kernel: usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 kernel: usb2: USB revision 1.0 kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub2: 2 ports with 2 removable, self powered kernel: pci0: serial bus, USB at device 29.7 (no driver attached) kernel: ohci0: NEC uPD 9210 USB controller mem 0xdf00-0xdf000fff irq 14 at device 7.0 on pci2 kernel: usb3: OHCI version 1.0 kernel: usb3: NEC uPD 9210 USB controller on ohci0 kernel: usb3: USB revision 1.0 kernel: uhub3: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub3: 3 ports with 3 removable, self powered kernel: ohci1: NEC uPD 9210 USB controller mem 0xdf001000-0xdf001fff irq 15 at device 7.1 on pci2 kernel: usb4: OHCI version 1.0 kernel: usb4: NEC uPD 9210 USB controller on ohci1 kernel: usb4: USB revision 1.0 kernel: uhub4: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 kernel: uhub4: 2 ports with 2 removable, self powered best regards, taavi On Wed, 11 Dec 2002, Nate Lawson wrote: On Wed, 11 Dec 2002, Taavi Talvik wrote: On Wed, 11 Dec 2002, Taavi Talvik wrote: Current as of yesterday (actually problem presist about month) hangs on reboot. Only message: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Turning off ACPI makes it reboot. Thanks for suggestion Gerrit! But how is ACPI related to problem? Why rebooting hangs between stoping `vnlru' and `bufdaemon' in ACPI case? The next message you'd see if it was working is Stopping ACPI. So acpi shutdown is probably what is hanging. No, Stopping ACPI appears normally only after stoping 'syncer' also. But in my situation hang happens between 'vnlru' and 'bufdaemon'. If console output is not buffered, what happens that last two prompts are not diapleyed? Any hints how I can futher debug it? Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks, buffers remaining... 2 2 done Uptime: 9m6s To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current hangs in reboot
On Wed, 11 Dec 2002, Taavi Talvik wrote: Current as of yesterday (actually problem presist about month) hangs on reboot. Only message: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Turning off ACPI makes it reboot. Thanks for suggestion Gerrit! But how is ACPI related to problem? Why rebooting hangs between stoping `vnlru' and `bufdaemon' in ACPI case? best regards, taavi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current hangs in reboot
On Wed, Dec 11, 2002 at 03:35:52PM +0200, Taavi Talvik wrote: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Turning off ACPI makes it reboot. Thanks for suggestion Gerrit! You're welcome. I just noticed I forgot to include the mailinglist in my answers to you. :) But how is ACPI related to problem? Why rebooting hangs between stoping `vnlru' and `bufdaemon' in ACPI case? I'd like to know that, too. :-) cu Gerrit -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current hangs in reboot
On Wed, 11 Dec 2002, Taavi Talvik wrote: On Wed, 11 Dec 2002, Taavi Talvik wrote: Current as of yesterday (actually problem presist about month) hangs on reboot. Only message: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Turning off ACPI makes it reboot. Thanks for suggestion Gerrit! But how is ACPI related to problem? Why rebooting hangs between stoping `vnlru' and `bufdaemon' in ACPI case? The next message you'd see if it was working is Stopping ACPI. So acpi shutdown is probably what is hanging. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current hangs in reboot
On Wed, 11 Dec 2002, Nate Lawson wrote: On Wed, 11 Dec 2002, Taavi Talvik wrote: On Wed, 11 Dec 2002, Taavi Talvik wrote: Current as of yesterday (actually problem presist about month) hangs on reboot. Only message: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Turning off ACPI makes it reboot. Thanks for suggestion Gerrit! But how is ACPI related to problem? Why rebooting hangs between stoping `vnlru' and `bufdaemon' in ACPI case? The next message you'd see if it was working is Stopping ACPI. So acpi shutdown is probably what is hanging. No, Stopping ACPI appears normally only after stoping 'syncer' also. But in my situation hang happens between 'vnlru' and 'bufdaemon'. If console output is not buffered, what happens that last two prompts are not diapleyed? Any hints how I can futher debug it? Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks, buffers remaining... 2 2 done Uptime: 9m6s best regards, taavi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
Kenneth D. Merry writes: Wow, I didn't actually expect my config would make things work differenty on your box. I'm very interested in whatever you turn up. The answer is...the USB code. [ Nick and Joe CCed ] If I comment out the following lines in my standard config for this machine, SMP works: # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices ... To add another datapoint, the USB code will prevent some alphas from rebooting cleanly in -stable. With USB compiled in, the machine will not get any ATA interrupts after a warm reboot. This change happened somewhere between 4.4 and 4.5. It doesn't seem to matter if the machine actually has USB enabled or not. Eg, it happens on a UP1000 which has USB hardware, but has it disabled in the firmware: chip0@pci0:0:0: class=0x06 card=0x chip=0x70061022 rev=0x25 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-751 Processor-to-PCI Bridge / Memory Ctrlr' class= bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x chip=0x70071022 rev=0x01 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-751 AGP and PCI-to-PCI Bridge (1x/2x AGP)' class= bridge subclass = PCI-PCI isab0@pci0:7:0: class=0x060100 card=0x chip=0x153310b9 rev=0xc3 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M1533 Aladdin IV ISA Bridge' class= bridge subclass = PCI-ISA sym0@pci0:8:0: class=0x01 card=0x chip=0x000f1000 rev=0x04 hdr=0x00 vendor = 'Symbios Logic (NCR) (LSI Logic)' device = '53C875, 53C876 Ultra-Wide SCSI (53C876 is dual-channel)' class= mass storage subclass = SCSI rp0@pci0:10:0: class=0x078000 card=0x chip=0x000511fe rev=0x04 hdr=0x00 vendor = 'Comtrol Corp' device = 'RocketPort 8-port' class= simple comms xl0@pci0:11:0: class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x64 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC' class= network subclass = ethernet atapci0@pci0:16:0: class=0x0101fa card=0x chip=0x522910b9 rev=0xc1 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M1543 Southbridge EIDE Controller' class= mass storage subclass = ATA chip1@pci0:17:0:class=0x00 card=0x chip=0x710110b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M7101 Power Management Controller' class= old subclass = non-VGA display device none0@pci2:5:0: class=0x03 card=0x0a351048 chip=0x3d07104c rev=0x11 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'TVP4020 AGP Permedia 2' class= display subclass = VGA Cheers, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
+---[ Glenn Gombert ]-- | There is a problem in -Current now between SCSI card(s) and the ATA | drivers, On my Dell 410 Workstation at work I commetned out the ATA driver | stuff (it was not used on that machine) and it booted fine, I think that | might just cure the SMP problem you are seeing too. I can normally boot fine, it's only under load that it hangs. I think it might actually be the AHC driver, not CAM itself. I don't have any other SCSI cards to test that theory though. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
On Sun, Feb 24, 2002 at 23:15:34 -0800, Matthew Dillon wrote: :... : stuff (it was not used on that machine) and it booted fine, I think that : might just cure the SMP problem you are seeing too. : :Thanks for the suggestion. : :Unfortunately it still hangs with SMP enabled and the ATA drivers commented :out of the GENERIC config. : :Ken :-- :Kenneth Merry Just as a data point, I've been running -current on a 2xCPU SMP system (DELL2550) for a few weeks and it's always booted fine. For the last few months I have noticed occassional freezes occuring at odd times long after boot. I have no idea why it happens. Your config works! I've attached the dmesg. Now the question is, what is the difference between GENERIC and your config that is causing the problem? (I suppose it makes sense that your config would work, since I think that Dell is a Serverworks-based system too.) I'll see if I can figure it out... Ken -- Kenneth Merry [EMAIL PROTECTED] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Feb 25 22:01:01 MST 2002 [EMAIL PROTECTED]:/usr/home/ken/perforce/FreeBSD-ken/src/sys/i386/compile/dilloncfg Preloaded elf kernel /boot/kernel.dillon/kernel at 0xc03c6000. Preloaded elf module /boot/kernel.dillon/acpi.ko at 0xc03c60b0. Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 2684289024 (2621376K bytes) avail memory = 2610569216 (2549384K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00f52e0 ACPI-0204: *** Error: AcpiLoadTables: Could not load namespace: AE_NOT_FOUND ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NOT_FOUND ACPI: table load failed: AE_NOT_FOUND npx0: math processor on motherboard npx0: INT 16 interface pcib0: ServerWorks host to PCI bridge at pcibus 0 on motherboard IOAPIC #1 intpin 10 - irq 2 IOAPIC #1 intpin 11 - irq 5 IOAPIC #1 intpin 15 - irq 9 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 0.1 on pci0 IOAPIC #1 intpin 14 - irq 11 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) ahc0: Adaptec aic7899 Ultra160 SCSI adapter port 0xd000-0xd0ff mem 0xfeafc000-0xfeafcfff irq 2 at device 5.0 on pci0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7899 Ultra160 SCSI adapter port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 5 at device 5.1 on pci0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: Intel Pro 10/100B/100+ Ethernet port 0xd400-0xd43f mem 0xfe90-0xfe9f,0xfeafd000-0xfeafdfff irq 9 at device 6.0 on pci0 fxp0: Ethernet address 00:30:48:21:bb:74 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge port 0x580-0x58f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 ATA33 controller port 0xffa0-0xffaf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at device 15.2 (no driver attached) pcib2: ServerWorks host to PCI bridge at pcibus 2 on motherboard IOAPIC #1 intpin 8 - irq 16 pci2: PCI bus on pcib2 pci2: network, ethernet at device 2.0 (no driver attached) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it orm0: Option ROMs at iomem 0xd1800-0xd27ff,0xc-0xcbfff on isa0 fdc0: enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and
Re: -current hangs with SMP enabled
: Just as a data point, I've been running -current on a 2xCPU SMP : system (DELL2550) for a few weeks and it's always booted fine. : : For the last few months I have noticed occassional freezes occuring : at odd times long after boot. I have no idea why it happens. : :Your config works! : :I've attached the dmesg. Now the question is, what is the difference :between GENERIC and your config that is causing the problem? : :(I suppose it makes sense that your config would work, since I think that :Dell is a Serverworks-based system too.) : :I'll see if I can figure it out... : :Ken :-- :Kenneth Merry Wow, I didn't actually expect my config would make things work differenty on your box. I'm very interested in whatever you turn up. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
On Mon, Feb 25, 2002 at 21:29:44 -0800, Matthew Dillon wrote: : Just as a data point, I've been running -current on a 2xCPU SMP : system (DELL2550) for a few weeks and it's always booted fine. : : For the last few months I have noticed occassional freezes occuring : at odd times long after boot. I have no idea why it happens. : :Your config works! : :I've attached the dmesg. Now the question is, what is the difference :between GENERIC and your config that is causing the problem? : :(I suppose it makes sense that your config would work, since I think that :Dell is a Serverworks-based system too.) : :I'll see if I can figure it out... : :Ken :-- :Kenneth Merry Wow, I didn't actually expect my config would make things work differenty on your box. I'm very interested in whatever you turn up. The answer is...the USB code. [ Nick and Joe CCed ] If I comment out the following lines in my standard config for this machine, SMP works: # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio# Diamond Rio 500 MP3 player device uscanner# Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet The USB module is still loaded when usbd cranks up, but it doesn't hang the machine when it is loaded as a module. I've tried two kernels, with the only difference being whether the usb code (as listed above) is enabled or not. The kernel with the USB stuff hangs. I've attached dmesg output from the working boot. Ken -- Kenneth Merry [EMAIL PROTECTED] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #4: Mon Feb 25 22:23:37 MST 2002 [EMAIL PROTECTED]:/usr/home/ken/perforce/FreeBSD-ken/src/sys/i386/compile/gondolin Preloaded elf kernel /boot/kernel.gondolin.smp/kernel at 0xc04c7000. Preloaded elf module /boot/kernel.gondolin.smp/acpi.ko at 0xc04c70b8. Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 2684289024 (2621376K bytes) avail memory = 2609504256 (2548344K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00f52e0 ACPI-0204: *** Error: AcpiLoadTables: Could not load namespace: AE_NOT_FOUND ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NOT_FOUND ACPI: table load failed: AE_NOT_FOUND npx0: math processor on motherboard npx0: INT 16 interface pcib0: ServerWorks host to PCI bridge at pcibus 0 on motherboard IOAPIC #1 intpin 10 - irq 2 IOAPIC #1 intpin 11 - irq 5 IOAPIC #1 intpin 15 - irq 9 pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 0.1 on pci0 IOAPIC #1 intpin 14 - irq 11 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) ahc0: Adaptec aic7899 Ultra160 SCSI adapter port 0xd000-0xd0ff mem 0xfeafc000-0xfeafcfff irq 2 at device 5.0 on pci0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7899 Ultra160 SCSI adapter port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 5 at device 5.1 on pci0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: Intel Pro 10/100B/100+ Ethernet port 0xd400-0xd43f mem 0xfe90-0xfe9f,0xfeafd000-0xfeafdfff irq 9 at device 6.0 on pci0 fxp0: Ethernet address 00:30:48:21:bb:74 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge port 0x580-0x58f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: ServerWorks ROSB4 ATA33 controller port 0xffa0-0xffaf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at device 15.2 (no driver
Re: -current hangs with SMP enabled
On 26-Feb-02 Kenneth D. Merry wrote: On Mon, Feb 25, 2002 at 21:29:44 -0800, Matthew Dillon wrote: : Just as a data point, I've been running -current on a 2xCPU SMP : system (DELL2550) for a few weeks and it's always booted fine. : : For the last few months I have noticed occassional freezes occuring : at odd times long after boot. I have no idea why it happens. : :Your config works! : :I've attached the dmesg. Now the question is, what is the difference :between GENERIC and your config that is causing the problem? : :(I suppose it makes sense that your config would work, since I think that :Dell is a Serverworks-based system too.) : :I'll see if I can figure it out... : :Ken :-- :Kenneth Merry Wow, I didn't actually expect my config would make things work differenty on your box. I'm very interested in whatever you turn up. The answer is...the USB code. [ Nick and Joe CCed ] If I comment out the following lines in my standard config for this machine, SMP works: Ah yes! We had a test machine at TWC that came in that we couldnt' install 4.5 on (even with the UP kernel on the boot disk) due to getting an interrupt storm of USB interrupts. # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio# Diamond Rio 500 MP3 player device uscanner# Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet The USB module is still loaded when usbd cranks up, but it doesn't hang the machine when it is loaded as a module. I've tried two kernels, with the only difference being whether the usb code (as listed above) is enabled or not. The kernel with the USB stuff hangs. I've attached dmesg output from the working boot. Ken -- Kenneth Merry [EMAIL PROTECTED] -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
+---[ Kenneth D. Merry ]-- | | The answer is...the USB code. I have also solved my problem, and my answer is SMB code.. When booting an SMP kernel with SMB enabled, trying to access /dev/smb0 returns device not configured (works fine in UP mode). Removing the SMB (and related options) from my kernel config and I'm through a buildworld. I'm going to do a few more to make sure it's not a fluke, but, somehow I think that's it. So can I take it the smbbus on my mobo is hosed? -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
* Kenneth D. Merry [EMAIL PROTECTED] [020224 16:56] wrote: I've got a SMP machine with a Supermicro P3TDE6 motherboard. (Serverworks HE-SL chipset, dual 1.26GHz Pentium III's.) It boots just fine with a GENERIC -current kernel (sources cvsupped yesterday at ~1500 MST), but hangs (at the Waiting 15 seconds for SCSI devices to settle message) when SMP and APIC_IO are enabled. Those two options are the only things different between the broken and working GENERIC kernels. I've attached dmesg output from the stock GENERIC kernel. Anyone have any ideas on how to get SMP working? I've had the same problem for a while now. Best of luck. :) -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
+---[ Kenneth D. Merry ]-- | | I've got a SMP machine with a Supermicro P3TDE6 motherboard. (Serverworks | HE-SL chipset, dual 1.26GHz Pentium III's.) | | It boots just fine with a GENERIC -current kernel (sources cvsupped | yesterday at ~1500 MST), but hangs (at the Waiting 15 seconds for SCSI | devices to settle message) when SMP and APIC_IO are enabled. I have a similar problem with -current and SMP. Heavy I/O on the SCSI system (say a buildworld or even an FSCK) causes a hang (no panic). I think interrupts go off and stay off. This happens with both the onboard and UFW PCI card, both Adaptec with ACPI on and off (it's happened since SMPng started, I figured it was one of those things that'd get fixed eventually). Although Matt's latest patches make me think it might be sooner rather than later, so I'll be crash testing again next weekend methinks. ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xd400-0xd4ff mem 0xedfee000-0xedfeefff irq 10 at device 9.0 on pci0 aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xd800-0xd8ff mem 0xedfef000-0xedfe irq 10 at device 9.1 on pci0 aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/255 SCBs ahc2: Adaptec 2940 Ultra SCSI adapter port 0xd000-0xd0ff mem 0xedfed000-0xedfedfff irq 9 at device 15.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs I try an SMP kernel about once a month. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
There is a problem in -Current now between SCSI card(s) and the ATA drivers, On my Dell 410 Workstation at work I commetned out the ATA driver stuff (it was not used on that machine) and it booted fine, I think that might just cure the SMP problem you are seeing too. At 11:15 AM 2/25/2002 +1000, Andrew Kenneth Milton wrote: +---[ Kenneth D. Merry ]-- | | I've got a SMP machine with a Supermicro P3TDE6 motherboard. (Serverworks | HE-SL chipset, dual 1.26GHz Pentium III's.) | | It boots just fine with a GENERIC -current kernel (sources cvsupped | yesterday at ~1500 MST), but hangs (at the Waiting 15 seconds for SCSI | devices to settle message) when SMP and APIC_IO are enabled. I have a similar problem with -current and SMP. Heavy I/O on the SCSI system (say a buildworld or even an FSCK) causes a hang (no panic). I think interrupts go off and stay off. This happens with both the onboard and UFW PCI card, both Adaptec with ACPI on and off (it's happened since SMPng started, I figured it was one of those things that'd get fixed eventually). Although Matt's latest patches make me think it might be sooner rather than later, so I'll be crash testing again next weekend methinks. ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xd400-0xd4ff mem 0xedfee000-0xedfeefff irq 10 at device 9.0 on pci0 aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xd800-0xd8ff mem 0xedfef000-0xedfe irq 10 at device 9.1 on pci0 aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/255 SCBs ahc2: Adaptec 2940 Ultra SCSI adapter port 0xd000-0xd0ff mem 0xedfed000-0xedfedfff irq 9 at device 15.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/255 SCBs I try an SMP kernel about once a month. -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Glenn Gombert [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
On Sun, Feb 24, 2002 at 21:02:02 -0500, Glenn Gombert wrote: There is a problem in -Current now between SCSI card(s) and the ATA drivers, On my Dell 410 Workstation at work I commetned out the ATA driver stuff (it was not used on that machine) and it booted fine, I think that might just cure the SMP problem you are seeing too. Thanks for the suggestion. Unfortunately it still hangs with SMP enabled and the ATA drivers commented out of the GENERIC config. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
On Sun, Feb 24, 2002 at 09:02:02PM -0500, Glenn Gombert wrote: There is a problem in -Current now between SCSI card(s) and the ATA drivers, For how long has this problem existed? This is being typed from a dual Athlon system with 5 SCSI busses (AHC,SYM,ISP) several disks, CD burnger; and with two IDE disks + ATAPI CDROM drive. FreeBSD dragon.nuxi.com 5.0-CURRENT FreeBSD #238: Fri Feb 22 21:56:02 PST 2002 I would really have noticed if my p0rn IDE disk and my SCSI system disk were not usable at the same time. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current hangs with SMP enabled
:... : stuff (it was not used on that machine) and it booted fine, I think that : might just cure the SMP problem you are seeing too. : :Thanks for the suggestion. : :Unfortunately it still hangs with SMP enabled and the ATA drivers commented :out of the GENERIC config. : :Ken :-- :Kenneth Merry Just as a data point, I've been running -current on a 2xCPU SMP system (DELL2550) for a few weeks and it's always booted fine. For the last few months I have noticed occassional freezes occuring at odd times long after boot. I have no idea why it happens. -Matt # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.260 2000/06/13 22:28:46 peter Exp $ machine i386 #cpuI386_CPU #cpuI486_CPU #cpuI586_CPU cpu I686_CPU ident DELL2550 maxusers0 hints TEST.hints#Default places to look for devices. options SCSI_DELAY=5000 #options MAXMEM=(64*1024) options DDB options INVARIANTS options INVARIANT_SUPPORT options SOFTUPDATES #optionsWITNESS #optionsSHMALL=65537 #optionsSHMMAXPGS=65537 #options GDB_REMOTE_CHAT options ALT_BREAK_TO_DEBUGGER # -Os broken # makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols makeoptions COPTFLAGS=-O -pipe #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking #optionsINET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem options NFSSERVER #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PSEUDOFS#Pseudofs options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #optionsSCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores #optionsP1003_1B#Posix P1003_1B real-time extensions #options_KPOSIX_PRIORITY_SCHEDULING #optionsKBD_INSTALL_CDEV# install a CDEV entry in /dev # To make an SMP kernel, the next two are needed # options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #optionsNCPU=2 # number of CPUs #optionsNBUS=8 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs device isa #device eisa device pci #optionsCOMPAT_OLDISA # compatability shims for lnc, fe, le #optionsCOMPAT_OLDPCI # compatability shims for lnc, vx # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp
Re: current hangs...
In message [EMAIL PROTECTED], John Baldwin writes: On 20-Jan-01 Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], John Baldwin writes: On 20-Jan-01 The Hermit Hacker wrote: On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? SMP, one scsi disk on each controller, /usr and /home ccd'ed. Is there any code dealing with disk I/O in the kernel that does the equivalent of this: while (!io_done) /* spin */ ; That assumes an interrupt will set io_done? Using DELAY() in places might explain this. Not that I know of. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
In message [EMAIL PROTECTED], Mark Murray writes: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? No, /usr is on ccd on this one :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
Mark Murray [EMAIL PROTECTED] types: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't think it's ccd. I get similar hangs with "make -j 20 buildworld" on a 2xPII-Xeon/450, 256M, two scsi disks on ahc without ccd. I think more likely it's related to the problems that sos is currently having/investigating. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
I have a recent -current that hangs in 'make -j36 world'. I am now running a UP kernel of the same date: # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Mon Jan 15 18:42:30 PST 2001 \ root@celebris:/usr/src/sys/compile/CELEBRIS i386 dmesg attached. tomdean dmesg from a UP kernel === 96 blocks, 0.3% fragmentation) IP Filter: already initialized de0: enabling BNC port Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Jan 15 18:42:30 PST 2001 root@celebris:/usr/src/sys/compile/CELEBRIS Timecounter "i8254" frequency 1193029 Hz Timecounter "TSC" frequency 131996485 Hz CPU: Pentium/P54C (132.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC real memory = 100663296 (98304K bytes) avail memory = 94597120 (92380K bytes) Preloaded elf kernel "kernel" at 0xc0334000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc033409c. Intel Pentium detected, installing workaround for F00F bug npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 ncr0: ncr 53c810 fast10 scsi port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 pci0: display, VGA at 6.0 (no driver attached) sis0: NatSemi DP83815 10/100BaseTX port 0xe800-0xe8ff mem 0xfedfa000-0xfedfafff irq 10 at device 7.0 on pci0 sis0: Ethernet address: 00:a0:cc:74:63:b4 miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto de0: Digital 21041 Ethernet port 0xe480-0xe4ff mem 0xfedfbe80-0xfedfbeff irq 15 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: IBM Enhanced (101/102-key) KC can't assign resources unknown: Microsoft PS/2 Mouse can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: LPT printer port can't assign resources unknown: Floppy Controller can't assign resources IP Filter: v3.4.13 initialized. Default = pass all, Logging = enabled Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1s1a da0 at ncr0 bus 0 target 0 lun 0 da0: QUANTUM FIREBALL1080S 1Q09 Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: TOSHIBA CD-ROM XM-5401TA 3605 Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [326227 x 2048 byte records] da2 at ncr0 bus 0 target 2 lun 0 da2: QUANTUM FIREBALL ST3.2S 0F0C Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) da1 at ncr0 bus 0 target 1 lun 0 da1: IBM DNES-309170 SAH0 Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) IP Filter: already initialized de0: enabling BNC port stray irq 7 stray irq 7 stray irq 7 stray irq 7 got 5 stray irq 7's: not logging anymore pid 27080 (communicator-4.7), uid 1001: exited on signal 10 (core dumped) microuptime() went backwards (272675.344496 - 272675.-694570216) microuptime() went backwards (287740.708251 - 287740.-694206432) pid 61804 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) pid 61824 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) pid 61834 (m6811-elf-gdb), uid 1001: exited on signal 11 (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On 20-Jan-01 The Hermit Hacker wrote: On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
In message [EMAIL PROTECTED], John Baldwin writes: On 20-Jan-01 The Hermit Hacker wrote: On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? SMP, one scsi disk on each controller, /usr and /home ccd'ed. dmesg: Booting [/boot/kernel/kernel]... stray irq 7 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Jan 19 23:21:40 CET 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268435456 (262144K bytes) avail memory = 258048000 (252000K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc031b000. Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00fdf20 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443LX (440 LX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller at device 2.1 on pci0 atapci0: Busmastering DMA not supported pci0: serial bus, USB at 2.2 (no driver attached) Timecounter "PIIX" frequency 3579545 Hz pci0: bridge, PCI-unknown at 2.3 (no driver attached) fxp0: Intel Pro 10/100B/100+ Ethernet port 0xfcc0-0xfcdf mem 0xfed0-0xfedf,0xfecdf000-0xfecd irq 19 at device 3.0 on pci0 fxp0: Ethernet address 00:a0:c9:82:bb:30 ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xf800-0xf8ff mem 0xfecff000-0xfecf irq 17 at device 9.0 on pci0 aic7895: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xf400-0xf4ff mem 0xfecfe000-0xfecfefff irq 17 at device 9.1 on pci0 aic7895: Wide Channel B, SCSI Id=7, 32/255 SCBs pci0: display, VGA at 13.0 (no driver attached) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: Parallel I/O on ppbus0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0400 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 2 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DDRS-34560W S97B Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc1 bus 0 target 0 lun 0 da1: IBM DDRS-34560W S97B Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) WARNING: / was not properly dismounted SMP: AP CPU #1 Launched! ccd0-3: Concatenated disk drivers swapon: adding /dev/da1s1b as swap device swapon: adding /dev/da0s1b as swap device Automatic boot in progress... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD
Re: current hangs...
On Sat, 20 Jan 2001, John Baldwin wrote: On 20-Jan-01 The Hermit Hacker wrote: On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? yes and yes ... ahc1: Adaptec 2940 Ultra SCSI adapter port 0xcc00-0xccff mem 0xef10-0xef100fff irq 17 at device 13.0 on pci0 da0 at ahc1 bus 0 target 0 lun 0 da0: SEAGATE ST36530N 1281 Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) da1 at ahc1 bus 0 target 1 lun 0 da1: WDIGTL WD91 ULTRA2 1.00 Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
I'll confirm a hang on both alpha i386 (both SCSI, qlogic ahc resp). The i386 was SMP. The Qlogic wasn't. Both were hung with phk's make -j 256 foolery. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
In message [EMAIL PROTECTED], Matt Dillon writes:
:
:Why not this:
:
:s = splbio();
:TAILQ_FOREACH(bp, vp-v_dirtyblkhd, b_vnbufs) {
First rule when making simple bug fixes by copying working code from one
source file to another is: Dont try to optimize the code on the
fly.
Personally speaking, I don't find the FOREACH macros any more readable
vs an explicit for loop. They hide too much... like for example the
fact that you are dependant on the current pointer remaining valid to
get the next pointer in the loop.
Is that any different from
for (i = 0; i N; i++) {
bla;
}
?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
On 30-Dec-00 Matt Dillon wrote:
#include sys/param.h
@@ -352,12 +352,25 @@
return (0);
/*
+ * MARK/SCAN initialization to avoid infinite loops
+ */
+ s = splbio();
+for (bp = TAILQ_FIRST(vp-v_dirtyblkhd); bp;
+ bp = TAILQ_NEXT(bp, b_vnbufs)) {
+bp-b_flags = ~B_SCANNED;
+ }
+ splx(s);
Why not this:
s = splbio();
TAILQ_FOREACH(bp, vp-v_dirtyblkhd, b_vnbufs) {
bp-b_flags = ~B_SCANNED;
}
We do have foreach queue(3) macros. :)
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
:
:Why not this:
:
:s = splbio();
:TAILQ_FOREACH(bp, vp-v_dirtyblkhd, b_vnbufs) {
First rule when making simple bug fixes by copying working code from one
source file to another is: Dont try to optimize the code on the
fly.
Personally speaking, I don't find the FOREACH macros any more readable
vs an explicit for loop. They hide too much... like for example the
fact that you are dependant on the current pointer remaining valid to
get the next pointer in the loop.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
On 01-Jan-01 Matt Dillon wrote:
:
:Why not this:
:
:s = splbio();
:TAILQ_FOREACH(bp, vp-v_dirtyblkhd, b_vnbufs) {
First rule when making simple bug fixes by copying working code from one
source file to another is: Dont try to optimize the code on the
fly.
That works.
Personally speaking, I don't find the FOREACH macros any more readable
vs an explicit for loop. They hide too much... like for example the
fact that you are dependant on the current pointer remaining valid to
get the next pointer in the loop.
Erm, I find one succint line easier to read than something sprawled across 2-3
lines of code. Also, I was never under the assumption that you could do a
*_FOREACH() loop while the list changed out from under you. I doubt anyone
else is either. :)
-Matt
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
A bug in specfs's fsync dating back to Kirk's original softupdates work
( which required a similar mark/scan fix to the FFS fsync ) appears to
have been exposed by recent pageout peformance commits I made.
I've committed a mark/scan fix to specfs's fsync, which appears
to solve the lockups Poul was getting doing a 'cvs update -PdA' under
-current. It should solve the problem for the other two people who
reported the same lockup.
I'm not sure why -stable isn't affected. The bug is in -stable as well.
I'll MFC it in two days unless I see complaints sooner. It's a simple
bug fix.
At some point I need to go through all the fsync implementations...
they need the same sort of placemarker fix that I threw into the
pageout daemon scan. The current code uses the 'goto loop' hack, which
is terribly inefficient when combined with a heavily loaded
softupdates-enabled system.
-Matt
Index: spec_vnops.c
===
RCS file: /home/ncvs/src/sys/miscfs/specfs/spec_vnops.c,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -r1.147 -r1.148
--- spec_vnops.c2000/12/26 19:41:37 1.147
+++ spec_vnops.c2000/12/30 23:32:24 1.148
@@ -31,7 +31,7 @@
* SUCH DAMAGE.
*
* @(#)spec_vnops.c8.14 (Berkeley) 5/21/95
- * $FreeBSD: src/sys/miscfs/specfs/spec_vnops.c,v 1.147 2000/12/26 19:41:37 dillon
Exp $
+ * $FreeBSD: src/sys/miscfs/specfs/spec_vnops.c,v 1.148 2000/12/30 23:32:24 dillon
+Exp $
*/
#include sys/param.h
@@ -352,12 +352,25 @@
return (0);
/*
+* MARK/SCAN initialization to avoid infinite loops
+*/
+ s = splbio();
+for (bp = TAILQ_FIRST(vp-v_dirtyblkhd); bp;
+ bp = TAILQ_NEXT(bp, b_vnbufs)) {
+bp-b_flags = ~B_SCANNED;
+ }
+ splx(s);
+
+ /*
* Flush all dirty buffers associated with a block device.
*/
loop:
s = splbio();
for (bp = TAILQ_FIRST(vp-v_dirtyblkhd); bp; bp = nbp) {
nbp = TAILQ_NEXT(bp, b_vnbufs);
+ if ((bp-b_flags B_SCANNED) != 0)
+ continue;
+ bp-b_flags |= B_SCANNED;
if (BUF_LOCK(bp, LK_EXCLUSIVE | LK_NOWAIT))
continue;
if ((bp-b_flags B_DELWRI) == 0)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
: :I'm seeing this kind of hang about twice a day on my build-box. : :Any clues ? insights ? When did this start occuring? I committed some pageout buffer-cache-related I/O pipelining a day or two ago to -current (which has been well tested under -stable and reasonably well tested under -current). But -current has generally been very unstable for me for months now and that makes it extremely difficult to isolate problems. What's the filesystem configuration being hit by the compile? Are you running any MFS or VN paritions? Is softupdates turned on on the underlying filesystem? On the face of it it looks like a bawrite() is being turned into a bdwrite() somehow and that spec_fsync() is hitting its 'goto loop' restart code and looping on the same buffer... which can happen if the bawrite() is being turned into a bdwrite(). It looks like spec_fsync() is in an infinite loop. -Matt :login: [halt - sent] :Stopped at siointr1+0xb1: jmp siointr1+0x1b7 :db ps : pid proc addruid ppid pgrp flag stat wmesg wchan cmd :39121 d56c7200 d581b0000 39120 24496 004006 2 ld :... : 121 d2a0a420 d568c0000 1 121 84 3 select c02bbed0 syslogd :5 d2a0aa80 d2f5c0000 0 0 000204 2 syncer :4 d2a0aca0 d2f5a0000 0 0 100204 3 psleep c02a4924 bufdaemon :3 d2a0aec0 d2f580000 0 0 000204 3 psleep c02b02e0 vmdaemon :2 d2a0b0e0 d2f560000 0 0 100204 3 psleep c0288018 pagedaemon : 21 d2a0b300 d2e2b0000 0 0 000204 6 swi0: tty:si :o : 20 d2a0b520 d2e290000 0 0 000204 6 irq1: atkbd0 : 19 d2a0b740 d2e270000 0 0 000204 6 irq6: fdc0 : 18 d2a0b960 d2e250000 0 0 000204 2 irq9: fxp0 :... : 14 d2a0c1e0 d2e1c0000 0 0 000204 3 rndslp c0295008 random :... : 13 d2a0c400 d2e1a0000 0 0 000204 6 swi4: vm : 12 d2a0c620 d2e180000 0 0 00020c 2 swi6: clock : 11 d2a0c840 d2e160000 0 0 000204 6 swi1: net : 10 d2a0ca60 d2a130000 0 0 00020c 2 idle :1 d2a0cc80 d2a110000 0 1 004284 3wait d2a0cc80 init :0 c02baf40 c03310000 0 0 010204 3 sched c02baf40 swapper :db where :No such command :db trace :siointr1(c104e400,cbb336b0,1,0,d2f5de78) at siointr1+0xb1 :siointr(c104e400,10,10,10,0) at siointr+0x4e :Xfastintr4(cbb336b0,cbb336b0,cbb336b0,cbb336b0,1) at Xfastintr4+0x25 :bdwrite(cbb336b0,0,0,cbb336b0,d2f54400) at bdwrite+0xb9 :bwrite(cbb336b0,d2f5def8,c0182c2d,d2f5df10,d2f5df04) at bwrite+0x76 :vop_stdbwrite(d2f5df10,d2f5df04,c0193695,d2f5df10,d2f5df1c) at vop_stdbwrite+0xe :vop_defaultop(d2f5df10,d2f5df1c,c017d49a,d2f5df10,c0274460) at vop_defaultop+0x15 :spec_vnoperate(d2f5df10,c0274460,d2f54400,cbb336b0,d2f5df48) at spec_vnoperate+0x15 :bawrite(cbb336b0,0,cbb336b0) at bawrite+0x32 :spec_fsync(d2f5df7c,d2f5df9c,c01857be,d2f5df7c,0) at spec_fsync+0x141 :spec_vnoperate(d2f5df7c) at spec_vnoperate+0x15 :sched_sync(0) at sched_sync+0x13e :fork_trampoline() at fork_trampoline+0x15 :db : :-- :Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 :[EMAIL PROTECTED] | TCP/IP since RFC 956 :FreeBSD committer | BSD since 4.3-tahoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
If possible, 'print *bp' from a gdb'd kernel dump if you can. I suspect this may be related to 'bp-b_xflags BX_BKGRDINPROG'. If a bitmap is undergoing a background write and is then dirtied a second time and bawrite()n, the bawrite() will be turned into a bdwrite() (because a prior write is already in progress). If this is the case we may have to implement the same MARK/SCAN code for spec_fsync() that we implemented for FFS's fsync code. FFS's fsync code got into infinite loops trying to fsync() buffers with softupdates dependancies -- whos bawrite()'s were being turned into bdwrite()'s due to the dependancies. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
In message [EMAIL PROTECTED], Matt Dillon writes: : :I'm seeing this kind of hang about twice a day on my build-box. : :Any clues ? insights ? When did this start occuring? Can't say for sure, it's certainly noticeable today, but I have not had much FreeBSD time recently so I would be hard pressed to say more definitively when it started. But -current has generally been very unstable for me for months now and that makes it extremely difficult to isolate problems. OFF TOPIC Yeah, I'm increasingly in favour of a "bake-out" period where no new subsystems are SMPng'ed until -current is stabilized. Sos tells me that running SMP is an instant death request these days. My SMP systems are not even powered on right now. /OFF TOPIC What's the filesystem configuration being hit by the compile? Are you running any MFS or VN paritions? Is softupdates turned on on the underlying filesystem? Two ATA disks one CCD striped, softupdates. On the face of it it looks like a bawrite() is being turned into a bdwrite() somehow and that spec_fsync() is hitting its 'goto loop' restart code and looping on the same buffer... which can happen if the bawrite() is being turned into a bdwrite(). It looks like spec_fsync() is in an infinite loop. There is no other signs of trouble, processes hang when they attempt some (but maybe not all) kind of I/O. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs...
I am seeing a couple of problems with -current. Running gdb on a recent -current, # uname -a FreeBSD dsl081-020-229-sea1.dsl-isp.net 5.0-CURRENT FreeBSD 5.0-CURRENT \ #1: Wed Dec 27 16:20:32 PST 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS i386 causes the console to go out into left field somewhere. # gdb hello (gdb) b main (gdb) r and all xterms stop responding, although keyboard input is echoed. Ctl-Alt-F1 switches to console. Keyboard input is echoed, but, not responded to. Clt-Alt-Esc breaks into the debugger, but, all looks like breaking into the debugger under normal operation. With -current SMP, I get Fatal Trap 12's during 'make world' and transactions to lpd. I have posted the SMP problem to -smp, and, am hiding and watching. So far, no resolution. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Did I miss something on the /dev/random hang? I don't know... During a `shutdown -r now`, the boot process hangs for more than an hour. I thought this was supposed to work. However, jwd's receipe for recovery works. I repeated this three times, although I only waited an hour the last time (dinner!). I am running a recent SMP system, uname and dmesg below. Are you _completely_ up to date with /etc/*? Dou you run mergemaster after each make world/make kernel? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
I cannot make mergemaster work. Tried twice earlier in the year and took several hours to recover... Don't know what my problem is. However, I have a script that compares and lists diffs in /etc/rc* and /etc/defaults/* to those in src/etc. Normally, I manually copy those files to /etc. # grep '$FreeBSD' /etc/rc /etc/rc.shutdown /etc/defaults/rc.conf /etc/rc:# $FreeBSD: src/etc/rc,v 1.239 2000/10/22 19:10:13 phk Exp $ /etc/rc.shutdown:# $FreeBSD: src/etc/rc.shutdown,v 1.15 2000/10/20 20:26:05 ache Exp$ /etc/defaults/rc.conf:# $FreeBSD: src/etc/defaults/rc.conf,v 1.83 2000/10/29 19:59:04 ume Exp $ These are the proper versions. After looking through rc.shutdown, 'Writing entropy file.' is not displayed. In /etc/defaults/rc.conf and /usr/src/etc/defaults/rc.conf, I have ... entrop^%]0y_file="/entropy" # Set to NO to disable caching entropy through reboots. ... Garble? Fixing this fixes the problem. Thanks Mark. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Did I miss something on the /dev/random hang? During a `shutdown -r now`, the boot process hangs for more than an hour. I thought this was supposed to work. However, jwd's receipe for recovery works. I repeated this three times, although I only waited an hour the last time (dinner!). I am running a recent SMP system, uname and dmesg below. tomdean = from the console = ... Doing additional network setup: portmap. Starting final network daemons: mountd nfsd rpc.statd nfsiod \ NFS access cache time=2. setting ELF ldconfig path: /usr/lib /usr/lib/compat \ /usr/X11R6/lib /usr/local/lib --- ^t at this point, after waiting an hour load: 0.00 cmd: ldconfig 137 [rndblk] 0.00u 0.00s 0% 104k ^\Reboot interrupted Nov 3 17:38:40 celebris /boot/kernel/kernel: pid 137 (ldconfig), \ uid 0: exited on signal 3 (core dumped) Enter full pathname of shell or RETURN for /bin/sh: # ls -al /etc /dev/random # exit Skipping disk checks ... Doing initial network setup:. ... uname -a == FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Nov 3 \ 16:30:23 PST 2000 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 === dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Fri Nov 3 16:30:23 PST 2000 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (122.68-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC real memory = 100663296 (98304K bytes) avail memory = 94740480 (92520K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0314000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc031409c. Intel Pentium detected, installing workaround for F00F bug npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 ncr0: ncr 53c810 fast10 scsi port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: Intel 82378IB PCI to ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 pci0: Matrox MGA Millennium 2064W graphics accelerator at 6.0 irq 9 de0: Digital 21041 Ethernet port 0xe880-0xe8ff mem 0xfedfbe80-0xfedfbeff irq 10 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: IBM Enhanced (101/102-key) KC can't assign resources unknown: Microsoft PS/2 Mouse can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: 16550 compatible COM device can't assign resources unknown: LPT printer port can't assign resources unknown: Floppy Controller can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1s1a da0 at ncr0 bus 0 target 0 lun 0 da0: QUANTUM FIREBALL1080S 1Q09 Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: QUANTUM EMPIRE_1080S 1240 Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: TOSHIBA CD-ROM XM-5401TA 3605 Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ncr0 bus 0 target 1 lun 0 da1: IBM DNES-309170 SAH0 Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) SMP: AP CPU #1 Launched! de0: enabling BNC port pid 137 (ldconfig), uid 0: exited on signal
Re: current hangs when boot
In message [EMAIL PROTECTED] Bigbear writes: : i update my system from 4.1 to current, when system boot, it hangs when: : start elf ldconfig: /usr/lib /usr/lib/compat /usr/X11R6/lib : why? This is not a hang, otherwise you would not have been able to boot by pressing ^C or ^T The files , especially rc files in /etc are not the newest ones. The script rc is suppose to use ldconfig to update the library database, but when it starts it waits. If you bypass this by pressing keys, the it might happen that you get errors with certain libraries, seeing that they are not loaded. So, all you need to do is to take /usr/src/etc and copy rc* /etc This solved the problem for me. I did a make buildworld and installworld yesterday and i got the problem on a second reboot. I had a look in the /etc directory and saw that the files did not install ... which makes sense since the spec of buildworld/installworld is that the etc dir is not updated. I started a make release 25 minutes ago, will see if the end result of a snapshot will give the same problem. P.S. After updating your files in /etc, do a shutdown -r now , the shutdown rc script will take care of the entropy factor next time around. : ^C also works. : : ^T is generally useful if you suspect something is hanging on bootup but : don't know what it is. We also found at bsdcon that lots of keystrokes would also make the system boot. Which reminds me of the Sun software problem report that had as the engineering reply: "Don't hit on the keyboard like a wild monkey" .. :-) -- Unix Software Developer/Engineer E-Mail: Johan Kruger [EMAIL PROTECTED] Date: 25-Oct-00 Time: 11:02:51 OS: FreeBSD 5.0-2724-SNAP All good things come to those who ... run FreeBSD -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
re: -current hangs during boot (UPDATING entry)
It does look like an updating entry is needed for this badly. I did the following things, some of which may not be needed, and now my -current boxes boot OK. 1. update MAKEDEV from /usr/src/etc, run MAKEDEV all 2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc 3. add random_load="YES" to /boot/loader.conf 4. update /etc/login.conf from /usr/src/etc 5. do a "shutdown -r now" which creates the entropy file and reboots Now the system boot does not hang at the ldconfig spots. It does look like there is a lot to do to get back on course, enough to justify adding to UPDATING. Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
Thanks for the updates. A few questions below. -John - Mark Hittinger's Original Message - It does look like an updating entry is needed for this badly. I did the following things, some of which may not be needed, and now my -current boxes boot OK. 1. update MAKEDEV from /usr/src/etc, run MAKEDEV all 2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc 3. add random_load="YES" to /boot/loader.conf or add the random device to the kernel config file. 4. update /etc/login.conf from /usr/src/etc I don't remember having to do this... was there a specific reason? 5. do a "shutdown -r now" which creates the entropy file and reboots Now the system boot does not hang at the ldconfig spots. It does look like there is a lot to do to get back on course, enough to justify adding to UPDATING. Later Mark Hittinger Earthlink [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. You can leave them in, with option "noauto", and mount them later with "mount -a -t mfs". -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
In message [EMAIL PROTECTED] Leif Neland writes: : Hi there, : : I've done a very recent week's make world(S) on -current, making : and installing world and kernel go fine, but all hang on boot, : with no error codes or msgs. : : Solution: Due to changes in the random/entropy stuff, you have to reboot : the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". : : (Why do we have a separate reboot command? Couldn't it just be an alias : for shutdown -r now?) reboot should be a seprate command. It should, however, cause the shutdown scripts to run unless it is run -f. shutdown implies sending all messages to all users of NFS filesystems, which isn't desirable in many cases. At least that's why my fingers type reboot to this day: On sunos 4.0 (really Solbourne OS/MP 4.0D) in a large company these messages would scare more people than they informed... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs when boot
In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : On Mon, 23 Oct 2000, Brian O'Shea wrote: : I am also having this problem. If you interrupt it (with ^\ to send : SIGQUIT), ldconfig generates a core. Then ldconfig will hang while : setting a.out ldconfig path: : : ^C also works. : : ^T is generally useful if you suspect something is hanging on bootup but : don't know what it is. We also found at bsdcon that lots of keystrokes would also make the system boot. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: devicerandom # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
It didn't work without the device line when I tested it last week(Thursday/Friday). -John - David O'Brien's Original Message - On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: device random # Entropy device Are you implying the random.ko module is broken? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
BSDcon Was: Re: current hangs when boot
On Tue, 24 Oct 2000, Warner Losh wrote:
We also found at bsdcon that lots of keystrokes would also make the
system boot.
Warner
For those of us that couldn't go, has anybody posted pictures from the con
yet? ...any kind of pictures - not just ones of keyboard bashing...
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
You need to put random_load="YES" into /boot/loader.conf. Optionally, you can load random.ko during the boot process. John W. De Boskey wrote: It didn't work without the device line when I tested it last week(Thursday/Friday). - David O'Brien's Original Message - On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote: 2. Make sure your kernel includes: devicerandom # Entropy device Are you implying the random.ko module is broken? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs when boot
On Tue, Oct 24, 2000 at 12:38:41PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : On Mon, 23 Oct 2000, Brian O'Shea wrote: : I am also having this problem. If you interrupt it (with ^\ to send : SIGQUIT), ldconfig generates a core. Then ldconfig will hang while : setting a.out ldconfig path: : : ^C also works. : : ^T is generally useful if you suspect something is hanging on bootup but : don't know what it is. We also found at bsdcon that lots of keystrokes would also make the system boot. Which reminds me of the Sun software problem report that had as the engineering reply: "Don't hit on the keyboard like a wild monkey" .. :-) -- Wilko Bulte Arnhem, the Netherlands [EMAIL PROTECTED] http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
On Mon, 23 Oct 2000, John W. De Boskey wrote: I'm beginning to think we need an updating entry. 1. Make sure /dev/random exists 'cd /dev sh MAKEDEV std' Unless you are using devfs. 2. Make sure your kernel includes: devicerandom # Entropy device Or the appropriate line in /boot/mumble.conf 3. Make sure /etc/rc is at rev 1.237 or higher. 4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.15 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. A better solution would be to increase the granularity of the file system mounts so that the MFS systems were mounted after the entropy gathering. There are a couple of reasons I changed the ordering on the two reseeding attempts, one of the big ones was that for the "manual" reseed (i.e., no entropy file) we want more parts of the system mounted so that we have more potential entropy gathering tools. Rest sounds good... Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs when boot
(Yikes, my message turned out to be a bit long, sorry) I did a little poking around. I'm running -current as of last Saturday: # uname -a FreeBSD panic.localdomain 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Oct 21 22:20:11 PDT 2000 [EMAIL PROTECTED]:/usr/obj/usr/local/cvs up/current/src/sys/PANIC i386 On Mon, Oct 23, 2000 at 12:27:25AM +, Bigbear wrote: i update my system from 4.1 to current, when system boot, it hangs when: start elf ldconfig: /usr/lib /usr/lib/compat /usr/X11R6/lib why? I am also having this problem. If you interrupt it (with ^\ to send SIGQUIT), ldconfig generates a core. Then ldconfig will hang while setting a.out ldconfig path: ^Csetting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout This can be interrupted too, and then it hangs while starting sshd. Interrupting sshd allows the boot to procede. I got a core from each program during the hang, and here's what I found: Here's the backtrace from the core obtained from ldconfig (rebuilt with -g) the first time around: (starting elf ldconfig) (gdb) bt #0 0x8054340 in read () #1 0x804c966 in mktemp () #2 0x804ca33 in arc4random_stir () #3 0x804cad9 in arc4random () #4 0x804c791 in mktemp () #5 0x804c692 in mkstemp () #6 0x804886a in write_elf_hints () #7 0x8048818 in update_elf_hints () #8 0x8048c61 in main () #9 0x8048139 in _start () And the second time around: (setting a.out ldconfig path) (gdb) bt #0 0x8054340 in read () #1 0x804c966 in mktemp () #2 0x804ca33 in arc4random_stir () #3 0x804cad9 in arc4random () #4 0x804c791 in mktemp () #5 0x804c692 in mkstemp () #6 0x8049590 in buildhints () #7 0x8048e39 in main () #8 0x8048139 in _start () And from sshd: (gdb) bt #0 0x28208784 in read () from /usr/lib/libc.so.4 #1 0x282081ce in __sread () from /usr/lib/libc.so.4 #2 0x281f67a6 in __srefill () from /usr/lib/libc.so.4 #3 0x281f23bd in fread () from /usr/lib/libc.so.4 #4 0x281217c1 in RAND_SSLeay () from /usr/lib/libcrypto.so.1 #5 0x28121869 in RAND_SSLeay () from /usr/lib/libcrypto.so.1 #6 0x281212cc in RAND_bytes () from /usr/lib/libcrypto.so.1 #7 0x28146099 in DSA_OpenSSL () from /usr/lib/libcrypto.so.1 #8 0x28146151 in BN_rand () from /usr/lib/libcrypto.so.1 #9 0x280e4561 in BN_is_prime_fasttest () from /usr/lib/libcrypto.so.1 #10 0x280e3e03 in BN_generate_prime () from /usr/lib/libcrypto.so.1 #11 0x280da4a8 in RSA_generate_key () from /usr/lib/libcrypto.so.1 #12 0x8059437 in getsockname () #13 0x804c35b in getsockname () #14 0x804b76d in getsockname () Running ldconfig manually, 'top' shows ldconfig sleeping on 'rndblk': PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND ... 228 root 46 0 216K 104K rndblk 0:00 0.00% 0.00% ldconfig More investigation: # fstat /dev/urandom USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME root ldconfig 2283 / 7973 crw-r--r-- urandom r /dev/urandom # ps auxw | grep ldconfig root 228 0.0 0.4 216 104 d0 I 2:18AM 0:00.00 ldconfig -elf /usr/lib This commit from Peter Wemm on Oct 18 might shed some light: peter 2000/10/18 03:39:18 PDT Modified files: sys/dev/random randomdev.c Log: Attempt to fix the random read blocking. The old code slept at priority "0" and without PCATCH, so it was uninterruptable. And even when it did wake up after entropy arrived, it exited after the wakeup without actually reading the freshly arrived entropy. I sent this to Mark before but it seems he is in transit. Mark: feel free to replace this if it gets in your way. Revision ChangesPath 1.16 +14 -15src/sys/dev/random/randomdev.c Maybe this is a related problem (except now random read blocking is interruptable?) -- Brian O'Shea [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
I'm beginning to think we need an updating entry. 1. Make sure /dev/random exists 'cd /dev sh MAKEDEV std' 2. Make sure your kernel includes: device random # Entropy device 3. Make sure /etc/rc is at rev 1.237 or higher. 4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.15 5. At this time, remove ALL MFS filesystems from /etc/fstab. They can be hand mounted after bootup or via a local rc startup script. 6. Reboot your system via 'init 6' or 'shutdown -r now' (or similar). Do not use 'reboot'. 7. If at any time during the boot process a 'cntrl-t' shows a process hung in 'rndblk', hit 'cntrl-\', 'ls -al /etc /dev/random', and then 'exit'. This should get your machine to boot for this session until you figure out which of the above are not done. -John - Brian O'Shea's Original Message - On Sun, Oct 22, 2000 at 07:35:39PM -0400, John W. De Boskey wrote: - David O'Brien's Original Message - On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. I saw this the other day... I've been examining the mfs code, and I'm not really sure why it needs to use random values... When ldconfig hangs, it is in a mkstemp() call. The mkstemp() function probably uses random numbers to generate unique file names: #0 0x8054340 in read () #1 0x804c966 in mktemp () #2 0x804ca33 in arc4random_stir () #3 0x804cad9 in arc4random () #4 0x804c791 in mktemp () #5 0x804c692 in mkstemp () #6 0x804886a in write_elf_hints () #7 0x8048818 in update_elf_hints () #8 0x8048c61 in main () #9 0x8048139 in _start () -brian -- Brian O'Shea [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs when boot
On Mon, 23 Oct 2000, Brian O'Shea wrote: I am also having this problem. If you interrupt it (with ^\ to send SIGQUIT), ldconfig generates a core. Then ldconfig will hang while setting a.out ldconfig path: ^C also works. ^T is generally useful if you suspect something is hanging on bootup but don't know what it is. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
jwd 5. At this time, remove ALL MFS filesystems from /etc/fstab. jwdThey can be hand mounted after bootup or via a local rc jwdstartup script. Is there any chance to mount MFS filesystem listed in /etc/fstab just after the /dev/random reseeding is done ? I cannot put up with that we cannot put 'mfs' line to /etc/fstab forever. Moreover, /tmp (common MFS candidate) is already used by X server after rebooting; you may not want to mount /tmp at hand later. Or, it's only for upgrading procedure, and we can put 'mfs' lines back? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot (UPDATING entry)
- Makoto MATSUSHITA's Original Message - jwd 5. At this time, remove ALL MFS filesystems from /etc/fstab. jwdThey can be hand mounted after bootup or via a local rc jwdstartup script. Is there any chance to mount MFS filesystem listed in /etc/fstab just after the /dev/random reseeding is done ? I cannot put up with that we cannot put 'mfs' line to /etc/fstab forever. Moreover, /tmp (common MFS candidate) is already used by X server after rebooting; you may not want to mount /tmp at hand later. Or, it's only for upgrading procedure, and we can put 'mfs' lines back? #5 above represents a bug in the current code. It needs to be fixed, but I don't know what the 'correct' thing to do is just yet. Does the FSIRAND code in mfs require crypto strength randomness? -John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
On Sun, 22 Oct 2000, Donny Lee wrote: Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. When boot, all go fine at the beginning, and stop right after showing the msg: : : /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, 0.1%fragmentation) then no more, I got to power off and on, and reboot using an old working kernel. metoo My hangs at loading ldconf. I can continue with ^C. It then hangs at loading aout-ldconf. I can continue with ^C It hangs a 3. time, where I again can continue with ^C. It then complains for missing .so's, naturally because the ldconf was interrupted, and some commands won't work because of that, but the system is at least somewhat working... /metoo I'll see if I can narrow it down somewhat. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
John W. De Boskey noticed me some points to check out, I now can boot my fbsd box with the recent built kernel. I disabled mfs, and random_load, these 2 made my fbsd box hangs (not really hangs, it looks like waiting for some jobs done) 2 times at boot. with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. -- // Donny Leif Neland wrote: When boot, all go fine at the beginning, and stop right after showing the msg: : /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks, 0.1%fragmentation) metoo My hangs at loading ldconf. I can continue with ^C. It then hangs at loading aout-ldconf. I can continue with ^C It hangs a 3. time, where I again can continue with ^C. It then complains for missing .so's, naturally because the ldconf was interrupted, and some commands won't work because of that, but the system is at least somewhat working... /metoo I'll see if I can narrow it down somewhat. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
leifn My hangs at loading ldconf. I can continue with ^C. Are you using MFS ? I suppose you are not. I've found that: - if /etc/fstab has 'mfs' line, system stops during mounting filesystem. Interrupting with CTRL-C works (and system goes to single user mode). - if /etc/fstab does not have 'mfs' line, system stops during ldconfig. Also interruptable. System is working (you can login from console), but something goes wrong (network interface doesn't work). Your case is the latter one, and previous email you have mentioned is the former one. I can reproduce both cases with a -current box cvsuped two days before. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. Solution: Due to changes in the random/entropy stuff, you have to reboot the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". not quite understand this... do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? (Why do we have a separate reboot command? Couldn't it just be an alias for shutdown -r now?) I don't know, it's there. :) try man reboot, it gives me lots. no it's not alias for any other commands. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
- Leif Neland's Original Message - On Sun, 22 Oct 2000, Donny Lee wrote: Hi there, I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. Solution: Due to changes in the random/entropy stuff, you have to reboot the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". (Why do we have a separate reboot command? Couldn't it just be an alias for shutdown -r now?) See pr 14829 and: http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/rc revision 1.235 for a few additional comments. -John Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
- Original Message - From: "Donny Lee" [EMAIL PROTECTED] To: "Leif Neland" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, October 22, 2000 10:59 AM Subject: Re: -current hangs during boot Leif Neland wrote: I've done a very recent week's make world(S) on -current, making and installing world and kernel go fine, but all hang on boot, with no error codes or msgs. Solution: Due to changes in the random/entropy stuff, you have to reboot the machine with "shutdown -r now" or Ctrl-alt-del, not "reboot". not quite understand this... do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? Exactly. Except not just after make world/kernel, every time you want to reboot/halt. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? Exactly. Except not just after make world/kernel, every time you want to reboot/halt. Does this make any different? shutdown is fine, but ctrl-alt-del is not so good, whenever I did this, the next boot takes a long time on fixing filesystems. -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: do you mean one should use "shutdown -r now" or Ctrl-Alt-Del instead of "reboot" right after make world and kernel? Exactly. Except not just after make world/kernel, every time you want to reboot/halt. Does this make any different? shutdown is fine, but ctrl-alt-del is not so good, whenever I did this, the next boot takes a long time on fixing filesystems. You mean your system doesn't unmount the disks at ctrl-alt-del? Does it a hard reset instead? Strange... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Leif Neland wrote: Does this make any different? shutdown is fine, but ctrl-alt-del is not so good, whenever I did this, the next boot takes a long time on fixing filesystems. You mean your system doesn't unmount the disks at ctrl-alt-del? Does it a hard reset instead? Strange... i might remember wrong, i haven't done so for a long time. Ok, i'm wrong... i'm just back from ctrl-alt-del. :) -- // Donny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
- David O'Brien's Original Message - On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote: with the mfs enable, it hangs there right after FILESYSTEM checking, and with random_load set to YES, it hangs at ldconfig. mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*. I saw this the other day... I've been examining the mfs code, and I'm not really sure why it needs to use random values... Anyone know the history on the '#ifdef FSIRAND' code? -john ps: break out of the boot sequence, 'ls -al /etc/ /dev/random' and then 'exit' will get around this and other problems, but requires hands on reboots. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current hangs during boot
Anyone know the history on the '#ifdef FSIRAND' code? Randomized file generation numbers to make NFS attacks more difficult, as far as I can remember. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs in make world (softupdates on ccd on ata)
Poul-Henning Kamp wrote: Make world hangs reliably for me right now: [snip] |yacc -d -o c-parse.c c-parse.y + 0 19921 1 83 -2 0 1276 932 getblk D p00:00.09 yacc -d -o c-parse.c c-parse.y This is a softupdates filesystem on a ccd on ata... The format used for mkstemp has been changed (4 chars. longer). Does the following patch work? Index: main.c === RCS file: /home/ncvs/src/usr.bin/yacc/main.c,v retrieving revision 1.11 diff -u -r1.11 main.c --- main.c 2000/01/10 08:54:09 1.11 +++ main.c 2000/01/10 17:47:33 @@ -304,7 +304,7 @@ if (tmpdir == 0) tmpdir = "/tmp"; len = strlen(tmpdir); -i = len + 13; +i = len + 17; if (len tmpdir[len-1] != '/') ++i; -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs in make world (softupdates on ccd on ata)
:Make world hangs reliably for me right now: :+ :|... :|/* starting time is 16:18:8 */ :|/* ending time is 16:18:8 */ :|ln -sf gxx-hash.h hash.h :|echo '#include "cp/cp-tree.def"' gencheck.h :|echo '#include "objc/objc-tree.def"' gencheck.h :|sed -e "/^ifobjc$/,/^end ifobjc$/d" -e "/^ifc$/d" -e "/^end ifc$/d" :/syv/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.in c-parse.y :|yacc -d -o c-parse.c c-parse.y :+ : :0 19921 1 83 -2 0 1276 932 getblk D p00:00.09 yacc -d -o :c-parse.c c-parse.y : :This is a softupdates filesystem on a ccd on ata... : :-- :Poul-Henning Kamp FreeBSD coreteam member :[EMAIL PROTECTED] "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! No vinum? Please ps axl and pick out any other processes stuck in odd places. Then gdb -k kernel.debug /dev/mem (assuming you have kernel.debug sitting around somewhere). proc 19921 back proc ...other processes... back ... note: if you have a custom .gdbinit that sets the base to hex you may have to type the process number in hex. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs in make world (softupdates on ccd on ata)
On Mon, 10 Jan 2000, Marcel Moolenaar wrote: The format used for mkstemp has been changed (4 chars. longer). Does the following patch work? Sorry, but FWIW I did test the change by recompiling cvs (which uses yacc) before I committed it :( I guess it was just the gods of stack which allowed that one to build. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs when dump is run?
Hello! Since Nov 12th, I've been having this problem, too. Is there a solution/workaround available yet? I'm using a SCSI DAT drive and making backups using dump or tar works, but amanda still manages to hang the machine! Many thanks, Christian. AFAIR Taavi Talvik wrote on Sa , 20 Nov 1999: On Fri, 19 Nov 1999, Poul-Henning Kamp wrote: If you're using the ata driver, please remove the ad_sleep() call at the bottom of the adopen() in ata-disk.c and see if that helps you. Yes, i am using ata driver, but your suggestion didn't help. Still same story. Crash dumps are available.. Current seems to hangs, when amanda tries to run dump. This appeared approximately 2 weeks ago, and is present in yesterdays current also. #0 0xc013daa4 in boot () #1 0xc013de41 in panic () #2 0xc011d739 in db_panic () #3 0xc011d6d9 in db_command () #4 0xc011d79e in db_command_loop () #5 0xc011f82f in db_trap () #6 0xc02011ef in kdb_trap () #7 0xc020f434 in trap () #8 0xc020144b in Debugger () #9 0xc01fcb06 in scgetc () #10 0xc01f8271 in sckbdevent () #11 0xc01f1a8f in atkbd_intr () #12 0xc021cd74 in atkbd_isa_intr () #13 0xc0217c66 in splx () #14 0xc0140a55 in tsleep () #15 0xc0146889 in diskopen () #16 0xc0170251 in spec_open () #17 0xc017014d in spec_vnoperate () #18 0xc01bb579 in ufs_vnoperatespec () #19 0xc016a57c in vn_open () #20 0xc01669dd in open () #21 0xc020fd02 in syscall () #22 0xc0201af6 in Xint0x80_syscall () #23 0x804b91a in ?? () #24 0x804b6b3 in ?? () [109:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.5 -N kernel.5 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND amanda 1365 99.0 0.0 6280 ?? R 1Jan70 0:00.00 (dump) root 1 0.0 0.0 5160 ?? ILs 1Jan70 0:00.02 /sbin/init -- root 2 0.0 0.0 00 ?? RL1Jan70 0:00.03 (pagedaemon) root 3 0.0 0.0 00 ?? DL1Jan70 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? RL1Jan70 0:00.03 (bufdaemon) root 5 0.0 0.0 00 ?? RL1Jan70 0:00.88 (syncer) --- Taavi Talvik| Internet: [EMAIL PROTECTED] Unineti Andmeside AS| phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs when dump is run?
On Fri, 19 Nov 1999, Poul-Henning Kamp wrote: If you're using the ata driver, please remove the ad_sleep() call at the bottom of the adopen() in ata-disk.c and see if that helps you. Yes, i am using ata driver, but your suggestion didn't help. Still same story. Crash dumps are available.. Current seems to hangs, when amanda tries to run dump. This appeared approximately 2 weeks ago, and is present in yesterdays current also. #0 0xc013daa4 in boot () #1 0xc013de41 in panic () #2 0xc011d739 in db_panic () #3 0xc011d6d9 in db_command () #4 0xc011d79e in db_command_loop () #5 0xc011f82f in db_trap () #6 0xc02011ef in kdb_trap () #7 0xc020f434 in trap () #8 0xc020144b in Debugger () #9 0xc01fcb06 in scgetc () #10 0xc01f8271 in sckbdevent () #11 0xc01f1a8f in atkbd_intr () #12 0xc021cd74 in atkbd_isa_intr () #13 0xc0217c66 in splx () #14 0xc0140a55 in tsleep () #15 0xc0146889 in diskopen () #16 0xc0170251 in spec_open () #17 0xc017014d in spec_vnoperate () #18 0xc01bb579 in ufs_vnoperatespec () #19 0xc016a57c in vn_open () #20 0xc01669dd in open () #21 0xc020fd02 in syscall () #22 0xc0201af6 in Xint0x80_syscall () #23 0x804b91a in ?? () #24 0x804b6b3 in ?? () [109:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.5 -N kernel.5 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND amanda 1365 99.0 0.0 6280 ?? R 1Jan70 0:00.00 (dump) root 1 0.0 0.0 5160 ?? ILs 1Jan70 0:00.02 /sbin/init -- root 2 0.0 0.0 00 ?? RL1Jan70 0:00.03 (pagedaemon) root 3 0.0 0.0 00 ?? DL1Jan70 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? RL1Jan70 0:00.03 (bufdaemon) root 5 0.0 0.0 00 ?? RL1Jan70 0:00.88 (syncer) --- Taavi Talvik| Internet: [EMAIL PROTECTED] Unineti Andmeside AS| phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs when dump is run?
Taavi Talvik [EMAIL PROTECTED] wrote: Current seems to hangs, when amanda tries to run dump. This appeared approximately 2 weeks ago, and is present in yesterdays current also. Not for me. I made the world yesterday, and this morning's backup (with dump) ran fine. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current hangs when dump is run?
If you're using the ata driver, please remove the ad_sleep() call at the bottom of the adopen() in ata-disk.c and see if that helps you. Poul-Henning In message [EMAIL PROTECTED], Taavi Talvi k writes: Current seems to hangs, when amanda tries to run dump. This appeared approximately 2 weeks ago, and is present in yesterdays current also. #0 0xc013daa4 in boot () (kgdb) bt #0 0xc013daa4 in boot () #1 0xc013de41 in panic () #2 0xc011d739 in db_panic () #3 0xc011d6d9 in db_command () #4 0xc011d79e in db_command_loop () #5 0xc011f82f in db_trap () #6 0xc02011fb in kdb_trap () #7 0xc020f444 in trap () #8 0xc0201457 in Debugger () #9 0xc01fcb12 in scgetc () #10 0xc01f827d in sckbdevent () #11 0xc01f1a9b in atkbd_intr () #12 0xc021cd84 in atkbd_isa_intr () #13 0xc0202fe2 in vec1 () #14 0xc0140a55 in tsleep () #15 0xc0146889 in diskopen () #16 0xc0170251 in spec_open () #17 0xc017014d in spec_vnoperate () #18 0xc01bb579 in ufs_vnoperatespec () #19 0xc016a57c in vn_open () #20 0xc01669dd in open () #21 0xc020fd12 in syscall () #22 0xc0201b06 in Xint0x80_syscall () #23 0x804b91a in ?? () #24 0x804b6b3 in ?? () #25 0x80491c0 in ?? () and ps shows [127:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.4 -N kernel.4 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND amanda 380 99.0 0.0 6280 ?? R 1Jan70 0:00.00 (dump) root 1 0.0 0.0 5160 ?? ILs 1Jan70 0:00.02 /sbin/init -- root 2 0.0 0.0 00 ?? RL1Jan70 0:00.01 (pagedaemon) root 3 0.0 0.0 00 ?? DL1Jan70 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? RL1Jan70 0:00.01 (bufdaemon) root 5 0.0 0.0 00 ?? RL1Jan70 0:00.28 (syncer) . I have kernel and core saved, if someone needs them. best regards, taavi --- Taavi Talvik| Internet: [EMAIL PROTECTED] Unineti Andmeside AS| phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
