Accessing fd0 (1440) floppies have been impossible with CURRENT
on both test machines here since 4.0 was released. The following
are as of cvsup yesterday:
(83) [11:30pm]
ttyp8:--ROOT--@mrynet (83): dd if=/dev/rfd0.1440 bs=512 >x
dd: /dev/rfd0.1440: Input/output error
0+0 record
It seems Giorgos Keramidas wrote:
> I built from sources cvsup'ed about 24 hours ago, my kernel and world,
> this afternoon. After enabling INVARIANTS and INVARIANT_SUPPORT, I
> booted and tried a lot of things. Nothing seemed to make the new kernel
> I had (and it's own modules + world) go craz
[cc:'d shin]
-On [2324 00:04], Dan Moschuk ([EMAIL PROTECTED]) wrote:
>
>Is anyone else seeing odd behaviour with a fairly recent -current, an ep
>driver nic card and fragmented packets?
Yes. And add to that a fxp card as well next to the ep card.
For some weird reason (almost) every packe
On Fri, 24 Mar 2000, Bruce Evans wrote:
> Yes. make.conf shouldn't even hint that globally changing CFLAGS is
> supported or good. Note that the suggested "most common use" has been
> bogus since -pipe was added to the default settings in rev.1.31
> (1998/05/01) of sys.mk.
Hmm. What is the cor
On Thu, 23 Mar 2000, Kris Kennaway wrote:
> Any objections to the following?
>
> Index: make.conf
> ===
> RCS file: /home/ncvs/src/etc/defaults/make.conf,v
> retrieving revision 1.101
> diff -u -u -r1.101 make.conf
> --- make.conf 2
On Thu, 23 Mar 2000, Matthew Dillon wrote:
> This problem should now be fixed, it's probably the problem I just fixed
> a moment ago in netinet/if_ether.c based on a thread in -hackers. The
> m_pullup() NULL check in arpintr() was broken, resulting in a NULL
> pointer dereference
Hi folks,
%On Thu, 23 Mar 2000, Kris Kennaway wrote:
%
%> Any objections to the following?
%
%I don't mind at all ... I was wondering about just taking out the ability
%to even USE -O2 in the compiler, but there're probably *some* non-kernel
%related reasons for using it, and we shouldn't block
Mike Smith wrote:
> > I've played around changing the spinloop to using DELAY (like the Linux model),
> > but this didn't prevent the controller from either "just" locking up or
> > crashing the whole machine with it. Changing various other places in a similar
> > manner (like replacing the bcopy
I just had to do that a few days ago, but it didn't work. Apparently
DOS is very stupid, and without dding the entire DOS partition it
wouldn't work. Who knows why. Low-levels are a bad idea. I know
someone who managed to ruin a number of disks trying that.
Laurence
Matthew Dillon wrote:
>
Try loading the loader (/boot/loader) rather than the kernel. You might
also try using the boot0 bootmanager (see the manpage for boot0cfg) with
the 'packet' option set, which will DTRT.
You may also need to rebuild boot1/boot2 with the 'packet mode' flags
set; see the boot1 sources in sys/b
Hello,
My FreeBSD partition is installed on a cyl. beyound
1024. So FreeBSD boot manager does not work.
Howerver with 3.4 release I was able to use
this great boot loader called GRUB. In there
I could mount a root file system and then load
the kernel. Something has changed in the 4.0 Release
an
> : This problem should now be fixed, it's probably the problem I just fixed
> : a moment ago in netinet/if_ether.c based on a thread in -hackers. The
> : m_pullup() NULL check in arpintr() was broken, resulting in a NULL
> : pointer dereference.
>
> inoue-san's patch survived
On Thu, 23 Mar 2000, Chuck Robey wrote:
> On Thu, 23 Mar 2000, Kris Kennaway wrote:
>
> > Any objections to the following?
>
> I don't mind at all ... I was wondering about just taking out the ability
> to even USE -O2 in the compiler, but there're probably *some* non-kernel
> related reasons f
I built from sources cvsup'ed about 24 hours ago, my kernel and world,
this afternoon. After enabling INVARIANTS and INVARIANT_SUPPORT, I
booted and tried a lot of things. Nothing seemed to make the new kernel
I had (and it's own modules + world) go crazy ;)
However, when I tried to run cdcontr
Forrest Aldrich wrote:
>
> Is not sysinstall built and installed with a typical make
> buildworld/installworld?
No.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
One Unix to rule them all, One Resolver to find them,
One
On Thursday, 23 March 2000 at 17:44:38 -0600, Dan Nelson wrote:
> In the last episode (Mar 23), Greg Lehey said:
>>
>> Agreed. This is on the Vinum wishlist, but it comes at the expense of
>> reliability (how long do you wait to cluster? What happens if the
>> system fails in between?). In addi
On Thu, Mar 23, 2000 at 01:33:11AM +0200, Giorgos Keramidas wrote:
>
> In the mean time, I've recompiled a freshly cvsup'ed kernel, booted it,
> and now I'm trying to build my world -- since it seems that compiling
> the kernel and/or `world' triggers the funny condition I'm running into.
I rebu
On 23-Mar-00 Mike Smith wrote:
> Just rebuild sysinstall, like I told you to start with. Or just bring
> the disks up by hand, which is much faster. Or even try Warner's
> 'diskprep' tool.
If anyone want diskprep, its at...
http://people.freebsd.org/~imp/diskprep
---
Daniel O'Connor sof
In the last episode (Mar 23), Greg Lehey said:
>
> Agreed. This is on the Vinum wishlist, but it comes at the expense of
> reliability (how long do you wait to cluster? What happens if the
> system fails in between?). In addition, for Vinum it needs to be done
> before entering the hardware dr
On Tuesday, 21 March 2000 at 9:29:56 -0800, Matthew Dillon wrote:
>>>
>>> I would think that track-caches and intelligent drives would gain
>>> much if not more of what clustering was designed to do gain.
>>
>> Hm. But I'd think that even with modern drives a smaller number of bigger
>> I/Os is p
On Thu, 23 Mar 2000, Kris Kennaway wrote:
> Any objections to the following?
I don't mind at all ... I was wondering about just taking out the ability
to even USE -O2 in the compiler, but there're probably *some* non-kernel
related reasons for using it, and we shouldn't block it at that
point.
Any objections to the following?
Index: make.conf
===
RCS file: /home/ncvs/src/etc/defaults/make.conf,v
retrieving revision 1.101
diff -u -u -r1.101 make.conf
--- make.conf 2000/03/22 00:49:20 1.101
+++ make.conf 2000/03/23 2
On Monday, 20 March 2000 at 22:52:59 +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Alfred Perlstein writes:
>> * Poul-Henning Kamp <[EMAIL PROTECTED]> [000320 11:45] wrote:
>>> In message <[EMAIL PROTECTED]>, Alfred Perlstein writes:
>>>
Keeping the currect cluster code is
On Monday, 20 March 2000 at 15:23:31 -0600, Dan Nelson wrote:
> In the last episode (Mar 20), Poul-Henning Kamp said:
>> In message <[EMAIL PROTECTED]>, Alfred Perlstein writes:
>>> * Poul-Henning Kamp <[EMAIL PROTECTED]> [000320 11:45] wrote:
Before we redesign the clustering, I would l
> >>Eventually all physical I/O needs a physical address. The quickest
> >>way to get to a physical address is to be given an array of vm_page_t's
> >>(which can be trivially translated to physical addresses).
> >
> > Not all: PIO access to ATA needs virtual access. RAID5 needs
> > v
On Monday, 20 March 2000 at 14:04:48 -0800, Matthew Dillon wrote:
>
> If a particular subsystem needs b_data, then that subsystem is obviously
> willing to take the virtual mapping / unmapping hit. If you look at
> Greg's current code this is, in fact, what is occuring the critica
On Monday, 20 March 2000 at 20:17:13 +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>
>>Well, let me tell you what the fuzzy goal is first and then maybe we
>>can work backwards.
>>
>>Eventually all physical I/O needs a physical address. The q
Yes, same here, and it looks like it's after the last ATAPI commit (worked
perfectly before that, Delta 44x ATAPI CD-ROM):
~> gdb -k /sys/compile/KUSHNIR/kernel.debug /var/crash/vmcore.1
[...]
IdlePTD 2797568
initial pcb at 232ce0
panicstr: page fault
[...]
---
#0 boot (howto=256) at ../../kern
In message <[EMAIL PROTECTED]> Matthew Jacob
writes:
: I'm an idiot - I should have paid closer attention to some other commits.
And the UPDATING file too :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Can you try instead the changes that I just committed to -current? I
> think that the problem shows up when the controller is heavily loaded;
> your patch will keep the load on the controller down, which may mask the
> 'real' bug.
I tried your approach (that was what I described with "fiddl
On Mar 23, Matthew Dillon wrote:
> Oh, addendum... I didn't see this email regarding an actual panic.
>
> There are two problems here, one of which (the nbufkv lockup) should
> be solved by my previous email.
>
> The second problem is this panic you are reporting, and I have no i
In message <[EMAIL PROTECTED]> Yoshinobu Inoue writes:
: I would like to narrow down the problem more and could you
: please try if this patch stop the problem or not?
: (The m_pullup() is recently added to if_rl.c. It should not be
: harmful, but I suspect that this might have invoked another
: h
In message <[EMAIL PROTECTED]> Brian Beattie
writes:
: > Winner! Much better than my personal favorite of bigbooty.flp. :-)
: >
: > - Jordan
: >
:
: Then that would make the CD LordWarfen.iso?
I had the chance to register john.net way back when. I was going to
name the machines warfen.john.
> I've found the easiest way to wedge the box is to perform a 'cvs up'
> (not cvsup) from a local repository over /usr/src or /usr/ports, this
> would always lockup my box with amr, if you have the time and disk
> space that would be a much better stressor than just make world.
I have done a cvs
> I've played around changing the spinloop to using DELAY (like the Linux model),
> but this didn't prevent the controller from either "just" locking up or
> crashing the whole machine with it. Changing various other places in a similar
> manner (like replacing the bcopy() in amr_quartz_get_work(
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000323 12:47] wrote:
> I've played around changing the spinloop to using DELAY (like the Linux model),
> but this didn't prevent the controller from either "just" locking up or
> crashing the whole machine with it. Changing various other places in a simila
usually ppp from laptop (3.4+pao) to home (4.0-stable) works fine. and then
sometimes it will get stuck in the following mode three N in a row.
ppp[547]: tun0: Chat: Send: AT^M
ppp[547]: tun0: Chat: Expect(5): OK
ppp[547]: tun0: Chat: Received: AT^M^M
ppp[547]: tun0: Chat: Received: OK^M
ppp
Oh, addendum... I didn't see this email regarding an actual panic.
There are two problems here, one of which (the nbufkv lockup) should
be solved by my previous email.
The second problem is this panic you are reporting, and I have no idea
what is causing it so this issue rema
Ok, this is NOT a softupdates *or* a vinum problem.
This is a buffer cache problem.
The problem is due to the large block size you are using when newfs'ing
the filesystem coupled with problems in geteblk() which causes severe
buffer cache KVM fragmentation. Softupdates exasp
Is anyone else seeing odd behaviour with a fairly recent -current, an ep
driver nic card and fragmented packets?
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messa
On Mar 15, Mathew Kanner wrote:
> On Mar 15, Greg Lehey wrote:
> > attention yet, but I do see that your problem relates to soft
> > updates. It's not clear that the soft updates themselves are a cause
> > of the problem, or just a facilitator, but it would be interesting to
> I did try it
I've played around changing the spinloop to using DELAY (like the Linux model),
but this didn't prevent the controller from either "just" locking up or
crashing the whole machine with it. Changing various other places in a similar
manner (like replacing the bcopy() in amr_quartz_get_work() with s
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: This problem should now be fixed, it's probably the problem I just fixed
: a moment ago in netinet/if_ether.c based on a thread in -hackers. The
: m_pullup() NULL check in arpintr() was broken, resulting in a NULL
: pointer d
This problem should now be fixed, it's probably the problem I just fixed
a moment ago in netinet/if_ether.c based on a thread in -hackers. The
m_pullup() NULL check in arpintr() was broken, resulting in a NULL
pointer dereference.
Ollivier Robert wrote:
>
> .( Here ) cr
>
> Will try, hope I'll be able to see them :)
>
> Is there a way to do a "sleep 5" ?
5000 ms
Or, to wait for a keypress:
key
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
One Unix to
At 9:45 AM -0800 2000/3/23, Matthew Dillon wrote:
> Make sure you also specify the INVARIANT_SUPPORT options (note: this
> one is not plural).
DOH!!!
foot
Rebooting now. We'll see if it works. Sigh ;-)
Thanks guys!
--
These are my opinion
> Is not sysinstall built and installed with a typical make
> buildworld/installworld?
As I told you in my original reply, _NO_.
> Anyways, I rebuilt it and it works now. Sysinstall was the culprit.
"I told you so".
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tel
Is not sysinstall built and installed with a typical make
buildworld/installworld?
Anyways, I rebuilt it and it works now. Sysinstall was the culprit.
_F
At 10:08 AM 3/23/00 -0800, Mike Smith wrote:
> > I tend to think there is something wrong with sysinstall... obviously, the
> > OS works
:I normally wouldn't recommend it. But the same situation with a different (not to be
:mentioned) OS happened to me.
:After hours of being frustrated, I decided the scsi controller went south. A
:cow-orker told me to LL the drive,
:and voila, magic. These were IBM LVD 10kRPM drives, brand spank
> I tend to think there is something wrong with sysinstall... obviously, the
> OS works as the internal drives (also LVD 10KRPM drives) work. Sysinstall
> just tells me there aren't any disks in the system.
>
> So, hope whomever maintains sysinstall is monitoring this conversation.
Sysinsta
I say again, DO NOT low-level format the drive. The _only_ situation
where it's worth taking this risk is when you're seeing errors from the
drive itself specifically referring to formatting issues; eg. 'address
mark not found'. There are no other circumstances which justify this
action, an
On Thu, 23 Mar 2000, Brad Knowles wrote:
>Folks,
>
> It looks to me like setting INVARIANTS in your kernel doesn't
>work in 4.0-STABLE.
>
[...]
>reference to `zerror'
>vm_zone.o: In function `zfreei':
>
> The kernel config is a bit large, so I will transmit it on
>request to inter
I tend to think there is something wrong with sysinstall... obviously, the
OS works as the internal drives (also LVD 10KRPM drives) work. Sysinstall
just tells me there aren't any disks in the system.
So, hope whomever maintains sysinstall is monitoring this conversation.
I will attempt ano
I normally wouldn't recommend it. But the same situation with a different (not to be
mentioned) OS happened to me.
After hours of being frustrated, I decided the scsi controller went south. A cow-orker
told me to LL the drive,
and voila, magic. These were IBM LVD 10kRPM drives, brand spankin new
:
:> Why not? The drives are empty LVD Drives, nothing bad'll happen.
:
:Apart from screwing up the factory format.
:
:> I mean, it may very well be sysinstall being massively out of sync, but it
:shouldn't hurt to LL the drives.
:
:It should, and will.
:
:--
:\\ Give a man a fish, and you feed
I just did a full buildworld/installworld and complete recompile
of RELENG_4 last night with INVARIANTS turned on, and I use makeoptions
DEBUG=-g. It worked fine.
Make sure you also specify the INVARIANT_SUPPORT options (note: this
one is not plural).
Hi,
>From yesterday and today cvsup + make world + kernel build : each time
i try to mount a cd (this is not related to a particular cd as the
same pb arises when the drive is empty...), my system reboot :
/kernel: Fatal trap 12: page fault while in kernel mode
/kernel: fault virtual address
Folks,
It looks to me like setting INVARIANTS in your kernel doesn't
work in 4.0-STABLE.
This one drove me batty for most of the day, until I remembered
that I had also enabled this stuff as well as a couple other changes
I had wanted to make to my kernel config.
In
Nick Hibma writes:
| The pointer to the source I can't give, because it has escaped me
| whether I sorted out the licensing issue with Doug Ambrisko. I'd rather
| would like to sort that out first.
This shouldn't be an issue since it is the same license as the netgraph
license from Whistle. I ha
Kris Kennaway wrote:
>
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > > Because the dlopen() of librsaintl.so fails.
> >
> > Ok, I give up :-) Why would that happen then ?
>
> I don't know :-)
I stuck a dlerror() in there and the problem is
usr/lib/librsaINTL.so: Undefined symbol "BN_mod_e
> options COMPAT_OLDISA
> options COMPAT_OLDPCI
I'm an idiot - I should have paid closer attention to some other commits.
Thanks!
>
> to my some-days-old kernel config file to make things compile and work
> again.
>
> The time seems to have come to new-busify pcvt
On Thu, Mar 23, 2000 at 11:46:57AM -0500, Sean O'Connell wrote:
> J McKitrick stated:
> > I'm not sure if this belongs on -stable or -current. Has anyone taken
> > a look at the timeout problem in the parallel port zip driver?
>
> Have you tried backing vpo.c down to 1.19 (1.20 was committed
> o
I'm not sure if this belongs on -stable or -current. Has anyone taken
a look at the timeout problem in the parallel port zip driver?
jm
--
Jonathon McKitrick -- [EMAIL PROTECTED]
Pure... unrefined... spice
---
> Why not? The drives are empty LVD Drives, nothing bad'll happen.
Apart from screwing up the factory format.
> I mean, it may very well be sysinstall being massively out of sync, but it shouldn't
>hurt to LL the drives.
It should, and will.
--
\\ Give a man a fish, and you feed him for a da
>From the keyboard of Matthew Jacob:
> Is someone planning on fixing this?
>
> ../../i386/isa/pcvt/pcvt_hdr.h:943: warning: `struct isa_device' declared inside
>parameter list
> ../../i386/isa/pcvt/pcvt_hdr.h:943: warning: its scope is only this definition or
>declaration, which is probably not
> For a long time I have noticed that when I build kdm from the kdebase
> port, it works.
> But if I used packages off either the CDs or ftp sites, it doesn't work.
> Specifically if I
> do a 'strings' on the binary and grep for /, some of the paths I see
> have XBINDIR
> rather than explicit refe
> MM... the countdown message is 10 seconds long. It crashes before
> going through the countdown???
Yes.
> Damn, I wish I could see the log of this boot.
I can't record it and it goes way too fast to tell.
> IIRC, you only have "include /boot/loader.4th" and "start" in your
> loader.rc, r
On 22/03, Jim Bloom wrote:
| I had hangs while linking the kernel as
| well as while trying to install a fixed one. Make sure you have a good backup
| of the kernel, I ended up with a zero byte kernel while trying to install the
| fixed one.
Well, running without swap is likely to suppress thos
> > His code is very generic, so I've got good hopes that the code will work
> > for many different devices (read: Entrega 25 pin, 9 pin, Keyspan
> > adapter and more).
>
> Any pointer to this driver ? I have a USB to 8 port serial from Digi
> and would love to try if the driver works with it.
A
Ollivier Robert wrote:
>
> According to Daniel C. Sobral:
> > Or just pressing space when the countdown message first appears...
>
> No time for that.
MM... the countdown message is 10 seconds long. It crashes before
going through the countdown???
Damn, I wish I could see the log of this b
On Thu, Mar 23, 2000 at 11:00:17AM +, Nick Hibma wrote:
>
> Yes. Doug Ambrisko (Whistle Communications) has written the beginnings
> of a driver (but it works!). I've meant to check out the work he has
> done and see for which devices this works. I will do that sometime this
> week (weekend p
Hi,
I know it isn't much (no debugger compiled in (yet)), but is
anybody else seeing panics like this:
mode = 0100644, inum = 214354, fs = /data0
panic: ffs_valloc: dup alloc
syncing disks... 23 13 4 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
giving up on 2 buffers
Uptime: 3m24s
Automatic
Have you overclocked your system? If you are using an Athlon box, do you
have an extra fan on the bridge chip?
MP3's are heavy on the processor and will get you this behaviour if
the system is prone to glitches.
My system had similar problem (Fine until you run a make world) and
Windows _never
Yes. Doug Ambrisko (Whistle Communications) has written the beginnings
of a driver (but it works!). I've meant to check out the work he has
done and see for which devices this works. I will do that sometime this
week (weekend probably, maybe tomorrow evening)
His code is very generic, so I've go
Ollivier Robert wrote:
>
> According to Mike Smith:
> > Try putting just "set autoboot_delay=0" in /boot/loader.rc and see if
> > that gives you a prompt.
>
> In loader.conf you mean ? loader.rc is supposed to contain Forth...
Forth + "user friendly" loader commands, which the above is supposed
This commit -- changing much of the configuration of GCC on a FreeBSD
host, has the potential to wreck havoc. One typo in these files can
render your compiler dead. I have tested these changes on both i386 and
DEC Alpha. However your environment may tickle an area of the
configuration mine didn
At 4:14 PM -0800 2000/3/22, Matthew Dillon wrote:
> Frankly, I have INVARIANTS (and INVARIANT_SUPPORT) turned on by default
> on all of my kernels.
If it's this useful and this lightweight, may I suggest that we
change the descriptive text around it in the LINT kernel, and cop
At 1:17 AM +0100 2000/3/23, FREENIX IS OVERRATED wrote:
> Without really tuning anything, after a bit of time, the time needed
> to do history lookups drops to microseconds, and as long as a `sync'
> isn't needed, innd doesn't get stuck. Theoretically, a sync, where
> you are in fact seeking
Why not? The drives are empty LVD Drives, nothing bad'll happen.
I mean, it may very well be sysinstall being massively out of sync, but it shouldn't
hurt to LL the drives.
-eric
Mike Smith wrote:
> > Try low-levelling the drives. The behavior sounds similar to what I had a long
>time ago, l
> According to Mike Smith:
> > Try putting just "set autoboot_delay=0" in /boot/loader.rc and see if
> > that gives you a prompt.
>
> In loader.conf you mean ? loader.rc is supposed to contain Forth...
I wrote the damn thing. I meant loader.rc. You're welcome to make the
appropriate changes
According to Mike Smith:
> Try putting just "set autoboot_delay=0" in /boot/loader.rc and see if
> that gives you a prompt.
In loader.conf you mean ? loader.rc is supposed to contain Forth...
--
Ollivier ROBERT -=- Eurocontrol EEC/TEC -=- [EMAIL PROTECTED]
The Postman hits! The Postman hits! Yo
> Try low-levelling the drives. The behavior sounds similar to what I had a long time
>ago, low level formatting them fixed the problem.
Not a good idea. Sounds more like sysinstall is massively out of sync
with the rest of the system; it's not updated with the rest of the world.
>
> -eric
>
>From the keyboard of Matthew Jacob:
> Is someone planning on fixing this?
Yes!
hellmuth
--
Hellmuth MichaelisTel +49 40 55 97 47-70
HCS Hanseatischer Computerservice GmbHFax +49 40 55 97 47-77
Oldesloer Strasse 97-99
83 matches
Mail list logo
