On 3/10/21 4:48 PM, Hans de Goede wrote:
Hi,
On 3/10/21 9:55 PM, Filipe Laíns wrote:
On Wed, 2021-03-10 at 15:24 -0500, Mark Hounschell wrote:
That is correct, I don't have any buttons bound to keyboard events. With
the original patch the G4(forward) and G5(Backward) buttons work in a
browser
Hi,
On 3/10/21 9:55 PM, Filipe Laíns wrote:
> On Wed, 2021-03-10 at 15:24 -0500, Mark Hounschell wrote:
>>
>> That is correct, I don't have any buttons bound to keyboard events. With
>> the original patch the G4(forward) and G5(Backward) buttons work in a
>> browser. I guess G7, G8, and G9 butto
On Wed, 2021-03-10 at 15:24 -0500, Mark Hounschell wrote:
>
> That is correct, I don't have any buttons bound to keyboard events. With
> the original patch the G4(forward) and G5(Backward) buttons work in a
> browser. I guess G7, G8, and G9 buttons are programmable to keyboard events?
>
> Howev
On 3/10/21 3:24 PM, Mark Hounschell wrote:
On 3/10/21 2:56 PM, Filipe Laíns wrote:
On Wed, 2021-03-10 at 13:55 -0500, Mark Hounschell wrote:
I have been using a Logitech wireless G602 mouse since forever. As of
kernel 5.10.11 I get the following kernel messages;
$dmesg | grep -i logitech
(sn
On 3/10/21 2:56 PM, Filipe Laíns wrote:
On Wed, 2021-03-10 at 13:55 -0500, Mark Hounschell wrote:
I have been using a Logitech wireless G602 mouse since forever. As of
kernel 5.10.11 I get the following kernel messages;
$dmesg | grep -i logitech
(snip)
.
.
.
Every mouse event seems to produc
On Wed, 2021-03-10 at 13:55 -0500, Mark Hounschell wrote:
> I have been using a Logitech wireless G602 mouse since forever. As of
> kernel 5.10.11 I get the following kernel messages;
>
>
> $dmesg | grep -i logitech
(snip)
> .
> .
> .
> Every mouse event seems to produce another "Unexpected inpu
I have been using a Logitech wireless G602 mouse since forever. As of
kernel 5.10.11 I get the following kernel messages;
$dmesg | grep -i logitech
[7.102140] usb 3-3.4: Manufacturer: Logitech
[ 10.036763] input: Logitech USB Receiver as
/devices/pci:00/:00:08.1/:16:00.3/usb3
Hi Holger,
Thanks for your patch.
there is an ongoing tree wide action to update all those common pattern
of checking for the -EPROBE_DEFER.
I thus propose, to first integrate the patch [i2c: stm32: Simplify with
dev_err_probe()] that has been proposed few days ago, and on top of that add an
add
We currently print errors twice when there is an actual error
when requesting a DMA channel, once in stm32f7_i2c_probe()
when stm32_i2c_dma_request() fails and once more in
stm32_i2c_dma_request() itself. stm32_i2c_dma_request() is only
called from stm32f7_i2c_probe(), so we could drop the duplicat
Hi Folks,
In one of our big cluster, due to capacity increase, more servers are
added to the cluster, and we saw from many pserver reporting error
message below:
"neighbour: ndisc_cache: neighbor table overflow!"
We've tested increasing the gc_thresh values in sysctl.conf, after
reboot, the erro
Am 25.10.2017 um 06:39 schrieb Michał Kępień:
>>> - Investigating the E LED. This requires taking a look at the DSDT
>>> dump from your laptop and searching for clues as to how this LED is
>>> handled. I will be happy to do that, but again, no promises about
>>> how much time it wil
> > - Investigating the E LED. This requires taking a look at the DSDT
> > dump from your laptop and searching for clues as to how this LED is
> > handled. I will be happy to do that, but again, no promises about
> > how much time it will take. (And given the nature of this task, I
Hi Michał,
> Thank you for providing us with further information.
Again, glad to help where I can.
>> Pressing the E button brings up some kind of Energy saving applet and
>> pressing the I button brings up an applet telling me about the hardware
>> in my laptop and its current state.
>
> These
> Hi Michał,
Hi Harvey,
Thank you for providing us with further information.
> Now I had the time to change the harddisk in my laptop to the Win7 one
> (It's 35 degrees out there - nice excuse to stay inside ;))
>
> What I found out:
> Neither the E nor the I LED work under Windows in my config
Hi Michał,
Now I had the time to change the harddisk in my laptop to the Win7 one
(It's 35 degrees out there - nice excuse to stay inside ;))
What I found out:
Neither the E nor the I LED work under Windows in my configuration.
There is no Bluetooth LED (maybe because there is a combined
WLAN/Blu
Hi Michał,
> A photo would be useful (though please do not attach it to your message,
> https://www.notebookcheck.net/fileadmin/_migrated/pics/Fujitsu-LB-E751-Tastatur_1j.jpg
That is exactly my laptop (well, except for those ugly windows badges ;))
To be completely sure I have taken two photos
Michał, Jonathan,
just a short note: I am currently on vacation in Spain. I have my laptop
with me and will report back as soon as I find the time. I will try to
help in any way that I can. I want my laptop to be as functional as
possible with linux.
Greetings
Harvey
Am 20.07.2017 um 08:42 schri
Hi Michal
On Thu, Jul 20, 2017 at 08:42:57AM +0200, Micha?? K??pie?? wrote:
> > I found your mail address in https://patchwork.kernel.org/patch/8598801/
> > and it seems you are somehow involved in the improvement for
> > fujitsu-laptop LED handling. If this does not 'belong' to you, maybe you
> >
> Hello,
Hi! Thank you for the report and sorry about the delay, but I have been
at a conference for the past week, having way less spare time than I
wish I had.
> I found your mail address in https://patchwork.kernel.org/patch/8598801/
> and it seems you are somehow involved in the improvement
+ intel-...@lists.freedesktop.org
On Thu, Oct 01, 2015 at 12:20:10AM -0700, Gary Barrueto wrote:
> Got a intel nuc i7 and am getting this when I start playing video in
> vlc and many times the system just freezes.
>
> Oct 1 00:08:59 inuc kernel: [ 81.127657] [ cut here
> ]
Got a intel nuc i7 and am getting this when I start playing video in
vlc and many times the system just freezes.
Oct 1 00:08:59 inuc kernel: [ 81.127657] [ cut here ]
Oct 1 00:08:59 inuc kernel: [ 81.127680] WARNING: CPU: 3 PID: 151
at /home/kernel/COD/linux/drivers/g
Dne 13.9.2015 v 11:56 Robert Jarzmik napsal(a):
> Petr Cvek writes:
>
>> During testing of these patches
>>
>> [PATCH] mmc: pxamci: fix card detect threaded interrupt
>> [PATCH 1/3] dmaengine: virt-dma: don't always free descriptor upon
>> completion
>>
>> I have found unrelated error.
Petr Cvek writes:
> During testing of these patches
>
> [PATCH] mmc: pxamci: fix card detect threaded interrupt
> [PATCH 1/3] dmaengine: virt-dma: don't always free descriptor upon
> completion
>
> I have found unrelated error.
>
> How to reproduce:
>
> 1) Remove any SD card
> 2) No
During testing of these patches
[PATCH] mmc: pxamci: fix card detect threaded interrupt
[PATCH 1/3] dmaengine: virt-dma: don't always free descriptor upon
completion
I have found unrelated error.
How to reproduce:
1) Remove any SD card
2) No CPLD initial power for card (in m
On Thu, 30 Jul 2015 17:23:22 +0100, Matt Fleming said:
> On Thu, 2015-07-16 at 22:25 +0800, Lee, Chun-Yi wrote:
> > Moved the function of transferring EFI status to kernel error for
> > later used by EFI stub.
> >
> > Signed-off-by: Lee, Chun-Yi
> > ---
>
On Thu, Jul 30, 2015 at 05:23:22PM +0100, Matt Fleming wrote:
> On Thu, 2015-07-16 at 22:25 +0800, Lee, Chun-Yi wrote:
> > Moved the function of transferring EFI status to kernel error for
> > later used by EFI stub.
> >
> > Signed-off-by: Lee, Chun-Yi
> > ---
On Thu, 2015-07-16 at 22:25 +0800, Lee, Chun-Yi wrote:
> Moved the function of transferring EFI status to kernel error for
> later used by EFI stub.
>
> Signed-off-by: Lee, Chun-Yi
> ---
> drivers/firmware/efi/vars.c | 33 -
> include/lin
Moved the function of transferring EFI status to kernel error for
later used by EFI stub.
Signed-off-by: Lee, Chun-Yi
---
drivers/firmware/efi/vars.c | 33 -
include/linux/efi.h | 33 +
2 files changed, 33 insertions(+), 33
lspci:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
04:01.0 Ethernet controller: SysKonnect SK-9871 V2.0 Gigabit Ethernet
1000Base-ZX Adapter, PCI64, Fiber ZX/SC (rev 18)
04:02.0 Ethernet controller: Realtek Semiconduct
the XID:
good card:
Sep 1 11:41:41 localhost kernel: [4.332165] r8169 Gigabit
Ethernet driver 2.3LK-NAPI loaded
Sep 1 11:41:41 localhost kernel: [4.332184] r8169 :01:00.0:
PCI INT A -> GSI 17 (level, low) -> IRQ 17
Sep 1 11:41:41 localhost kernel: [4.332236] r8169 :01:00.0:
here the dmesg (from /var/log/kernel.log)
http://pastebin.com/gcHgTYXZ
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://w
Roberto Spadim :
[...]
> ethtool show eth2 and eth1 as up and running and eth2 as fibre but
> it's a TP board?!
It happens with old model r8169 boards that go south during netdev
whatchdog recovery handler.
Please send the XID line included in dmesg output at startup.
> i'm considering eth2 a b
hi guys, an problem occured, could anyone try to help me? i think it's
hardware error, but it's nice a second opnion
if i remove eth2 cable bond0 and everything work
the eth2 is running (yellow led on board) at 10mbps, but it's a
1000mbps (normally a green led on board) link, the other side is
runn
Hi,
I send this mail as information/suggestion for improvements of Linux
kernel. I have identified and solved the problem below some years ago.
I think that it would be great if the changes could be part of generic
distributions in the future as the affects availability when using
Linux in emb
On Tue, 2012-09-04 at 16:28 -0700, Andrew Morton wrote:
> On Fri, 31 Aug 2012 18:55:59 -0600
> Shuah Khan wrote:
>
> > Add kernel error message to track iotlb overflow buffer triggers to
> > understand
> > how often the overflow buffer gets used.
> &g
On Fri, 31 Aug 2012 18:55:59 -0600
Shuah Khan wrote:
> Add kernel error message to track iotlb overflow buffer triggers to understand
> how often the overflow buffer gets used.
>
> Signed-off-by: Shuah Khan
> ---
> lib/swiotlb.c |1 +
> 1 file changed, 1 insertion(+)
On Fri, 2012-08-31 at 18:55 -0600, Shuah Khan wrote:
> Add kernel error message to track iotlb overflow buffer triggers to understand
> how often the overflow buffer gets used.
Does this change look reasonable? My intent is to be able to assess how
often the overflow buffer usage gets tri
On 7/20/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
Hi Werner,
On 7/20/07, werner <[EMAIL PROTECTED]> wrote:
> To: linux-kernel@vger.kernel.org
>
>
> copied from the screen:
>
> ...
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> Starting udevd: /sbin/udevd -- daemon
>
Hi Werner,
On 7/20/07, werner <[EMAIL PROTECTED]> wrote:
To: linux-kernel@vger.kernel.org
copied from the screen:
...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
Starting udevd: /sbin/udevd -- daemon
[cut here]---
Kernel BUG at mm/slub.c:2401!
That
To: linux-kernel@vger.kernel.org
copied from the screen:
...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
Starting udevd: /sbin/udevd -- daemon
[cut here]---
Kernel BUG at mm/slub.c:2401!
Invalid opcode: [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0060:
Hi,
[netdev added to CC]
[EMAIL PROTECTED] pisze:
I got following error message when I try to upload file to remote server.
The log generated in remote server is as per below.
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1284)
recvmsg bug: copied BC00D548 seq BC00DAFC
KERNEL:
I got following error message when I try to upload file to remote server.
The log generated in remote server is as per below.
KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c (1284)
recvmsg bug: copied BC00D548 seq BC00DAFC
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags &
On Friday 30 March 2007 03:36, Zach wrote:
> kern.log:Mar 29 23:44:36 netrek kernel: spurious 8259A interrupt: IRQ7.
A spurious interrupt isn't necessarily a "spurious kernel error",
it means that the kernel went to service an interrupt and didn't
find any sources.
I just noticed this weird kernel message while looking through
/var/log/ , I have never noticed this error to occur before and below
is the only mention of it I could find in my log files:
netrek:/var/log# grep IRQ7 *
kern.log:Mar 29 23:44:36 netrek kernel: spurious 8259A interrupt: IRQ7.
kernel:
I run Fedora Core 6 on the 'compaq nc6320' laptop. I am using the
'2.6.19.1' kernel.
While booting the kernel, I noticed the following 3 messages:
1. PCI: BIOS Bug: MCFG area at f800 is not E820-reserved
PCI: Not using MMCONFIG.
After some search, I commented out the 'e820_all_mapped()'
Hi,
I included my module into the main kernel object
file by modifying the top Makefile i.e obj-y magic.
Now, when I reboot the system the module works. But in
the new hardware detection phase, X server and other
applications failed. The kernel prompted to repair the
file system and to reboot t
Hi,
after changing from 2.2.17 - kernel (where no such
issues were noticeable) to 2.2.19 (with 'enable
dma-support' etc compiled into kernel)
Would be very nice if you could tell me if the error
is related to my harddrive (hardware) or is maybe a
kernel-bug and at which version it should be fixed
I am getting the same message with kernel 2.2.19 on a Vaio 505VE. (Celeron
333 with 128 megs of memory.) I usually see the message when copying
large quantites from the PCMCIA CD-ROM to the hard drive.
On Sun, 22 Apr 2001, Andreas Neidhardt wrote:
> Hello from Germany,
>
> I have trouble with
Hello from Germany,
I have trouble with a 2.2.18 kernel on a Gigabyte GA 5AX Rev. 5.2
Mainboard.
I have a lot of entrys in /var/log/messages like this:
kernel: probable hardware bug: clock timer configuration lost - probably
a VIA686a.
horst kernel: probable hardware bug: restoring chip configur
My personal experience strongly suggests that the NVdriver is the
culprit.
Try geting rid of it.
Arthur
On Sun, 4 Mar 2001, Romain Chantereau wrote:
> Hi,
>
> I didn't know where send this bug report, so I send it here as writen in
> the Doc... Sorry if I mistake...
>
> Ok, I have a Debian sid
Hi,
I didn't know where send this bug report, so I send it here as writen in
the Doc... Sorry if I mistake...
Ok, I have a Debian sid (sic), on a AMD K6-2 300, on a Asus P5A, I have
enabled AGP etc...
Ah ! My graphic card is a Riva TNT, and I use it with the Nvidia driver
0.9.6..
Ok, let's talk
On Tue, Dec 12, 2000 at 12:53:33PM +0100, jordi wrote:
> I try to upgrade my 2.2.5-17 kernel to 2.4-test11 but when I put make
> modules_install and it is in pcmacia module the make crash because it
> put -F option.
>
> when I see the syntax not appear this option and I don't have a answer?
>
>
hi
I try to upgrade my 2.2.5-17 kernel to 2.4-test11 but when I put make
modules_install and it is in pcmacia module the make crash because it
put -F option.
when I see the syntax not appear this option and I don't have a answer?
You can help me?
Thanks a lot for all
Jordi Pallarès
-
To un
53 matches
Mail list logo
