CVSup'd today [Wed Nov 5 17:15:14 CST 2003] and buildworld fails.
$ make buildworld
.
===> lib/libpcap
yacc -d -p pcapyy -o grammar.c /usr/src/lib/libpcap/../../contrib/libpcap/grammar.y
ln -sf grammar.h tokdefs.h
lex -t -Ppcapyy /usr/src/lib/libpcap/../../contrib/libpcap/scanner.l > scann
TB --- 2003-11-05 05:58:20 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-05 05:58:20 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-11-05 05:58:20 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
TB --- 2003-11-05 05:30:02 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-05 05:30:02 - starting CURRENT tinderbox run for amd64/amd64
TB --- 2003-11-05 05:30:02 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64
TB --- /usr/bin/cvs -f -R -q -d/home/
TB --- 2003-11-05 05:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-05 05:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-11-05 05:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/
> can you make a patch for cdparanoia as well?
> cdparanoia is also broken on recent -CURRENT and testing will be easy.
There is already a PR. I will rewise my patch to use __FreeBSD__ in the
patch file instead of using ${EXTRA_PATCHES}.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/57226
Thi
On 2003-11-04 19:51 -0800, Jeffrey Katcher wrote:
> I have a new system (IBM ThinkPad T40 (gorgeous, too :)). In order to use
> the WiFi card (ath) I need to install -current. What's the accepted best way?
> 1) Install 5.1-RELEASE and cvsup from there.
> 2) Install 5-1-CURRENT snapshot and cvsup
Hello!
On Mon, Nov 03, 2003 at 11:14:03PM -0600, Scot W. Hetzel wrote:
> Below is a patch to fix WINE for the new ATA driver.
>
> I created this patch based on the ideals from a previous user
> who had patched 3 other ports to work with -CURRENT's new ATA
> driver.
>
> Could someone familar wit
I have a new system (IBM ThinkPad T40 (gorgeous, too :)). In order to use
the WiFi card (ath) I need to install -current. What's the accepted best way?
1) Install 5.1-RELEASE and cvsup from there.
2) Install 5-1-CURRENT snapshot and cvsup to "real" current.
3) Something else I haven't thought of.
On Wed, 5 Nov 2003, Eirik Oeverby wrote:
> Eirik Oeverby wrote:
> > Just for those interested:
> > I do *not* get any messages at all from the kernel (or elsewhere) when
> > my mouse goes haywire. And it's an absolute truth (just tested back and
> > forth 8 times) that it *only* happens with SCHE
On Wed, 5 Nov 2003, Eirik Oeverby wrote:
> Alex Wilkinson wrote:
> > On Wed, Nov 05, 2003 at 12:27:04AM +0100, Eirik Oeverby wrote:
> >
> > Just for those interested:
> > I do *not* get any messages at all from the kernel (or elsewhere) when
> > my mouse goes haywire. And it's an a
Sorry, all I have are these lines from messages.
I returned and saw that the machine had rebooted.
Nothing more:
Nov 5 02:46:42 cale syslogd: kernel boot file is /boot/kernel/kernel
Nov 5 02:46:42 cale kernel: instruction pointer= 0x8:0xc054c85d
Nov 5 02:46:42 cale kernel: stack pointer
Alex Wilkinson wrote:
On Wed, Nov 05, 2003 at 12:27:04AM +0100, Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back and
forth 8 times) that it *only* happe
On Wed, Nov 05, 2003 at 12:27:04AM +0100, Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back and
forth 8 times)
Eirik Oeverby wrote:
Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back
and forth 8 times) that it *only* happens with SCHED_ULE and *only*
with old versions (
Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back and
forth 8 times) that it *only* happens with SCHED_ULE and *only* with old
versions (~1.50) and the very la
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back and
forth 8 times) that it *only* happens with SCHED_ULE and *only* with old
versions (~1.50) and the very latest ones (1.75 as I'
Sheldon Hearn wrote:
On (2003/11/04 09:29), Eirik Oeverby wrote:
The problem is two parts: The mouse tends to 'lock up' for brief moments
when the system is under load, in particular during heavy UI operations
or when doing compile jobs and such.
The second part of the problem is related, and is
I've had this problem on my laptop since I bought it last year and started
running -current. It's annoying, but luckily doesn't happen very often.
My gut feeling here is that the psm driver isn't servicing its interrupts
fast enough and characters are being dropped out of the FIFO. Maybe it's
ti
TB --- 2003-11-04 22:43:43 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-04 22:43:43 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-11-04 22:43:43 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
On Tue, Nov 04, 2003 at 11:13:26PM +0100, Morten Johansen wrote:
> Me too. Have had this problem since I got a "Intellimouse" PS/2
> wheel-mouse. (It worked fine with previous mice (no wheel)).
> With any scheduler in 5-CURRENT and even more frequent in 4-S
On Tuesday 04 November 2003 23:11, Lukas Ertl wrote:
> On Tue, 4 Nov 2003, Harald Schmalzbauer wrote:
> > ad0: 39083MB [79408/16/63] at ata0-master UDMA100
> > acd0: CDROM at ata1-master PIO4
> >
> > So dma is NOT enabled although the sysctl is 1
>
> For ATAPI devices you need hw.ata.atapi_dma=1.
On Tue, 4 Nov 2003, Sheldon Hearn wrote:
On (2003/11/04 09:29), Eirik Oeverby wrote:
> The problem is two parts: The mouse tends to 'lock up' for brief moments
> when the system is under load, in particular during heavy UI operations
> or when doing compile jobs and such.
> The second part of the
On Tue, 4 Nov 2003, Harald Schmalzbauer wrote:
> ad0: 39083MB [79408/16/63] at ata0-master UDMA100
> acd0: CDROM at ata1-master PIO4
>
> So dma is NOT enabled although the sysctl is 1
For ATAPI devices you need hw.ata.atapi_dma=1.
regards,
le
--
Lukas Ertl eMail:
Salve,
with today's -current (~21:30 UTC) I get hw.ata.atapi_dma listed again. But
it's said to be 1 so dma should be enabled I think.
dmesg says:
Timecounters tick every 1.000 msec
GEOM: create disk ad0 dp=0xc2d97570
ad0: 39083MB [79408/16/63] at ata0-master UDMA100
acd0: CDROM at ata1-master
On Tue, Nov 04, 2003 at 12:56:07PM -0500, John Baldwin wrote:
Yes. As long as you have 'device apic' in your kernel config,
APICs will be used to route interrupts even on UP machines if
the machine includes an MP Table or ACPI is being used and it
c
Hi,
Looking over the code for nmount(), I think I noticed a few bugs.
(tried send-pr, but the lack of a web-front-end at freebsd.org,
and a decent mail system locally means that's not a runner)
nmount() calls vfs_nmount() pretty much directly after copying in
the io vector from userland.
vfs_nmount
On Tue, Nov 04, 2003 at 02:20:19PM -0500, John Baldwin wrote:
>
> On 04-Nov-2003 Tillman Hodgson wrote:
> > It occurs to me that this is likely related to the new interrupt code.
> > that tends to imply that the fix is "wait a few days and re-cvsup", but
> > I thought folks here would be intereste
On Tue, 4 Nov 2003, Sheldon Hearn wrote:
> On (2003/11/04 09:29), Eirik Oeverby wrote:
>
> > The problem is two parts: The mouse tends to 'lock up' for brief moments
> > when the system is under load, in particular during heavy UI operations
> > or when doing compile jobs and such.
> > The second
> I've gone ahead and made it a debug message again in -current. It's
Worked. I now get
kernel: info: [drm] Initialized rdeon 1.9.0 20020828 on minor 0
kernel: drm0: [MPSAFE]
Thanks!
Mike Squires
SM P6DGH/AiW 7200
___
[EMAIL PROTECTED] mailing list
Subject: RE: xl0 watchdog timeout,
On Tue, 04 Nov 2003 12:23:19 -0500 (EST), John Baldwin wrote:
> Try disabling ACPI. ACPI is unable to route any of your PCI interrupts,
I tried disabling ACPI. It works fine. Thanks John.
> so all your PCI interrupts are hosed. You can try to talk with the fol
Ok,
to get back a working and floppydrive detection on FreeBSD/alpha:
What's about the attached patch?
I moved in fd_probe()
if (fd->type == FDT_NONE && (fd->fdu == 0 || fd->fdu == 1)) {
out of the
#if defined(__i386__) || defined(__amd64__)
block and created an #else section (like it wa
I got this nonsensical error from sed while trying to update python:
/usr/bin/sed -i.bak -e 's,/usr/doc/python-docs-,/usr/local/share/doc/python,g'
/usr/ports/lang/python/work/Python-2.3.2/Lib/pydoc.py
sed: /usr/ports/lang/python/work/Python-2.3.2/Lib/pydoc.py: No such file or directory
But the
On 04-Nov-2003 Bruce Evans wrote:
>> > - on a BP6, UP kernels without apic work except for cyintr(), but SMP
>> > kernels have problems with missing interrupts for ata devices and hang
>> > at boot time.
>>
>> Is this related to the ata-lowlevel commit you mentioned above?
>
> No. It looks l
On 04-Nov-2003 Tillman Hodgson wrote:
> It occurs to me that this is likely related to the new interrupt code.
> that tends to imply that the fix is "wait a few days and re-cvsup", but
> I thought folks here would be interested in seeing Sparc64 feedback.
The new interrupt code did not affect spa
On Tue, 4 Nov 2003, Nils Andreas Hakansson wrote:
> I've disabled softupdates because of
> a panic("softdep_move_dependencies: need merge code");
Can't comment on this bit. Might want to send e-mail to Kirk directly.
> Could someone take a look at this?
>
> pst: timeout mfa=0x0032d5d0 cmd=0x0
> > The following is without the local changes:
> > - cyintr(int unit) panics becauase it is passed a pointer to somewhere.
> > I think all compat_isa devices are broken for unit 0 because unit 0
> > is represented by a null pointer.
>
> Ah, ok. Yes, this is a semantic change. To try and supp
On 04-Nov-2003 Lukas Ertl wrote:
> On Tue, 4 Nov 2003, John Baldwin wrote:
>
>> Well, a kernel without SMP and just 'device apic' should work fine, and
>> a kernel with both SMP and 'device apic' should also work fine.
>
> But 'device apic' is necessary nowadays? Maybe that should be noted
> so
On 04-Nov-2003 Bruce Evans wrote:
> On Tue, 4 Nov 2003, John Baldwin wrote:
>
>> On 04-Nov-2003 Lukas Ertl wrote:
>> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
>> >
>> >> I somehow can't get at a good vmcore :-(. But I found out that the
>> >> machine boots fine in "Safe Mode", where DMA and hw.ata
On Tuesday 04 November 2003 19:38, John Baldwin wrote:
> On 04-Nov-2003 Harald Schmalzbauer wrote:
> > On Tuesday 04 November 2003 18:19, John Baldwin wrote:
> >> On 04-Nov-2003 Lukas Ertl wrote:
> >> > On Tue, 4 Nov 2003, John Baldwin wrote:
> >> >> On 04-Nov-2003 Lukas Ertl wrote:
> >> >> > On Tu
On 04-Nov-2003 Harald Schmalzbauer wrote:
> On Tuesday 04 November 2003 18:19, John Baldwin wrote:
>> On 04-Nov-2003 Lukas Ertl wrote:
>> > On Tue, 4 Nov 2003, John Baldwin wrote:
>> >> On 04-Nov-2003 Lukas Ertl wrote:
>> >> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
>> >> >> I somehow can't get at a
On Tue, Nov 04, 2003 at 02:17:35PM +0100, Antoine Jacoutot wrote:
> What is really strange is that "tun" is compiled in the kernel, but the
> module is started anyway ???
>
> $ kldstat
> Id Refs AddressSize Name
> 16 0xc040 35aef8 kernel
> 21 0xc075b000 4cd10acpi.ko
>
On 04-Nov-2003 Harti Brandt wrote:
> On Tue, 4 Nov 2003, Harti Brandt wrote:
>
> HB>On Tue, 4 Nov 2003, John Baldwin wrote:
> HB>
> HB>JB>
> HB>JB>On 04-Nov-2003 Harti Brandt wrote:
> HB>JB>>
> HB>JB>> Hi,
> HB>JB>>
> HB>JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
On 04-Nov-2003 Brian F. Feldman wrote:
> Steve Ames <[EMAIL PROTECTED]> wrote:
>>
>> For the past few weeks my -CURRENT system has been locking up. With a
>> recent kernel (from 11/2) the following appears:
>>
>> Fault trap 12: page fault while in kernel mode
>> fault virtual address = 0x24
>>
On 04-Nov-2003 Harald Schmalzbauer wrote:
> Hi all,
>
> with today's -current (with the new irq stuff) I get the following messages
> wich I haven't had before:
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> unknown: can't assign resources (port)
> unknown: can't assign resources
On Tue, 4 Nov 2003, John Baldwin wrote:
> Well, a kernel without SMP and just 'device apic' should work fine, and
> a kernel with both SMP and 'device apic' should also work fine.
But 'device apic' is necessary nowadays? Maybe that should be noted
somewhere.
regards,
le
--
Lukas Ertl
Hi all,
I've got the following trying to debug
FreeBSD current ( Mon Oct 27 16:34:36 CET 2003) on a serial terminal.
Hardware:
Supermicro x5da8
dual xeon 2.66Ghz
2GB ecc ddr ram
Tekram 390u2we (system on a 36GB disc)
promise sx6000 ( home on 6 WD1200JB (raid 5))
Intel(R) PRO/1000 (on motherboard
On Tue, 4 Nov 2003, John Baldwin wrote:
> On 04-Nov-2003 Lukas Ertl wrote:
> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
> >
> >> I somehow can't get at a good vmcore :-(. But I found out that the
> >> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned off.
> >
> > Ok, if I set hw.a
On Tuesday 04 November 2003 18:19, John Baldwin wrote:
> On 04-Nov-2003 Lukas Ertl wrote:
> > On Tue, 4 Nov 2003, John Baldwin wrote:
> >> On 04-Nov-2003 Lukas Ertl wrote:
> >> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
> >> >> I somehow can't get at a good vmcore :-(. But I found out that the
> >> >
It occurs to me that this is likely related to the new interrupt code.
that tends to imply that the fix is "wait a few days and re-cvsup", but
I thought folks here would be interested in seeing Sparc64 feedback.
-T
--
[It] contains "vegetable stabilizer" which sounds ominous. How unstable
are v
for a list of commands, 'help' for more detailed help.
OK boot -v
SMAP type=01 base= len=0009e400
SMAP type=02 base=0009e400 len=1c00
SMAP type=02 base=000dc000 len=00024000
SMAP type=01 base=0010 len=f7d
Hi.
> > I also have an ASUS motherboard with an Intel 875P
> > chipset.
>
> Can you post a dmesg? Note that if you want
> hyperthreading,
> you need to enable it in your BIOS. The ACPI (and
> soon the
> MPTable) drivers will not use HT CPUs unless HT is
> enabled in
> the BIOS. My test machine
On 04-Nov-2003 Harti Brandt wrote:
> On Tue, 4 Nov 2003, Harti Brandt wrote:
>
> HB>On Tue, 4 Nov 2003, John Baldwin wrote:
> HB>
> HB>JB>
> HB>JB>On 04-Nov-2003 Harti Brandt wrote:
> HB>JB>>
> HB>JB>> Hi,
> HB>JB>>
> HB>JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
On 04-Nov-2003 Shin-ichi Yoshimoto wrote:
> Subject: RE: xl0 watchdog timeout,
> On Tue, 04 Nov 2003 10:39:44 -0500 (EST), John Baldwin wrote:
>> Can you please provide a full dmesg?
>
> yes.
Try disabling ACPI. ACPI is unable to route any of your PCI interrupts,
so all your PCI interrupts are
On 04-Nov-2003 Lukas Ertl wrote:
> On Tue, 4 Nov 2003, John Baldwin wrote:
>
>>
>> On 04-Nov-2003 Lukas Ertl wrote:
>> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
>> >
>> >> I somehow can't get at a good vmcore :-(. But I found out that the
>> >> machine boots fine in "Safe Mode", where DMA and hw.a
On Tue, 4 Nov 2003, Harti Brandt wrote:
HB>On Tue, 4 Nov 2003, John Baldwin wrote:
HB>
HB>JB>
HB>JB>On 04-Nov-2003 Harti Brandt wrote:
HB>JB>>
HB>JB>> Hi,
HB>JB>>
HB>JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
HB>JB>> worked until yesterday, but with the new interru
Steve Ames <[EMAIL PROTECTED]> wrote:
>
> For the past few weeks my -CURRENT system has been locking up. With a
> recent kernel (from 11/2) the following appears:
>
> Fault trap 12: page fault while in kernel mode
> fault virtual address = 0x24
> fault code = supervisor read, page not present
>
On Tuesday 04 November 2003 17:10, Harald Schmalzbauer wrote:
> Hi all,
>
> with today's -current (with the new irq stuff) I get the following messages
> wich I haven't had before:
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> unknown: can't assign resources (port)
> unknown: can't
On Tue, 4 Nov 2003, Harti Brandt wrote:
HB>On Tue, 4 Nov 2003, John Baldwin wrote:
HB>
HB>JB>
HB>JB>On 04-Nov-2003 Harti Brandt wrote:
HB>JB>>
HB>JB>> Hi,
HB>JB>>
HB>JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
HB>JB>> worked until yesterday, but with the new interru
Hi all,
with today's -current (with the new irq stuff) I get the following messages
wich I haven't had before:
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: can't assign resources (port)
unknown: can't assign resources (port)
unknown: can't assign resources (port)
unknown:
Subject: RE: xl0 watchdog timeout,
On Tue, 04 Nov 2003 10:39:44 -0500 (EST), John Baldwin wrote:
> Can you please provide a full dmesg?
yes.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University
On Tue, 4 Nov 2003, John Baldwin wrote:
JB>
JB>On 04-Nov-2003 Harti Brandt wrote:
JB>>
JB>> Hi,
JB>>
JB>> I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
JB>> worked until yesterday, but with the new interrupt code it doesn't boot
JB>> anymore. It works for the standard HZ,
On Tue, 4 Nov 2003, John Baldwin wrote:
>
> On 04-Nov-2003 Lukas Ertl wrote:
> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
> >
> >> I somehow can't get at a good vmcore :-(. But I found out that the
> >> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned off.
> >
> > Ok, if I set hw
On (2003/11/03 13:38), Brooks Davis wrote:
> I've sent mail to both his FreeBSD address and the one on the IPFilter
> homepage. If anyone knows a reliable way to communicate with him, that
> would be useful.
The latter address works, but he's terrible with email, by his own
admission. If you do
For the past few weeks my -CURRENT system has been locking up. With a
recent kernel (from 11/2) the following appears:
Fault trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc049d0db
stack pointer
On 04-Nov-2003 Shin-ichi Yoshimoto wrote:
> After cvsup and make world, I could't use xl0 and kernel said "kernel:
> xl0: watchdog timeout".
>
># dmesg
> [snip]
> xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xe400-0xe47f
> mem 0xea
> 02-0xea02007f irq 10 at device 18.0 on pci0
On 04-Nov-2003 Lukas Ertl wrote:
> On Tue, 4 Nov 2003, Lukas Ertl wrote:
>
>> I somehow can't get at a good vmcore :-(. But I found out that the
>> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned off.
>
> Ok, if I set hw.ata.ata_dma=0 in loader.conf, it boots fine. Could t
On 04-Nov-2003 Harti Brandt wrote:
>
> Hi,
>
> I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
> worked until yesterday, but with the new interrupt code it doesn't boot
> anymore. It works for the standard HZ, but if I set HZ=1000 I get a double
> fault. I suspect a race c
On (2003/11/04 09:29), Eirik Oeverby wrote:
> The problem is two parts: The mouse tends to 'lock up' for brief moments
> when the system is under load, in particular during heavy UI operations
> or when doing compile jobs and such.
> The second part of the problem is related, and is manifested by
On 04-Nov-2003 Claus Guttesen wrote:
> Hi.
>
>> I have an ASUS system with 2 CPUs that I need to run
>> at HZ=1. This
>> worked until yesterday, but with the new interrupt
>> code it doesn't boot
>> anymore. It works for the standard HZ, but if I set
>> HZ=1000 I get a double
>
> Compiled a
Matteo Riondato wrote:
Well, it did not change anything :(
What is really strange is that "tun" is compiled in the kernel, but the
module is started anyway ???
I had the same problem last year and solved it by removing
device tun
from the kernel configuration file.
Yes, I though about it. But s
Il Mar, 2003-11-04 alle 14:17, Antoine Jacoutot ha scritto:
> Max Laier wrote:
> > AJ>
> > AJ> module_register: module if_tun already exists!
> > AJ> Module if_tun failed to register: 17
> > AJ> can't re-use a leaf (if_tun_debug)!
> > AJ> --
Hi.
> I have an ASUS system with 2 CPUs that I need to run
> at HZ=1. This
> worked until yesterday, but with the new interrupt
> code it doesn't boot
> anymore. It works for the standard HZ, but if I set
> HZ=1000 I get a double
Compiled a new kernel with source from Nov. 3'rd where
SMP and
Max Laier wrote:
> AJ>
> AJ> module_register: module if_tun already exists!
> AJ> Module if_tun failed to register: 17
> AJ> can't re-use a leaf (if_tun_debug)!
> AJ>
>
AJ> Is there a kernel option I m
Hi,
I have an ASUS system with 2 CPUs that I need to run at HZ=1. This
worked until yesterday, but with the new interrupt code it doesn't boot
anymore. It works for the standard HZ, but if I set HZ=1000 I get a double
fault. I suspect a race condition in the interrupt handling. My config
file
Hello Antoine,
Tuesday, November 4, 2003, 10:55:22 AM, you wrote:
AJ> I just migrated a 4.8 server to -CURRENT and I have one question.
AJ> At boot time I get the following message:
AJ>
AJ> module_register: module if_tun already exists!
AJ> Module
On Tue, 4 Nov 2003, Shin-ichi Yoshimoto wrote:
> After cvsup and make world, I could't use xl0 and kernel said "kernel:
> xl0: watchdog timeout".
>
> # dmesg
> [snip]
> xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xe400-0xe47f
> mem 0xea
> 02-0xea02007f irq 10 at device 18.0 on pc
On Tue, 4 Nov 2003, Lukas Ertl wrote:
> I somehow can't get at a good vmcore :-(. But I found out that the
> machine boots fine in "Safe Mode", where DMA and hw.ata.wc is turned off.
Ok, if I set hw.ata.ata_dma=0 in loader.conf, it boots fine. Could there
be some issue with ATAng + new interrup
On Tue, 4 Nov 2003, Lukas Ertl wrote:
> I've yet to find out if I can get a good vmcore + backtrace, but I'm
> having a machine that panics when going from singleuser to multiuser on
> boot with a new kernel from today.
>
> The panicking process is 'idle', the trap number is 30, and it says
> "unk
After cvsup and make world, I could't use xl0 and kernel said "kernel:
xl0: watchdog timeout".
# dmesg
[snip]
xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xe400-0xe47f
mem 0xea
02-0xea02007f irq 10 at device 18.0 on pci0
xl0: Ethernet address: 00:04:75:3c:6b:ad
miibus0: on xl0
Hi,
I've yet to find out if I can get a good vmcore + backtrace, but I'm
having a machine that panics when going from singleuser to multiuser on
boot with a new kernel from today.
The panicking process is 'idle', the trap number is 30, and it says
"unknown/reserved trap". More info is coming as
TB --- 2003-11-04 09:10:17 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-04 09:10:17 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-11-04 09:10:17 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
Hi :)
I just migrated a 4.8 server to -CURRENT and I have one question.
At boot time I get the following message:
module_register: module if_tun already exists!
Module if_tun failed to register: 17
can't re-use a leaf (if_tun_debug)!
--
TB --- 2003-11-04 07:40:27 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-04 07:40:27 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-11-04 07:40:27 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
On Mon, 3 Nov 2003, John Baldwin wrote:
> On 01-Nov-2003 Soren Schmidt wrote:
> > It seems Sean Chittenden wrote:
> >> Howdy. I'm not sure if this is a ULE bug or a KSE bug, or both, but,
> >> for those interested (this is using ule 1.67, rebuilding world now),
> >> here's my stack. I couldn't f
It seems Anshuman Kanwar wrote:
Ehem, this machine is NOT ServerWorks based, its Intel...
> rack2-102.nyc# pciconf -l
> [EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x254c8086 rev=0x01
> hdr=0x00
> [EMAIL PROTECTED]:2:0: class=0x060400 card=0x chip=0x25438086 rev=0x01
> hdr=
Jeff Roberson wrote:
On Mon, 3 Nov 2003, Eirik Oeverby wrote:
Hi,
Just recompiled yesterday, running sched_ule.c 1.75. It seems to have
re-introduced the bogus mouse events I talked about earlier, after a
period of having no problems with it. The change happened between 1.69
and 1.75, and there'
John Baldwin wrote:
I'm committing the new i386 interrupt and SMP code, so buckle your
seat belts. :) I'll be intentionally breaking the kernel build at
the start and re-enable it with the last commit when I am done.
Is this *only* for SMP systems, or will the interrupt code also affect
UNIprocess
On Mon, Nov 03, 2003 at 06:37:26PM +0100, Andreas Klemm wrote:
> Cc'd to Stijn <[EMAIL PROTECTED]>.
> Many thanks Stijn, for making that patch available!
No problem, but I'd like it if you also thank Mark Santcroos for making
that patch in the first place -- I'm just the messenger here...
> So no
On Mon, Nov 03, 2003 at 01:38:56PM -0800, Sam Leffler wrote:
> The problem appears to be caused by someone reclaming routing table entries
> while they are in use. This would likely be a reference counting problem.
>
> You didn't provide any information about system kernel config or hardware
>
89 matches
Mail list logo
