Hello,
I tested the PCI_INTR_FIXUP option. Unfortunately, it didn't help.
Is the Perc H330 officially supported? If so, the problem must be with my
hardware combination. If the H330 isn't officially supported, I've lost
hope of getting the server to run with NetBSD.
Thank you for your effor
hello. So, if I understand you correctly, after the BIOS change, the
system errors out
whether it's booted cold or warm? And, the errors are the same, that is, yu're
getting cmd
timeouts?
So, what are the BIOS options related to APIC handling?
Also, you might try build
Hello,
I changed the BIOS settings for the APIC. Now the error occurs much
earlier. The timeout messages appear before the INIT scripts begin
processing. After that, the boot process stops at this point.
I also tested the current kernel. The behavior is the same as with version
10.1.
Than
hello. One thing I notice in your boot messages is the following:
x2APIC available but disabled by DMAR table
I'm not sure what this is trying to tell you, but you might investigate to see
why that apic is
not fully enabled. What are the settings options in your BIOS menus,
particularly
On Tue, 24 Jun 2025, Christoph Badura wrote:
On Sun, Jun 22, 2025 at 09:32:30AM +0200, 6b...@6bone.informatik.uni-leipzig.de
wrote:
I've enabled debugging. Unfortunately, I'm stuck with the analysis.
The last crash happened last night. However, when the problem
occurred, write operations on
On Mon, 23 Jun 2025, Greg A. Woods wrote:
At Mon, 23 Jun 2025 11:24:14 -0700, Brian Buhrow wrote:
Subject: Re: Re: Re: problems with netbsd-10 and PERC controllers
3. Have yu brought up the Perc's RAID configuration menu to confirm
the raid sets are healthy and that you're n
On Tue, Jun 24, 2025 at 09:45:34AM +0200, Christoph Badura wrote:
> On Tue, Jun 24, 2025 at 09:42:50AM +0200, Christoph Badura wrote:
> > There are bits of useful information missing:
> >
> > You could show us the relevant autoconfiguration messages for the system.
> > You could upload the entire
On Tue, Jun 24, 2025 at 09:42:50AM +0200, Christoph Badura wrote:
> There are bits of useful information missing:
>
> You could show us the relevant autoconfiguration messages for the system.
> You could upload the entire dmesg output to dmesgd.
> What system exactly are you using?
> Does the mach
On Sun, Jun 22, 2025 at 09:32:30AM +0200, 6b...@6bone.informatik.uni-leipzig.de
wrote:
> I've enabled debugging. Unfortunately, I'm stuck with the analysis.
> The last crash happened last night. However, when the problem
> occurred, write operations on the system were no longer possible.
> So, the
hello. The information that a warm reset doesn't come up clean is
useful information.
In looking at mfii.c, it looks like there are two possible sources of the
problem. The first
is the one I've mentioned earlier, that somehow, interrupt handling gets
mangled during
operations and in
Hello,
I've enabled debugging. Unfortunately, I'm stuck with the analysis. The
last crash happened last night. However, when the problem occurred, write
operations on the system were no longer possible. So, there are no records
of the debug output :-(
Thank you for your efforts
Regards
Uwe
On Sun, 22 Jun 2025, Brian Buhrow wrote:
Hello. Given the word that this machine previously ran Linux and not
oldeer versions of
NetBSD, I'm more convinced you have an incompatibility between the the machines
implementation
of MSI/MSIX interrupt handling and NetBSD's implementation
Hello. Given the word that this machine previously ran Linux and not
oldeer versions of
NetBSD, I'm more convinced you have an incompatibility between the the machines
implementation
of MSI/MSIX interrupt handling and NetBSD's implementation. Some suggestions
of things to try
to see if
> I'm stuck with the analysis. The last crash happened last night.
I am sure Leipzig is currently experiencing the same series of hot
days we are. Your failures appear to correlate.
They last time one of my (mostly idle) systems would wegde up during
disk operations only a walk into the datacent
Hello,
I'll try to answer your questions. The server was previously running on
Linux. Therefore, I can't say how it behaves with older NetBSD versions. I
only know that there were no problems with Linux. Therefore, I assume
there are no hardware errors.
The Perc H330 is an internal controlle
15 matches
Mail list logo
