On Oct 17, 2003, at 10:25 AM, Nate Lawson wrote:
The problem is USB although ACPI magnifies it. USB devices can
generate
wake events. In my current testing of a new acpi_cpu driver, I've
found
that just having the USB bus enabled in the kernel (with no devices
attached) causes it to generate a
On Thursday, July 3, 2003, at 10:59 AM, Julian Elischer wrote:
It makes sense to export the values set by tunables into the sysctl
MIB, but by their
very nature they're not suitable for conversion to sysctls.
= Mike
So is what you are saying...
"tuneables should be converted at boot to read-onl
On Thursday, July 3, 2003, at 10:28 AM, Nate Lawson wrote:
I personally think that all tunable should be read-only (or rw if
possible) sysctls...
I'm still not sure why we have both mechanisms. Perhaps a useful
approach
would be to sweep the tree for tunables and change them to sysctls with
appr
On Wednesday, December 11, 2002, at 12:33 AM, User Takawata wrote:
If this mobo will always
require a custom .AML file I want to commit the one I have and start a
table of mobo/BIOS's and the custom .AML files we offer.
You will need version information of the bytecode.
Wasn't someone alread
On Sunday, November 10, 2002, at 12:19 AM, Terry Lambert wrote:
Michael Smith wrote:
On Saturday, November 9, 2002, at 04:12 AM, Terry Lambert wrote:
Repeat: #1 is power profiles
I don't see why this requires an 'acpid'. You want a control tool,
sure, but power policy is not
On Saturday, November 9, 2002, at 04:12 AM, Terry Lambert wrote:
Repeat: #1 is power profiles
I don't see why this requires an 'acpid'. You want a control tool,
sure, but power policy is not something that needs a daemon.
o replacing devices in a multipurpose bay, which may take one
of a n
On Friday, November 8, 2002, at 11:42 PM, Frode Nordahl wrote:
Why do you need an acpid?
misc stuff
That's not going to get you anywhere.
instruct dhclient to get a new lease on resume (maybe free it on
sleep),
try to configure wlan if no link detected on ethernet etc.
This doesn't warran
Heh, finally someone that's actually trying to fix this. 8)
The "right" thing is going to be to fix the MTRR code to preserve the
extra MTRR bits; I've tried a few times to get some documentation on what
these other bits mean without any luck.
You'll need to hide these bits from the layers ab
> For ISA, this ends up being a 16M limit; I think the 2G limit
> on Alpha is because the limit is 32 bits, but there is some
> signed math that should be unsigned.
No, Terry, it has to do with the PCI bridge's translation mapping
hardware, and if we supported it (which we don't seem to) then th
> > > Should I hold onto this card or should I suck it up and get
> > > a 3ware online somewhere?
>
> Be a man and buy a SCSI RAID controller. The Adaptec 5400S is
> all you'll ever need =-)
You will tell me where I can buy disks for $1/GB and hotswap carriers at
$20 a pop, right? 8)
--
To a
> Yeah, you do. I fully understood _that_ context; I think Mike
> was talking about other context. It's pretty clear to me that
> ranges ought to be per bridge chipset, rather than global... I
> thought that that was what the option was working around: that
> they were not.
I can't imagine how
> What's the basis of the assumption that the I/O range is
> unsupported in the first place, and why isn't it true for this
> bridge chip, if it's a valid assumption for others?
The information was provided in the debugging output and code that Alfred
supplied in earlier messages. The short ans
>
> This avoids a panic when probing, there's probably still some
> badness going on with make/destroy dev in this driver.
Pending commentary from Scott, I think you should commit this.
> Should I hold onto this card or should I suck it up and get
> a 3ware online somewhere?
By all means use i
> Is there a way that we can "fix" this without blindly allowing bad
> bus_alloc_resources ? I'm a bit confused as to wheather our code is
> behaving oddly or if it's just the device violating some spec...
Yes, our code is busted; it should check both ranges and get the
arithmetic right. I bel
> I just got the Adaptec 4 port IDE raid card 2400A.
>
> It doesn't probe right:
> asr0: could not map memory
>
> I added some debug printouts to the asr driver and pci code.
>
> asr0: mem 0xf600-0xf7ff irq 5 at device 5
> .1 on pci2
> pcib2: device asr0 requested unsupported memory ra
It would be good to see where this actually is when it traps; DDB would
help.
(Sorry if this has already been dealt with)
> For a couple of days, I have been consistent panics whenever I mount
> an NFS filesystem on a newly made -CURRENT. Things seem to work fine
> when NFS is actually built i
Please don't file a PR against something like this in -current until
you've established that it's not a transient problem.
In this case, it looks like a possibly corrupt kernel; you're dying very
early on after jumping into the kernel.
> On Mon, Mar 25, 2002 at 06:05:14AM -0800, Hiten Pandya
Folks, the "autoload failed" message is just telling you that you have
ACPI, but there is no ACPI KLD on the floppy.
It has absolutely nothing whatsoever to do with your problem. By the
sound of it, you've got a corrupted floppy image.
--
To announce that there must be no criticism of the p
Trim your cc's.
> I'm sorry, but simply not liking the idea of someone else doing a
> particular optimization now verses later is not a good enough reason
> to require that 40+ hours worth of work be thrown away when that
> other person has stated, repeatedly, that he will suppor
Just a quick note to let people know that the 3ware driver twe(4) driver
has been updated to deal with 3ware's latest firmware releases.
These changes have been tested for a couple of weeks now.
One other important note for owners of 7xxx series controllers; the 7.4
firmware update is due out
> In message: <[EMAIL PROTECTED]>
> Michael Smith <[EMAIL PROTECTED]> writes:
> : No. This would mean that sio(4) will attach to any IrDa port and
> : preclude an IrDa-specific driver from doing so.
> :
> : If any variation of this patch is comm
> > > So try adding
> > > {0x10f0a34d, NULL}
> > > to sio_ids in /sys/dev/sio/sio_isa.c
> >
> > It works:
> >
> > sio0 port 0x3f8-0x3ff irq 4 on acpi0
> > sio0: type 16550A
> > sio1 port 0x280-0x287,0x2f8-0x2ff irq 3 on acpi0
> > sio1: type 16550A
>
> I have tried this patch for Sony VAIO PC
> This is a multi-part message in MIME format.
> --741846253D1D9002AE8EAD96
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> zhuravlev alexander wrote:
> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> > unknown: can't assign resources
>
> Wow! This did away with the once-a-minute error messages from Notify()s
> on processor objects on my laptop.
>
> However, I am now getting frequent panics from from a GIANT_REQUIRED
> assertion in kmem_malloc(). kmem_malloc() gets called via malloc() from
> AcpiOsAllocate(), without Giant loc
--- Blind-Carbon-Copy
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
To: [EMAIL PROTECTED]
Subject: 3ware 6xxx-series controllers and 6.9 firmware
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 18 Feb 2002 03:35:32 -0800
From: Michael Smith <[EMAIL PROTEC
> >:I would like to see "the PIIX problem" caught on camera, personally.
> >:We're aware of one errata for it already, and we work around it. If
> >:there's another problem, or ideally if someone has some relatively quick
> >:code to test it, that would be much better.
> >
> >Holy shit.
> Ok, here is a patch that executes a brute-force solution to the
> asynchronous counter problem.
>
> Basically it figures out a mask and then the timer code loops until two
> masked reads yield the same value, guarenteeing that we haven't caught
> the timer during a carry.
>
>
> :I would like to see "the PIIX problem" caught on camera, personally.
> :We're aware of one errata for it already, and we work around it. If
> :there's another problem, or ideally if someone has some relatively quick
> :code to test it, that would be much better.
>
> Holy shit. We
> If this patch cures the PIIX problem, something I'm not at all convinced
> about, it should go in, if not only the comment should go in.
I would like to see "the PIIX problem" caught on camera, personally.
We're aware of one errata for it already, and we work around it. If
there's another p
29 matches
Mail list logo
