headers
Doug Ambrisko | 1 Apr 2012 01:13

Re: [stable-ish 9] Dell R815 ipmi(4) attach failure

Doug Ambrisko writes:
| Sean Bruno writes:
| | Noting a failure to attach to the onboard IPMI controller with this dell
| | R815.  Not sure what to start poking at and thought I'd though this over
| | here for comment.
| | 
| | -bash-4.2$ dmesg |grep ipmi
| | ipmi0: KCS mode found at io 0xca8 on acpi
| | ipmi1: <IPMI System Interface> on isa0
| | device_attach: ipmi1 attach returned 16
| | ipmi1: <IPMI System Interface> on isa0
| | device_attach: ipmi1 attach returned 16
| | ipmi0: Timed out waiting for GET_DEVICE_ID
| 
| I've run into this recently.  A quick hack to fix it is:
| 
| Index: ipmi.c
| ===================================================================
| RCS file: /cvs/src/sys/dev/ipmi/ipmi.c,v
| retrieving revision 1.14
| diff -u -p -r1.14 ipmi.c
| --- ipmi.c	14 Apr 2011 07:14:22 -0000	1.14
| +++ ipmi.c	31 Mar 2012 19:18:35 -0000
|  <at>  <at>  -695,7 +695,6  <at>  <at>  ipmi_startup(void *arg)
|  	if (error == EWOULDBLOCK) {
|  		device_printf(dev, "Timed out waiting for GET_DEVICE_ID\n");
|  		ipmi_free_request(req);
| -		return;

Correction get rid of the ipmi_free_request as well.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oliver Brandmueller | 1 Apr 2012 12:08
X-Face

Re: 9-STABLE, ZFS, NFS, ggatec - suspected memory leak

Hi,

On Fri, Mar 30, 2012 at 09:02:03PM +0000, Philip M. Gollucci wrote:
> http://lists.freebsd.org/pipermail/freebsd-questions/2012-March/239643.html
> 
> Same issue different thread.  Different software.
> 
> Its not NFS, its ZFS.
> 
> I don't really have a place to try it on 8.2, but my hunch from things
> I've done rather similarly which don't cause tell me its a new issue in
> 9.0, though I won't swear by that.

I'll see, if I can setup a machine running 8 to take some of the 
partitions over - but chances aren't really great. Thanx for the hint to 
you thread.

Also I'll start graphing (or at least logging) some of the higher values 
from vmstat that seems suspicious and ever growing to me to see if I can 
match one of them to the growth rate I see for mir wired mem apart from 
ARC and L2ARC headers.

- Oliver

--

-- 
| Oliver Brandmueller          http://sysadm.in/         ob <at> sysadm.in |
|                        Ich bin das Internet. Sowahr ich Gott helfe. |
Permalink | Reply | 0 comments |
headers
Oliver Brandmueller | 1 Apr 2012 21:31
X-Face

Re: 9-STABLE, ZFS, NFS, ggatec - suspected memory leak

Hi,

On Fri, Mar 30, 2012 at 09:02:03PM +0000, Philip M. Gollucci wrote:
> http://lists.freebsd.org/pipermail/freebsd-questions/2012-March/239643.html
> 
> Same issue different thread.  Different software.
> 
> Its not NFS, its ZFS.
> 
> I don't really have a place to try it on 8.2, but my hunch from things
> I've done rather similarly which don't cause tell me its a new issue in
> 9.0, though I won't swear by that.

Just digging around I find one value ever-growing in vmstat -z and being 
by far the biggest "USED" value:

virgin# while ( 1 )
while? echo -n `date`: ; vmstat -z | fgrep NAMEI | sed 's/  */ /g'
while? sleep 10
while? end
Sun Apr 1 21:26:33 CEST 2012:NAMEI: 1024, 0, 9150656, 1152,288542469, 0, 0
Sun Apr 1 21:26:43 CEST 2012:NAMEI: 1024, 0, 9150877, 1187,288546408, 0, 0
Sun Apr 1 21:26:53 CEST 2012:NAMEI: 1024, 0, 9150966, 1226,288549358, 0, 0
Sun Apr 1 21:27:03 CEST 2012:NAMEI: 1024, 0, 9151079, 1241,288551944, 0, 0
Sun Apr 1 21:27:13 CEST 2012:NAMEI: 1024, 0, 9151264, 1184,288555091, 0, 0
Sun Apr 1 21:27:23 CEST 2012:NAMEI: 1024, 0, 9151338, 1238,288557632, 0, 0
Sun Apr 1 21:27:33 CEST 2012:NAMEI: 1024, 0, 9151488, 1344,288560345, 0, 0
Sun Apr 1 21:27:43 CEST 2012:NAMEI: 1024, 0, 9151610, 1350,288563532, 0, 0
Sun Apr 1 21:27:53 CEST 2012:NAMEI: 1024, 0, 9151765, 1451,288567086, 0, 0
Sun Apr 1 21:28:03 CEST 2012:NAMEI: 1024, 0, 9151935, 1409,288570645, 0, 0
(Continue reading)

Permalink | Reply | 1 comment |
headers
Torfinn Ingolfsen | 1 Apr 2012 23:11
X-Face
Picon
Favicon

Re: FreeBSD 9.0 - GPT boot problems?

On Sat, 24 Mar 2012 17:26:03 +0100
Torfinn Ingolfsen <torfinn.ingolfsen <at> getmail.no> wrote:

> Hi,
> I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470).
> I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and
selecting it from the boot menu on the machine.
> I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme
for 9.0 (GPT).
> The installation was painless (many thanks to all who made it that way), but when I try to boot the machine
from the SSD afterwards, I just get this message from the BIOS:
> "ERROR: No boot disk has been detected or the disk has failed."
> I tried selecting the SSD from the boot menu (via F12) instead (it shows up as "EFI: M4-CT128M4SSD2"), but
got the same message.
> I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice.

