schrieb John Baldwin am 17.10.2012 19:19 (localtime):
> Are you using any RAID volumes? The only shutdown handler in mpt that looks
> like it might want interrupts to work is mpt_raid_shutdown(). It needs to use
> polled I/O instead of disabling interrupts I think. Try this:
>
> Index: mpt_raid
On Oct 17, 2012, at 8:58 AM, Guy Helmer wrote:
> On Oct 12, 2012, at 8:54 AM, Guy Helmer wrote:
>
>>
>> On Oct 10, 2012, at 1:37 PM, Alexander V. Chernikov
>> wrote:
>>
>>> On 10.10.2012 00:36, Guy Helmer wrote:
On Oct 8, 2012, at 8:09 AM, Guy Helmer wrote:
> I'm seein
On Wed, Oct 17, 2012 at 4:56 PM, Rainer Duffner wrote:
> I tried to install 9.1-RC2 amd64 on two disks that previously had some
> version of Solaris installed (with grub as boot-manager).
> The installation would always be successful, but it would just boot to
> grub and then sit there.
>
RC1 was
Hi,
I tried to install 9.1-RC2 amd64 on two disks that previously had some version
of Solaris installed (with grub as boot-manager).
The installation would always be successful, but it would just boot to grub and
then sit there.
It's a rather old G1 BL460C blade, but 9.0 installs flawlessly.
I
On Wed, Oct 17, 2012 at 11:38:57PM +0300, Andriy Gapon wrote:
> I've found that on quite a few modern systems the ACPI platform advertises
> some
> useless thermal zones, which always return some hardcoded temperatures.
> E.g. I have Asus P8Z77-M PRO near me and it also reports two thermal zones.
on 17/10/2012 23:15 Derek Kulinski said the following:
> Hello everyone,
>
> I'm unable to read temperature Gigabyte H77-DH3H motherboard. Is that
> motherboard supported or am I doing it incorrectly?
>
> When trying to access hw.acpi.thermal everything appears to be ok, but
> it is not, the syst
Hello everyone,
I'm unable to read temperature Gigabyte H77-DH3H motherboard. Is that
motherboard supported or am I doing it incorrectly?
When trying to access hw.acpi.thermal everything appears to be ok, but
it is not, the system always returns 27,8C and 29,8C which fooled me
initially - the val
-Ursprüngliche Nachricht-
Von: John Baldwin
An: freebsd-stable@freebsd.org
Cc: h.schmalzba...@omnilan.de
Gesendet: 17.10.'12, 20:46
On Tuesday, October 16, 2012 5:24:44 am Harald Schmalzbauer wrote:
Hello,
I have 9.1-RC2 running in an ESXi 5.1 guest.
I use 'lsisas' as virtual SCSI-C
In article
,
wynnwil...@gmail.com writes:
>I've tried the 2.4.4 driver from Intel's site, but it still has the
>same problems. Is a lagg using lacp with the ix interfaces working for
>anyone else?
You bet.
lagg0: flags=8943
metric 0 mtu 9120
options=401bb
ether 04:7d:7b:a5:88:f0
On Tuesday, October 16, 2012 5:24:44 am Harald Schmalzbauer wrote:
> Hello,
>
> I have 9.1-RC2 running in an ESXi 5.1 guest.
> I use 'lsisas' as virtual SCSI-Controller and mpt attaches and finds 1068E.
>
> Everything is working fine until the first 'shutdown -r now':
> The second boot pauses fo
I'm testing out a networking configuration that creates a lagg1
interface that uses lacp with the ix0 and ix1 interfaces. The lagg1
interface I've set up always just reports:
laggport: ix1 flags=18
laggport: ix0 flags=18
Missing the ACTIVE flag that working lagg interfaces report.
The built in ix
On Oct 12, 2012, at 8:54 AM, Guy Helmer wrote:
>
> On Oct 10, 2012, at 1:37 PM, Alexander V. Chernikov
> wrote:
>
>> On 10.10.2012 00:36, Guy Helmer wrote:
>>>
>>> On Oct 8, 2012, at 8:09 AM, Guy Helmer wrote:
>>>
I'm seeing a consistent new kernel panic in FreeBSD 8.3:
I'm not s
12 matches
Mail list logo
