Complete hangs while extracting source

Jakob Breivik Grimstveit jakob at
Mon Oct 3 00:44:08 PDT 2005

David Kirchner wrote on Sun, 02 Oct 2005 16:50:

> On 10/2/05, Jakob Breivik Grimstveit <jakob at> wrote:
> > How can I tell? I doubt this to be the problem, since I experience same
> > problem on two other machines as well. Only thing they share (except same
> > lousy administrator :-) is that they all run on AMD CPUs (1700+, 1800+ and
> > 3500+).
> dmesg will show you irqs, but you can also find it using systat's
> "vmstat" mode. It'll also allow you to monitor interrupt activity.
> It's best used from the console of the machine. I would guess you'd
> want to watch for two drivers, sharing an interrupt, and both
> incrementing at the same rate. (I've seen that before, and it was
> associated with severe performance problems, but unfortunately I do
> not recall how it was fixed.)

My machine at work (AMD1700+) has same problems - here is it's dmesg IRQs:

[jakobbg at nusse ~]$ dmesg | grep -i irq
ioapic0 <Version 0.3> irqs 0-23 on motherboard
rl0: <Accton MPX 5030/5038 10/100BaseTX> port 0xec00-0xecff mem 0xdfffff00-0xdfffffff irq 19 at device 8.0 on pci0
uhci0: <VIA 83C572 USB controller> port 0xe000-0xe01f irq 21 at device 16.0 on pci0
uhci1: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 21 at device 16.1 on pci0
uhci2: <VIA 83C572 USB controller> port 0xe800-0xe81f irq 21 at device 16.2 on pci0
pcm0: <VIA VT8235> port 0xdc00-0xdcff irq 22 at device 17.5 on pci0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
unknown: <PNP0f13> can't assign resources (irq)
drm0: <Matrox G550 (AGP)> mem 0xdf000000-0xdf7fffff,0xdfefc000-0xdfefffff,0xdc000000-0xddffffff irq 16 at device 0.0 on pci1

While doing this:

$ cd /tmp && tar
jxf /usr/ports/distfiles/openoffice.org2.0/OOo_1.9m130_source.tar.bz2 

During it's entire run I ran this as well (my computer did nothing else
during that time):

while(true); do date >> vmstat.log && vmstat -i >> vmstat.log && sleep 1; done

The logfile can be found at
<>. Are you able to parse
anything usable from it?

Thanks in advance. If you need anything else, please just ask - I am very
eager to find the cause of these problems.

Jakob Breivik Grimstveit, <>, 48298152
Besøk Newsergalleriet: <>

No violence, gentlemen -- no violence, I beg of you! Consider the furniture!
-- Sherlock Holmes

More information about the freebsd-questions mailing list