On Thu, 29 Dec 2011 07:29:51 -0800, walt wrote:
> This change appears to be somewhere in userland, though, not in the kernel
> per se. I copied the kernel .config file from my working amd64 machine to
> the 'broken' ~amd64 machine and recompiled the kernel.
>
> No improvement. I had to enable t
On 12/29/2011 02:09 AM, Mick wrote:
On Thursday 29 Dec 2011 07:10:19 Lubos Kolouch wrote:
walt, Wed, 28 Dec 2011 17:01:59 -0800:
Sometime in the last month or so (when I wasn't looking) my ~x86 and
~amd64 machines quit working when I try to run wireshark or tcpdump,
etc, but I don't know exactl
On Thursday 29 Dec 2011 07:10:19 Lubos Kolouch wrote:
> walt, Wed, 28 Dec 2011 17:01:59 -0800:
> > Sometime in the last month or so (when I wasn't looking) my ~x86 and
> > ~amd64 machines quit working when I try to run wireshark or tcpdump,
> > etc, but I don't know exactly when or why. (My amd64
walt, Wed, 28 Dec 2011 17:01:59 -0800:
> Sometime in the last month or so (when I wasn't looking) my ~x86 and
> ~amd64 machines quit working when I try to run wireshark or tcpdump,
> etc, but I don't know exactly when or why. (My amd64 machine still
> sniffs packets normally.)
>
> I get this sam
4 matches
Mail list logo
