John Baldwin writes:
>
> Ok, your BIOS is buggy, but I think I can work around it.
> http://www.FreeBSD.org/~jhb/patches/acpi_irq.patch
>
Thanks, now it's working much better!
New dmesg and vmstat-i at http://tomppa.iki.fi/~tomppa/FreeBSD/
Tomppa
__
Tomi Vainio writes:
> My old MSI-6120 SMP system has been unusable quite a while with ACPI.
> I've got these so far:
> - Couldn't get vector from ISR
> - vmstat -i shows high interrupt rates and system is very slow
> - kernel trap 12 panic
>
> Latest problem is something like this:
> pf
My old MSI-6120 SMP system has been unusable quite a while with ACPI.
I've got these so far:
- Couldn't get vector from ISR
- vmstat -i shows high interrupt rates and system is very slow
- kernel trap 12 panic
Latest problem is something like this:
pfs_vncache_unload(): 2 entries remaining
curr
Hi,
Once again we cvsupped latest ATA code changes and nothing much
changed. Only after couple minutes of stress testing system will
freeze. Though error message is little different than before.
Tomppa
ad5: TIMEOUT - READ_DMA retrying (2 retries left)
ata2: resetting devices ..
ata2: reset t
Hi,
Current ATA code is still unusable unstable. We cvsupped latest
source yesterday and tried our standard stress test copy between two
vinum volumes. Once we even got 12 hour uptime but today it won't
take longer than couple minutes before system freezes. Situation is
even worse if we replace
Hi,
I'd like to give a try for this new code solving lost interrupts but
current code still doesn't find all my slave disks. Is there anything
what might help on this?
Tomppa
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinf
Once again our vinum build failed. This time it could do over 90% of
14 hours of work and we didn't got a panic just a "hang". Only we
could do while system was printing ata error messages was to press
reset button. Difference to earlier situation is that we put back old
3c905 xl-card and remove
Dag-Erling Smørgrav writes:
>
> An NMI almost certainly indicates a hardware failure.
>
Lucas James writes:
>
> It could be a power supply on the way out. I had an old dual P-166 that
> rebooted misterously until I took out two CD-ROM drives I wanted
> for another
> machine. (replace
After adding more disks to this system it dies continously. Last two
traces look quite the same.
Tomppa
---clipclip---
login: kernel trap 19 with interrupts disabled
NMI ... going to debugger
kernel: type 19 trap, code=0
Stopped at rtcintr+0x57: callrtcin
db> trace
rtcintr(0) at rtc
Once again our current platform is unstable. Two weeks ago we had
problems with kmem allocator and this was "fixed" by adding more
memory and Dag-Erling Smørgrav still investigating those panics. Now
we got different looking panic and there is core available if someone
wants to take a peek on it.
Dag-Erling Smørgrav writes:
>
> It would be really useful to know where the fault lies. We might even
> (God forbid!) figure out a way to fix it. You can easily force the
> system to boot with less than the full amount of memory by setting
> hw.physmem to e.g. "64m" in /boot/loader.conf or
Dag-Erling Smørgrav writes:
>
> The backtrace you showed seems to indicate that the panic happened
> somewhere in the softupdates code, but IIRC that code has a fairly
> conservative built-in limit on memory consumption and degrades
> gracefully when it hits that limit. It's likely that some
Dag-Erling Smørgrav writes:
> Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> writes:
> > First maxusers was 0 then when changed it to 8.
>
> That's a regression. Keep it at 0.
>
I understood that there is a bug on new kmem allocator and this was an
attempt to r
Doug White writes:
> On Tue, 9 Sep 2003, Tomi Vainio - Sun Finland wrote:
>
> > Tomi Vainio - Sun Finland writes:
> > > Our system died when using iozone -a to ~300G vinum partition made
> > > from four disks. Sources were cvsupped 7.9.2003.
> > >
Tomi Vainio - Sun Finland writes:
> Our system died when using iozone -a to ~300G vinum partition made
> from four disks. Sources were cvsupped 7.9.2003.
>
Second panic an hour later. Any good ideas how to fix this?
Tomppa
panic: kmem_malloc(4096): kmem_map too small: 28229
Our system died when using iozone -a to ~300G vinum partition made
from four disks. Sources were cvsupped 7.9.2003.
Tomppa
kmem_malloc(8192): kmem_map too small: 28229632 total allocated
db> trace
Debugger(c03cc728,c0429ce0,c03db0bd,ca6c4800,100) at Debugger+0x54
panic(c03db0bd,1000,1aec000,
Martin Blapp writes:
>
> Hi,
>
> > Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just
> > fine.
>
> with the freebsd dhclient, or a unmodified V3.0.1rc9 one ?
>
> > For some reason Cisco dhcp server doesn't like FreeBSD anymore
> > if connect comes from an0 driver :-
Martin Blapp writes:
>
> Hi,
>
> > DHCPREQUEST on em0 to 255.255.255.255 port 67
> > DHCPACK from 212.226.167.254
> > bound to 212.226.167.247 -- renewal in 228123 seconds.
>
> So the first time it works ? You get an IP here ...
>
> > an0: Found Link on interface
> > DHCPDISCOVER on
Martin Blapp writes:
>
> Why don't you get an IP here ? Does the server see your requests ?
> If not, the an0 driver is broken for your card.
>
> IMHO it's not dhclient fault here.
>
> Martin
Did you look Cisco's dump where Windows DHCPDISCOVER appears as
0100.4096.3856.e7 but FreeBSD is
Martin Blapp writes:
>
> How old is your CURRENT installation ? Can you run dhclient in verbose
> mode and in foreground (-d -v) and maybe compile if with -DDEBUG ?
>
I've supped current on last Saturday.
Here are debug logs and how Cisco sees the situation. Windows XP
debug from Cisco is qu
Doug Ambrisko writes:
>
> I assume you are using a pccard version.
>
> It only a problem newer firmware. It works ... just noisy!
>
> You can try this patch to -current that should make it quiet.
> There is a bug with -current and setting the TX speed that I need
> to work on. Looks li
Peter Radcliffe writes:
> Tomi Vainio - Sun Finland <[EMAIL PROTECTED]> probably said:
> > Peter Radcliffe writes:
> > > Cisco have changed the operation of the card with newer firmware and
> > > havn't released docs on working with the newer firm
Peter Radcliffe writes:
>
> Have you got recent firmware on the cisco card ? The newer windows
> driver will "helpfully" upgrade it for you silently. If it has
> upgraded, downgrade it. The freebsd driver doesn't yet work with the
> new firmware.
>
> Cisco have changed the operation of the
I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now
it's broken. I just upgraded to new Toshiba Tecra M1 and reinstalled
FreeBSD there and now I get "an0: record length mismatch -- expected
430, got 440 for Rid ff68" errors. I already tried with old laptop
with latest kernel an
Something has changed during last week because my Fxtv stopped working
in DGA mode. I'm back running old kernel so any clues what might
cause this?
Tomppa
FreeBSD 5.1-CURRENT #3: Sun Aug 10 00:57:18 EEST 2003
FreeBSD 5.1-CURRENT #4: Sat Aug 16 21:17:19 EEST 2003
***clip clip***
Copyright (c)
Giorgos Keramidas writes:
>
> I have FreeBSD installed on two primary slices of my machine, as you
> can see from the df(1) output below. I can boot FreeBSD fine, if I
> copy the boot record of the slice my root partition lives in:
>
> # df /
> Filesystem 1K-blocksUsedA
I've used Windows NT boot menu for years to boot FreeBSD from the
second disk on my machines. I've used bootpart DOS program to do this
but now I can't find correct way to do FreeBSD boot block for it.
Earlier there was a diskid definition in some Makefile to change. How
should I do this now?
Is anyone using IBM microdrive with latest current? Should it work?
My laptop is Toshiba CT3440 running current cvsupped last weekend.
My Cisco Aironet and Linksys network cards are working just fine with
this new card concept.
pccard0: Allocation failed for cfe 0
ata2 at port 0x100-0x10f irq 11
Glenn Gombert writes:
> I get the following error when trying to rebuild the last couple of
> days...
>
> ../sys/kern/syscalls.master
> syscall.master : line 55: syscall number out of sync at 7 ...
>
> line is: struct rusage * rsuage ) ; } wait4 wait_args int
>
I've seen this and if I
I'm still using old 16bit Linksys card and it's not working with
newcard. Otherwise newcard is just fine with my Toshiba 3440 when
using Cisco Aironet 340. Newcard don't detect Linksys as it should.
Is anyone using this card?
--- newcard ---
Jun 30 14:58:38 phb kernel: ed0: at port
0x100-0x11f
Hi,
I have had this same problem couple months already. Last time I asked
about this I didn't get any answers. I'am running latest current
cvsupped during the weekend and XFree86-4.2.0 is also compiled couple
hours ago. xdm and startx are otherwise just fine but I can't write
anything. Everyt
I'm running current cvsupped two days ago. This time my X broke
down. It don't accept anything from keyboard. Situation is same when
using xdm or startx. I think last working world build was done two
weeks ago. XFree86-4.2.0 was built 30.3.2002 and I already tried to
built X-server from scrat
Steve Kargl writes:
> On Wed, Apr 24, 2002 at 02:19:29AM +0300, Tomi Vainio - Sun Finland - wrote:
> > I haven't been able to build new world since Apr14 or so. I have
> > cvsupped sources multiple times and buildworld always fails on neqn.
> > If I remove this ne
I haven't been able to build new world since Apr14 or so. I have
cvsupped sources multiple times and buildworld always fails on neqn.
If I remove this next it fails on grog and so on. Any good ideas
what's wrong?
Tomppa
c++ -O -pipe
-I/f/local/sup/5.0/gnu/usr.bin/groff/src/prproc/eqn/../..
Manfred Antar writes:
> Here it is:
> CPU: Overdrive Pentium II/Pentium II Xeon/Celeron (331.11-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0x1632 Stepping = 2
>
>Features=0x183fbff
> Programming 24 pins in IOAPIC #0
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> cpu
Manfred Antar writes:
>
> I'm using one of these boards for about 3 years with SMP.
> I'm running current with a kernel from sources current as of 1/2 hour ago
> no problem.
> The cpu's I'm using are the PentiumPro Overdrive processors that
> intel put out. I've been using these the last 6
Hi,
We've tried to get my brothers dual cpu intel pr440fx up with current
cvsupped two days ago. This machine has worked just fine couple years
with stable but we had some problems with latest X so we also updated
system to current. We've been booting this system whole day just
trying different
Hi,
This card should be a prism2 clone and it works with Linux prism2
driver. I have tried to get this work with current but no luck yet.
Jul 4 21:48:35 phb pccardd[174]: Card "Nokia"("C110/C111 Wireless LAN
Card") [(null)] [(null)] matched "Nokia" ("C110/C111 Wireless LAN Card") [(null)]
[(n
Mark Santcroos writes:
>
> I have contacted the author and he made a last change in the interrupt
> setup.
>
> I have made a small stand alone package for -CURRENT, it holds the .c, the
> linux object file, a Makefile and a script to create the necessary device
> files. (If you want it in
Kenneth D. Merry writes:
>
> Hmm. Well, I definitely haven't seen this before. The only thing I can
> figure is that we got into some sort of infinite rescan loop. I don't know
> how spinning up the disk (or trying to) would trigger a rescan.
>
My system has been up and running 21 hours
Benjamin Close writes:
> Is anyone looking into converting the Linux winmodem driver (
> Lucent Technologies binary object file compiled together with the linux
> kernel serial driver) into a freebsd device?
>
Please check http://www.geocities.com/wtnbkysh/ . It should work
under 4.2R.
Kenneth D. Merry writes:
>
> This should be fixed as of rev 1.22 of scsi_all.c. There was an errant
> search and replace that caused the 'start' bit in the start/stop unit to
> always be set to 0 (stop). So automatic spinups wouldn't work, and
> 'camcontrol start' wouldn't work.
>
Thanks,
Kenneth D. Merry writes:
>
> Can you do the following:
>
> camcontrol stop da1
> camcontrol tur da1 -v
> [ then you can start it back up with camcontrol start ]
>
> What I want to see here is the sense information coming back from the drive
> when it is spun down.
>
> The new error
Hi,
My source disk is quite noisy so normally I stop it after building the
world and restart it once a week. Couple weeks this restart hasn't
worked as before. Only way to start disk again is reboot.
camcontrol stop 1:2:0
Unit stopped successfully
mount /f
mount: /dev/da1s1e: Input/output er
Cameron Grant writes:
>
> i'm not happy with some of the things the driver does, so until i can modify
> it i won't commit it. this necessitates having hardware to test with, which
> i should be getting in the near future.
>
Nice to know that someone is even thinking about what to do with
Mixer stuff was modified couple days ago. Does anyone have working
ich driver? I got original driver from
http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this
site is dead. Does author (Katsurajima Naoto) of this driver read
FreeBSD mailing lists? Could someone include this d
Tomi Vainio - Sun Finland - writes:
>
> We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it
> with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with
> three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk).
> All 9G disks are qu
Mike Smith writes:
> > First motherboard we tried was Intel PPro 200Mhz (FX440 based I
> > think/Natoma?). Second one is newer 633MHz Celeron system but I don't
> > know manufacturer.
>
> But the same symptoms? Have you tried replacing the controller (or even
> just the onboard RAM)?
Mike Smith writes:
> > This is not so bad but 5-30 minutes after this command system will
> > always panic.
> > cd /uu ; dump 0buf 126 - /w | restore xbf 126 -
> >
> > mode = 0100644, inum = 720391, fs = /uu
> > panic: ffs_valloc: dup alloc
>
> This looks like memory or PCI data corrupti
Mark Newton writes:
>
> > sense = 3 asc = 11 asq = 0
> > This is not so bad but 5-30 minutes after this command system will
> > always panic.
>
> Are you surprised? The system is complaining that it's having intermittent
> difficulty accessing the disk, so it shouldn't be at all surpr
Hi,
We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it
with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with
three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk).
All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System
is working quite
SB128 sound support has been broken over a week now. I don't who has
made changes on 26th Oct but after these changes I can't get any sound
out of my machine. Sources cvsupped 25th Oct still worked fine.
Tomppa
--
SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland
Tomi V
I cvsupped latest sources two days ago and it broke my sounds. I
cannot watch TV with sound anymore. Pervious kernel was built on
20.5.2000. I'm using voxware driver because it supports my old PAS16
card. How to fix this?
Tomppa
--
SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 E
I'm still using old voxware driver on 5.0 current system because it is
only way to get support for my Pro Audio Spectrum card. But there is
one problem on playback. It's 5% too fast and it sounds annoying.
If I play these same mp3 files through pcm/sbc driver everything is
ok. It's also easy t
54 matches
Mail list logo