Please test the following diff for brgphy(4), especially for bge(4).
Also for bnx(4) and gem(4), any other NICs if I've forgotten any.
Please send a full dmesg.
Index: brgphy.c
===
RCS file: /cvs/src/sys/dev/mii/brgphy.c,v
retrievin
You are seeing this message in Text format. if your email is in the junk
folder, add the sender email to your address book and move this email into your
inbox to view the HTML version.
On Wed, 10 Jun 2009 12:02:00 -0700
Philip Guenther wrote:
> On Wed, Jun 10, 2009 at 10:49 AM, Thomas Pfaff wrote:
> > On Wed, 10 Jun 2009 09:30:30 -0700
> > Philip Guenther wrote:
> >> It's easy enough to change the code to suppress the error message in
> >> that case ...
> >
> > In case that's
On Wed, Jun 10, 2009 at 10:49 AM, Thomas Pfaff wrote:
> On Wed, 10 Jun 2009 09:30:30 -0700
> Philip Guenther wrote:
>> On Wed, Jun 10, 2009 at 9:17 AM, Thomas Pfaff wrote:
>> > Jun 10 18:09:44 ws hotplugd[5252]: waitpid: No child processes
>>
>> It's easy enough to change the code to suppress the
On Wed, 10 Jun 2009 09:30:30 -0700
Philip Guenther wrote:
> On Wed, Jun 10, 2009 at 9:17 AM, Thomas Pfaff wrote:
> > Jun 10 18:09:44 ws hotplugd[5252]: waitpid: No child processes
>
> It's easy enough to change the code to suppress the error message in
> that case ...
In case that's what you end
On Wed, Jun 10, 2009 at 9:17 AM, Thomas Pfaff wrote:
> I'm getting a lot of "hotplugd[pid]: waitpid: Error 10" (No child
processes)
> when I attach and detach umass(4) devices. This happens almost every time.
>
> Seems hotplugd is getting an extra SIGCHLD from somewhere. I guess this
> issue is p
I'm getting a lot of "hotplugd[pid]: waitpid: Error 10" (No child processes)
when I attach and detach umass(4) devices. This happens almost every time.
Seems hotplugd is getting an extra SIGCHLD from somewhere. I guess this
issue is pretty harmless (only pollutes the logs), but it got me curious
On Wed, Jun 10, 2009 at 06:26:46PM +0800, danielcavan...@aanet.com.au wrote:
> > Please test this ecpecially if your system was one of those that had
> > problems with this patch when it was in the tree before 4.5 release.
>
> i noticed that you've already checked in this diff but i thought i'd se
> Please test this ecpecially if your system was one of those that had
> problems with this patch when it was in the tree before 4.5 release.
i noticed that you've already checked in this diff but i thought i'd send
in my dmesg anyway because it has some strange conflicts in it that
weren't there
> Sending out an initial attempt at implementing C-states for APCI CPUs.
> The C-states are used to implement the CPU idle loop per CPU.
>
> Please send dmesgs of booting using this patch.
it reboots my macbook pro as soon as it hits the acpi stuff. the below
dmesg is from a completely current ker
10 matches
Mail list logo