Just an update: 
today I connected another disk to the machine (I used a sata-to-usb adapter, but I think that doesn't
matter), this disk is MBR-partitioned,
and the machine boots from this with no problems using the boot menu (via F12).
root <at> kg-vm2# gpart show -p da1
=>       63  117210177    da1  MBR  (55G)
         63   29350692  da1s1  freebsd  (14G)
   29350755   29360079  da1s2  freebsd  [active]  (14G)
   58710834   58499406         - free -  (27G)

The non-working disk looks like this:
root <at> kg-vm2# gpart show -p ada0
=>       34  250069613    ada0  GPT  (119G)
         34        128  ada0p1  freebsd-boot  (64k)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kevin Oberman | 2 Apr 2012 01:48
Picon

Re: FreeBSD 9.0 - GPT boot problems?

On Sun, Apr 1, 2012 at 2:11 PM, Torfinn Ingolfsen
<torfinn.ingolfsen <at> broadpark.no> wrote:
> On Sat, 24 Mar 2012 17:26:03 +0100
> Torfinn Ingolfsen <torfinn.ingolfsen <at> getmail.no> wrote:
>
>> Hi,
>> I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470).
>> I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and
selecting it from the boot menu on the machine.
>> I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme
for 9.0 (GPT).
>> The installation was painless (many thanks to all who made it that way), but when I try to boot the machine
from the SSD afterwards, I just get this message from the BIOS:
>> "ERROR: No boot disk has been detected or the disk has failed."
>> I tried selecting the SSD from the boot menu (via F12) instead (it shows up as "EFI: M4-CT128M4SSD2"), but
got the same message.
>> I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice.
>
> Just an update:
> today I connected another disk to the machine (I used a sata-to-usb adapter, but I think that doesn't
matter), this disk is MBR-partitioned,
> and the machine boots from this with no problems using the boot menu (via F12).
> root <at> kg-vm2# gpart show -p da1
> =>       63  117210177    da1  MBR  (55G)
>         63   29350692  da1s1  freebsd  (14G)
>   29350755   29360079  da1s2  freebsd  [active]  (14G)
>   58710834   58499406         - free -  (27G)
>
> The non-working disk looks like this:
> root <at> kg-vm2# gpart show -p ada0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Philip M. Gollucci | 2 Apr 2012 03:38

Re: 9-STABLE, ZFS, NFS, ggatec - suspected memory leak

On 4/1/12 3:31 PM, Oliver Brandmueller wrote:
> Philip:
>
> Are you using:
>
> - another file system (like UFS/FFS for the system or similar?)
> - ZFS snapshots
> - ZFS send
>
> on the system?
>
> Can you also see the NAMEI growth?

