Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-current Digest, Vol 71, Issue 15

6 views

Skip to first unread message

freebsd-cur...@freebsd.org

unread,

Aug 5, 2004, 6:04:42 PM8/5/04

Send freebsd-current mailing list submissions to
freebsd...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-current
or, via email, send a message with subject or body 'help' to
freebsd-cur...@freebsd.org

You can reach the person managing the list at
freebsd-cu...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-current digest..."

Today's Topics:

1. Re: xmms crashes CURRENT (Gleb Smirnoff)
2. Re: So much entropy it's coming out of our ears? (Sam Leffler)
3. Re: So much entropy it's coming out of our ears? (Chuck Swiger)
4. Re: fxp lost on current (Don L. Belcher)
5. SiI3112a possible workaround? (Jason Andresen)
6. Re: [current tinderbox] failure on powerpc/powerpc
(Dag-Erling Sm?rgrav)
7. Re: Instant Reboots (was: Re: Postgresql locks up server - no
response at all) (Eric Anholt)
8. RE: ATA driver races with interrupts (Daniel Eriksson)
9. Re: Instant Reboots (was: Re: Postgresql locks up server - no
response at all) (Geoff Speicher)
10. Re: HEADS UP! boot2 problems (Jeremy Chadwick)
11. Re: 5.2.1-R panic still occurs on a recent -CURRENT (Markie)
12. Re: /dev/vga (pa...@freebsd.org)
13. Re: [PLEASE TEST] Better support for Synaptics Touchpads
(David Wolfskill)
14. can see my reboot command idle 22 minutes :( (Bjoern A. Zeeb)
15. Re: Unable to build recent kernels (Doug White)
16. Re: can see my reboot command idle 22 minutes :( (Jeremy Chadwick)
17. Installing cdevsw_add(), cdevsw_remove() man pages in
-current? (Craig Rodrigues)
18. Re: SiI3112a possible workaround? (Doug White)
19. no text in gnome after portuprade (Tony Montana)
20. Re: [PLEASE TEST] Better support for Synaptics Touchpads
(Philip Paeps)
21. Fatal trap 12 in kern_ptrace (Dan Nelson)
22. Re: can see my reboot command idle 22 minutes :( (Bjoern A. Zeeb)
23. IPSEC broken (FAST_IPSEC works)? (Alexander Leidinger)
24. Re: gvinum resetconfig (Lukas Ertl)
25. Re: SiI3112a possible workaround? (S?ren Schmidt)
26. Re: Vinum status (Craig Boston)
27. Re: gvinum resetconfig (Mike B)
28. Re: no text in gnome after portuprade (Scott Lambert)
29. Re: Watchdog timeouts with ACPI (John Baldwin)
30. Re: Watchdog timeouts with ACPI (John Baldwin)
31. Re: kernel panic when accessing digi serial multi io.
(John Baldwin)
32. Re: Atomic operations on i386/amd64 (John Baldwin)
33. Re: no text in gnome after portuprade (Joe Marcus Clarke)

----------------------------------------------------------------------

Message: 1
Date: Thu, 5 Aug 2004 19:51:16 +0400
From: Gleb Smirnoff <gle...@freebsd.org>
Subject: Re: xmms crashes CURRENT
To: Robert Watson <rwa...@freebsd.org>
Cc: cur...@freebsd.org
Message-ID: <20040805155...@cell.sick.ru>
Content-Type: text/plain; charset=koi8-r

On Thu, Aug 05, 2004 at 10:19:51AM -0400, Robert Watson wrote:
R> What function is at 0xc055b780? You can use addr2line or gdb -k to work
R> that out, I believe.

/usr/src/sys/kern/subr_kdb.c:228

0xc055b780 is in kdb_enter (/usr/src/sys/kern/subr_kdb.c:228).
223 if (kdb_dbbe != NULL && kdb_active == 0) {
224 if (msg != NULL)
225 printf("KDB: enter: %s\n", msg);
226 breakpoint();
227 }
228 }
229
230 /*
231 * Initialize the kernel debugger interface.
232 */

R> Also, it would be interesting to "options KDB_TRACE" can get a trace in
R> this panic...

I'll try.

--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE

------------------------------

Message: 2
Date: Thu, 5 Aug 2004 08:53:14 -0700
From: Sam Leffler <s...@errno.com>
Subject: Re: So much entropy it's coming out of our ears?
To: Richard Coleman <rcol...@criticalmagic.com>
Cc: freebsd...@freebsd.org
Message-ID: <20040805085...@errno.com>
Content-Type: text/plain; charset="iso-8859-1"

On Thursday 05 August 2004 07:33 am, Richard Coleman wrote:
> Sam Leffler wrote:
> > gathering through fast paths. I've suggested for a long time that
> > this sort of collection should be enabled only under dire
> > circumstances and never by default. Regardless the last time I
> > looked at the entropy harvesting it used a model where entropy was
> > unilateraly sent for harvest and discarded when too plentiful. I
> > term this the "push model". I've advocated a "pull model" where the
> > PRNG requests entropy when a low water mark is hit and/or a hybrid
> > scheme where producers have some sort of flow control or feedback
> > mechanism.
> >
> > Everything that goes on inside the PRNG is a separate issue.
> >
> > Sam
>
> In general, by using a push model, you open yourself up to the possibility
> that the attacker could exhaust the entropy at just the right time so he
> can control what entropy is harvested on the next run of the PRNG. But in
> this case, we might be able to get away with it, since the PRNG is still
> cryptographically strong even when there is no new entropy flowing into the
> system (as long at the attacker doesn't know the initial state of the
> pool). Rekeying and reseeding the pool are primarily to give you forward
> security and to recover if the entropy pool has been compromised.
>
> But a push system is still better if it doesn't impact performance too
> much.

Push vs pull and exhaustion depends on your system config which is why I
hedged with "or a hybrid scheme". If a system has a reasonable h/w entropy
source it should be able to pull enough entropy on demand to keep everyone
happy. I know this to be true for at least 4 crypto parts that include a h/w
RNG. On systems like this you want to just shutdown all other forms of
entropy gathering unless you're paranoid about having a single source of
entropy.

Sam

------------------------------

Message: 3
Date: Thu, 05 Aug 2004 12:03:09 -0400
From: Chuck Swiger <csw...@mac.com>
Subject: Re: So much entropy it's coming out of our ears?
To: Robert Watson <rwa...@FreeBSD.ORG>
Cc: Sam Leffler <s...@errno.com>
Message-ID: <41125A3D...@mac.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

Robert Watson wrote:
> On Thu, 5 Aug 2004, Mark Murray wrote:
[ ...snip Sam's comments about push versus pull models of
harvesting entropy... ]
>> Yarrow is not conducive to "water-mark" type flow-control, but I'm
>> looking at replacing Yarrow with Fortuna (code at an advanced stage).
>> This should improve things all-round.
>
> Could we do the rate limiting on the sender side, then, by making a
> guestimate at a maximum useful entropy rate? [ ... ]
> I.e., add a "entropy_gathered" int that uses a unlocked read to test for
> non-zero, and is decremented while holding one of the harvesting mutexes
> if it's non-zero. Reset it in a callout a few times a second, and set it
> to some small value, like 4. This will result in the gathering of some
> entropy each second, but not so much that it seriously hits the packet
> delivery path in higher workloads.

For what it's worth, this sounds like a pretty good approach to me.

Given that Yarrow maintains an estimate of the amount of entropy available, it
ought to be easy to use that to decide whether "4" or some other value is
appropriate. If the entropy pool is "full", leave entropy_gathered == 0, or
perhaps set it to a small value as Robert suggests so that we're still
churning a few random bits into the pool. If entropy is being used, set
entropy_gathered equal to some bigger value which is appropriate for the how
much new entropy the pool would like to get over the next interval.

Furthermore, the code which does the entropy gathering might even choose to
pay attention to how much entropy is desired and alter their sensitivity a bit
(ie, how many of the least-significant bits from a timestamp based on the
interval between when the last two packets were received are trusted to be
"random").

[ This part is a good candidate for a sysctl, so those who are concerned about
the purity of their entropy can choose that the entropy harvesting code be
pessimistic, whereas others who just want /dev/random to output reasonably
random stuff without much overhead can choose to get just that, instead. ]

Perhaps change the name from entropy_gathered to entropy_wanted? That seems
to best describe what it's being used for...

--
-Chuck

------------------------------

Message: 4
Date: Thu, 05 Aug 2004 12:03:39 -0400
From: "Don L. Belcher" <d...@siad.net>
Subject: Re: fxp lost on current
To: freebsd...@freebsd.org
Message-ID: <41125A5B...@siad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Don L. Belcher wrote:

>
>
> Don L. Belcher wrote:
>
>>
>>
>> M. Warner Losh wrote:
>>
>>> In message: <2004062708...@carver.gumbysoft.com>
>>> Doug White <dwh...@gumbysoft.com> writes:
>>> : On Sat, 26 Jun 2004, Don L. Belcher wrote:
>>> : : > I seem to have lost my fxp card in current ( It was working
>>> about 1 or 2
>>> : > months ago ). If somebody could point out to me what code I
>>> should be
>>> : > looking at, I would appreciate it.
>>> : >
>>> : > I provided pciconf info attachments, one from release 4 the
>>> other from
>>> : > current.
>>> : : Hm, pci bus 3 seems to have vanished. Have you tried a BIOS update?
>>>
>> The BIOS is the latest.
>>
>>>
>>> Alternatively, since I'm joining the thread late, do you have a
>>> cardbus bridge?
>>>
>>>
>> This is a Gateway SOLO 9500 laptiop, the fxp is a mini pci card.
>>
> I forgot to answer the question, yes it has a cardbus bridge

OS pulled in for date=2004.04.24.00.00.00 stops working
OS pulled in for date=2004.04.23.00.00.00 stops works
I assume this means a change on April 23 aggravates this problem?
When looking for changes on this date I could not find anything.

relevant part of dmesg from non working version:
pcib3: <ACPI PCI-PCI bridge> at device 6.0 on pci2
pcib3: secondary bus 3
pcib3: subordinate bus 3
pcib3: I/O decode 0x3000-0x3fff
pcib3: memory decode 0xf0600000-0xf07fffff
pcib3: prefetched decode 0xfff00000-0xfffff
ACPI PCI link initial configuration:
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.4.0
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.8.0
ACPI PCI link before setting link priority:
ACPI PCI link before fixup for boot-disabled links:
ACPI PCI link after fixup for boot-disabled links:
ACPI PCI link arbitrated configuration:
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.4.0
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.8.0
pci3: <ACPI PCI bus> on pcib3
pci3: physical bus=3
pcm0: <ESS Technology Allegro-1> port 0x4000-0x40ff irq 5 at device 8.0
on pci2
pcm0: failed to enable memory mapping!

relevant part of dmesg from working version in April:

pcib3: <ACPI PCI-PCI bridge> at device 6.0 on pci2
pcib3: secondary bus 3
pcib3: subordinate bus 3
pcib3: I/O decode 0x3000-0x3fff
pcib3: memory decode 0xf0600000-0xf07fffff
pcib3: prefetched decode 0xfff00000-0xfffff
---- initial configuration ------------------------
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.4.0
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.8.0
---- before setting priority for links ------------
---- before fixup boot-disabled links -------------
---- after fixup boot-disabled links --------------
---- arbitrated configuration ---------------------
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.4.0
\\_SB_.PCI0.LPC0.LNKB irq 10: [ 10] low,level,sharable 3.8.0
pci3: <ACPI PCI bus> on pcib3
pci3: physical bus=3
map[10]: type 1, range 32, base f0600000, size 12, enabled
map[14]: type 4, range 32, base 00003400, size 6, enabled
map[18]: type 1, range 32, base f0700000, size 20, enabled
pcib3: matched entry for 3.4.INTA (src \\_SB_.PCI0.LPC0.LNKB)
pcib3: slot 4 INTA is routed to irq 10
found-> vendor=0x8086, dev=0x1229, revid=0x08
bus=3, slot=4, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0013, statreg=0x0290, cachelnsz=8 (dwords)
lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x38
(14000 ns)
intpin=a, irq=10
powerspec 2 supports D0 D1 D2 D3 current D0
map[10]: type 1, range 32, base f0601000, size 8, enabled
map[14]: type 4, range 32, base 00003800, size 3, enabled
map[18]: type 4, range 32, base 00003000, size 8, enabled
pcib3: matched entry for 3.8.INTA (src \\_SB_.PCI0.LPC0.LNKB)
pcib3: slot 8 INTA is routed to irq 10
found-> vendor=0x11c1, dev=0x0448, revid=0x01
bus=3, slot=8, func=0
class=07-80-00, hdrtype=0x00, mfdev=0
cmdreg=0x0003, statreg=0x0290, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0xfc (63000 ns), maxlat=0x0e (3500 ns)
intpin=a, irq=10
powerspec 2 supports D0 D2 D3 current D0
fxp0: <Intel 82559 Pro/100 Ethernet> port 0x3400-0x343f mem
0xf0700000-0xf07fffff,0xf0600000-0xf0600fff irq 10 at device 4.0 on
pci3
pcib3: device fxp0 requested decoded memory range 0xf0600000-0xf0600fff
pcib2: device fxp0 requested decoded memory range 0xf0600000-0xf0600fff
fxp0: using memory space register mapping
fxp0: PCI IDs: 8086 1229 1668 1100 0008
fxp0: Dynamic Standby mode is disabled
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: bpf attached

------------------------------

Message: 5
Date: Thu, 05 Aug 2004 12:04:18 -0400
From: Jason Andresen <jand...@mitre.org>
Subject: SiI3112a possible workaround?
To: freebsd...@freebsd.org
Message-ID: <41125A82...@mitre.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I was searching the net today and I came across this little gem in a
Linux mailing list:

http://www.uwsg.iu.edu/hypermail/linux/kernel/0307.3/1349.html

Notably:

1) As some others suggested on the list, the problem with very slow
transfer and timeouts if you try to enable DMA, can be fixed by the
following lines in an appropriate rc file:

hdparm -X66 -d1 /dev/hda
echo "max_kb_per_request:15" > /proc/ide/hdX/settings
(repeat for both drives, e.g. hde and hdg).

As I have one of these unfortunate controllers, I was wondering if it is
possible to do something like this in FreeBSD? sysctl doesn't seem to
have anything and I'm not sure what to look for in the sources. Does
FreeBSD have any sort of analog to the above hdparm command?

------------------------------

Message: 6
Date: Thu, 05 Aug 2004 18:04:28 +0200
From: d...@des.no (Dag-Erling Sm?rgrav)
Subject: Re: [current tinderbox] failure on powerpc/powerpc
To: FreeBSD Tinderbox <tind...@freebsd.org>
Cc: pow...@freebsd.org
Message-ID: <xzpoelp...@dwp.des.no>
Content-Type: text/plain; charset=iso-8859-1

FreeBSD Tinderbox <tind...@freebsd.org> writes:
> TB --- 2004-08-05 14:25:23 - patching the sources
> TB --- 2004-08-05 14:25:23 - cd /home/tinderbox/sandbox/CURRENT/powerpc/powerpc/src
> TB --- 2004-08-05 14:25:23 - /usr/bin/patch -f -s -i/home/tinderbox/sandbox/powerpc.diff
> TB --- 2004-08-05 14:25:23 - WARNING: /usr/bin/patch returned exit code 2
> TB --- 2004-08-05 14:25:23 - ERROR: failed to apply patch to source tree

Sorry, I forgot to make sure the patch was relative to src.

DES
--
Dag-Erling Smørgrav - d...@des.no

------------------------------

Message: 7
Date: Thu, 05 Aug 2004 10:07:04 -0700
From: Eric Anholt <e...@lclark.edu>
Subject: Re: Instant Reboots (was: Re: Postgresql locks up server - no
response at all)
To: Geoff Speicher <ge...@speicher.org>
Cc: cur...@freebsd.org
Message-ID: <1091725623.911.10.camel@leguin>
Content-Type: text/plain

On Thu, 2004-08-05 at 06:16, Geoff Speicher wrote:
> On Wed, Aug 04, 2004 at 03:26:13PM -0700, Eric Anholt wrote:
> > On Wed, 2004-08-04 at 15:07, Geoff Speicher wrote:
> > > On Wed, Aug 04, 2004 at 03:34:49PM -0600, Scott Long wrote:
> > > > Geoff Speicher wrote:
> > > >
> > > > >FWIW, in mid-late July, my problems were not PREEMPTION-related. I
> > > > >tried everything I could to get usable threaded apps under XFree86, but
> > > > >my Athlon XP rebooted every time I tried to run kdm, Firefox, etc.
> > > > >
> > > > >This included all four combinations of PREEMPTION and ULE/4BSD. Rolling
> > > > >back to July 1 was the only thing that worked for me.
> > > >
> > > > Yeah, the instant reboots have hit me too. Disabling PREEMPTION did
> > > > seem to help this for me, but then it might have been a coincidence.
> > > > Incidentally, what video drivers are you using?
> > >
> > > Snippets from /var/log/XFree86.0.log:
> > >
> > > (II) ATI: ATI driver (version 6.4.18) for chipsets: ati, ativga
> > > (--) RADEON(0): Chipset: "ATI Radeon VE/7000 QY (AGP)" (ChipID = 0x5159)
> > > (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
> > > (II) Module radeon: vendor="The XFree86 Project"
> > > compiled for 4.3.0, module version = 4.0.1
> > > Module class: XFree86 Video Driver
> > > ABI class: XFree86 Video Driver, version 0.6
> > >
> > > (II) RADEON(0): [drm] loaded kernel module for "radeon" driver
> > > (II) RADEON(0): Direct rendering enabled
> >
> > Does this happen without using threaded apps? More specifically, does
> > it continue if you disable DRI in your X config? If so, please send me
> > your dmesg.
>
> Hey, disabling DRI did the trick. Aside from things being remarkably
> slow, it's remarkably stable. ;) Threaded X apps or no, I'm running
> a July 19 kernel with no instant reboots. PREEMPTION disabled,
> WITNESS enabled (I misspoke in another message when I said WITNESS was
> disabled---apparently I fiddled more than I had remembered). Toggling
> DRI back on and restarting X/kdm reboots immediately.

While you didn't send your dmesg, I'm betting that you've got VIA 8377
AGP. We're misconfiguring it, it seems. I'm working on a patch, please
watch http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/69953 for a fix.

--
Eric Anholt e...@lclark.edu
http://people.freebsd.org/~anholt/ anh...@FreeBSD.org

------------------------------

Message: 8
Date: Thu, 5 Aug 2004 19:11:22 +0200
From: "Daniel Eriksson" <daniel_k...@telia.com>
Subject: RE: ATA driver races with interrupts
To: 'S?ren Schmidt'<s...@DeepCore.dk>
Cc: freebsd...@freebsd.org
Message-ID:
<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAMYTGmVxmR0Oc6P/8t/P6dgE...@telia.com>

Content-Type: text/plain; charset="iso-8859-1"

Søren Schmidt wrote:

> > I just applied your patch to clean sources dated
> 2004.08.04.13.00.00 and ran
> > some tests. Everything seems to be working as it should
> (just like after the
> > serialization patch from Ville-Pertti that I tried
> earlier). I will continue
> > running with this patch applied to see if it stays stable.
>
> Good! please keep me posted!

Unfortunately the machine disconnected one of the SATA discs earlier today.
It did so out-of-the-blue, because there was no activity at all on either of
the two discs other than the SMART monitor.

Aug 5 11:45:47 fortify kernel: ad20: WARNING - removed from configuration
Aug 5 11:45:47 fortify kernel: ata10-master: FAILURE - unknown CMD (0xb0)
timed out
Aug 5 11:45:47 fortify smartd[882]: Device: /dev/ad20, not capable of SMART
self-check

No other interesting messages in the log. The channel was, as usual,
completely locked after this and it took an extended power-off (2 min) to
unlock it (I really don't know what is up with that).

Once the channel was unlocked it booted up but page-faulted in the middle of
detecting the attached discs (another reboot took care of that problem, not
sure if the page fault info is interesting at all, but here it is):

[...]
ad16: 114473MB <WDC WD1200JB-00DUA3> [232581/16/63] at ata8-master UDMA100
ad18: 26059MB <Maxtor 92732U8> [52946/16/63] at ata9-master UDMA66
ad20: 239372MB <Maxtor 7Y250M0> [486344/16/63] at ata10-master SATA150
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0580904
stack pointer = 0x10:0xdd6e5c1c
frame pointer = 0x10:0xdd6e5c44
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 35 (swi5: clock sio)
[thread 100036]
Stopped at propagate_priority+0x84: movl 0x24(%eax),%eax
db> trace
propagate_priority(c2734420,c078a9a0,c056f8a9,c0790780,c26e47d0) at
propagate_priority+0x84
turnstile_wait(c2735bc0,c078e960,c078a9a0,0,c27440ac) at
turnstile_wait+0x31c
_mtx_lock_sleep(c078e960,c2734420,0,0,0) at _mtx_lock_sleep+0xe8
softclock(0,0,ffffffff,ffffbfff,ffffffff) at softclock+0x248
ithread_loop(c26d0080,dd6e5d48,ffffffff,ffffffff,ffffffff) at
ithread_loop+0x1a8
fork_exit(c05439c0,c26d0080,dd6e5d48) at fork_exit+0x80
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xdd6e5d7c, ebp = 0 ---

It should have looked something like this:
[...]
ad16: 114473MB <WDC WD1200JB-00DUA3> [232581/16/63] at ata8-master UDMA100
ad18: 26059MB <Maxtor 92732U8> [52946/16/63] at ata9-master UDMA66
ad20: 239372MB <Maxtor 7Y250M0> [486344/16/63] at ata10-master SATA150
ad22: 238475MB <WDC WD2500JD-00FYB0> [484521/16/63] at ata11-master SATA150
ar0: 476950MB <ATA RAID0 array> [60802/255/63] status: READY subdisks:
disk0 READY on ad4 at ata2-master
disk1 READY on ad5 at ata2-slave
ar1: 478744MB <ATA RAID0 array> [61031/255/63] status: READY subdisks:
disk0 READY on ad6 at ata3-master
disk1 READY on ad7 at ata3-slave
ar2: 388962MB <ATA RAID0 array> [49585/255/63] status: READY subdisks:
disk0 READY on ad9 at ata4-slave
disk1 READY on ad8 at ata4-master
ar3: 228946MB <ATA RAID0 array> [29186/255/63] status: READY subdisks:
disk0 READY on ad15 at ata7-slave
disk1 READY on ad16 at ata8-master
Waiting 5 seconds for SCSI devices to settle
[...]

I have switched back to the patch from Ville-Pertti that serializes the
controller for now, to see if that is more stable.

/Daniel Eriksson

------------------------------

Message: 9
Date: Thu, 5 Aug 2004 13:20:41 -0400
From: Geoff Speicher <ge...@speicher.org>
Subject: Re: Instant Reboots (was: Re: Postgresql locks up server - no
response at all)
To: Eric Anholt <e...@lclark.edu>
Cc: cur...@freebsd.org
Message-ID: <20040805172...@sirius.speicher.org>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 05, 2004 at 10:07:04AM -0700, Eric Anholt wrote:
> On Thu, 2004-08-05 at 06:16, Geoff Speicher wrote:
> > On Wed, Aug 04, 2004 at 03:26:13PM -0700, Eric Anholt wrote:
> > > On Wed, 2004-08-04 at 15:07, Geoff Speicher wrote:
> > > >
> > > > Snippets from /var/log/XFree86.0.log:
> > > >
> > > > (II) ATI: ATI driver (version 6.4.18) for chipsets: ati, ativga
> > > > (--) RADEON(0): Chipset: "ATI Radeon VE/7000 QY (AGP)" (ChipID = 0x5159)
> > > > (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o
> > > > (II) Module radeon: vendor="The XFree86 Project"
> > > > compiled for 4.3.0, module version = 4.0.1
> > > > Module class: XFree86 Video Driver
> > > > ABI class: XFree86 Video Driver, version 0.6
> > > >
> > > > (II) RADEON(0): [drm] loaded kernel module for "radeon" driver
> > > > (II) RADEON(0): Direct rendering enabled
> > >
> > > Does this happen without using threaded apps? More specifically, does
> > > it continue if you disable DRI in your X config? If so, please send me
> > > your dmesg.
> >
> > Hey, disabling DRI did the trick. Aside from things being remarkably
> > slow, it's remarkably stable. ;) Threaded X apps or no, I'm running
> > a July 19 kernel with no instant reboots. PREEMPTION disabled,
> > WITNESS enabled (I misspoke in another message when I said WITNESS was
> > disabled---apparently I fiddled more than I had remembered). Toggling
> > DRI back on and restarting X/kdm reboots immediately.
>
> While you didn't send your dmesg, I'm betting that you've got VIA 8377
> AGP. We're misconfiguring it, it seems. I'm working on a patch, please
> watch http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/69953 for a fix.

Sorry, I thought you wanted the dmesg if and only if the reboots
continued with DRI disabled.

You guessed right:

agp0: <VIA 8377 (Apollo KT400/KT400A/KT600) host to PCI bridge> mem 0xe0000000-0xe7ffffff at device 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0

Geoff

------------------------------

Message: 10
Date: Thu, 5 Aug 2004 10:34:12 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: HEADS UP! boot2 problems
To: FreeBSD Current List <cur...@freebsd.org>
Message-ID: <20040805173...@parodius.com>
Content-Type: text/plain; charset=us-ascii

All,

This commit works great. I also tested boot0sio (just for fun), works
fine as well.

Greatly appreciated; and a big thanks to Matt Dillon (as usual). :-)

On Thu, Aug 05, 2004 at 06:27:28AM +0000, Alexander Kabaev wrote:
> On Fri, Jul 30, 2004 at 03:21:19PM +0000, Alexander Kabaev wrote:
> > On Thu, Jul 29, 2004 at 08:39:43PM -0600, Scott Long wrote:
> > > All,
> > >
> > > The GCC 3.4 import seems to have broken the boot2 loader on at least
> > > i386. This doesn't affect normal world and kernel builds and installs,
> > > but does affect writing new bootblocks via the disklabel program. You
> > > should refrain from doing this until it gets fixed. It's being looked
> > > into right now.
> > >
> > > Scott
> >
> > Commit below made boot2 usable again.
>
> As suggested by Matt Dillon, the problems were caused by imcompletely
> zeroed out BSS. I merged approproate fixes from DragonflyBSD in commit
> below. Success/failure reports from people affected are appreciated.
>
> kann 2004-08-05 06:00:05 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/boot/i386/boot2 boot1.S
> sys/boot/i386/btx/lib btxcsu.s
> Log:
> Move boot2 BSS zeroing into btx startup code out of boot1. boot1 does not
> have clear idea on boot2 BSS size and leaves portion of it not zeroed out.
> btxcsu.s is in much better position for this job.
>
> Obtained from: DragonflyBSD (with minor adjustments)
>
> Revision Changes Path
> 1.29 +0 -4 src/sys/boot/i386/boot2/boot1.S
> 1.4 +9 -1 src/sys/boot/i386/btx/lib/btxcsu.s
>
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

------------------------------

Message: 11
Date: Thu, 5 Aug 2004 18:34:15 +0100
From: "Markie" <mark....@dsl.pipex.com>
Subject: Re: 5.2.1-R panic still occurs on a recent -CURRENT
To: "FreeBSD Current" <freebsd...@freebsd.org>
Message-ID: <00e601c47b12$7b469eb0$f800000a@laptop>
Content-Type: text/plain; charset="iso-8859-1"

----- Original Message -----
From: "Markie" <mark....@dsl.pipex.com>
To: "FreeBSD Current" <freebsd...@freebsd.org>
Sent: Friday, July 30, 2004 5:40 PM
Subject: Re: 5.2.1-R panic still occurs on a recent -CURRENT

| Here's the vmstat logs tar'd then gzipped. The filenames indicate the time of
| the 'snapshot' in the format of:
|
| vmstat.day.month.year.hour (year was probably very unnecessary but oh well :-)
|
| ----- Original Message -----
| From: "Markie" <mark....@dsl.pipex.com>
| To: "FreeBSD Current" <freebsd...@freebsd.org>
| Sent: Friday, July 30, 2004 1:46 AM
| Subject: 5.2.1-R panic still occurs on a recent -CURRENT
|
|
| | Hi all.
| |
| | You may or may not remember I was having trouble with 5.2.1-R giving me
random
| | panics along the lines of panic: kmem_malloc(4096): kmem_map too small: xxxx
| | total allocated. It was suggested that I updated to CURRENT to see if the
| issue
| | had been fixed.
| |
| | Well, my server just rebooted. The strange thing is though I didn't get a
| | crashdump this time... and it did a background fsck on / aswell, which was
| | really nice because it booted up so quickly. Is it safe though? I thought
| bgfsck
| | wasn't allowed on / yet?
| |
| | I can't remember who replied last time but I was told to log vmstat -mz
every
| | hour incase of memory leaks, so I have alot of vmstat hourly files if that
| might
| | determine the cause of my panic. I also logged netstat -m but if that isn't
| any
| | help then I can just get rid of all those.
| |
| | I also noticed something in the logs not long (or right before) it paniced
| this
| | time:
| |
| | Jul 30 01:19:57 bone kernel: arpresolve: can't allocate llinfo for
| | xxx.xxx.xxx.xxxrt
| | Jul 30 01:19:58 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not
| | allocate llinfo
| | Jul 30 01:19:58 bone kernel: arpresolve: can't allocate llinfo for
| | xxx.xxx.xxx.xxxrt
| | Jul 30 01:19:58 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not
| | allocate llinfo
| | Jul 30 01:19:58 bone kernel: arpresolve: can't allocate llinfo for
| | xxx.xxx.xxx.xxxrt
| | Jul 30 01:19:59 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not
| | allocate llinfo
| | Jul 30 01:19:59 bone kernel: arpresolve: can't allocate llinfo for
| | xxx.xxx.xxx.xxxrt
| | Jul 30 01:20:00 bone kernel: arplookup xxx.xxx.xxx.xxx failed: could not
| | allocate llinfo
| |
| | Alot of those. Not sure what it means exactly but could it be related in any
| | way?
| |
| | What do you suggest I do? Would you like to take a look at these vmstat
files?
| |
| | Thanks in advance.
| |
| | P.S Any ideas why it might not have saved a core dump this time? All I got
was
| | "Jul 30 01:21:39 bone savecore: no dumps found" I have dumpdev set in
rc.conf
| | too. Maybe it didn't panic but spontaneously rebooted, perhaps because of a
| | change in -CURRENT? Or is spontaneous rebooting hardware problems?
| |
|

--------------------------------------------------------------------------------

| _______________________________________________
| freebsd...@freebsd.org mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-current
| To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
|

Any ideas? No one else seems to have a problem with this panic randomly
appearing but me... :-S Need some more info?

------------------------------

Message: 12
Date: Thu, 5 Aug 2004 18:38:09 +0100
From: pa...@freebsd.org
Subject: Re: /dev/vga
To: Gleb Smirnoff <gle...@freebsd.org>
Cc: cur...@freebsd.org
Message-ID: <2004080517...@myrddin.originative.co.uk>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 05, 2004 at 06:42:06PM +0400, Gleb Smirnoff wrote:
> On Thu, Aug 05, 2004 at 12:59:30AM +0100, Paul Richards wrote:
> P> I can't start X anymore it complains about being unable to mmap
> P> /dev/vga.
>
> I have /dev/io and /dev/mem disappered in today's CURRENT :)

Yeah, same happened to me but I fixed that and now X complains about
/dev/vga.

------------------------------

Message: 13
Date: Thu, 5 Aug 2004 10:58:32 -0700 (PDT)
From: David Wolfskill <da...@catwhisker.org>
Subject: Re: [PLEASE TEST] Better support for Synaptics Touchpads
To: freebsd...@freebsd.org, phi...@freebsd.org
Message-ID: <200408051758....@bunrab.catwhisker.org>

>Date: Thu, 5 Aug 2004 09:12:36 +0200
>From: Philip Paeps <phi...@freebsd.org>
>To: freebsd...@freebsd.org
>Subject: [PLEASE TEST] Better support for Synaptics Touchpads
>Sender: owner-free...@freebsd.org

>Since the original synaptics support was added to psm, there have been some
>reports of malfunctions and missing magic. I've tried to fix all that, but
>it's still work in progress.

>If you happen to own a laptop with a synaptics touchpad, please help test:

> <http://people.freebsd.org/~philip/psm.diff>

OK; I'm running it now (and I have PSM_DEBUG set to 1 in the kernel).

>So far, I've had one report of a panic, possibly related to an extra gadget
>chained through the the touchpad. If you're extra masochistic, and your
>laptop has one of these extra gadgets, you might like to remove the #if 0
>around line 2537 and the #endif around line 2568 of your sys/isa/psm.c.

>Please report successes and failures :-)

Nothing extra attached; no panics. I confirm Alexandre "Sunny"
Kovalenko's results -- single touchpad tap acts as left mouse button
press/release event, but double-tap-and-drag doesn't seem to work so
well. Double- and triple-taps themselves seem OK, though.

[My test was trying to quit from ical: I can click on the "File" button,
but as soon as the mouse leaves the area of that button, the drop-down
menu that showed up, and that includes the "Exit" selection,
disappears.]

It is definitely a large step in a positive direction -- thanks! :-)

Peace,
david
--
David H. Wolfskill da...@catwhisker.org
I do not "unsubscribe" from email "services" to which I have not explicitly
subscribed. Rather, I block spammers' access to SMTP servers I control,
and encourage others who are in a position to do so to do likewise.

------------------------------

Message: 14
Date: Thu, 5 Aug 2004 18:10:00 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb...@lists.zabbadoz.net>
Subject: can see my reboot command idle 22 minutes :(
To: FreeBSD current mailing list <cur...@freebsd.org>
Message-ID:
<Pine.BSF.4.53.04...@e0-0.zab2.int.zabbadoz.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi,

have a 1 year old 5.1-RELEASE system with SCSI and one 120GB IDE
disk.

The IDE disk got used for daily dumps since january.
Tonight I got this error:

kernel: ad0: READ command timeout tag=0 serv=0 - resetting
kernel: ata0: resetting devices ..

serial console had been unuseable at that point but sshing/telnetting
onto the system still worked.

A dump had still been running. kill -9 didn't help much nor did
reboot. The reboot simply hung other services terminated so no longer
been able to telnet onto the machine.

Hands on resetted the machine and it got up booting fine, serial
console worked. It started background fsck and I went away.

45 minutes later fsck simply hang, had not been able to kill -9
it.

this time dmesg showed:
ad0: WRITE command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..

Stopped some services by hand and did some funny things,
commented out the ide disk in /etc.fstab and typed reboot.

Well the machine ist still up an running:

bz@machine: {107} w
7:58PM up 1:06, 6 users, load averages: 0.05, 0.16, 0.08
USER TTY FROM LOGIN@ IDLE WHAT
bz p0 shell 7:30PM 26 ls -l /dump/
bz p1 shell 7:32PM 25 sync
bz p2 shell 7:33PM 22 reboot
^^^^^^^^^^
bz p3 shell 7:39PM 11 atacontrol reinit 0
..
bz p5 shell 7:47PM - w

see the reboot there :((

I can still log in by ssh, do funny things but everything accessing
the IDE disk simply hangs...

Unfortunately this is 5.1-RELEASE so no
machine# sysctl debug.enter_debugger=ddb
sysctl: unknown oid 'debug.enter_debugger'

hands on again ...

--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT

------------------------------

Message: 15
Date: Thu, 5 Aug 2004 11:15:41 -0700 (PDT)
From: Doug White <dwh...@gumbysoft.com>
Subject: Re: Unable to build recent kernels
To: Mark Murray <ma...@grondar.org>
Cc: "Robin P. Blanchard" <robin.b...@gactr.uga.edu>
Message-ID: <2004080511...@carver.gumbysoft.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 4 Aug 2004, Mark Murray wrote:

> > cat >> your_kernel_config_file <<EOF
> > device mem
> > device null
> > device zero
> > EOF
>
> Only the first one. "device mem"

Some stuff might want "device io" too :)

--
Doug White | FreeBSD: The Power to Serve
dwh...@gumbysoft.com | www.FreeBSD.org

------------------------------

Message: 16
Date: Thu, 5 Aug 2004 11:29:55 -0700
From: Jeremy Chadwick <fre...@jdc.parodius.com>
Subject: Re: can see my reboot command idle 22 minutes :(
To: FreeBSD current mailing list <cur...@freebsd.org>
Message-ID: <20040805182...@parodius.com>
Content-Type: text/plain; charset=us-ascii

You should probably update the system ASAP. Soren has made major
improvements to the ATA layer, and may in fact address any issues
you're having in the past.

Is the IDE disk an IBM/Hitachi drive per chance? I've seen this
happen on them. It's a known ""feature"", which (from what I understand)
was supposed to be removed in later models, but I haven't bothered to
check.

Also: after upgrading, consider installing ports/sysutils/smartmontools
and enabling SMART on the drive/in the BIOS. You may have a drive
that's going bad -- IDE isn't known for reliability these days.

Hope this helps.

On Thu, Aug 05, 2004 at 06:10:00PM +0000, Bjoern A. Zeeb wrote:
> Hi,
>
> have a 1 year old 5.1-RELEASE system with SCSI and one 120GB IDE
> disk.
>
> The IDE disk got used for daily dumps since january.
> Tonight I got this error:
>
> kernel: ad0: READ command timeout tag=0 serv=0 - resetting
> kernel: ata0: resetting devices ..
>
> serial console had been unuseable at that point but sshing/telnetting
> onto the system still worked.
>
> A dump had still been running. kill -9 didn't help much nor did
> reboot. The reboot simply hung other services terminated so no longer
> been able to telnet onto the machine.
>
> Hands on resetted the machine and it got up booting fine, serial
> console worked. It started background fsck and I went away.
>
> 45 minutes later fsck simply hang, had not been able to kill -9
> it.
>
> this time dmesg showed:
> ad0: WRITE command timeout tag=0 serv=0 - resetting
> ata0: resetting devices ..
>
> Stopped some services by hand and did some funny things,
> commented out the ide disk in /etc.fstab and typed reboot.
>
> Well the machine ist still up an running:
>
> bz@machine: {107} w
> 7:58PM up 1:06, 6 users, load averages: 0.05, 0.16, 0.08
> USER TTY FROM LOGIN@ IDLE WHAT
> bz p0 shell 7:30PM 26 ls -l /dump/
> bz p1 shell 7:32PM 25 sync
> bz p2 shell 7:33PM 22 reboot
> ^^^^^^^^^^
> bz p3 shell 7:39PM 11 atacontrol reinit 0
> ..
> bz p5 shell 7:47PM - w
>
> see the reboot there :((
>
> I can still log in by ssh, do funny things but everything accessing
> the IDE disk simply hangs...
>
>
> Unfortunately this is 5.1-RELEASE so no
> machine# sysctl debug.enter_debugger=ddb
> sysctl: unknown oid 'debug.enter_debugger'
>
>
> hands on again ...
>
> --
> Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
> _______________________________________________
> freebsd...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

------------------------------

Message: 17
Date: Thu, 5 Aug 2004 14:33:33 -0400
From: Craig Rodrigues <rod...@crodrigues.org>
Subject: Installing cdevsw_add(), cdevsw_remove() man pages in
-current?
To: freebsd...@freebsd.org
Message-ID: <20040805183...@crodrigues.org>
Content-Type: text/plain; charset=us-ascii

Hi,

According to:
http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html

cdevsw_add() and cdevsw_remove() were removed in 500104.

If so, is there any point in installing man pages for these functions?

--- share/man/man9/Makefile.orig Thu Aug 5 14:32:04 2004
+++ share/man/man9/Makefile Thu Aug 5 14:32:18 2004
@@ -34,8 +34,6 @@
BUS_SETUP_INTR.9 \
byteorder.9 \
cd.9 \
- cdevsw_add.9 \
- cdevsw_remove.9 \
condvar.9 \
contigmalloc.9 \
copy.9 \

--
Craig Rodrigues
http://crodrigues.org
rod...@crodrigues.org

------------------------------

Message: 18
Date: Thu, 5 Aug 2004 12:01:39 -0700 (PDT)
From: Doug White <dwh...@gumbysoft.com>
Subject: Re: SiI3112a possible workaround?
To: Jason Andresen <jand...@mitre.org>
Cc: freebsd...@freebsd.org
Message-ID: <2004080511...@carver.gumbysoft.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 5 Aug 2004, Jason Andresen wrote:

> hdparm -X66 -d1 /dev/hda
> echo "max_kb_per_request:15" > /proc/ide/hdX/settings
> (repeat for both drives, e.g. hde and hdg).
>
> As I have one of these unfortunate controllers, I was wondering if it is
> possible to do something like this in FreeBSD? sysctl doesn't seem to
> have anything and I'm not sure what to look for in the sources. Does
> FreeBSD have any sort of analog to the above hdparm command?

'atacontrol mode' allows you to set the speeds on a per-device basis.

For the max_kb_per_request thing, thre isnt' a way to set that that I know
of, but it might be something that we could quirk in the driver.

--
Doug White | FreeBSD: The Power to Serve
dwh...@gumbysoft.com | www.FreeBSD.org

------------------------------

Message: 19
Date: Thu, 5 Aug 2004 12:27:10 -0700 (PDT)
From: Tony Montana <tonymon...@yahoo.com>
Subject: no text in gnome after portuprade
To: freebsd...@freebsd.org
Message-ID: <2004080519271...@web20225.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii

No text under icons or under folders or in actual text
files after doing a portupgrade. any ideas how to
correct this problem?

__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail

------------------------------

Message: 20
Date: Thu, 5 Aug 2004 21:41:11 +0200
From: Philip Paeps <phi...@freebsd.org>
Subject: Re: [PLEASE TEST] Better support for Synaptics Touchpads
To: freebsd...@freebsd.org
Message-ID: <20040805194...@fasolt.home.paeps.cx>
Content-Type: text/plain; charset=us-ascii

On 2004-08-05 10:58:32 (-0700), David Wolfskill <da...@catwhisker.org> wrote:
> Philip Paeps <phi...@freebsd.org> wrote:
> > If you happen to own a laptop with a synaptics touchpad, please help test:
> >
> > <http://people.freebsd.org/~philip/psm.diff>
>
> OK; I'm running it now (and I have PSM_DEBUG set to 1 in the kernel).
>
> > Please report successes and failures :-)
>
> Nothing extra attached; no panics.

Something tells me the panic was phk saw was caused by the bit I if'ed out.
Now if someone with extra gadgets could confirm that...

> I confirm Alexandre "Sunny" Kovalenko's results -- single touchpad tap acts
> as left mouse button press/release event, but double-tap-and-drag doesn't
> seem to work so well. Double- and triple-taps themselves seem OK, though.

The 'double-tap-and-drag' is not yet implemented. I'm still working on that,
as well as on 'virtual scrolling' and 'tossing' the pointer.

> [My test was trying to quit from ical: I can click on the "File" button,
> but as soon as the mouse leaves the area of that button, the drop-down menu
> that showed up, and that includes the "Exit" selection, disappears.]

Do you notice any improvement when you run moused with '-a 0.75' or similar?
I'm trying to decide how much to slow the acceleration down by default. I'm
seeing good results with 0.75 but I was having good results with the current
default too. Maybe I'm just handy? *grin*

> It is definitely a large step in a positive direction -- thanks! :-)

Good to know :-)

- Philip

--
Philip Paeps Please don't Cc me, I am
phi...@freebsd.org subscribed to the list.

Anything you try to fix will take longer and cost more than
you thought.

------------------------------

Message: 21
Date: Thu, 5 Aug 2004 15:03:18 -0500
From: Dan Nelson <dne...@allantgroup.com>
Subject: Fatal trap 12 in kern_ptrace
To: freebsd...@freebsd.org
Cc: freebsd...@freebsd.org
Message-ID: <2004080520...@dan.emsphone.com>
Content-Type: text/plain; charset=us-ascii

Recently I've been seeing libpthreaded processes just hang suddenly. ps
shows them in the STOPped state, and ps -H shows that all threads are
idle except for one, which is waiting on a lock (I've seen ufs and wait
on different occasions). Killing the process results in an instant
system freeze. I tried gdb'ing one this time, and was rewarded with
the following trap:

kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 03
fault virtual address = 0x44
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc058ae4c
stack pointer = 0x10:0xdef5db84
frame pointer = 0x10:0xdef5dc04
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 63683 (gdb)

At this point the system froze so I couldn't get a full stack trace,
but:

$ addr2line -f -e kernel.debug 0xc058ae4c
kern_ptrace
../../../kern/sys_process.c:659

658 if (saved_pid <= PID_MAX) {
659 p->p_xthread->td_flags &= ~TDF_XSIG;
660 p->p_xthread->td_xsig = data;

It looks like p_xthread is null when it shouldn't be. This is an Aug 02
kernel, so no PREEMPTION.

--
Dan Nelson
dne...@allantgroup.com

------------------------------

Message: 22
Date: Thu, 5 Aug 2004 20:06:15 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb...@lists.zabbadoz.net>
Subject: Re: can see my reboot command idle 22 minutes :(
To: FreeBSD current mailing list <cur...@freebsd.org>
Message-ID:
<Pine.BSF.4.53.04...@e0-0.zab2.int.zabbadoz.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 5 Aug 2004, Jeremy Chadwick wrote:

> You should probably update the system ASAP. Soren has made major
> improvements to the ATA layer, and may in fact address any issues
> you're having in the past.

I know. ARP and all that. Machine hadn't been updated for other
reasons.

> Is the IDE disk an IBM/Hitachi drive per chance? I've seen this

No, Maxtor imho.

> Hope this helps.

this had not been the problem (though triggered the other one maybe).

The problem had been that though multiuser worked quite fine,
the kernel didn't mannage to get the reboot done.

even a kill -INT 1 didn't reboot the machine. I could just type
ahead for another few minutes until I killed some of the hanging
sutdown scripts and my ssh and then only hands on helped again.

kill -INT 1 is supposed to reboot even if kill -TSTP 1 does not work ?

--
Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT

------------------------------

Message: 23
Date: Thu, 5 Aug 2004 22:30:27 +0200
From: Alexander Leidinger <Alex...@Leidinger.net>
Subject: IPSEC broken (FAST_IPSEC works)?
To: cur...@freebsd.org
Message-ID: <20040805223...@Magellan.Leidinger.net>
Content-Type: text/plain; charset=US-ASCII

Hi,

I've replaced a 4.10 server with a 5-current (Jul 18, without
PREEMPTION, with MSIZE=512) one. Both have the same IPSEC config
(kernel, setkey, racoon, gif). But the 5-current one isn't able to
transfer data over the VPN (no ping, no telnet to a port on a host on
the other side of the tunnel).

Racoon is able to negotiate a connection:
---snip---
# setkey -D
No SAD entries.

# ping host_behind_b:
[waiting long enough, but no output]
[ctrl-c]

# setkey -D
a b
esp mode=tunnel spi=3635833369(0xd8b66a19) reqid=0(0x00000000)
E: 3des-cbc 11d159c7 53846874 895eacfd 66074dc4 36350ac2 f09fe17a
A: hmac-md5 bf041de9 225ebf60 dac19d00 23653b39
seq=0x00000002 replay=4 flags=0x00000000 state=mature
created: Aug 5 22:10:27 2004 current: Aug 5 22:10:30 2004
diff: 3(s) hard: 300(s) soft: 240(s)
last: Aug 5 22:10:28 2004 hard: 0(s) soft: 0(s)
current: 272(bytes) hard: 0(bytes) soft: 0(bytes)
allocated: 2 hard: 0 soft: 0
sadb_seq=1 pid=561 refcnt=2
b a
esp mode=tunnel spi=116056914(0x06eae352) reqid=0(0x00000000)
E: 3des-cbc 053d94f1 edef8617 69d25dca e69ec7db ad3c9a1a 0838a24c
A: hmac-md5 04d024d9 96b2c61e 6ecc79e4 f2393bc4
seq=0x00000000 replay=4 flags=0x00000000 state=mature
created: Aug 5 22:10:27 2004 current: Aug 5 22:10:30 2004
diff: 3(s) hard: 300(s) soft: 240(s)
last: hard: 0(s) soft: 0(s)
current: 0(bytes) hard: 0(bytes) soft: 0(bytes)
allocated: 0 hard: 0 soft: 0
sadb_seq=0 pid=561 refcnt=1
---snip---

tcpdump while doing a "ping host_behind_b":
---snip---
21:43:53.966704 IP a.500 > b.500: isakmp: phase 2/others ? oakley-quick[E]
21:43:55.112454 IP b.500 > a.500: isakmp: phase 2/others ? oakley-quick[E]
21:43:55.120021 IP a.500 > b.500: isakmp: phase 2/others ? oakley-quick[E]
21:44:55.331956 IP b.500 > a.500: isakmp: phase 2/others ? inf[E]
21:47:14.475946 IP a > b: ESP(spi=0x754e1e4d,seq=0x1)
21:47:14.484644 IP b > a: ESP(spi=0x03a777cb,seq=0x1)
21:47:15.483319 IP a > b: ESP(spi=0x754e1e4d,seq=0x2)
21:47:15.489887 IP b > a: ESP(spi=0x03a777cb,seq=0x2)
21:47:16.493331 IP a > b: ESP(spi=0x754e1e4d,seq=0x3)
21:47:16.499916 IP b > a: ESP(spi=0x03a777cb,seq=0x3)
21:47:17.503348 IP a > b: ESP(spi=0x754e1e4d,seq=0x4)
21:47:17.514614 IP b > a: ESP(spi=0x03a777cb,seq=0x4)
21:47:18.513362 IP a > b: ESP(spi=0x754e1e4d,seq=0x5)
21:47:18.520057 IP b > a: ESP(spi=0x03a777cb,seq=0x5)
21:47:56.970054 IP a.500 > b.500: isakmp: phase 2/others ? oakley-quick[E]
21:47:58.115081 IP b.500 > a.500: isakmp: phase 2/others ? oakley-quick[E]
21:47:58.122636 IP a.500 > b.500: isakmp: phase 2/others ? oakley-quick[E]
21:49:00.330423 IP b.500 > a.500: isakmp: phase 2/others ? inf[E]
21:53:00.318424 IP b.500 > a.500: isakmp: phase 2/others ? inf[E]
---snip---

tcpdump on the gif interface shows nothing.

"netstat -s -p ipsec" reports:
---snip---
ipsec:
106 inbound packets processed successfully
0 inbound packets violated process security policy
0 inbound packets with no SA available
0 invalid inbound packets
0 inbound packets failed due to insufficient memory
0 inbound packets failed getting SPI
0 inbound packets failed on AH replay check
0 inbound packets failed on ESP replay check
0 inbound packets considered authentic
0 inbound packets failed on authentication
ESP input histogram:
3des-cbc: 106
102 outbound packets processed successfully
0 outbound packets violated process security policy
5 outbound packets with no SA available
0 invalid outbound packets
0 outbound packets failed due to insufficient memory
0 outbound packets with no route
ESP output histogram:
3des-cbc: 102
7526 SPD cache lookups
3235 SPD cache misses
---snip---

A kernel with FAST_IPSEC instead of IPSEC works as expected (ping
reports the round trip time, tcpdump shows traffic on the gif interface
and a quick test with telnet to a port on host_behind_b shows the
expected output).

The system is supposed to go into production soon, so I can't guarantee
I can do "expensive" tests if someone comes up with a patch or needs
some data which is only available if IPSEC instead of FAST_IPSEC is
used.

Bye,
Alexander.

--
I'm available to get hired (preferred in .lu).

http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7

------------------------------

Message: 24
Date: Thu, 5 Aug 2004 22:36:40 +0200 (CEST)
From: Lukas Ertl <l...@FreeBSD.org>
Subject: Re: gvinum resetconfig
To: Shaun Courtney <sh...@gvmail.vine.co.za>
Cc: cur...@FreeBSD.org
Message-ID: <200408052...@korben.in.tern>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Thu, 5 Aug 2004, Shaun Courtney wrote:

> I'm looking for some help with geom_vinum (gvinum) and the resetconf
> command. I've moved some disk around but they still keep the old gvinum
> configuration. i've tried resetconfig aka vinum but it just returns to
> the prompt ;(

'resetconfig' needs to be implemented first (no, I'm not lazy, I just
spent two days in a row to build my new kitchen, and I'm still not
finished yet :-/).

You can wipe the config by doing 'dd if=/dev/zero of=/dev/ad0s1e bs=32k
count=10' (but only, when geom_vinum isn't loaded).

cheers,
le

--
Lukas Ertl http://homepage.univie.ac.at/l.ertl/
l...@FreeBSD.org http://people.freebsd.org/~le/

------------------------------

Message: 25
Date: Thu, 05 Aug 2004 23:17:32 +0200
From: S?ren Schmidt<s...@DeepCore.dk>
Subject: Re: SiI3112a possible workaround?
To: Jason Andresen <jand...@mitre.org>
Cc: freebsd...@freebsd.org
Message-ID: <4112A3EC...@DeepCore.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Jason Andresen wrote:
> I was searching the net today and I came across this little gem in a
> Linux mailing list:
>
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0307.3/1349.html
>
> Notably:
>
> 1) As some others suggested on the list, the problem with very slow
> transfer and timeouts if you try to enable DMA, can be fixed by the
> following lines in an appropriate rc file:
>
> hdparm -X66 -d1 /dev/hda
> echo "max_kb_per_request:15" > /proc/ide/hdX/settings
> (repeat for both drives, e.g. hde and hdg).
>
> As I have one of these unfortunate controllers, I was wondering if it is
> possible to do something like this in FreeBSD? sysctl doesn't seem to
> have anything and I'm not sure what to look for in the sources. Does
> FreeBSD have any sort of analog to the above hdparm command?

The ATA driver already limits transfers to 8K on the older stepping of
that bugridden silicon. Could you please mail me the complete output of
a dmesg and the output of pciconf -l ? I've newer been able to reproduce
this problem so I'd like to know what exact HW causes this so we can try
a workaround if possible...

BTW you should definitly try to update your install to the latest
-current as I've just committed some race fixes that might help you on
that chip as well...

-Søren

------------------------------

Message: 26
Date: Thu, 5 Aug 2004 16:20:25 -0500
From: Craig Boston <cr...@xfoil.gank.org>
Subject: Re: Vinum status
To: Paul Mather <pa...@gromit.dlib.vt.edu>
Cc: freebsd...@FreeBSD.org
Message-ID: <20040805212025.GA28645@nowhere>
Content-Type: text/plain; charset=us-ascii

FWIW, root-on-gvinum seems to be working on my test server here.
Swapping over it also passes basic stress testing (dd from zero to null
with very large block sizes).

The system does seem to be quite a bit slower than before, but that may
be related to having PREEMPTION disabled (this is an SMP system). I'll
see how it responds once that whole situation is resolved.

win2ktest# gvinum l
3 drives:
D drive3 State: up /dev/da0s1e A: 0/8675 MB (0%)
D drive2 State: up /dev/ad2s1e A: 0/8675 MB (0%)
D drive1 State: up /dev/ad0s1e A: 0/8675 MB (0%)

5 volumes:
V root State: up Plexes: 3 Size: 128 MB
V swap State: up Plexes: 1 Size: 1024 MB
V usr State: up Plexes: 1 Size: 14 GB
V var State: up Plexes: 1 Size: 512 MB
V tmp State: up Plexes: 1 Size: 256 MB

7 plexes:
P root.p0 C State: up Subdisks: 1 Size: 128 MB
P root.p1 C State: up Subdisks: 1 Size: 128 MB
P root.p2 C State: up Subdisks: 1 Size: 128 MB
P swap.p0 R5 State: up Subdisks: 3 Size: 1024 MB
P usr.p0 R5 State: up Subdisks: 3 Size: 14 GB
P var.p0 R5 State: up Subdisks: 3 Size: 512 MB
P tmp.p0 R5 State: up Subdisks: 3 Size: 256 MB

15 subdisks:
S root.p0.s0 State: up D: drive1 Size: 128 MB
S root.p1.s0 State: up D: drive2 Size: 128 MB
S root.p2.s0 State: up D: drive3 Size: 128 MB
S swap.p0.s0 State: up D: drive1 Size: 512 MB
S swap.p0.s1 State: up D: drive2 Size: 512 MB
S swap.p0.s2 State: up D: drive3 Size: 512 MB
S usr.p0.s0 State: up D: drive1 Size: 7651 MB
S usr.p0.s1 State: up D: drive2 Size: 7651 MB
S usr.p0.s2 State: up D: drive3 Size: 7651 MB
S var.p0.s0 State: up D: drive1 Size: 256 MB
S var.p0.s1 State: up D: drive2 Size: 256 MB
S var.p0.s2 State: up D: drive3 Size: 256 MB
S tmp.p0.s0 State: up D: drive1 Size: 128 MB
S tmp.p0.s1 State: up D: drive2 Size: 128 MB
S tmp.p0.s2 State: up D: drive3 Size: 128 MB

--
Craig

------------------------------

Message: 27
Date: Thu, 05 Aug 2004 17:22:30 -0400
From: Mike B <m...@cinci.rr.com>
Subject: Re: gvinum resetconfig
To: Lukas Ertl <l...@freebsd.org>
Cc: cur...@freebsd.org
Message-ID: <4112A516...@cinci.rr.com>
Content-Type: text/plain; charset=us-ascii; format=flowed

Lukas Ertl wrote:
> On Thu, 5 Aug 2004, Shaun Courtney wrote:
>
>> I'm looking for some help with geom_vinum (gvinum) and the resetconf
>> command. I've moved some disk around but they still keep the old gvinum
>> configuration. i've tried resetconfig aka vinum but it just returns to
>> the prompt ;(
>
>
> 'resetconfig' needs to be implemented first (no, I'm not lazy, I just
> spent two days in a row to build my new kitchen, and I'm still not
> finished yet :-/).
>
> You can wipe the config by doing 'dd if=/dev/zero of=/dev/ad0s1e bs=32k
> count=10' (but only, when geom_vinum isn't loaded).
>

Is it is possible to remove individual device definitions (EX: drive a
device /dev/adx)? I was playing around with
a bunch of vnode disks which I've since gotten rid of, but the drive
defs are still saved in the config of my real disks.

Thanks, Mike

------------------------------

Message: 28
Date: Thu, 5 Aug 2004 16:54:54 -0500
From: Scott Lambert <lam...@lambertfam.org>
Subject: Re: no text in gnome after portuprade
To: freebsd...@freebsd.org
Message-ID: <2004080521...@laptop.lambertfam.org>
Content-Type: text/plain; charset=us-ascii

On Thu, Aug 05, 2004 at 12:27:10PM -0700, Tony Montana wrote:
> No text under icons or under folders or in actual text
> files after doing a portupgrade. any ideas how to
> correct this problem?

When this happenned to me, I forced a portupgrade of some font related
package, IIRC. You could always use the big hammer:

portupgrade -fr gnome*

I may have used the big hammer myself. My gnome stuff seems to have
been updated about all on about the same day.

Hmm, scrollkeeper is jogging my memory. Something was messed up with
the permissions of the /var/db/scroollkeeper stuff or maybe it was
a corruption of some sort. When I was watching what happenned with
portupgrade and backtracking the ports that failed it all came back
to scrollkeeper somehow. I think I blew away some of the files in
/var/db/scroolkeeper/TOC then portupgrade -f'd scroolkeeper.

--
Scott Lambert KC5MLE Unix SysAdmin
lam...@lambertfam.org

------------------------------

Message: 29
Date: Thu, 5 Aug 2004 17:47:53 -0400
From: John Baldwin <j...@FreeBSD.org>
Subject: Re: Watchdog timeouts with ACPI
To: freebsd...@FreeBSD.org
Cc: Bill Moran <wmo...@potentialtech.com>
Message-ID: <20040805174...@FreeBSD.org>
Content-Type: text/plain; charset="iso-8859-1"

On Sunday 01 August 2004 10:12 am, Bill Moran wrote:
> Just cvsupped current and rebuilt everything last night (July 31) and I
> get watchdog timeouts on my NIC when ACPI is enabled. All seems to work
> well with ACPI turned off.
>
> dmesg is attached. Email me if there's any more information I can collect
> to help get this working better. I'm not subscribed to current@, so
> send it direct.

Try ACPI with apic diesbled (set hint.apic.0.disabled=1 at the loader prompt),
it appears that your MP Table is busted so you aren't using the apic when you
don't use ACPI.

--
John Baldwin <j...@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org

------------------------------

Message: 30
Date: Thu, 5 Aug 2004 17:47:53 -0400
From: John Baldwin <j...@FreeBSD.org>
Subject: Re: Watchdog timeouts with ACPI
To: freebsd...@FreeBSD.org
Cc: Bill Moran <wmo...@potentialtech.com>
Message-ID: <20040805174...@FreeBSD.org>
Content-Type: text/plain; charset="iso-8859-1"

Try ACPI with apic diesbled (set hint.apic.0.disabled=1 at the loader prompt),
it appears that your MP Table is busted so you aren't using the apic when you
don't use ACPI.

--
John Baldwin <j...@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org

------------------------------

Message: 31
Date: Thu, 5 Aug 2004 17:50:51 -0400
From: John Baldwin <j...@FreeBSD.org>
Subject: Re: kernel panic when accessing digi serial multi io.
To: freebsd...@FreeBSD.org, rob...@mpe.mpg.de
Message-ID: <20040805175...@FreeBSD.org>
Content-Type: text/plain; charset="iso-8859-1"

On Monday 02 August 2004 10:27 am, Klaus Robert Suetterlin wrote:
> Dear all,
>
> I use a Digi Xem (16 serial ports) with FreeBSD Current.
>
> geclab2# kldload digi
> digi0 mem 0xb0800000-0xb0bfffff irq 30 at device 4.0 on pci0
> digi0: Digiboard PCI PC/Xem ASIC, 16 ports found
>
> This worked ok until I updated last week.
>
> geclab2# uname -a
> FreeBSD geclab2.cips.mpg.de 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Thu Jul 29
> 17:14:49 CEST 2004 k...@geclab2.cips.mpg.de:/usr/obj/usr/src/sys/GECLAB2
> i386
>
> Now every time I access any serial port on the digi I get a kernel
> panic. My normal (sio0, sio1) serial ports work ok. It's not
> always the same panic but always about mutexes or Giant etc. Here
> is one as an example:
>
> geclab2# cu -l /dev/ttyD0.2
> panicpanic: process 530(cu):2 holds Giant but isn't blocked on a lock
>
> KDB: enter: panic
> [thread 100006]
> Stopped at kdb_enter+0x2b: nop
> db> where
> kdb_enter(c0632982) at kdb_enter+0x2b
> panic(c063567d,212,c20be83c,2,c0642312) at panic+0xbb
> propagate_priority(c1de3840,c068cc70,c0688aa0,c1de3840,c1dd8340) at
> propagate_pr iority+0x142
> turnstile_wait(c1dd8340,c0688aa0,c20bd2c0,c0688aa0,2,c0631d0e,212) at
> turnstile_ wait+0x2de
> _mtx_lock_sleep(c0688aa0,0,c06302e4,21f) at _mtx_lock_sleep+0x11b
> _mtx_lock_flags(c0688aa0,0,c06302e4,21f) at _mtx_lock_flags+0x83
> ithread_loop(c1de0b80,d8f6bd48,c1de0b80,c04ae198,0) at ithread_loop+0x11c
> fork_exit(c04ae198,c1de0b80,d8f6bd48) at fork_exit+0xa4
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0x1, eip = 0, esp = 0xd8f6bd7c, ebp = 0 ---

Do you have an SMP machine? If so, does adding 'options NO_ADAPTIVE_MUTEXES'
to your kernel fix the panic?

--
John Baldwin <j...@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org

------------------------------

Message: 32
Date: Thu, 5 Aug 2004 17:59:53 -0400
From: John Baldwin <j...@FreeBSD.org>
Subject: Re: Atomic operations on i386/amd64
To: freebsd...@FreeBSD.org
Cc: Tim Robbins <t...@FreeBSD.org>
Message-ID: <20040805175...@FreeBSD.org>
Content-Type: text/plain; charset="iso-8859-1"

On Thursday 05 August 2004 01:04 am, Tim Robbins wrote:
> Is there any particular reason why atomic_load_acq_*() and
> atomic_store_rel_*() are implemented with CMPXCHG and XCHG instead of
> MOV on i386/amd64 UP?

Actually, using mov instead of lock xchg for store_rel reduced performance in
some benchmarks Scott ran on an SMP machine, I'm guessing due to the higher
latency of locks becoming available to other CPUs. I'm still waiting for
benchmark results on UP to see if the change should be made under #ifndef SMP
or some such.

> Also, could we use MFENCE/LFENCE/SFENCE in combination with MOV on
> SMP systems instead of LOCK CMPXCHG / (implied LOCK) XCHG?

MFENCE and LFENCE only exist on the P4. SFENCE only exists on P3+, so to do
so you'd lose the ability to run on PII's and earlier. Also, if you use more
than SFENCE you lose PIII's. Note that amd64 could probably be changed
though since they might all have fences, in which case that might be
something to benchmark on both UP and SMP to see what kind of difference it
makes.

--
John Baldwin <j...@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org

------------------------------

Message: 33
Date: Thu, 05 Aug 2004 18:02:26 -0400
From: Joe Marcus Clarke <mar...@marcuscom.com>
Subject: Re: no text in gnome after portuprade
To: Scott Lambert <lam...@lambertfam.org>
Cc: freebsd...@freebsd.org
Message-ID: <1091743346.739.48.camel@gyros>
Content-Type: text/plain; charset="us-ascii"

On Thu, 2004-08-05 at 17:54, Scott Lambert wrote:
> On Thu, Aug 05, 2004 at 12:27:10PM -0700, Tony Montana wrote:
> > No text under icons or under folders or in actual text
> > files after doing a portupgrade. any ideas how to
> > correct this problem?
>
> When this happenned to me, I forced a portupgrade of some font related
> package, IIRC. You could always use the big hammer:
>
> portupgrade -fr gnome*
>
> I may have used the big hammer myself. My gnome stuff seems to have
> been updated about all on about the same day.
>
> Hmm, scrollkeeper is jogging my memory. Something was messed up with
> the permissions of the /var/db/scroollkeeper stuff or maybe it was
> a corruption of some sort. When I was watching what happenned with
> portupgrade and backtracking the ports that failed it all came back
> to scrollkeeper somehow. I think I blew away some of the files in
> /var/db/scroolkeeper/TOC then portupgrade -f'd scroolkeeper.

This problem is almost always related to binaries being linked to
multiple versions of pango. A portupgrade -rf pango should clean things
up.

Joe

--
PGP Key : http://www.marcuscom.com/pgp.asc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040805/cb81f0b8/attachment.bin

------------------------------

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

End of freebsd-current Digest, Vol 71, Issue 15
***********************************************

0 new messages