On Wed, 26 Jul 2006 13:07:19 -0400
Sven Willenberger <[EMAIL PROTECTED]> wrote:
>
> Feargal Reilly presumably uttered the following on 07/24/06
> 11:48:
> >> > Looking again at dumpfs, it appears to say that this is
> >> > formatted with a block size of 8K, and a fragment size of
> >> > 2K, b
On Thu, Jul 27, 2006 at 02:25:19AM -0400, Mike Jakubik wrote:
> Jiawei Ye wrote:
> >On 7/27/06, Mike Jakubik <[EMAIL PROTECTED]> wrote:
> >>I don't want to spend $50 extra per system, just so i can read the
> >>temperature, and not even use any of the IPMI functions. I need a simple
> >>and scripta
On Wed, Jul 26, 2006 at 02:52:53PM -0400, Mike Jakubik wrote:
> David Duchscher wrote:
> >
> >On Jul 26, 2006, at 11:09 AM, Bruno Ducrot wrote:
> >>Does this one support IPMI?
> >
> >Yes, the Supermicro PDSMi supports the IPMI 2.0 module and I can
> >confirm that it works with the IPMI ported drive
While trying to debug why I couldn't use powerd(8) with two batteries in
my IBM T41 (which seems related to kern/97383), I turned on SW_WATCHDOG
only to get an almost immediate panic after turning it on with
watchdog(8). Sources are from July 10 RELENG_6. Backtrace
http://people.freebsd.org/~erwin/
Jiawei Ye wrote:
On 7/27/06, Mike Jakubik <[EMAIL PROTECTED]> wrote:
I don't want to spend $50 extra per system, just so i can read the
temperature, and not even use any of the IPMI functions. I need a simple
and scriptable way to get the values, acpi sysctls are ideal for this.
What about usin
Roland Smith wrote:
On Wed, Jul 26, 2006 at 02:52:53PM -0400, Mike Jakubik wrote:
David Duchscher wrote:
On Jul 26, 2006, at 11:09 AM, Bruno Ducrot wrote:
Does this one support IPMI?
Yes, the Supermicro PDSMi supports the IPMI 2.0 module and I can
confirm that it works with the IPMI ported dr
On Thu, Jul 27, 2006 at 03:31:56PM +0200, O. Hartmann wrote:
> Roland Smith wrote:
> >On Wed, Jul 26, 2006 at 02:52:53PM -0400, Mike Jakubik wrote:
> >>David Duchscher wrote:
> >>>On Jul 26, 2006, at 11:09 AM, Bruno Ducrot wrote:
> Does this one support IPMI?
> >>>Yes, the Supermicro PDSMi supp
Hello,
Following an interesting discussion about temperature monitoring on
this mailing list, I decided to try this on a machine with the Gigabyte
K8-NF-9 motherboard (the only machine which I can get a /dev/smb0
device on).
It runs 6.1-stable:
[EMAIL PROTECTED] uname -a
FreeBSD kg-fil.kg4.no 6.1-
Bruno Ducrot wrote:
Could you please try (if you have a working smb device)
# smbmsg -p
Well, i don't think its being detected/supported. I tried loading all
the smbus related kernel modules, but no device.
Id Refs AddressSize Name
19 0xc040 2d1624 kernel
21 0xc06d2
Fabian Keil <[EMAIL PROTECTED]> wrote:
> Fabian Keil <[EMAIL PROTECTED]> wrote:
>
> > Peter Thoenen <[EMAIL PROTECTED]> wrote:
> >
> > > To you have pf running? If so can you turn it off for a bit a see
> > > if you still crash. On my box I was getting all sorts of witness
> > > kbd backtraces
Sven Willenberger wrote:
> This was an upgrade from a 5.x system (UFS2); a full fsck did in fact fix the
> problem (for now).
Because of past experience I recommend that you disable
background fsck (it has a switch in /etc/rc.conf). There
are failure scenarios with background fsck that can lead
Feargal Reilly <[EMAIL PROTECTED]> wrote:
> BTW, anybody know what the best method be for double-checking
> df's figures would be? du?
No, du(1) only sees files that have links (i.e. directory
entries). It doesn't see deleted files that occupy space
as long as processes still have them open, wh
Mike Jakubik <[EMAIL PROTECTED]> wrote:
> Bruno Ducrot wrote:
> > Could you please try (if you have a working smb device)
> > # smbmsg -p
>
> Well, i don't think its being detected/supported. I tried loading all
> the smbus related kernel modules, but no device.
>
> Id Refs AddressSi
On Thu, Jul 27, 2006 at 11:09:51AM -0400, Mike Jakubik wrote:
> Bruno Ducrot wrote:
> >Could you please try (if you have a working smb device)
> >
> ># smbmsg -p
> >
>
> Well, i don't think its being detected/supported. I tried loading all
> the smbus related kernel modules, but no device.
>
>
On Thursday 27 July 2006 12:13 pm, Bruno Ducrot wrote:
> It should be ichsmb with a ich7 southbridge IIRC, but there is a
> missing pci id onto sys/ichsmb/ichsmb_pci.c, (it should be
> 0x27da8086).
>
> Maybe the ich7 isn't supported yet. I don't have time to check
> more ATM. I'll look intel spec
Bruno Ducrot wrote:
It should be ichsmb with a ich7 southbridge IIRC, but there is a
missing pci id onto sys/ichsmb/ichsmb_pci.c, (it should be
0x27da8086).
Maybe the ich7 isn't supported yet. I don't have time to check
more ATM. I'll look intel specs tomorrow.
It indeed is a ich7.
[EMAI
Jung-uk Kim wrote:
FYI, see kern/85106:
http://www.freebsd.org/cgi/query-pr.cgi?pr=85106
Great, i will try the patch shortly.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, se
*
*> >* I have "device iwi" in my kernel configuration. Should I remove it and
*> >* use a module instead? Or is this supposed to work?
*
This is from the firmware(9) support code. Add "options firmware" and you
should be fine. You will still need to load the firmware blobs as modules,
but that
Well, here are the patch results.
The controller is detected:
ichsmb0: port 0x1100-0x111f irq
19 at device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
smbus0: on ichsmb0
smb0: on smbus0
However communication does not seem to work:
# smbmsg -p
Probing for devices on /dev/smb0:
Device @0x30: rw
De
[EMAIL PROTECTED]:31:3: class=0x0c0500 card=0x618015d9 chip=0x24d38086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) SMBus Controller'
class= serial bus
subclass = SMBus
2006/7/27, Oliver Fromme <[EMAIL PROTECTED]>:
Mike Jakubik <[EMA
On Wednesday 26 July 2006 18:31, Mike Jakubik wrote:
> Are there any plans to MFC the last few commits to kern_resource.c to
> -STABLE? I have a number of machines which flood the logs with "calcru:
> negative runtime" messages every time w, ps or top is used, so im hoping
> these may fix the is
Have you tried using the firmware from iwi-firmware-kmod, rather than
iwi-firmware. I am using the former on a Thinkpad T42 and it is working ok.
-mark
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
T
John Baldwin wrote:
On Wednesday 26 July 2006 18:31, Mike Jakubik wrote:
Are there any plans to MFC the last few commits to kern_resource.c to
-STABLE? I have a number of machines which flood the logs with "calcru:
negative runtime" messages every time w, ps or top is used, so im hoping
the
Yes, I have. I just did another CVSup, and when I recompiled -kmod it did
indeed put a bunch of .ko files in /build/modules, but a) I still get a
whole bunch of Can't load firmware complaints, and b) it doesn't work. It
goes through the DISCOVER process, but doesn't get any offers it recognizes.
I
> From: "Don Wilde" <[EMAIL PROTECTED]>
> Yes, I have. I just did another CVSup, and when I recompiled -kmod it did
> indeed put a bunch of .ko files in /build/modules, but a) I still get a
> whole bunch of Can't load firmware complaints, and b) it doesn't work. It
> goes through the DISCOVER proce
Hello,
I have a curious problem which at first sight seems related to the
end-June MFC of if_re :
- I 'mount -o nfsv3,intr,noconn,-r=32768,-w=32768
<-stable-server>:/files/bsd /files/bsd '
- (/usr/ports and /usr/src are symlinks to /files/bsd/*) quickly
after a portinstall/portversion e
[Please don't top-post]
On Thursday 27 July 2006 21:01, Don Wilde wrote:
> Yes, I have. I just did another CVSup, and when I recompiled -kmod it did
> indeed put a bunch of .ko files in /build/modules, but a) I still get a
> whole bunch of Can't load firmware complaints, and b) it doesn't work. It
Andrew Thompson wrote:
> On Wed, Jul 26, 2006 at 01:28:12PM -0700, Sam Leffler wrote:
>> Henrik Brix Andersen wrote:
>>> Oh? Sounds interesting, where can I find these patches?
>> The work has always been in perforce.freebsd.org; look in the sam_wifi
>> branch. The code will not hit head until fol
On 7/27/06, Max Laier <[EMAIL PROTECTED]> wrote:
[Please don't top-post]
On Thursday 27 July 2006 21:01, Don Wilde wrote:
> Yes, I have. I just did another CVSup, and when I recompiled -kmod it
did
> indeed put a bunch of .ko files in /build/modules, but a) I still get a
> whole bunch of Can't
Someone mentionned that you can't reach the smbus on ASUS boards.
That's because they turn it off in the BIOS. They turn it on and off as
they
need to read stuff for their SMI (well on some of their boards at least).
you can turn it on again using pciconf. but I forget the exact incantation.
(
On 7/27/06, Don Wilde <[EMAIL PROTECTED]> wrote:
On 7/27/06, Max Laier <[EMAIL PROTECTED]> wrote:
>
> [Please don't top-post]
>
> On Thursday 27 July 2006 21:01, Don Wilde wrote:
> > Yes, I have. I just did another CVSup, and when I recompiled -kmod it
> did
> > indeed put a bunch of .ko files
Sam Leffler wrote:
> Andrew Thompson wrote:
>> On Wed, Jul 26, 2006 at 01:28:12PM -0700, Sam Leffler wrote:
>>> Henrik Brix Andersen wrote:
Oh? Sounds interesting, where can I find these patches?
>>> The work has always been in perforce.freebsd.org; look in the sam_wifi
>>> branch. The code w
On 7/27/06, Don Wilde <[EMAIL PROTECTED]> wrote:
On 7/27/06, Don Wilde <[EMAIL PROTECTED]> wrote:
>
>
> On 7/27/06, Max Laier < [EMAIL PROTECTED]> wrote:
> >
> > [Please don't top-post]
> >
> > On Thursday 27 July 2006 21:01, Don Wilde wrote:
> > > Yes, I have. I just did another CVSup, and whe
It happens that I noticed two odd networking problems recently.
One of them is easily reproducible, and I have it tracked down
to one innocuous-looking line in my /etc/pf.conf. The other
is a problem in a chat server that I run, with a few hundred
people on it, and is much more of a hassle to rep
At 9:07 PM -0400 7/27/06, Garance A Drosihn wrote:
But if I restart pf after adding these lines to pf.conf:
# Allow all outgoing tcp and udp connections and keep state
pass out quick proto { tcp, udp } all keep state
then I have the problem where the second 'lpq' from a remote
host w
At 9:18 PM -0400 7/27/06, Garance A Drosihn wrote:
At 9:07 PM -0400 7/27/06, Garance A Drosihn wrote:
But if I restart pf after adding these lines to pf.conf:
# Allow all outgoing tcp and udp connections and keep state
pass out quick proto { tcp, udp } all keep state
then I have the
Good morning!
On Thu, Jul 27, 2006 at 09:47:42PM +0200, Arno J. Klaassen wrote:
> - I 'mount -o nfsv3,intr,noconn,-r=32768,-w=32768
><-stable-server>:/files/bsd /files/bsd '
Does nfsv3 default to TCP? If not have you tried lowering your
blocksite to, say, 8192?
Regards,
Patrick
--
punkt.d
37 matches
Mail list logo