The system is 100% zfs.
zmirror for the os (2 disks)
zmysqlL(zmirror) for mysql logs (2disks +1 cache(ssd))
zmysqlD(raidz2) for mysql data (11 disks + 1cache(ssd) +1zil(ssd))

No snapshots
No zfs send/recv, but there might be in the future.

I have not charted NAMEI growth, but I can try it monday I think.

--

-- 
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci <at> p6m7g8.com) c: 703.336.9354
Member,                           Apache Software Foundation
Committer,                        FreeBSD Foundation
Consultant,                       P6M7G8 Inc.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ken Smith | 2 Apr 2012 05:58
Favicon

8.3-RC2 Available...


The second Release Candidate build of the 8.3-RELEASE release cycle is
now available on the FTP servers for the amd64, i386, pc98, and sparc64
architectures.  The MD5/SHA256 sums are at the bottom of this message.
The ISO images and, for architectures that support it, the memory stick
images are available here:

  ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/8.3/

(or any of the FreeBSD mirror sites).

What will likely be the package sets for the upcoming release have been
placed on the RC2 images.  For the disc1 images due to size issues only
the English documentation package is available.  The memstick images
include the documentation packages for all languages but no other
packages.  The dvd images include all of the documentation packages as
well as enough packages to set up a basic graphical workstation.

Unless a show-stopper caliber problem is found this will be the last
test build of the 8.3-RELEASE cycle.  Some nits that came up as part of
getting RC2 ready have put us off the original schedule.  I just updated
the schedule, available here:

  http://www.freebsd.org/releases/8.3R/schedule.html

to reflect a new target date for starting up the release builds of April
9th, 2012.  The release announcement itself should be three to four days
after the builds start.  It will take a little time for the update I
just made to go live on the Web site.
(Continue reading)

Permalink | Reply | 1 comment |
headers
grarpamp | 2 Apr 2012 08:53
Picon

Re: 8.3-RC2 Available...

Is it right to presume virtualbox package will be available
in 8.3-RELEASE? As it is currently not available in
packages-8.3-release/All or packages-8-stable/All
for i386 or amd64. I will probably make the move to
9.0 stable as it is currently available there for both
and that is the future of things.
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Tom Evans | 2 Apr 2012 11:56

Re: Text relocations in kernel modules

On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao <ryao <at> cs.stonybrook.edu> wrote:
>> There are no security implications, no system resources to be wasted.
>>
>> And if you think there are security implications, then lets see a
>> proof-of-concept.
>
> If I find time to write a proof-of-concept, I promise to publish it
> publicly. Your security team will find out when everyone else does.

Richard, I'm not sure what you are trying to accomplish here. You have
had a clear explanation of why certain things are done in a certain
way in the FreeBSD codebase, and a confirmation that they do not think
it causes any security issues in FreeBSD.

Your response is to threaten to write an exploit against FreeBSD, and
distribute it publicly before disclosing to security <at> .

Are you trying to be an ass? Someone disagrees with you on the
internet, so you throw all the toys out the pram?

Tom
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 23 comments |
headers
John Baldwin | 2 Apr 2012 14:49
Picon
Favicon

Re: [stable-ish 9] Dell R815 ipmi(4) attach failure

On Friday, March 30, 2012 5:30:34 pm Sean Bruno wrote:
> 
> > This is the relevant bits:
> > 
> > Handle 0x2600, DMI type 38, 18 bytes
> > IPMI Device Information
> > 	Interface Type: KCS (Keyboard Control Style)
> > 	Specification Version: 2.0
> > 	I2C Slave Address: 0x10
> > 	NV Storage Device: Not Present
> > 	Base Address: 0x0000000000000CA8 (I/O)
> > 	Register Spacing: 32-bit Boundaries
> > 
> > Note the '32-bit' boundaries.  I think ACPI doesn't support that for its 
> > attachment (well, it does if they specify each port as a separate thing in 
> > _CRS).  Can you get acpidump -d output?
> > 
> 
> Aye, here ya go. 
> 
> http://people.freebsd.org/~sbruno/acpidump_r815.txt

Hmm, that actually looks correct.  Try sabotaging the ACPI attach just for 
testing (i.e. add a 'return (ENXIO)' to the top of the probe routine in 
ipmi_acpi.c) just to see if that makes a difference.  If not, then I think the 
BMC is just broken or your BIOS is lying.

--

-- 
John Baldwin
_______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |

Gmane