On Thursday, January 06, 2011 3:08:04 am per...@pluto.rain.com wrote:
> John Baldwin wrote:
>
> > ... even NFS UDP mounts maintain their own set of "socket" state
> > to manage retries and retransmits for UDP RPCs.
>
> Not according to what I remember of th
t, but 8 is certainly more fragile
than 7 for mounting NFS on boot.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
has the
problem (a pure 8 system also has the same symptoms, so it's not a problem
due to mixing a 7 world with 8 kernel).
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
like
"1g" for size?
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
aving an #ifdef.
Finally, I would adjust the wording in the manpage to not say that this
modifies the MSGBUF_SIZE option, but that this tunable is the same as
adjusting MSGBUF_SIZE. Other than that I think it is fine.
--
John Baldwin
___
freebsd-sta
). I also see that Scott
> Long suggested that it might make it for the release of 8.2.
> Is this still the case? Do you think we'll have this driver in 8.2?
It was not merged to 8 in time for 8.2. It will hopefully be present in 8.3.
--
John Baldwin
_
tested before 8.3 is
released.
> Cheers,
> Rumen Telbizov
>
> On Tue, Jan 25, 2011 at 10:17 AM, John Baldwin wrote:
>
> > On Tuesday, January 25, 2011 11:26:12 am Rumen Telbizov wrote:
> > > Hello everyone,
> > >
> > > I saw a discussion not far ba
owever, look at what hw.physmem says (and the realmem and availmem lines in
dmesg). realmem is actually not that useful as it is not a count of the
amount of memory, but the address of the highest memory page available. There
can be less memory available than that
On Wednesday, January 26, 2011 8:20:28 am Bartosz Stec wrote:
> W dniu 2011-01-26 14:06, John Baldwin pisze:
> > On Wednesday, January 26, 2011 7:20:34 am Bartosz Stec wrote:
> >> Guys,
> >>
> >> could someone explain me this?
> >>
> >>
On Wednesday, January 26, 2011 1:04:02 pm Marco van Tol wrote:
> On Wed, Jan 26, 2011 at 12:35:56PM -0500, John Baldwin wrote:
> > On Wednesday, January 26, 2011 8:20:28 am Bartosz Stec wrote:
> > > W dniu 2011-01-26 14:06, John Baldwin pisze:
> > > > On Wednesda
o synchronize the updates to
the flags member with other threads attempting to acquire the lock. The
VN_LOCK_A*() macros now invoke these routines, and the softupdates code
uses these routines to temporarly enable recursion on buffer locks.
Reviewed by: kib
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Monday, January 31, 2011 5:29:24 pm John Hickey wrote:
> On Mon, Jan 31, 2011 at 12:00:29PM -0500, John Baldwin wrote:
> (kgdb) vprint vp
> 0xd417633c: tag none, type VBAD
> usecount 0, writecount 0, refcount 1 mountedhere 0x0
> flags (VI_DOOMED)
> lock type uf
ed while
> /usr/src/sys/sys wasn't :-( .
Hmm, I noticed this recently as well, but wasn't sure if anyone else had seen
this.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
gt;
> > ___
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> >
>
>
epository instead of a directory of patches against a CVS checkout), I will
probably hack it to support using etcupdate to manage /etc updates as well.
(etcupdate uses something akin to 'svn up' to update files in /etc, so things
like $FreeBSD$ changes just auto-update assuming they don'
tors hard-coded as
constant values in the code.
Unfortunately there is no register that tells us which illegal vector was
posted.
Were you doing anything related to changing the state of device interrupts
(cpuset -x, kldload, kldunload, etc.) when this happened?
--
John Baldwin
On Wednesday, March 02, 2011 8:07:59 am Mike Tancsa wrote:
> On 3/2/2011 7:55 AM, John Baldwin wrote:
> >
> > Hmm, the interrupt pins on the each lapic look fine (they all either have a
> > legal vector, are using NMI delivery, or are masked).
> >
> > All of t
On Wednesday, March 02, 2011 7:39:56 pm Yanhui Shen wrote:
> `CPU0: local APIC error 0x40"
>
> I get this error on my ThinkPad R400(Intel Core2 T6570).
Do you get a hang or does the machine keep working fine?
--
John Baldwin
___
umption if 'orig_object' only has cache pages and no currently-swapped out
pages (or if the swapped out pages are not in the range of the new object)?
I've cc'd Alan to see if he has any ideas.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
apic" that includes I/O APIC (local_apic.c) which defines in a
> ifdef KDTRACE_HOOKS ( cyclic_clock_func_t cyclic_clock_func[MAXCPU]; ).
> Since the lack of I/O APIC being used, sys/x86/isa/clock.c needs its own
> definition of the same cyclic_clock_func, so I have added this in
also use nvidia-settings to configure several things like multiple
monitors, etc. rather easily.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
merly was sio1:
>
> sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on
> acpi0
> sio0: type 16550A, console
> sio0: [FILTER]
>
> Thus, I'm unable to run getty.
>
> I belive that this issue might be related to ACPI, as similar problem
>
enumerating the ports backwards which 8 handles
by matching hinted devices based on resources. That has nothing to do with
either sio(4) or uart(4) if so.
The BMC port usually uses the resources from COM2 by default which our default
hints assign to sio1/uart1.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
quot;
> hint.sio.1.port="0x2F8"
> hint.sio.1.irq="3"
> hint.sio.2.at="isa"
> hint.sio.2.disabled="1"
> hint.sio.2.port="0x3E8"
> hint.sio.2.irq="5"
> hint.sio.3.at="isa"
> hint.sio.3.disabled="1"
device is your COM1. Do you have a copy of your current
dmesg available? I'm curious if sio0 failed to probe the UAR1 device and then
later attached to UAR2.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freeb
> Sure, this is my non-verbose dmesg: http://www.frasunek.com/tmp/dmesg.txt
>
> It's from 7.3-RELEASE, but on 7.4 I get the same behaviour.
Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait
until you get a verbose dmesg
://www.frasunek.com/tmp/dmesg-verb.txt
Hummm. Can you do a few things:
1) Add a printf to sioprobe() in sys/dev/sio/sio.c to output an error message
when it fails to allocate a SYS_RES_IOPORT device at the very beginning.
2) Capture 'acpidump -d'
}
The _STA method is used to query a device's status, and a status of 0 means
that the device is disabled. I believe that this means that when you have
SOL enabled (SOLE?) that COM1 is marked inactive so the OS ignores the device.
--
John Baldwin
For that reason, i386 cannot set
mp_maxid optimally.
Note that the only guarantee made with regards to mp_maxid is that all
CPU IDs for all active CPUs in the system will be <= mp_maxid. There is
no guarantee of denseness of CPU IDs (there can be holes), or even that
the CPUs start
and sio1 and seeing
if
sio1 suddenly shows up as working and valid. If so, then the changes in 8 to
bind
unit numbers using hints might work for you to get COM1 back as sio0.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lis
round that issue by recognizing that case and
keeping COM2 at sio1. That would then have allowed sio0 to probe at isa0.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
e the last two actually *working* in /boot/loader.conf? Can you
> verify by looking at them via sysctl? AFAIK they shouldn't work, since
> they lack double-quotes around the values. Parsing errors are supposed
> to throw you back to the loader prompt. See loader.conf(5) for the
> syn
= 'VT8251 Standard PCIe Root Port'
> class = bridge
> subclass = PCI-PCI
> cap 10[40] = PCI-Express 1 root port max data 128(256) link x0(x1)
> cap 01[68] = powerspec 2 supports D0 D3 current D0
> cap 05[70] = MSI supports 1 message, 64 bit, vector
hitespace, so
foo=bar
bar=42G
baz="foo bar"
are fine, but
baz=foo bar
will fail.
This is similar to normal shell syntax for assigning to variables.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Saturday, April 30, 2011 2:42:11 am Wiktor Niesiobedzki wrote:
> 2011/4/29 Wiktor Niesiobedzki :
> > 2011/4/28 Jack Vogel :
> >> On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin wrote:
> >>>
> >>> On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedz
e acpi(4) man page?
>
> There's also a mention of this variable in a file called
> src/tools/tools/sysdoc/tunables.mdoc, but I'm not sure what that is.
Hmm, it appears that it is indeed deprecated.
--
John Baldwin
___
freebsd-stable@freeb
5 at syscallenter+0x1e5
> #11 0xff808aca5b at syscall+0x4b
> #12 0xff80895292 at Xfast_syscall+0xe2
You need to trace the thread that owns the lock (in this case 619). I thought
the kernel automatically did that actually, but maybe it on
tire buildworld
to test backing them out.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
;, 0x10 },
{ 0x9710, 0x9820, 0x1000, 1, "NetMos NM9820 Serial Port", 0x10 },
{ 0x9710, 0x9835, 0x1000, 1, "NetMos NM9835 Serial Port", 0x10 },
{ 0x9710, 0x9865, 0xa000, 0x1000, "NetMos NM9865 Serial Port", 0x10 },
--
John Baldwin
__
On Thursday, May 26, 2011 3:01:35 pm Willy Offermans wrote:
> Dear John and FreeBSD friends,
>
> On Wed, May 25, 2011 at 12:36:30PM -0400, John Baldwin wrote:
> > On Saturday, May 21, 2011 5:20:37 am Willy Offermans wrote:
> > > Dear FreeBSD friends,
> > >
>
On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> On 5/26/2011 4:12 PM, John Baldwin wrote:
> >
> > Hmm, can you get 'pciconf -lb' output?
> >
> > Hmm, wow, I wonder how uart(4) works at all. It tries to reuse it's softc
> >
On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> Dear John and FreeBSD friends,
>
> On Fri, May 27, 2011 at 08:05:56AM -0400, John Baldwin wrote:
> > On Thursday, May 26, 2011 4:58:37 pm Mike Tancsa wrote:
> > > On 5/26/2011 4:12 PM, John Baldwin wrote:
>
On Friday, May 27, 2011 10:43:23 am Mike Tancsa wrote:
> On 5/27/2011 8:05 AM, John Baldwin wrote:
>
> >
> > Oh, hmm, looks like the clock has an unusual multiplier. Does it work if
you
> > use 'cu -l -s 1200' to talk at 9600 for example? (In general use
On Friday, May 27, 2011 1:54:54 pm Mike Tancsa wrote:
> On 5/27/2011 12:00 PM, John Baldwin wrote:
> >>
> >> uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> >> rev=0x02 hdr=0x00
> >> vendor = 'Exar Corp.'
On Friday, May 27, 2011 1:54:54 pm Mike Tancsa wrote:
> On 5/27/2011 12:00 PM, John Baldwin wrote:
> >>
> >> uart2@pci0:5:0:0: class=0x070002 card=0x20282205 chip=0x015213a8
> >> rev=0x02 hdr=0x00
> >> vendor = 'Exar Corp.'
On Friday, May 27, 2011 3:38:04 pm Mike Tancsa wrote:
> On 5/27/2011 3:33 PM, John Baldwin wrote:
> >
> > Actually, can you just try this:
> >
> > Index: pucdata.c
>
> Hi,
> Patch applies, but it doesnt compile on RELENG_8
Ugh, looks like the offset
On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote:
> Hello John and FreeBSD friends,
>
> On Fri, May 27, 2011 at 10:43:34AM -0400, John Baldwin wrote:
> > On Friday, May 27, 2011 10:38:02 am Willy Offermans wrote:
> > > Dear John and FreeBSD friends,
> > >
On Friday, June 03, 2011 8:34:54 am Willy Offermans wrote:
> Dear John and FreeBSD friends,
>
> On Tue, May 31, 2011 at 11:01:23AM -0400, John Baldwin wrote:
> > On Monday, May 30, 2011 5:25:14 am Willy Offermans wrote:
> > > Hello John and FreeBSD friends,
> > >
On Friday, June 03, 2011 3:00:09 pm Willy Offermans wrote:
> Hello John and FreeBSD friends,
>
> On Fri, Jun 03, 2011 at 09:48:26AM -0400, John Baldwin wrote:
> > On Friday, June 03, 2011 8:34:54 am Willy Offermans wrote:
> > > Dear John and FreeBSD friends,
> > &g
akes
it all the way through that, start walking through the BTX init code.
Oddly enough, BTX had to run at least once so that boot2 could find the loader
and kick off the btxldr.S.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Monday, June 13, 2011 11:26:53 am Guido Falsi wrote:
> On Thu, Jun 09, 2011 at 03:43:15PM -0400, John Baldwin wrote:
> > On Thursday, June 09, 2011 11:28:20 am Guido Falsi wrote:
> > > Hi!
> > >
> > > I'm having a problem with BTX hanging on an HP
ode to support C/H/S addressing from
zfsldr. The ZFS and GPT bootstraps always just use EDD LBA addressing.
MFC after:2 weeks
Modified:
head/sys/boot/i386/boot2/Makefile
head/sys/boot/i386/common/drv.c
head/sys/boot/i386/zfsboot/Makefile
head/sys/boot/i386/zfsboot/zfsldr.S
--
On Friday, June 17, 2011 11:30:28 am Guido Falsi wrote:
> On Mon, Jun 13, 2011 at 11:45:07AM -0400, John Baldwin wrote:
> >
> > Ouch. Well, these can be a PITA to disassemble. ndisasm from the
devel/nasm
> > port is a good x86 disassembler that you can use. You will need
On Friday, June 17, 2011 1:06:22 pm Henri Hennebert wrote:
> On 06/16/2011 19:35, John Baldwin wrote:
> > On Thursday, June 16, 2011 8:45:41 am Zhihao Yuan wrote:
> >> Exactly. The MFCed ZFSv28 is different from any patch maintained by
> >> mm@. Maybe some untested cha
On Saturday, June 18, 2011 5:04:07 am Henri Hennebert wrote:
> On 06/17/2011 19:37, John Baldwin wrote:
> > On Friday, June 17, 2011 1:06:22 pm Henri Hennebert wrote:
> >> On 06/16/2011 19:35, John Baldwin wrote:
> >>> On Thursday, June 16, 2011 8:45:41 am Zhihao Y
On Tuesday, June 21, 2011 5:51:22 am Henri Hennebert wrote:
> On 06/20/2011 15:51, John Baldwin wrote:
> > On Saturday, June 18, 2011 5:04:07 am Henri Hennebert wrote:
> >> On 06/17/2011 19:37, John Baldwin wrote:
> >>> On Friday, June 17, 2011 1:06:22 pm Henri He
On Tuesday, June 21, 2011 10:50:14 am Henri Hennebert wrote:
> On 06/21/2011 15:01, John Baldwin wrote:
> > Index: zfsldr.S
> > ===
> > --- zfsldr.S(revision 223339)
> > +++ zfsldr.S(working
On Tuesday, June 21, 2011 12:15:58 pm Henri Hennebert wrote:
> On 06/21/2011 17:55, John Baldwin wrote:
> > On Tuesday, June 21, 2011 10:50:14 am Henri Hennebert wrote:
> >> On 06/21/2011 15:01, John Baldwin wrote:
>
On Tuesday, June 21, 2011 3:02:28 pm Henri Hennebert wrote:
> On 06/21/2011 19:51, John Baldwin wrote:
> > On Tuesday, June 21, 2011 12:15:58 pm Henri Hennebert wrote:
> >> On 06/21/2011 17:55, John Baldwin wrote:
> >>> On Tuesday, June 21, 2011 10:50:14 am Henri He
On Tuesday, June 21, 2011 4:13:20 pm Henri Hennebert wrote:
> On 06/21/2011 21:25, John Baldwin wrote:
> and I get:
>
> Read error: 04
Hmm, that is the error for an invalid sector. Try this patch. It reshuffles
a few more things and adds code to dump the low 32-bits of the LBA
.ascii "LBA: "
+lba: .asciz "\r\n"
+msg_part: .asciz "Boot error"
-prompt: .asciz " error\r\n"
+prompt:.asciz "\r\n"
.org PRT_OFF,0x90
--
John Baldwin
___
msg_read: .asciz "Read"
-msg_part: .asciz "Boot"
+msg_chs: .asciz "CHS not supported"
+msg_read: .ascii "Read error: "
+read_err: .asciz "XX"
+msg_lba: .ascii "LBA: "
+lba: .asciz "\r\n&q
.asciz "CHS not supported"
+msg_read: .ascii "Read error: "
+read_err: .asciz "XX"
+/*
+msg_lba: .ascii "LBA: "
+lba: .asciz "\r\n"
+ */
+msg_dot: .asciz "."
+msg_part: .asciz "Boot
On Wednesday, June 22, 2011 8:11:36 am Kurt Jaeger wrote:
> Hi!
>
> Can someone have a look at
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=154469
>
> and commit it ? So that it ends up in 8.3 8-} ?
Does the patch from OpenBSD fix the problem for y
for amr devices.
>
> I would like to disable 64-bit addressing for the SATA card, but
> permit it for the SCSI card. Is this possible?
You'd have to hack the driver perhaps to only disable 64-bit DMA for certain
PCI IDs. It probably
On Monday, July 18, 2011 5:06:40 pm Scott Long wrote:
> On Jul 18, 2011, at 12:02 PM, John Baldwin wrote:
> > On Friday, July 15, 2011 6:07:31 pm Mark McConnell wrote:
> >> Dear folks,
> >>
> >> I have two LSI raid cards, one of which (SCSI 320-I) supports
On Monday, July 18, 2011 5:22:26 pm Scott Long wrote:
>
> On Jul 18, 2011, at 3:14 PM, John Baldwin wrote:
>
> > On Monday, July 18, 2011 5:06:40 pm Scott Long wrote:
> >> On Jul 18, 2011, at 12:02 PM, John Baldwin wrote:
> >>> On Friday, July 15,
obed at 2,282 MHz, which is too
> }high. I think that's the problem. Can you please try the attached
> }patch?
>
> Yes, I have seen core freq wobble around for most of the time I've owned it,
> but usually close to 2200.
Possibly try disabling legacy USB
4/amd64/tsc.c (.../stable/8/sys) (revision 224114)
@@ -87,7 +92,7 @@
printf("Calibrating TSC clock ... ");
tscval[0] = rdtsc();
- DELAY(100);
+ DELAY_TSCCAL(100);
tscval[1] = rdtsc();
tsc_freq = tscval[1] - tscval[0];
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
nately the attachment was lost, can you post it to a URL?
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
.
>
>
> Erms Sorry forgot about that.
>
> http://people.freebsd.org/~miwi/90b1.png
Can you get a stack trace?
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Tuesday, August 02, 2011 5:11:58 pm Martin Wilke wrote:
>
> On Aug 3, 2011, at 12:56 AM, John Baldwin wrote:
>
> > On Tuesday, August 02, 2011 8:58:10 am Martin Wilke wrote:
> >>
> >> On Aug 2, 2011, at 6:58 PM, Lystopad Olexandr wrote:
> >>
>
bout 8-STABLE at the moment …)
>
> Thanks,
>
> Jan Mikkelsen
Committed to HEAD, will MFC in a week or so, thanks!
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubs
on 224898)
+++ pucdata.c (working copy)
@@ -862,6 +862,13 @@ const struct puc_cfg puc_pci_devices[] = {
.config_function = puc_config_syba
},
+ {
+ 0x4348, 0x3253, 0x, 0,
+ "WinChipHead Dual Port RS-232",
+ DEFAULT_RCLK,
+ PUC_PORT_2S, 0x10
On Tuesday, August 16, 2011 3:53:17 pm Yuri wrote:
> On 08/16/2011 08:57, John Baldwin wrote:
> > For multiport devices you will want to add an entry to
sys/dev/puc/pucdata.c
> > and use the puc driver instead of patching uart directly. Perhaps this:
>
> John,
>
&g
On Tuesday, August 16, 2011 4:59:42 pm Yuri wrote:
> On 08/16/2011 13:57, John Baldwin wrote:
> > Hmmm, can you get devinfo -v output? Specifically there should be two
> > children of puc0 and they should have extra data specifying what type of
port
> > each child device is.
optional uart puc | uart pccard | uart
pci
dev/uart/uart_bus_scc.coptional uart scc
dev/uart/uart_core.c optional uart
dev/uart/uart_dbg.coptional uart gdb
--
John Baldwin
___
freebsd-stable@fre
Do a backtrace given %eip and %ebp as args
define bt
set $_eip = $arg0
set $_ebp = $arg1
set $i = 0
while ($_ebp != 0 || $_eip != 0)
printf "%2d: pc ", $i
if ($_eip != 0)
x/1i $_eip
else
INTR_TYPE_BIO,
NULL, mfi_intr, sc, &sc->mfi_intr)) {
device_printf(sc->mfi_dev, "Cannot set up interrupt\n");
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Wednesday, August 31, 2011 3:24:12 pm Sergey Kandaurov wrote:
> On 31 August 2011 21:34, John Baldwin wrote:
> > I'd like some folks to test a patch to the mfi(4) driver that may help to
> > address issues several folks have reported. The patch does two things,
> &
On Wednesday, August 31, 2011 5:27:09 pm Sergey Kandaurov wrote:
> On 1 September 2011 01:17, John Baldwin wrote:
> > On Wednesday, August 31, 2011 3:24:12 pm Sergey Kandaurov wrote:
> >> On 31 August 2011 21:34, John Baldwin wrote:
> >> > I'd like some folks t
. Maybe look to see if the
machines were doing something unusual at that time (a cron job, etc.)?
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
...
I boot 8 kernels on machines with a 7 world and back to a 7 kernel all the
time without any issues. Did you upgrade your world to 8 and then try to boot
it with a 7.4 kernel?
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://
On Wednesday, September 07, 2011 10:13:11 am Arnaud Lacombe wrote:
> Hi,
>
> On Wed, Sep 7, 2011 at 9:54 AM, John Baldwin wrote:
> > On Tuesday, September 06, 2011 5:55:09 pm Arnaud Lacombe wrote:
> >> Hi,
> >>
> >> I got a strange boot failure when
/* log string */
asserttoken(sp, KEYWORD);
asserttoken(sp, STRING);
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "f
0;
+ /* Turn off all interrupts */
+ E1000_WRITE_REG(&adapter->hw, E1000_IMC, 0x);
for (int i = 0; i < adapter->num_queues; i++, vector++, que++) {
rid = vector +1;
--
John Baldwin
___
freebsd-stable
rmed in 2010/08/06:
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/Attic/busdma_machdep.c.diff?r1=1.74.2.6;r2=1.74.2.7
>
> I've rolled it back using recent RELENG_6 sources and packet corruption have
> disappeared.
It may be a bug in the rl(4) driver? Perhaps this is a
f a dma tag created in de(4) is TULIP_DATA_PER_DESC bytes.
In Rx path it allocates a new mbuf with m_getcl(9) so the length of
the mbuf is MCLBYTES which is greater than a segment size specified by
the dma tag. This segment size mismatch caused a voluntary panic.
Fix the panic by settting the mbuf len
interface when it encounters an error and from your log it
didn't unwedge even after several resets. In that case there isn't a lot we
can do since we can't talk to the watchdog to turn it off.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
t
wasn't easy to debug unfortunately. :(
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Monday, October 10, 2011 2:38:55 pm Larry Rosenman wrote:
> On 10/10/2011 10:47 AM, John Baldwin wrote:
> > On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote:
> >> Any ideas on which side or what might be broke here?
> >>
> >> ler/MAIL-ARCHIVE/2008/
> >> Node Kind: directory
> >> Schedule: normal
> >> Last Changed Author: brueffer
> >> Last Changed Rev: 226671
> >> Last Changed Date: 2011-10-23 19:37:57 +0100 (Sun, 23 Oct 2011)
> >>
> >>
> >> It's looking like the mfiutil quer
On Tuesday, November 08, 2011 6:39:07 pm Vincent Hoffman wrote:
> On 08/11/2011 22:24, Vincent Hoffman wrote:
> > On 08/11/2011 19:50, John Baldwin wrote:
> >> On Wednesday, November 02, 2011 5:47:38 pm Vincent Hoffman wrote:
> >>> On 28/10/2011 04:14,
On Thursday, November 10, 2011 5:59:28 am Vincent Hoffman wrote:
> On 09/11/2011 14:39, John Baldwin wrote:
> > On Tuesday, November 08, 2011 6:39:07 pm Vincent Hoffman wrote:
> >> On 08/11/2011 22:24, Vincent Hoffman wrote:
> >>> On 08/11/2011 19:50, John Baldwin
w.freebsd.org/~jhb/patches/mfi.patch with the 'pci_alloc_msix' call changed
to
'pci_alloc_msi'.
You forgot to mention what happened from those tests, did any of them work?
--
John Baldwin
___
freebsd-stable@freebsd.org mailing
On Thursday, November 10, 2011 5:59:28 am Vincent Hoffman wrote:
> On 09/11/2011 14:39, John Baldwin wrote:
> > On Tuesday, November 08, 2011 6:39:07 pm Vincent Hoffman wrote:
> >> On 08/11/2011 22:24, Vincent Hoffman wrote:
> >>> On 08/11/2011 19:50, John Baldwin
to be something new in 8.
I suspect it has to do with some of the changes to rtld such that it now
always blocks signals while resolving symbols (or something along those
lines IIRC). It makes throwing exceptions slow as well.
--
John Baldwin
___
freebs
apply this patch, no need to backport the fix in 1.62 as that
fix should not be needed if you are using MSI.
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
don't know if it will help with your performance, but I have some patches
to allow the NFS server to cluster writes. You can try
www.freebsd.org/~jhb/patches/nfs_server_cluster.patch. I've tested it on 8,
but it should probably apply fine to 9.
--
John Baldwin
__
7;ve updated the patch at the URL so it should
now work for the new server. Sorry. :/
--
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
1 - 100 of 961 matches
Mail list logo
