the lines of the patch
sent to me earlier or something even more beautiful.
Thanks in advance and kind regards,
Udo
On 14-10-2020 10:37, Pavel Machek wrote:
> On Wed 2020-10-14 10:34:21, Udo van den Heuvel wrote:
>> On 14-10-2020 10:27, Pavel Machek wrote:
>>>> One should hav
On 14-10-2020 10:27, Pavel Machek wrote:
>> One should have thought about stuff beforehand.
>
> We did. And decided this is best solution.
Then the thought process went awry.
>> The non-selectability is not my fault.
>
> It also does not affect you in any way.
It does.
/boot fills up even
On 14-10-2020 10:11, Pavel Machek wrote:
>> It's a computer, not a disco-light or anything like that.
>
> And you probably have numlock LED.
On the case? no way.
It is on the keyboard, a separate device, and already has a function.
We also have a caps lock LED and scroll lock LED there, with
On 14-10-2020 09:58, Pavel Machek wrote:
> Contrary to his claims, Udo very probably has LEDs in his systems...
We have a visible power LED.
WE have a HDD LED.
The board has LEDs, yes, but the SilverStone Fortress FT02 hides them
fairly well.
I did not ask for LEDs nor need them this way.
It's a
On 14-10-2020 07:07, Randy Dunlap wrote:
> On 10/13/20 9:56 PM, Udo van den Heuvel wrote:
>> I.e.: it looks like I will lose some funcionality when I disable
>> SND_HDA_CODEC_REALTEK.
>
> OK. At present you can't have it both ways, i.e., SND_HDA_CODEC_REALTEK
> w
On 14-10-2020 06:49, Randy Dunlap wrote:
> If you disable SND_HDA_CODEC_REALTEK, then the rest of the
> LED kconfig symbols can be disabled.
Sure,
but:
# dmesg|grep audi
(...)
[ 19.971537] snd_hda_codec_generic hdaudioC0D0: ignore pin 0x7, too
many assigned pins
[ 19.973547]
On 13-10-2020 18:03, Randy Dunlap wrote:
> On 10/13/20 8:53 AM, Randy Dunlap wrote:
>> [adding LED people + list]
>>
>> On 10/13/20 6:24 AM, Udo van den Heuvel wrote:
(...)
>>>> So how do I disable this stuff?
>>>>
>
> I was able
of it?
Or else please explain how to make this work on a Gigabyte Technology
Co., Ltd. X570 AORUS PRO...
Kind regards,
Udo
On 13-10-2020 11:24, Udo van den Heuvel wrote:
> Hello,
>
> While looking at the 5.9 kernel config I noticed there is no easy way to
> disable LED support in genera
Hello,
While looking at the 5.9 kernel config I noticed there is no easy way to
disable LED support in general.
There's this NEW_LEDS thing that is not shown, etc.
So I get:
# make oldconfig
scripts/kconfig/conf --oldconfig Kconfig
*
* Restart config...
*
*
* LED Support
*
LED Support
Hello,
I was AFK when this occurred.
What happened and what can I to help get this fixed?
[207927.171466] cp210x 5-4.1:1.0: device disconnected
[264738.655873] INFO: task Link Monitor:84552 blocked for more than 120
seconds.
[264738.655875] Not tainted 5.6.13 #29
[264738.655876] "echo 0 >
On 19-10-2019 13:22, Udo van den Heuvel wrote:
> When I boot this workstation, the nvme disks appear in /dev/ without
> their partitions.
# ls -l /dev/nv*
crw--- 1 root root 251, 0 Oct 19 13:43 /dev/nvme0
brw-rw 1 root disk 259, 1 Oct 19 13:43 /dev/nvme0n1
crw--- 1 root ro
Linux-guru's,
When I boot this workstation, the nvme disks appear in /dev/ without
their partitions. fdisk shows there are partitions but cannot write a
new partitions table, mentions a busy disk.
These processes are busy with the nvme disks:
root 236 2 0 13:08 ?00:00:00
Hello,
After installing some fresh nvme drives in the system I noticed these in
dmesg:
[ 87.866255] fuse: init (API version 7.31)
[ 380.017552] nvme0n1: p1 p2
[ 381.101504] nvme0n1: p1 p2
[ 492.177525] nvme0n1: p1 p2
[ 527.965910] nvme1n1: p1 p2
[ 529.041589] nvme1n1: p1 p2
[
Hello,
To fix the 'ppp0: recursion detected' messages we see on our firewall I
found a solution at:
https://forum.openwrt.org/t/pptp-recursion-detected-system-reboot-itself/12585
Can we please implement this solution if deemed OK?
Kind regards,
Udo
On 04-10-2019 06:57, Udo van den Heuvel wrote:
> To fix the 'ppp0: recursion detected' messages we see on our firewall I
> found a solution at:
>
> https://forum.openwrt.org/t/pptp-recursion-detected-system-reboot-itself/12585
>
> Can we please implement this solution if deem
On 09-06-18 11:50, Udo van den Heuvel wrote:
My Holux GPSport 245 was used to download a gpx track. Afterwards I
turned the device off while it was attached to USB so it could charge.
Later I found these messages you can find below.
Actually I removed the charging Holux GPSport from the USB
On 09-06-18 11:50, Udo van den Heuvel wrote:
My Holux GPSport 245 was used to download a gpx track. Afterwards I
turned the device off while it was attached to USB so it could charge.
Later I found these messages you can find below.
Actually I removed the charging Holux GPSport from the USB
Hello,
My Holus GPSport 245 was used to download a gpx track. Afterwards I
turned the device off while it was attached to USB so it could charge.
Later I found these messages you can find below.
Is this an actual bug?
# dmesg
[213812.789603] amdgpu: [powerplay] pp_dpm_get_temperature was not
Hello,
My Holus GPSport 245 was used to download a gpx track. Afterwards I
turned the device off while it was attached to USB so it could charge.
Later I found these messages you can find below.
Is this an actual bug?
# dmesg
[213812.789603] amdgpu: [powerplay] pp_dpm_get_temperature was not
On 10-05-18 16:26, Udo van den Heuvel wrote:
> May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
> May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
These appear every ~25 minutes:
May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
May 10 16:0
On 10-05-18 16:26, Udo van den Heuvel wrote:
> May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
> May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
These appear every ~25 minutes:
May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
May 10 16:0
Hello,
My Asrock QC5000M-ITX/PH baord booted into 4.16.8 recently and after a
while we noticed messages like:
May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
How can we fix this these? (previous kernel did not
Hello,
My Asrock QC5000M-ITX/PH baord booted into 4.16.8 recently and after a
while we noticed messages like:
May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
May 10 16:00:04 v kernel: do_IRQ: 1.37 No irq handler for vector
How can we fix this these? (previous kernel did not
Hello,
Ever since booting into 4.15.18 I had two incidents of 'irq xx: nobody
cared (try booting with the "irqpoll" option)'.
Before that 4.9.60 ran for months without issue.
What could be the cause?
Kind regards,
Udo
96.747946] snd_hda_codec_hdmi hdaudioC1D0: HDMI ATI/AMD: no speaker
Hello,
Ever since booting into 4.15.18 I had two incidents of 'irq xx: nobody
cared (try booting with the "irqpoll" option)'.
Before that 4.9.60 ran for months without issue.
What could be the cause?
Kind regards,
Udo
96.747946] snd_hda_codec_hdmi hdaudioC1D0: HDMI ATI/AMD: no speaker
by running a `find /` over ssh to
the box. So perhaps it is an interrupt related issue?
Please help find the root cause.
Kind regards,
Udo
On 24-05-17 15:04, Udo van den Heuvel wrote:
> Hello,
>
> This issue occurs on VIA Epia M910E.
> Both interfaces suffer from this.
>
by running a `find /` over ssh to
the box. So perhaps it is an interrupt related issue?
Please help find the root cause.
Kind regards,
Udo
On 24-05-17 15:04, Udo van den Heuvel wrote:
> Hello,
>
> This issue occurs on VIA Epia M910E.
> Both interfaces suffer from this.
>
.
Kind regards,
Udo
On 23-05-17 18:07, Udo van den Heuvel wrote:
> Hello,
>
> I noticed multiple times that VIA velocity interface stop functioning
> without reason but is revived after and `ifdown ethX; ifup ethX`.
> No data is transferred until the `fix` is applied.
> No errors
.
Kind regards,
Udo
On 23-05-17 18:07, Udo van den Heuvel wrote:
> Hello,
>
> I noticed multiple times that VIA velocity interface stop functioning
> without reason but is revived after and `ifdown ethX; ifup ethX`.
> No data is transferred until the `fix` is applied.
> No errors
Hello,
I noticed multiple times that VIA velocity interface stop functioning
without reason but is revived after and `ifdown ethX; ifup ethX`.
No data is transferred until the `fix` is applied.
No errors are shown in dmesg or /var/log/messages w.r.t. the interface.
How to find the root cause?
Hello,
I noticed multiple times that VIA velocity interface stop functioning
without reason but is revived after and `ifdown ethX; ifup ethX`.
No data is transferred until the `fix` is applied.
No errors are shown in dmesg or /var/log/messages w.r.t. the interface.
How to find the root cause?
Hello,
My dmesg shows a lot of these:
[920255.822392] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:12.0
domain=0x0006 address=0x0080 flags=0x0020]
[920255.823404] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:12.0
domain=0x0006 address=0x0080 flags=0x0020]
# cat
Hello,
My dmesg shows a lot of these:
[920255.822392] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:12.0
domain=0x0006 address=0x0080 flags=0x0020]
[920255.823404] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:12.0
domain=0x0006 address=0x0080 flags=0x0020]
# cat
Hello,
Kernel 4.4.8 works fine.
During 4.4.13 boot fbcon.ko is not loaded, thus the monitor goes into
sleep until xorg is started.
Kernel .config is identical between 4.4.8 and 4.4.13.
fbcon.ko is built during the kernel compilation.
fbcon.ko is in the initramfs for 4.4.13. (verified by
Hello,
Kernel 4.4.8 works fine.
During 4.4.13 boot fbcon.ko is not loaded, thus the monitor goes into
sleep until xorg is started.
Kernel .config is identical between 4.4.8 and 4.4.13.
fbcon.ko is built during the kernel compilation.
fbcon.ko is in the initramfs for 4.4.13. (verified by
Hello,
On 3.18.11 the card was functioning OK.
On 4.4.3 I get:
1.894086] HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
[1.894198] HiSax: W6692 driver Rev. 1.18.2.4
[1.894364] Found: Dynalink/AsusCom IS64PH, I/O base: 0xd000, irq: 6
[1.894490] HiSax: IS64PH config irq:6 I/O:d000
[
Hello,
On 3.18.11 the card was functioning OK.
On 4.4.3 I get:
1.894086] HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
[1.894198] HiSax: W6692 driver Rev. 1.18.2.4
[1.894364] Found: Dynalink/AsusCom IS64PH, I/O base: 0xd000, irq: 6
[1.894490] HiSax: IS64PH config irq:6 I/O:d000
[
On 2016-03-02 15:43, Udo van den Heuvel wrote:
> [2.048185] Winbond 6692: IRQ 6 count 0
> [2.048292] Winbond 6692: IRQ(6) getting no interrupts during init 3
> [2.048592] HiSax: Card Winbond 6692 not installed !
>
> I reserved some IRQs in the BIOS of the box but dif
On 2016-03-02 15:43, Udo van den Heuvel wrote:
> [2.048185] Winbond 6692: IRQ 6 count 0
> [2.048292] Winbond 6692: IRQ(6) getting no interrupts during init 3
> [2.048592] HiSax: Card Winbond 6692 not installed !
>
> I reserved some IRQs in the BIOS of the box but dif
On 2015-10-05 15:16, Udo van den Heuvel wrote:
> Did I miss anything that is needed to avoid this?
> Is this a known issue?
>
> Please let me know.
Finally I got some logging.
I booted into 4.1.10 in single user mode. All appeared fine.
Then I went to multi user or whatever the s
On 2015-10-05 15:16, Udo van den Heuvel wrote:
> Did I miss anything that is needed to avoid this?
> Is this a known issue?
>
> Please let me know.
Finally I got some logging.
I booted into 4.1.10 in single user mode. All appeared fine.
Then I went to multi user or whatever the s
Hello,
My x86_64 box loses network and also develops disk access issues shortly
after booting into Fedora using self-built kernels 4.1.9 and 4.1.10.
First boot into 4.1.9. made one sata disk drop out of the raid-10. Disk
was fine after going back to 4.1.7.
4.1.8 appears to work fine.
Did I miss
Hello,
My x86_64 box loses network and also develops disk access issues shortly
after booting into Fedora using self-built kernels 4.1.9 and 4.1.10.
First boot into 4.1.9. made one sata disk drop out of the raid-10. Disk
was fine after going back to 4.1.7.
4.1.8 appears to work fine.
Did I miss
All,
On 2014-11-01 05:51, Udo van den Heuvel wrote:
> I'll test this today, I hope.
Works!
Kind regards,
Udo
--
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://vg
Hello,
On 2014-10-31 18:47, Hans Verkuil wrote:
> Fixed by this patch: https://patchwork.linuxtv.org/patch/26302/
I'll test this today, I hope.
Thanks!!
Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hello,
Booting into 3.17.2 on one box I saw:
[ 15.070260] microcode: CPU0: patch_level=0x01b7
[ 15.279454] Linux video capture interface: v2.00
[ 15.315043] microcode: CPU0: new patch_level=0x01c7
[ 15.319519] microcode: CPU1: patch_level=0x01b7
[ 15.323966] microcode:
Hello,
Booting into 3.17.2 on one box I saw:
[ 15.070260] microcode: CPU0: patch_level=0x01b7
[ 15.279454] Linux video capture interface: v2.00
[ 15.315043] microcode: CPU0: new patch_level=0x01c7
[ 15.319519] microcode: CPU1: patch_level=0x01b7
[ 15.323966] microcode:
Hello,
On 2014-10-31 18:47, Hans Verkuil wrote:
Fixed by this patch: https://patchwork.linuxtv.org/patch/26302/
I'll test this today, I hope.
Thanks!!
Kind regards,
Udo
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
All,
On 2014-11-01 05:51, Udo van den Heuvel wrote:
I'll test this today, I hope.
Works!
Kind regards,
Udo
--
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
Hello,
Here's a 3.16.2 dmesg that is a tad m ore complete but still the usb
errors fill up the buffer.
I want to try a bisect and cloned Linus' tree but need commit numbers
for 3.16.2 and .3 to start the bisect process.
Where can I find these?
Do we have a suspect 3.16.3 commit that I could try
Hello,
Here's a 3.16.2 dmesg that is a tad m ore complete but still the usb
errors fill up the buffer.
I want to try a bisect and cloned Linus' tree but need commit numbers
for 3.16.2 and .3 to start the bisect process.
Where can I find these?
Do we have a suspect 3.16.3 commit that I could try
On 2014-10-13 14:26, Chuck Ebbert wrote:
>> How can I capture the output easily?
>
> Add "boot_delay=3000" to the kernel command line. This will add a 3
> second delay between each line. Then take pictures of the screen
> while it boots. And try to time the shots so you take them during the
>
On 2014-10-13 14:26, Chuck Ebbert wrote:
How can I capture the output easily?
Add boot_delay=3000 to the kernel command line. This will add a 3
second delay between each line. Then take pictures of the screen
while it boots. And try to time the shots so you take them during the
delays.
On
On 2014-10-13 14:14, Peter Hurley wrote:
> Why incomplete? No kernel command line, no version stamp, no CPU info,
> no memory map, no IRQ routing info, etc.
>
# cat /proc/cmdline
ro root=/dev/myvg/rootlv noexec=on noexec32=on vga=0x0F01
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
On 2014-10-13 14:14, Peter Hurley wrote:
>> Incomplete dmesg attached for 3.16.2.
>
> Why incomplete? No kernel command line, no version stamp, no CPU info,
> no memory map, no IRQ routing info, etc.
Because the buffer is filled with other stuff and scrolls out.
>>> And rubbish is not
>> very
On 2014-10-12 19:42, Peter Hurley wrote:
> On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
>> The problem:
>> During the first few seconds of bootup the kernel gets into some sort of
>> loop and rapidly prints loads of register-like things and then a load of
>> ru
On 2014-10-12 19:42, Peter Hurley wrote:
On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a load of
rubbish.
I did `make clean
On 2014-10-13 14:14, Peter Hurley wrote:
Incomplete dmesg attached for 3.16.2.
Why incomplete? No kernel command line, no version stamp, no CPU info,
no memory map, no IRQ routing info, etc.
Because the buffer is filled with other stuff and scrolls out.
And rubbish is not
very
On 2014-10-13 14:14, Peter Hurley wrote:
Why incomplete? No kernel command line, no version stamp, no CPU info,
no memory map, no IRQ routing info, etc.
# cat /proc/cmdline
ro root=/dev/myvg/rootlv noexec=on noexec32=on vga=0x0F01
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
Hello,
3.16.2 boots and works fine.
Kernels 3.16.3 and newer crash very early during boot. (did not yet try
3.17)
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a load of
rubbish.
I did `make
Hello,
3.16.2 boots and works fine.
Kernels 3.16.3 and newer crash very early during boot. (did not yet try
3.17)
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a load of
rubbish.
I did `make
: Etron Technology, Inc. EJ168 USB 3.0 Host
Controller (rev 01)
03:06.0 Serial controller: MosChip Semiconductor Technology Ltd. PCI
9835 Multi-I/O Controller (rev 01)
And the Etron EJ168 is the only USB3 provider here?
How can we fix this issue?
Kind regards,
Udo
On 2014-08-08 05:42, Udo van
: Etron Technology, Inc. EJ168 USB 3.0 Host
Controller (rev 01)
03:06.0 Serial controller: MosChip Semiconductor Technology Ltd. PCI
9835 Multi-I/O Controller (rev 01)
And the Etron EJ168 is the only USB3 provider here?
How can we fix this issue?
Kind regards,
Udo
On 2014-08-08 05:42, Udo van
Hello,
I get WARNINGs when trying to use a Logitech C615 cam.
See attachment for full dmesg of errors but excerpt below:
[80346.835015] xhci_hcd :02:00.0: ERROR: unexpected command
completion code 0x11.
[80346.835027] usb 6-2: Not enough bandwidth for altsetting 11
[80346.835137]
Hello,
I get WARNINGs when trying to use a Logitech C615 cam.
See attachment for full dmesg of errors but excerpt below:
[80346.835015] xhci_hcd :02:00.0: ERROR: unexpected command
completion code 0x11.
[80346.835027] usb 6-2: Not enough bandwidth for altsetting 11
[80346.835137]
Hello,
What went wrong here?
Please let me know!
Kind regards,
Udo
Jun 29 06:59:20 surfplank2 kernel: [ 5263.255573] [ cut here
]
Jun 29 06:59:20 surfplank2 kernel: [ 5263.255587] WARNING: CPU: 2 PID:
10113 at drivers/media/v4l2-core/videobuf2-core.c:2011
Hello,
What went wrong here?
Please let me know!
Kind regards,
Udo
Jun 29 06:59:20 surfplank2 kernel: [ 5263.255573] [ cut here
]
Jun 29 06:59:20 surfplank2 kernel: [ 5263.255587] WARNING: CPU: 2 PID:
10113 at drivers/media/v4l2-core/videobuf2-core.c:2011
On 2014-06-01 19:42, Francois Romieu wrote:
> Udo van den Heuvel :
> [...]
>> On two boxes with rtl network chip I see connections going down.
>
> Do you notice netdev watchdog messages in the kernel log ?
I do not see messages that look like that.
>> 3.14.1 has the iss
Hello,
On two boxes with rtl network chip I see connections going down.
An ifdown eth0;ifup eth0 fixes this.
3.14.1 has the issue.
How can I fix this more elegantly?
Below is info from both boxes from lspci and dmesg:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
Hello,
On two boxes with rtl network chip I see connections going down.
An ifdown eth0;ifup eth0 fixes this.
3.14.1 has the issue.
How can I fix this more elegantly?
Below is info from both boxes from lspci and dmesg:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
On 2014-06-01 19:42, Francois Romieu wrote:
Udo van den Heuvel udo...@xs4all.nl :
[...]
On two boxes with rtl network chip I see connections going down.
Do you notice netdev watchdog messages in the kernel log ?
I do not see messages that look like that.
3.14.1 has the issue.
Does
Hello,
After returning from holiday I found this in dmesg:
[1724773.295579] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[1725207.771256] BUG: scheduling while atomic: irq/20-serial/1299/0x0202
[1725207.771260] Modules linked in: btrfs lzo_compress zlib_deflate bnep
bluetooth
Hello,
After returning from holiday I found this in dmesg:
[1724773.295579] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[1725207.771256] BUG: scheduling while atomic: irq/20-serial/1299/0x0202
[1725207.771260] Modules linked in: btrfs lzo_compress zlib_deflate bnep
bluetooth
People,
Here's an issue with ethernet connectivity that stops working but is
resurrected with an `ifdown eth0; ifup eth0`.
The board is a Jetway JNC84E-LF with AMD Athlon(tm) II X2 235e Processor.
Network chip: 02:00.0 Ethernet controller: Realtek Semiconductor Co.,
Ltd. RTL8111/8168/8411 PCI
People,
Here's an issue with ethernet connectivity that stops working but is
resurrected with an `ifdown eth0; ifup eth0`.
The board is a Jetway JNC84E-LF with AMD Athlon(tm) II X2 235e Processor.
Network chip: 02:00.0 Ethernet controller: Realtek Semiconductor Co.,
Ltd. RTL8111/8168/8411 PCI
Hello,
Can someone please summarise the status of the xhci_hcd debugging I
found after booting into 3.12.2?
I did not see these messages before and I do not yet understand the
added value for a mere user of this exciting xhci technology.
Can we please have them go away if really there's noting
Hello,
Can someone please summarise the status of the xhci_hcd debugging I
found after booting into 3.12.2?
I did not see these messages before and I do not yet understand the
added value for a mere user of this exciting xhci technology.
Can we please have them go away if really there's noting
Hello,
I found this in /var/log/messages:
Sep 26 03:37:36 recorder kernel: BUG: unable to handle kernel NULL
pointer dereference at 0008
Sep 26 03:37:36 recorder kernel: IP: []
__rb_insert_augmented+0x23/0x200
Sep 26 03:37:36 recorder kernel: PGD cf8d5067 PUD caf6a067 PMD 0
Sep 26
Hello,
I found this in /var/log/messages:
Sep 26 03:37:36 recorder kernel: BUG: unable to handle kernel NULL
pointer dereference at 0008
Sep 26 03:37:36 recorder kernel: IP: [8122e393]
__rb_insert_augmented+0x23/0x200
Sep 26 03:37:36 recorder kernel: PGD cf8d5067 PUD caf6a067
On 2013-08-27 19:41, Andreas Mohr wrote:
>> What could this be?
>> Is it really a software issue?
>> If so: how could I help fix this?
>
> Perhaps watching the output of some input event tools could help
> gather some clues to eventually get it nailed down?
Sure.
First my input:
When I run this
On 2013-08-27 19:41, Andreas Mohr wrote:
What could this be?
Is it really a software issue?
If so: how could I help fix this?
Perhaps watching the output of some input event tools could help
gather some clues to eventually get it nailed down?
Sure.
First my input:
When I run this small
On 2013-08-27 17:40, Peter Hurley wrote:
> [ +cc Greg KH, Jiri S ]
>
> On 08/26/2013 01:53 AM, Udo van den Heuvel wrote:
>> Hello,
>>
>> I am stuck with a weird keyboard related issue:
>> Since a few weeks I see loads of ^@^@^@^@^@^@ appear on the
On 2013-08-27 17:40, Peter Hurley wrote:
[ +cc Greg KH, Jiri S ]
On 08/26/2013 01:53 AM, Udo van den Heuvel wrote:
Hello,
I am stuck with a weird keyboard related issue:
Since a few weeks I see loads of ^@^@^@^@^@^@ appear on the text console
[...]
What could this be?
Is it really
Hello,
I am stuck with a weird keyboard related issue:
Since a few weeks I see loads of ^@^@^@^@^@^@ appear on the text console
while the PC_speaker beeps when this box is in runlevel 3.
When xorg is running the ^@^@^@ stream stops, as does the beeping, but I
can notice that selecting text,
Hello,
I am stuck with a weird keyboard related issue:
Since a few weeks I see loads of ^@^@^@^@^@^@ appear on the text console
while the PC_speaker beeps when this box is in runlevel 3.
When xorg is running the ^@^@^@ stream stops, as does the beeping, but I
can notice that selecting text,
Hello,
This morning I did a luksOpen on an external harddisk and saw:
# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie
Hello,
This morning I did a luksOpen on an external harddisk and saw:
# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie
On 2013-03-28 15:35, Alan Stern wrote:
>>> When my dmesg gives me a growing number of lines like the one below,
>>> what is going on?
>>>
>>> ohci_hcd :00:12.0: urb 88023025c500 path 2 ep1in 6c16 cc 6
>>> --> status -71
>>>
>>> Please let me know!
>
> -71 errors indicate a low-level
On 2013-03-28 15:35, Alan Stern wrote:
When my dmesg gives me a growing number of lines like the one below,
what is going on?
ohci_hcd :00:12.0: urb 88023025c500 path 2 ep1in 6c16 cc 6
-- status -71
Please let me know!
-71 errors indicate a low-level problem on the USB bus.
Hello,
When my dmesg gives me a growing number of lines like the one below,
what is going on?
ohci_hcd :00:12.0: urb 88023025c500 path 2 ep1in 6c16 cc 6
--> status -71
Please let me know!
Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Hello,
When my dmesg gives me a growing number of lines like the one below,
what is going on?
ohci_hcd :00:12.0: urb 88023025c500 path 2 ep1in 6c16 cc 6
-- status -71
Please let me know!
Kind regards,
Udo
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
On 2013-03-11 22:23, David Rientjes wrote:
> On Fri, 8 Mar 2013, Udo van den Heuvel wrote:
>
>> [3663200.799579] SLAB: Unable to allocate memory on node 0 (gfp=0xd0)
>> [3663200.799581] cache: size-65536, object size: 65536, order: 4
>> [3663200.799583] node 0: slabs:
On 2013-03-11 22:23, David Rientjes wrote:
On Fri, 8 Mar 2013, Udo van den Heuvel wrote:
[3663200.799579] SLAB: Unable to allocate memory on node 0 (gfp=0xd0)
[3663200.799581] cache: size-65536, object size: 65536, order: 4
[3663200.799583] node 0: slabs: 6/6, objs: 6/6, free: 0
On 2013-03-08 14:11, Udo van den Heuvel wrote:
> Hello,
>
> I found this in dmesg:
slabtop:
Active / Total Objects (% used): 784982 / 981439 (80.0%)
Active / Total Slabs (% used) : 62996 / 63077 (99.9%)
Active / Total Caches (% used) : 119 / 196 (60.7%)
Active / T
Hello,
I found this in dmesg:
[3663200.373989] pwc: Philips PCVC740K (ToUCam Pro)/PCVC840 (ToUCam II)
USB webcam detected.
[3663200.779617] khubd: page allocation failure: order:4, mode:0xd0
[3663200.779621] Pid: 274, comm: khubd Not tainted 3.6.11 #22
[3663200.779622] Call Trace:
Hello,
I found this in dmesg:
[3663200.373989] pwc: Philips PCVC740K (ToUCam Pro)/PCVC840 (ToUCam II)
USB webcam detected.
[3663200.779617] khubd: page allocation failure: order:4, mode:0xd0
[3663200.779621] Pid: 274, comm: khubd Not tainted 3.6.11 #22
[3663200.779622] Call Trace:
On 2013-03-08 14:11, Udo van den Heuvel wrote:
Hello,
I found this in dmesg:
slabtop:
Active / Total Objects (% used): 784982 / 981439 (80.0%)
Active / Total Slabs (% used) : 62996 / 63077 (99.9%)
Active / Total Caches (% used) : 119 / 196 (60.7%)
Active / Total Size (% used
Hello,
Below is a dmesg of a SLAB issue I did not yet see before.
A 3.6.11 kernel on a x86_64 Fedora 17 box from kernel.org.
I attached a SATA disk and mounted the encrypted FS after using luksOpen.
So what went wrong?
I do have another instance of this failure below.
[2752132.099772] sd
Hello,
Below is a dmesg of a SLAB issue I did not yet see before.
A 3.6.11 kernel on a x86_64 Fedora 17 box from kernel.org.
I attached a SATA disk and mounted the encrypted FS after using luksOpen.
So what went wrong?
I do have another instance of this failure below.
[2752132.099772] sd
On 2013-01-22 15:36, Boris Ostrovsky wrote:
>
>
> On 01/22/2013 09:13 AM, Udo van den Heuvel wrote:
>> Gigabyte demonstrate that using ESX 5i IOMMU works fine.
I forwarded the malinglist links with the patch(es) to Gigabyte support
and they forwarded the info t
1 - 100 of 266 matches
Mail list logo
