tek HDA driver, along 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:
>&g
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 soon
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 sepa
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
&
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] snd_hda_codec_g
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 to d
rid 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
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 (NEW_LEDS)
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 [nvm
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
[ 651.030
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 soluti
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
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 pro
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
allocatio
the issue 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
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?
Thi
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 /sys/bus
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 unpacking)
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
[1.
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 syst
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 an
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
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 majord...@vger.kerne
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: CPU1:
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 t
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
> dela
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
acpi
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 de
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
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 cle
controller: 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:4
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
__vb2_queue_ca
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.
RTL8111/8168/841
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 6lowp
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 Exp
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 rea
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 03:
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 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
[
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, scroll
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 val
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 p
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" i
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-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:
[3663200.779629
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 7:0:0:
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 to the BIO
On 2013-01-23 00:29, Suravee Suthikulanit wrote:
> message in "dmesg".
>
> "AMD-Vi: Applying erratum 746 for IOMMU at :00:00.2"
[1.091733] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40
I assume that is correct.
Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscrib
On 2013-01-23 00:29, Suravee Suthikulanit wrote:
> I sent out a patch
> (http://marc.info/?l=linux-kernel&m=135889686523524&w=2) which should
> implement
> the workaround for AMD processor family15h model 10-1Fh erratum 746 in
> the IOMMU driver.
> In your case, the output from "setpci -s 00:00.02
On 2013-01-22 17:12, Boris Ostrovsky wrote:
>> Seen once over here. Correlated with raid-check.
>
> Then the answer from Gigabyte doesn't prove anything. You can also boot
> Linux without seeing this problem in most cases.
That was my situation until the first time it hit.
> Your BIOS does not h
On 2013-01-22 15:36, Boris Ostrovsky wrote:
>> Gigabyte demonstrate that using ESX 5i IOMMU works fine. (with pictures
>> attached).
>
> There are no attachments to your message.
Correct, gigabyte did send them via their support web-interface.
Do yo uneed to see them? They just show IOMMU enabled
Gigabyte demonstrate that using ESX 5i IOMMU works fine. (with pictures
attached).
What can we bring against that?
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/ma
On 2013-01-21 23:35, Suravee Suthikulpanit wrote:
> Would you please try the following and check the output value
> on your system?
>
> # setpci -s 00:00.02 F0.w=90
> # setpci -s 00:00.02 F4.w
# setpci -s 00:00.02 F0.w=90
# setpci -s 00:00.02 F4.w
0050
#
Udo
--
To unsubscribe from this list: s
On 2013-01-21 16:32, Borislav Petkov wrote:
>>> [0.220187] AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
>>
>> Yes, that are BIOS bugs too that prevent interrupt remapping to function
>> reliably. But the good thing is that these bugs can be detected easily
>> to enable a workaround
On 2013-01-21 15:37, Boris Ostrovsky wrote:
>>> Btw, can't we add a quirk to disable NB clock gating? Maybe Boris and
>>> Jacob could help. CCed.
>
>
> Are you talking about erratum 746?
Link please?
If we have a link I could add that to the Gigabyte case.
Udo
--
To unsubscribe from this list:
On 2013-01-21 14:09, Borislav Petkov wrote:
>> Let's see what happens...
>
> Btw, while we're at it, here's some more h0rkage from my PD box:
>
> [0.220022] [Firmware Bug]: AMD-Vi: IOAPIC[9] not in IVRS table
> [0.220078] [Firmware Bug]: AMD-Vi: IOAPIC[10] not in IVRS table
> [0.22013
On 2013-01-20 12:50, Borislav Petkov wrote:
>> Right, Udo, you can try Gigabyte first.
>
> Btw, you're running the latest BIOS from them, I assume?
Nope. But I am beyond their first released BIOS, I am running one of
their beta BIOSes. I am two beta updates behind current with F3g.
They list as d
On 2013-01-20 12:48, Borislav Petkov wrote:
> On Sun, Jan 20, 2013 at 12:40:11PM +0100, Jörg Rödel wrote:
>> Yes, the BIOS vendor can fix this issue. They need to disable NB clock
>> gating for the IOMMU.
>
> Right, Udo, you can try Gigabyte first.
I just did so and referred to the kernel.org bug
Hello Jörg,
On 2013-01-20 12:19, Jörg Rödel wrote:
> On Sun, Jan 20, 2013 at 11:40:20AM +0100, Udo van den Heuvel wrote:
>> Hello,
>>
>> On 2013-01-20 11:36, Borislav Petkov wrote:
>>> I know just the guy, CCed. :-)
>>
>> Thanks for the quick respon
Hello,
On 2013-01-20 11:36, Borislav Petkov wrote:
> I know just the guy, CCed. :-)
Thanks for the quick response!
I found this similar case:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073384
Kind regards,
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Hello,
See below for a part of the logging on this F2A85X-UP4 with AMD
a10-5800k. Box was raid checking I guess.
Jan 20 03:42:08 s3 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="3031" x-info="http://www.rsyslog.com";]
rsyslogd was HUPed
Jan 20 04:11:17 s3 kernel: AMD-Vi: Compl
Hello,
Found this one on one of the boxes:
BUG: unable to handle kernel paging request at 3b1c
IP: [] find_get_page+0x33/0x80
PGD 115a8a067 PUD 11901f067 PMD 0
Oops: [#1] PREEMPT SMP
Modules linked in: vfat msdos fat nls_utf8 isofs fuse binfmt_misc
cpufreq_ondemand f71882fg tda10
On 2012-11-19 17:41, Alan Stern wrote:
> On Sat, 17 Nov 2012, Udo van den Heuvel wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
>
> Secondly, try building a kernel with the patch below and
> CONFIG_USB_DEBUG enabled. Let's see wha
On 2012-11-19 17:41, Alan Stern wrote:
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 40 0 0 0 IO-APIC-edge timer
1:631640677734 IO-APIC-edge
On 2012-11-19 17:41, Alan Stern wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 39 0 0 0 IO-APIC-edge timer
1:716721730
On 2012-07-15 20:28, Alan Stern wrote:
> Um, I think you missed the point. The whole idea of the test is to see
> what happens while the controller is unbound from the driver. Binding
> it again defeats the purpose.
The problem still happens. irq 18 is dsiabled every now and then.
This time on
Well,
The issue appeared again.
irq 18 was disabled, one pwc webcam was on that irq.
This time on new hardware: Gigabyte F2A85X-UP4 with A10-5800K APU.
The box was busy with it's raid10 array, this time, by running bonnie++;
also a raid-check was in progress. (unknown at the time)
So what does t
On 2012-07-15 17:55, Udo van den Heuvel wrote:
> After doing this I could modprobe pwc and start mrtg without problem.
Euh: s/mrtg/motion/
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majo
On 2012-07-15 17:35, Alan Stern wrote:
> echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/unbind
Afterwards I did:
> echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/bind
And I saw:
Jul 15 17:50:30 surfplank2 kernel: ohci_hcd :00:13.1: remove, state 1
Jul 15 17:50:30 surfplank2 kernel: usb
On 2012-07-15 16:28, Udo van den Heuvel wrote:
> After disabling:
And somewhat later:
bus pci, device :00:12.0
OHCI Host Controller
ohci_hcd
OHCI 1.0, NO legacy support registers, rh state running
control 0x083 HCFS=operational CBSR=3
cmdstatus 0x0 SOC=0
intrstatus 0x0024 FNO
On 2012-07-12 16:54, Alan Stern wrote:
> On Thu, 12 Jul 2012, Udo van den Heuvel wrote:
>
>> # cat /proc/interrupts
(...)
>> 18: 25190 18052161 21311 IO-APIC-fasteoi
>> ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7
(...)
>> So what can we
On 2012-07-12 15:43, Jan Ceuleers wrote:
> On 07/12/2012 03:23 PM, Udo van den Heuvel wrote:
>> How to list what modules/programs are using that irq?
>
> cat /proc/interrupts
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 40 0
On 2012-07-11 17:15, Alan Stern wrote:
> On Wed, 11 Jul 2012, Udo van den Heuvel wrote:
>
>> New occurrence:
>
>> Any clues and/or updates?
>
> Didn't you see the message I posted on Monday?
>
> http://marc.info/?l=linux-usb&m=134186054713868&am
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49 box3 ntpd[
On 2012-07-09 22:28, Francois Romieu wrote:
> Udo van den Heuvel :
> [...]
>> Is my hardware dying or is it the kernel?
>
> Try adding eb2dc35d99028b698cdedba4f5522bc43e576bd2 if you own a 8168evl.
>
> If you don't, try reverting 036dafa28da1e2565a8529d
Hello,
Ever since 3.4.4 I see lots more of:
Jul 9 19:08:01 box4 kernel: r8169 :03:00.0: eth0: link up
Jul 9 19:10:07 box4 kernel: r8169 :03:00.0: eth0: link up
Jul 9 19:16:44 box4 kernel: r8169 :03:00.0: eth0: link up
Jul 9 19:17:07 box4 kernel: r8169 :03:00.0: eth0: link up
Ju
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>> Hello,
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49
Hello,
One moment the box is runing OK.
One moment the 3.4.4 kernel decides to disable an interrupt.
Why?
Jul 8 07:43:49 box3 ntpd[5067]: parse: convert_rawdcf: INCOMPLETE DATA
- time code only has 1 bits
Jul 8 07:44:53 box3 kernel: irq 18: nobody cared (try booting with the
"irqpoll" option)
J
Andrew Morton wrote:
> On Tue, 27 Nov 2007 13:50:53 -0500
> Dave Jones <[EMAIL PROTECTED]> wrote:
>
>> On Tue, Nov 27, 2007 at 05:08:26PM +0100, Udo van den Heuvel wrote:
(...)
>> > Yes, I think that's a big step in the right direction!
(...)
>> Andrew,
Andrew Morton wrote:
>> Andrew, want to throw that in the -mm pile for a while?
>
> Did that, renamed to "via-rng: enable secondary noise source on CPUs where
> it is present".
>
> Has anyone tested it?
I hope so; I did not yet get that far since the patche does not compile
on 2.6.23.8. I was as
Cyrill Gorcunov wrote:
> [Udo van den Heuvel - Sat, Dec 01, 2007 at 12:00:53PM +0100]
> | I only had teh bug once, that was the reason for my post.
> | Since then the system has been busy, with intervals, doing kernel
> | compiles and no repeat of the BUG yet...
> | It's a VIA
Dave Jones wrote:
> > > Something like this perhaps ?
> >
> > Yes, I think that's a big step in the right direction!
> >
> > But I am no expert and cannot really judge how necessary or correct the
> > implementation is w.r.t. the 'undefined' function bits for CPU's that
> > lack a certain
Cyrill Gorcunov wrote:
> | > Could you try it and report me how it works?
> |
> | Yes I can!
> | Thanks for the patch.
> | But how can I reproduce the (possible) bug the easiest?
> | It `just happened` during compiling.
> | So I compile some more?
>
> yes i think that is the way we could catch it
Dave Jones wrote:
> On Mon, Nov 26, 2007 at 06:02:39PM +0100, Udo van den Heuvel wrote:
>
> > I did not know we are already that far ;-)
> > I mean: can this patch be aplied without hurting C3/C7 CPU's with just
> > one RNG? Maybe an expert needs to test/answer?
&
Andrew Morton wrote:
> On Sun, 11 Nov 2007 19:49:08 +0100 Udo van den Heuvel <[EMAIL PROTECTED]>
> wrote:
>
>> Any reason why the second rng on the VIA C7 CPU is not enabled?
(...)
> Does the patch work?
Yes, at least:
dd if=/dev/hwrng of=/dev/null bs=1024 count=1024
s
Rafael J. Wysocki wrote:
> On Saturday, 24 of November 2007, Udo van den Heuvel wrote:
>> Hello,
>>
>> What happened in the attached messages?
>> It was on a VIA Epia EN12000, while compiling.
>> Yes, the machine has been stable before and after that issue.
&
Hello,
What happened in the attached messages?
It was on a VIA Epia EN12000, while compiling.
Yes, the machine has been stable before and after that issue.
So I suspect no hardware issues.
Kind regards,
Udo
messages.recorder.gz
Description: application/gzip
Hello,
Any reason why the second rng on the VIA C7 CPU is not enabled?
Kind regards,
Udo
--- old/drivers/char/hw_random/via-rng.c2007-11-11 19:39:49.0
+0100
+++ new/drivers/char/hw_random/via-rng.c2007-11-11 19:40:41.0
+0100
@@ -41,6 +41,7 @@
VIA_STRFILT_
Andrew Morton wrote:
>> On Sun, 2 Sep 2007 04:55:20 -0700 Andrew Morton <[EMAIL PROTECTED]> wrote:
>>> On Sat, 25 Aug 2007 14:57:17 +0200 Udo van den Heuvel <[EMAIL PROTECTED]>
>>> wrote:
>>> Udo van den Heuvel wrote:
>>>> Now it works:
&g
1 - 100 of 141 matches
Mail list logo
