On Fri, Mar 12, 2010 at 2:55 PM, Joel Sing wrote:
> The issue has already been investigated and kettenis@ committed a fix during
> n2k10. However, the fix that allowed these servers to work happened to break
> other systems that were previously working, hence the change was backed out.
> I believe
On Fri, Mar 12, 2010 at 1:55 PM, Joel Sing wrote:
> The issue has already been investigated and kettenis@ committed a fix during
> n2k10. However, the fix that allowed these servers to work happened to break
> other systems that were previously working, hence the change was backed out.
> I believe
On Friday 12 March 2010, FRLinux wrote:
> Hey guys, sent an acpi dump with dmesg info a couple of months ago to
> this list hoping the developers might be able to fix this. Just
> letting you know that 4.7 snapshot still reboots the box unless you
> disable ppb*. Any way i can help?
The issue has
On Thu, Mar 11, 2010 at 3:00 PM, FRLinux wrote:
> Hey guys, sent an acpi dump with dmesg info a couple of months ago to
> this list hoping the developers might be able to fix this. Just
> letting you know that 4.7 snapshot still reboots the box unless you
> disable ppb*. Any way i can help?
Would
Hey guys, sent an acpi dump with dmesg info a couple of months ago to
this list hoping the developers might be able to fix this. Just
letting you know that 4.7 snapshot still reboots the box unless you
disable ppb*. Any way i can help?
Cheers,
Steph
On Wed, Jan 13, 2010 at 4:28 PM, Ted Unangst wrote:
> The reason disabling the last line /sometimes/ works is that if it's a
> bus, you then prevent probing of all the attached devices.
Sorry, my formulation was not the most accurate. I meant that in my
case, when disabling the whole ppb*, it is
On Tue, Jan 12, 2010 at 3:26 PM, FRLinux wrote:
>> However, it hangs later on just after printing out following lines:
>>
>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>> mem address conflict 0xff00/0x1000
>> pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x0c
>> "Intel E7520 E
2010/1/12 FRLinux :
> On Tue, Jan 12, 2010 at 6:05 PM, Marcin wrote:
>> However, it hangs later on just after printing out following lines:
>>
>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>> mem address conflict 0xff00/0x1000
>> pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0
On Tue, Jan 12, 2010 at 6:05 PM, Marcin wrote:
> I tried current - the good news is the problem with freeze at startup is
gone
> - kernel boots immediately.
>
> However, it hangs later on just after printing out following lines:
>
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> mem addres
2010/1/12 Kenneth R Westerback :
> Please try -current as of today (Jan 13, 2010 Melbourne time), there were
> number of significant fixes committed in the last couple of days.
Hi,
I tried current - the good news is the problem with freeze at startup is gone
- kernel boots immediately.
However,
On Tue, Jan 12, 2010 at 05:44:57AM -0600, J.D. Bronson wrote:
> I just joined this thread today, but had a similar issue with an IBM
> 305 machine.
>
> On 4.5, it would randomly just shut down. No reason. Nothing in any
> logs, it was as if the power was pulled.
>
> I have 2 identical IBM 305 mac
I would try a -current but the 4.6-STABLE I have in use on Machine #1
has been running fine and I am not seeing reboots or unexpected
shutdowns as the OP has been experiencing.
The Machine #2 will only run -current and I can't figure that out when
they are identical. I suspect 4.7 will run fin
I just joined this thread today, but had a similar issue with an IBM 305
machine.
On 4.5, it would randomly just shut down. No reason. Nothing in any
logs, it was as if the power was pulled.
I have 2 identical IBM 305 machines and it was happening on both, so
that technically ruled out any s
On Mon, Jan 11, 2010 at 10:03 PM, Marcin wrote:
> I ran into the same issue with IBM x336 while trying to launch 4.6
> after installation.
> I checked 4.6 ISO and -current, neither of them booted successfully.
>
> My x336s are fairly standard machines (4GB of RAM, 2x3.2GHz Xeon, 2x73GB SCSI)
> how
2009/10/22 FRLinux :
> I have several IBM x series 336 servers and attempted to upgrade them
> today.
(...)
> When applied and i issued a reboot, the server rebooted after locking
> at this line:
>
> "Intel E7520 Error Reporting" rev 0x0c at pci0 dev 0 function 1 not configured
> ppb0 at pci0 dev 2
*bump*
On Thu, Nov 5, 2009 at 3:51 PM, FRLinux wrote:
> On Mon, Nov 2, 2009 at 5:07 PM, FRLinux wrote:
>> Cannot really send an acpidump, as it reboots the server...
>
> Here is the acpidump from 4.5 running on the same server:
>
> # acpidump
> /*
> RSD PTR: Checksum=85, OEMID=IBM, RsdtAddress=0
On Fri, Oct 30, 2009 at 4:20 PM, Marco Peereboom wrote:
> no. kettenis needs to see a pci -v -xx of this machine. Send in the
> acpidump -o as well. I can't volunteer his time so he'll look at it
> whenever he'll look at it.
# pcidump -v -xx
Domain /dev/pci0:
0:0:0: Intel E7520 Host
0
no. kettenis needs to see a pci -v -xx of this machine. Send in the
acpidump -o as well. I can't volunteer his time so he'll look at it
whenever he'll look at it.
On Fri, Oct 30, 2009 at 04:08:43PM +, FRLinux wrote:
> On Fri, Oct 30, 2009 at 1:48 PM, Marco Peereboom wrote:
> > Run a -curre
On Fri, Oct 30, 2009 at 1:48 PM, Marco Peereboom wrote:
> Run a -current system. This could be a pci resource allocation issue.
Hello again,
It surely is, even leaving acpi enabled, the only way to allow the
machine to boot is to disable ppb*
It affect all the IBM Xseries 336 that I have.
I j
Run a -current system. This could be a pci resource allocation issue.
On Fri, Oct 30, 2009 at 11:27:10AM +, FRLinux wrote:
> On Thu, Oct 29, 2009 at 7:11 PM, Joachim Schipper
> wrote:
> >> Hello, the problem is related to the network cards alright. Disabling
> >> ppb* allows it to boot. My p
On Thu, Oct 29, 2009 at 7:11 PM, Joachim Schipper
wrote:
>> Hello, the problem is related to the network cards alright. Disabling
>> ppb* allows it to boot. My problem is that even if I disable a card in
>> the bios, i cannot boot the system. I tried to disable ppb2 but it
>> doesn't seem to take
On Thu, Oct 29, 2009 at 06:06:03PM +, FRLinux wrote:
> On Wed, Oct 28, 2009 at 4:13 PM, Joachim Schipper
> wrote:
> > Just to check the obvious: did you disable acpi when booting after the
> > install? (And did you try both bsd and bsd.mp? The latter is less like
> > the install kernel than th
On Wed, Oct 28, 2009 at 4:13 PM, Joachim Schipper
wrote:
> Just to check the obvious: did you disable acpi when booting after the
> install? (And did you try both bsd and bsd.mp? The latter is less like
> the install kernel than the former.)
>
Hello, the problem is related to the network cards a
On Wed, Oct 28, 2009 at 03:36:34PM +, FRLinux wrote:
> On Mon, Oct 26, 2009 at 9:03 PM, Marco Peereboom wrote:
> > Does it have broadcom nics?
> >
> > if do disable those and try again.
>
> Hello still the same problem. Out of curiosity, tried to boot off the
> amd64 CD but failing the same.
On 28 October 2009 c. 18:36:34 FRLinux wrote:
> On Mon, Oct 26, 2009 at 9:03 PM, Marco Peereboom
wrote:
> As I asked, can anyone tell me which flags are disabled during the
> install ? (disabling acpi during install was enough to get the system
> installed but then it won't boot...)
You can just
On Mon, Oct 26, 2009 at 9:03 PM, Marco Peereboom wrote:
> Does it have broadcom nics?
>
> if do disable those and try again.
Hello still the same problem. Out of curiosity, tried to boot off the
amd64 CD but failing the same. Suggestions?
As I asked, can anyone tell me which flags are disabled d
On Mon, Oct 26, 2009 at 9:03 PM, Marco Peereboom wrote:
> Does it have broadcom nics?
>
> if do disable those and try again.
I do. I'll try that tomorrow.
On a related matter, can anyone tell me which switches are disabled
during an OpenBSD install (using the official ISO) ? That would help
me n
Does it have broadcom nics?
if do disable those and try again.
On Mon, Oct 26, 2009 at 08:24:51PM +, FRLinux wrote:
> On Fri, Oct 23, 2009 at 12:28 PM, FRLinux wrote:
> > 2009/10/23 Vadim Zhukov :
> >> My $0.02: try to disable intagp, agp, inteldrm, drm devices.
> >
> > Thanks, tried disabli
On Fri, Oct 23, 2009 at 12:28 PM, FRLinux wrote:
> 2009/10/23 Vadim Zhukov :
>> My $0.02: try to disable intagp, agp, inteldrm, drm devices.
>
> Thanks, tried disabling a fair few based on successful boot log but
> still fails after wsdisplay0
>
> Also, as pointed out, before 4.6, it just works.
2009/10/23 Vadim Zhukov :
> My $0.02: try to disable intagp, agp, inteldrm, drm devices.
Thanks, tried disabling a fair few based on successful boot log but
still fails after wsdisplay0
Also, as pointed out, before 4.6, it just works.
Cheers,
Steph
On 23 October 2009 c. 14:34:49 FRLinux wrote:
> On Fri, Oct 23, 2009 at 11:08 AM, FRLinux wrote:
> > Hello
> >
> > I have generated a verbose trace using a com port on the server,
> > this is by booting the official 4.6 i386 install CD.
>
> Alright, disabling ACPI allows me to install the system,
On Fri, Oct 23, 2009 at 11:08 AM, FRLinux wrote:
> Hello
>
> I have generated a verbose trace using a com port on the server, this
> is by booting the official 4.6 i386 install CD.
Alright, disabling ACPI allows me to install the system, but then on
reboot, even disabling ACPI makes the system re
Hello
I have generated a verbose trace using a com port on the server, this
is by booting the official 4.6 i386 install CD.
boot> boot -c
booting cd0a:/4.6/i386/bsd.rd: 5651156+913072 [52+211008+196339]=0x6a6260
entry point at 0x200120
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regen
On Thu, Oct 22, 2009 at 9:20 PM, wrote:
> I've seen the same on IBM x346 - install goes fine, reboot, and then it does
> not
> want to play nice.
Installs and boot of all previous versions up until 4.6 work. I rolled
back the server to 4.5 home release and it is back and running.
Quoting FRLinux :
> Hello,
>
> I have several IBM x series 336 servers and attempted to upgrade them
> today. My usual way is to use a build server which makes a release for
> my servers. It went well on that server (which is the only one not
> being an IBM x336, that will teach me...) so decided
35 matches
Mail list logo
