Andrew Snow wrote:
Another thing that I believe would help: Voting on PRs.
Currently a maintainer has no idea if a PR is due to one guy's flakey
hardware or if 50 people have had the same problem and are waiting for a
fix.
For each major problem report, there are probably many people who tr
Another thing that I believe would help: Voting on PRs.
Currently a maintainer has no idea if a PR is due to one guy's flakey
hardware or if 50 people have had the same problem and are waiting for a
fix.
For each major problem report, there are probably many people who tried
FreeBSD on part
On Sep 17, 2008, at 4:33 PM, Robert Watson wrote:
An important factor is whether or not we consider the release a
highly maintainable release, and while we have intuitions at the
time of release, that's something we can only learn in the first
couple of months after it's in production. I do
Hello,
> Well, bus_alloc_resource() will allocate resources for the BAR and update the
> BAR for you, the question is if you need to hardcode the range to
> bus_alloc_resource() or not.
It is necessary for a pci device to set the BAR, if the device
would use memory or I/O space, isn't it? I d
On Wed, 17 Sep 2008, Jo Rhett wrote:
On Mon, 15 Sep 2008, Jo Rhett wrote:
Robert, I'd like to point out to you that when I complained about 6.2's
accelerated EoL, I was soundly boxed around the ears and told that I
should have been paying attention to the projected EoL date when we
decided t
On Mon, 15 Sep 2008, Jo Rhett wrote:
Robert, I'd like to point out to you that when I complained about
6.2's accelerated EoL, I was soundly boxed around the ears and told
that I should have been paying attention to the projected EoL date
when we decided to roll out 6.2 across the business.
On Sep 16, 2008, at 12:38 AM, Matthew Seaman wrote:
On 'long term support of release branches' -- a volunteer project is
always
going to struggle to provide this without some form of income to
support the
necessary hardware and personnel resources needed. Or in other
words, if
FreeBSD users
On Tue, Sep 16, 2008 at 04:30:26PM +1000, Andrew Snow wrote:
I think FreeBSD is getting in a difficult position now because
there's
so much cool new stuff being shoe-horned in, but without the
necessary
volume of contributors to back it up with testing and bug fixes.
On Sep 15, 2008, at 11:
On Wednesday 17 September 2008 11:04:33 am Michel Talon wrote:
> Hello,
>
> when testing FreeBSD-7.1-BETA i discovered that the floppy disk
> controller doesn't work correctly. Trying to format a floppy (perhaps
> with bad blocks) i get:
> Processing fdformat: ioctl(FD_FORM): Device not configured
Hi!
I got curious in dtrace, and after mr's sys/amd64/amd64/trap.c
commit (r183050, thanx! :) I was able to build a kernel that could
kldload dtraceall on 7-stable amd64, but trying even simple things like
dtrace -n tick-1sec
only runs for a short time, or not at all, ending with $subject
On Wed, Sep 17, 2008 at 01:03:46PM -0400, Ed Maste wrote:
> On Wed, Sep 17, 2008 at 09:25:37AM -0700, Jeremy Chadwick wrote:
>
> > On Wed, Sep 17, 2008 at 07:36:46AM -0400, Stephen Clark wrote:
> > > I am trying to get a crash dump but am unable to with FreeBSD
> > > 6.3-RELEASE-p2
> > >
> > > [.
| By Richard Arends <[EMAIL PROTECTED]>
| [ 2008-09-17 07:05 +0200 ]
> On Tue, Sep 16, 2008 at 09:24:26PM -0700, Jeremy Chadwick wrote:
>
> > Since you're still in the market: I've heard wonderful things about any
> > of the USB serial adapters that use the
John Baldwin wrote:
> Oliver Fromme wrote:
> > [...]
> > Now i'm wondering: Has the ACPI blacklist been removed
> > intentionally, or is this a regression? Certainly I did
> > not find any mentioning of it in UPDATING or anywhere
> > else.
>
> This is a regression. Try this fix:
>
On Wednesday 17 September 2008 07:47:18 am Oliver Fromme wrote:
> Hello,
>
> I have recently updated a machine to 7-stable.
> ACPI doesn't seem to work correctly on this machine.
> With earlier versions of FreeBSD (including the latest
> RELENG_6), I got this line in dmesg:
>
>ACPI disabled b
On Tuesday 16 September 2008 10:58:54 pm KAHO Toshikazu wrote:
> Hello,
>
> I am sorry to mistake copying message-id and break mail thread.
>
> >> I tried looking for this device in the DSDT, I don't see anything which
> >> obviously resembles it. The equivalent Linux driver has a means of
> >>
On Wed, Sep 17, 2008 at 09:25:37AM -0700, Jeremy Chadwick wrote:
> On Wed, Sep 17, 2008 at 07:36:46AM -0400, Stephen Clark wrote:
> > I am trying to get a crash dump but am unable to with FreeBSD 6.3-RELEASE-p2
> >
> > [...]
> > reboot -d
> > ...
> > dumping 255M 2 chunks
> >
> >
> > Then nothing
On Wed, Sep 17, 2008 at 07:36:46AM -0400, Stephen Clark wrote:
> I am trying to get a crash dump but am unable to with FreeBSD 6.3-RELEASE-p2
>
> /etc/defaults/rc.conf
> dumpdir="/var/crash"# Directory where crash dumps are to be stored
> savecore_flags="" # Used if dumpdev is enabled abo
On Wed, Sep 17, 2008 at 03:30:45PM +0400, Dmitry Morozovsky wrote:
> Colleagues,
>
> 3 of 4 times this machine failed to boot, panicing somewhere in late kernel
> initialization phase (before /sbin/init is executed)
>
> {snip}
We have many (specifically, 6) PDSMI+ (not PDSMI) boxes which do not
On Wed, 17 Sep 2008, Dmitry Morozovsky wrote:
DM> Colleagues,
DM>
DM> 3 of 4 times this machine failed to boot, panicing somewhere in late kernel
DM> initialization phase (before /sbin/init is executed)
DM>
DM> I have serial console and KDB enabled, so can do experiments.
Update:
booting GENE
On September 17, 2008, Robert Watson wrote:
> On Mon, 15 Sep 2008, Norbert Papke wrote:
> > With WITNESS enabled, I now experience panics and could not follow your
> > instructions. There is no core dump. The following gets logged to
> > /var/log/messages:
> >
> > shared lock of (rw) udpinp @ /us
Hello,
when testing FreeBSD-7.1-BETA i discovered that the floppy disk
controller doesn't work correctly. Trying to format a floppy (perhaps
with bad blocks) i get:
Processing fdformat: ioctl(FD_FORM): Device not configured
instead of the normal E letter. I then checked the same problem is
present
Hello List,
I am trying to get a crash dump but am unable to with FreeBSD 6.3-RELEASE-p2
/etc/defaults/rc.conf
dumpdir="/var/crash"# Directory where crash dumps are to be stored
savecore_flags="" # Used if dumpdev is enabled above, and present.
Z2873# sysctl -a |grep physmem
hw.physme
Hello,
I have recently updated a machine to 7-stable.
ACPI doesn't seem to work correctly on this machine.
With earlier versions of FreeBSD (including the latest
RELENG_6), I got this line in dmesg:
ACPI disabled by blacklist. Contact your BIOS vendor.
And everything was fine. The box runs
Colleagues,
3 of 4 times this machine failed to boot, panicing somewhere in late kernel
initialization phase (before /sbin/init is executed)
I have serial console and KDB enabled, so can do experiments.
Last two crashes:
Fatal trap 12: page fault while in kernel mode
fault virtual address
On Mon, 15 Sep 2008, Norbert Papke wrote:
With WITNESS enabled, I now experience panics and could not follow your
instructions. There is no core dump. The following gets logged to
/var/log/messages:
shared lock of (rw) udpinp @ /usr/src/sys/netinet/udp_usrreq.c:864
while exclusively locked
Joseph Olatt wrote:
> Gavin Atkinson wrote:
> > Out of interest, what motherboard is this on?
>
> Is there a way to find out the motherboard details without
> opening up the box?
Yes. Install and run dmidecode from ports/sysutils/dmidecode.
Best regards
Oliver
--
Oliver Fromme, secnet
26 matches
Mail list logo
