Sat, Nov 22, 2003 at 13:08:10, netch (Valentin Nechayev) wrote about geom-ata
forever cycle:
VN 5.1-current of 2003-11-20 hangs during kernel initialization with forever
VN cycle around geom partitioning detection and ATA read failure.
VN Message rate is too fast to record, no stopping
5.1-current of 2003-11-20 hangs during kernel initialization with forever
cycle around geom partitioning detection and ATA read failure.
Message rate is too fast to record, no stopping is available, no serial
console.
Previous 5-current on this machine was of 2003-05-23.
How to diagnose?
dmesg of
Sat, Nov 22, 2003 at 05:45:09, nickh wrote about Re: geom-ata forever cycle:
Personally I dont think this is GEOM related. I had a drive start doing
Yes, it is ATAng related, AFAIS, but triggers GEOM forever cycle.
this to me (happens often as I work in a large datacenter) and the drive is
Sat, Nov 01, 2003 at 20:38:36, s.wingate (Steve Wingate) wrote about Re: Dualbooting
STABLE CURRENT:
I don't like the sound of that. I'll just stick with STABLE until 5.x is
really ready.
-STABLE will have the same problem since its in boot0 and the BIOS, not
the OS on the partition its
Wed, Oct 22, 2003 at 03:14:33, strick (Dan Strick) wrote about UFS file system
problem in either stable or current:
DS There seems to be an inconsistency between release 4.9-RC and 5.1 ufs
DS support. If I fsck the same ufs (type 1 of course) file system on
DS both releases, each claims that
Wed, Oct 29, 2003 at 17:32:29, dwhite (Doug White) wrote about Re: problems with
sysinstall:
Well, I understand it for slices. But why I can't create new partition
in exist slice and newfs it? It was OK in -stable.
DW yes, this is a change to -current. It is for your own safety.
Don't
Wed, Oct 29, 2003 at 05:44:44, sem (Sergey Matveychuk) wrote about problems with
sysinstall:
SM The first one: when I install -current on disk where WinXP on first
SM slice, sysinstall brakes WinXP boot complete. I got 'Missing operation
SM system' everytime. Even I've tried 'fixboot' and
Sun, Oct 26, 2003 at 18:58:52, q (Ulrich Spoerlein) wrote about Sysinstall's
fdisk/disklabel should be improved:
US First of all, the Partition Editor has the 'A' option to use all of the
US available HDD space. It creates a DOS-compatible slice (starting at
US sector 63 and ending on cylinder
Wed, Oct 29, 2003 at 16:43:12, q (Ulrich Spoerlein) wrote about Re: Sysinstall's
fdisk/disklabel should be improved:
It is NOT useless. Why do you think it is? Perhaps you don't relize
that some BIOS's wont boot from a hard disk that isn't partitioned to
agree with the specifications of
Fri, Jun 06, 2003 at 03:01:02, DougB wrote about Re: Way forward with BIND 8:
FYI, for those wondering why I'm not considering BIND 9 for import, please
see http://people.freebsd.org/~dougb/whybind8.html
Among other things: standard resolver is waaay(tm) old. Even keeping with BIND8,
it
Fri, May 30, 2003 at 18:53:16, segr (Stephane Raimbault) wrote about FreeBSD
5.1-BETA2 boot up messages:
SR I just noticed that when I boot up in FreeBSD 5.1-BETA2 I get a whole bunch of
SR messages fly by the screen (see below for errors from /var/log/messages).
SR Does anyone know what is
Fri, May 30, 2003 at 17:38:04, larse (Lars Eggert) wrote about Re: Libthr stable
enough for testing:
LE I tried, but the following is a surefire way to freeze my SMP box solid
LE at the moment (with today's libthr):
SCHED_ULE or SCHED_4BSD?
-netch-
Fri, Dec 06, 2002 at 23:07:36, netch (Valentin Nechayev) wrote about no psm
interrupt; lock order reversal:
VN 5.0-RC of 2002.12.05.12.00.00-UTC
VN Bigger problem that it can't obtain interrupts from PS/2 mouse,
VN hence mouse fails to work. systat shows no int 12 issued at all.
ACPI
Wed, Jan 01, 2003 at 21:39:33, tlambert2 (Terry Lambert) wrote about Re: 5.0-RC2
informal PR: 90 sec sendmail delay:
TL It's an editorial complaint. I don't like the breaking the
TL program into seperate programs by function. IMO, DJB is wrong,
TL and this does nothing to enhance security.
Fri, Dec 06, 2002 at 13:11:51, osa (Sergey A. Osokin) wrote about Re: cvsup weird
problem:
SAO Any other idea? :-)
Remove src/contrib/gcc/INSTALL/ and sup checkouts directory simultaneously,
this usually fixes such errors ;)
Delete src/contrib/gcc/INSTALL
Cannot delete
5.0-RC of 2002.12.05.12.00.00-UTC
Lock order reversal without panic:
lock order reversal
1st 0xc2e30708 vnode interlock (vnode interlock) @
/var/HEAD/src/sys/kern/vfs_subr.c:939
2nd 0xc033c3c0 vm page queue mutex (vm page queue mutex) @
/var/HEAD/src/sys/vm/vm_kern.c:424
Bigger problem that
Sat, Jun 30, 2001 at 00:16:53, cristjc (Crist J. Clark) wrote about fd0c mount(8)
Race:
mount: /dev/fd0c: No such file or directory
That is, even though once I drop into single-user mode we see the
symlink for /dev/fd0c, it does not seem like it was there when 'mount
-a -t nonfs' is
Thu, Jun 21, 2001 at 15:02:37, TJ (T.J. Kniveton) wrote about From -current to
-stable?:
I followed the directions on the freebsd web site to grab the latest
-stable sources, but it looks like somehow I got the -current sources,
built and installed them (doh!).
Everything is working ok,
I.
A session under screen, or sshd, or any another:
netch@iv:~tty
/dev/ttyp2
netch@iv:~ls -l /dev/tty /dev/ttyp2
crw--w 1 netch tty5, 2 Jun 24 13:09 /dev/tty
crw--w 1 netch tty5, 2 Jun 24 13:09 /dev/ttyp2
root@iv:~##ls -l /dev/ttyp*
crw--w 1 netch tty5, 2
Sun, Jun 24, 2001 at 19:21:20, rb (Bob Bishop) wrote about su broken?:
su appears to be asking for a password when invoked by root, eg:
# su bin -c pwd
Password:
root@iv:~##su bin -c pwd
This account is currently not available.
root@iv:~##su -m bin -c pwd
/root
Broken, surely?
Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about
Problems with md5 -p:
I reproduce it stably on my -current. The second checksum is constant
and it is MD5 checksum of an empty stream:
root@iv:/usr/HEAD/src/sbin/md5##md5 /dev/null
d41d8cd98f00b204e9800998ecf8427e
ChangesPath
1.20.2.2 +46 -52src/sbin/md5/md5.c
Before them the case when MDFilter(0) should be called, checked separately
(argc==1). After them it is not checked, fix argument processing
is somehow wrong. IMO these commits should be reverted.
Valentin Nechayev wrote:
Sun, Jun 24
Sat, Jun 16, 2001 at 23:21:33, Tor.Egge ([EMAIL PROTECTED]) wrote about Re: ps 'D'
state - ?:
Are `select' and `nanosleep' disk uninterruptable waits? ;|
No. The ps command gave wrong output.
flag = k-ki_p-ki_flag;
- sflag = k-ki_p-ki_flag;
+ sflag = k-ki_p-ki_sflag;
-current, cvsup: date=2001.06.03.00.00.00
Normally worked, but after Ctrl-Alt-Del:
IdlePTD 4038656
initial pcb at 32f940
panicstr: from debugger
panic messages:
---
panic: free: multiple frees
panic: from debugger
Uptime: 25m49s
(kgdb) bt
#0 0xc0199a36 in dumpsys ()
#1 0xc0199823 in boot ()
Sat, May 26, 2001 at 22:03:34, barry (Barry Lustig) wrote about Re: Boot time memory
issue:
SMAP type=01 base= 0010 len= 13ef
[...]
Did that and got the same error. I put a printf just before the
pa_indx++ in machdep.c and watched it increment by 2's all the way
Wed, May 23, 2001 at 21:26:37, jkoshy (Joseph Koshy) wrote about Date for a working
-current?:
I'm in the processing of bring a 5-current system of Oct 2000 vintage
more upto-date.
The kernel built around May 23rd 2001, has been quite unstable, with
numerous warning on lock order
Wed, May 23, 2001 at 15:43:50, nk (Norbert Koch) wrote about downgrade:
Is it possible to downgrade a machine from -current to -stable?
A ~month ago I downgraded my home system from -current to -stable (RELENG_4)
via buildworld+installworld. But to do it successfully I had to
replace
Sun, May 20, 2001 at 19:53:29, barry (Barry Lustig) wrote about Boot time memory
issue:
Do verbose boot (`boot -v') with large SC_HISTORY_SIZE (1000 at least,
2000 at most), and after boot check for SMAP ... lines at the very
beginning of the kernel boot log at /dev/console. (They are not
Mon, Mar 19, 2001 at 16:02:08, mark (Mark Murray) wrote about "Re: random woes ("no
RSA support in libssl and libcrypto")":
ssh: no RSA support in libssl and libcrypto. See ssl(8)
[...]
It seems the compatibility with the previous minor of urandom has
been silently removed (I assume
/var -alldirs -maproot=root: -network 192.168.5 -mask 255.255.255.0
showmount -e showed 192.168.5 was being interpreted as 192.168.0.5
This is the correct interpretation.
Changing -network to 192.168.5.0 fixed it, naturally, but the 192.168.5
used to work.
It was broken, then. :-)
Sun, Mar 18, 2001 at 16:41:03, des (Dag-Erling Smorgrav) wrote about "Interesting
backtrace...":
I finally caught a backtrace from one of those recurring stack smash
panics. I've been getting a few of these every day for a couple of
weeks now but never caught a dump; I caught this one by
A simple but intensive fork bomb were started on 5.0-current UP machine.
After it, /var/log/messages contains:
Mar 3 19:16:46 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:46 iv last message repeated 42 times
Mar 3 19:16:46
The problem that when random device was not seeded, boot simply hangs (on
ldconfig! why?) Ugly init(8) gives no chance to stop booting and fall to
reboot or single mode again via ctrl-alt-del or another key combination;
sleeping on "rndblk" channel in ldconfig is not interruptible; only DDB or
Sun, Oct 15, 2000 at 20:52:59, netch wrote about "(1) hanging up on ldconfig; (2)
entropy file read failed":
This is also entropy file and random device problem.
ldconfig which hangs: pid=107, flag=004006, stat=3, wchan=c0336f80,
wmesg=rndblk - waits for random data (?)
This handing appeared
Following is partial dmesg output from 5.0(13)-CURRENT-20001002 kernel
with advanced debugging prints:
==={{{
mi_startup(): call subsystem 0x880(142606336), microuptime is 1.4027506
mi_startup(): call subsystem 0x880(142606336), microuptime is 1.4027897
mi_startup(): call subsystem
At Fri, 6 Oct 2000 22:00:23 + (UTC), jhb wrote:
JB The problem was that the interrupt threads for the clk interrupt introduced
JB enough latency that occasionally (mostly during a heavy load of interrupts)
JB tc_windup() wasn't called soon enough to update the timecounter. Making
On my
System in question is:
root@nn:~##uname -mrs
FreeBSD 5.0-CURRENT i386
root@nn:~##grep FreeBSD_version /usr/include/sys/param.h
#undef __FreeBSD_version
#define __FreeBSD_version 500012/* Master, propagated to newvers */
root@nn:~##
cvsup was Sep 8, approximately at 18:00 GMT.
`top -I'
Hello John Baldwin!
microuptime() went backwards (1.7682417 - 1.997434)
I recall reading in -current earlier this week that someone was
looking for victims getting this. What further information can I provide?
JB This is a SMPng issue on UP machines.
I have obtained the same on non-SMP
Hello Eivind Eklund!
Sun, Nov 07, 1999 at 14:25:22, eivind wrote about "Re: cvs commit: src/libexec/uucpd
uucpd.c"
in cvs-commiters@, cvs-all@:
Just for the record, this is considered a really bad thing, because
one common error is typing the password when the username is being
ANK for j in 1 2 3 4 5 6 7 8 9 10; do
ANK echo -n $i $j
~~ ;(
ANK nohup sh -c 'while :; do find /usr -type f | xargs fgrep zukabuka;
ANK done' \
/dev/null 21
ANK echo
ANK done
-- --
Valentin Nechayev
ne...@lucky.net
II:LDXIII/MCMLXXII.CCC
To Unsubscribe
40 matches
Mail list logo
