From: Sven Van Asbroeck
[ Upstream commit 796a2665ca3e91ebaba7222f76fd9a035714e2d8 ]
On arm imx6, when opening the chip's netdev, the whole Linux
kernel intermittently hangs/freezes.
This is caused by a bug in the driver code which tests if pcie
interrupts are working correctly, using the softw
From: Sven Van Asbroeck
[ Upstream commit 796a2665ca3e91ebaba7222f76fd9a035714e2d8 ]
On arm imx6, when opening the chip's netdev, the whole Linux
kernel intermittently hangs/freezes.
This is caused by a bug in the driver code which tests if pcie
interrupts are working correctly, using the softw
From: Sven Van Asbroeck
[ Upstream commit 796a2665ca3e91ebaba7222f76fd9a035714e2d8 ]
On arm imx6, when opening the chip's netdev, the whole Linux
kernel intermittently hangs/freezes.
This is caused by a bug in the driver code which tests if pcie
interrupts are working correctly, using the softw
On Thu, 12 Nov 2020 15:47:41 -0500 Sven Van Asbroeck wrote:
> From: Sven Van Asbroeck
>
> On arm imx6, when opening the chip's netdev, the whole Linux
> kernel intermittently hangs/freezes.
>
> This is caused by a bug in the driver code which tests if pcie
> interrupts are working correctly, usi
From: Sven Van Asbroeck
On arm imx6, when opening the chip's netdev, the whole Linux
kernel intermittently hangs/freezes.
This is caused by a bug in the driver code which tests if pcie
interrupts are working correctly, using the software interrupt:
1. open: enable the software interrupt
2. open
On Mon, Jun 8, 2020 at 12:28 PM Qian Cai wrote:
>
> On Mon, Jun 08, 2020 at 12:00:11PM -0700, Kees Cook wrote:
> > On Mon, Jun 08, 2020 at 02:04:08PM +0800, kernel test robot wrote:
> > > The issue seems due to the lack of "-fsanitize-undefined-trap-on-error"
> > > in clang.
> >
> > Hm? No, that'
On Mon, Jun 08, 2020 at 12:00:11PM -0700, Kees Cook wrote:
> On Mon, Jun 08, 2020 at 02:04:08PM +0800, kernel test robot wrote:
> > The issue seems due to the lack of "-fsanitize-undefined-trap-on-error" in
> > clang.
>
> Hm? No, that's supported in Clang (at least as far back as Clang 9.)
>
> >
On Mon, Jun 08, 2020 at 02:04:08PM +0800, kernel test robot wrote:
> The issue seems due to the lack of "-fsanitize-undefined-trap-on-error" in
> clang.
Hm? No, that's supported in Clang (at least as far back as Clang 9.)
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the fi
setup_code |
0 | 13 ||
+-++++
If you fix the issue, kindly add following tag
Reported-by: kernel test robot
early console in setup code
BUG: kernel hang in
Hi all,
On Thu, 1 Nov 2018 09:13:07 +0800 kernel test robot
wrote:
>
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit b179f0826c6a13563c5ce0554c6da6748a1fa699
>
On Wed, Aug 1, 2018 at 3:31 PM, Ram Gupta wrote:
> I compiled standard 3.10 kernel on Centos 7.2. Once I boot with the
> compiled kernel it hangs with the message "early console in setup code
> Probing EDD (edd=off to disable)... ok". I need to make custom kernel but
> this kernel is standard wi
I compiled standard 3.10 kernel on Centos 7.2. Once I boot with the
compiled kernel it hangs with the message "early console in setup code
Probing EDD (edd=off to disable)... ok". I need to make custom kernel but
this kernel is standard without any code changes. This is on x86_64 bit
processor. H
st
[ 21.734553] test 3125 random rhlist add/delete operations
[ 21.813107] Started 10 threads, 0 failed, rhltable test returns 0
BUG: kernel hang in boot stage
# HH:MM RESULT GOOD
BAD GOOD_BUT_DIRTY DIRTY_NOT_BAD
git bisect start 7
ing concurrent rhashtable access from 10 threads
[ 21.577749] test 3125 add/delete pairs into rhlist
[ 21.734553] test 3125 random rhlist add/delete operations
[ 21.813107] Started 10 threads, 0 failed, rhltable test returns 0
BUG: kernel hang in boot stage
gt; | 0 | 0 | 1 |
> +------+++---+---+
>
> [9.996837] Freeing unused kernel memory: 68K
> [9.997637] rodata_test: all tests were successful
> /etc/rc
Hi Jens,
On Fri, Apr 27, 2018 at 06:52:58PM -0600, Jens Axboe wrote:
On 4/24/18 3:00 PM, kernel test robot wrote:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-linus
commit ed74ae
On 4/24/18 3:00 PM, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
> for-linus
>
> commit ed74ae03424684a6ad8a973c3fa727c6b4162432
> Author: Bart Va
cards
> [ 14.958301] fmc fake-design-for-testing-f001: Driver has no ID:
matches all
> [ 14.960428] fmc_chardev fake-design-for-testing-f001: Created misc
device "fake-design-for-testing-f001"
> BUG: kernel hang in boot stage
>
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 3be8828fc507cdafe7040a3dcf361a2bcd8e305b upstream.
Avoid that the recently introduced call_rcu() call in the SCSI core
triggers a double call_rcu() call.
Reported-by: N
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 3be8828fc507cdafe7040a3dcf361a2bcd8e305b upstream.
Avoid that the recently introduced call_rcu() call in the SCSI core
triggers a double call_rcu() call.
Reported-by: N
On Sun, 24 Dec 2017, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/pti
>
> commit 92a0f81d89571e3e8759366e050ee05cc545ef99
> Author: Thomas Gleixner
ache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] BRK [0x07cb7000, 0x07cb7fff] PGTABLE
[0.00] BRK [0x07cb8000, 0x07cb8fff] PGTABLE
[0.00] BRK [0x07cb9000, 0x07cb9fff] PGTABLE
[0.00] BRK [0x07cba000, 0x07cbafff] PGTABLE
BUG: kernel han
| 11 |
+-+++++
early console in setup code
BUG: kernel hang in early-boot stage, last printk: early console in setup code
Linux version 4.14.0-00111-g264d55b #73
Command line: root=/dev/ram0 hung_task_panic=1 debug
: selftest passed
[0.004000] ACPI: Core revision 20170728
BUG: kernel hang in boot stage
[0.00] Initmem setup node 0 [mem 0x1000-0x1ffdbfff]
[0.00] On node 0 totalpages: 130938
[0.00] DMA zone: 64 pages used for memmap
[0.00] DMA zone: 21 page
On Tue, Oct 24, 2017 at 4:59 PM, Andrey Konovalov wrote:
> Hi!
>
> While fuzzing the kernel with syzkaller I've been getting kernel hangs
> within the asix driver.
>
> On commit 6cff0a118f23b98c604a3604ea9de11338e24fbe (4.14-rc6+).
>
> As far as I can tell the issue is that asix_phy_reset() doesn'
Hi!
While fuzzing the kernel with syzkaller I've been getting kernel hangs
within the asix driver.
On commit 6cff0a118f23b98c604a3604ea9de11338e24fbe (4.14-rc6+).
As far as I can tell the issue is that asix_phy_reset() doesn't
enforce proper timeout.
asix_phy_reset() calls asix_mdio_read() in a
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 9c2fb296dde16a1bb81277be7b32cec881fe1153
Author: Kees Cook
AuthorDate: Mon Oct 16 20:01:58 2017 +0100
Commit: Mark Brown
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
commit d5923ebd7cd211e5925383296723b0fab857afe4
Merge: 11b1743a0d92d 6061efb6ee6fc
Author: Ingo Molnar
AuthorDate: Tue Aug 29 16:19:54 2017
Hi Guys,
I just found that sometimes v4.12-rc6 kernel hang happens during
booting, please see the following stack trace:
[ OK ] Listening on LVM2 poll daemon socket.
INFO: rcu_preempt detected stalls on CPUs/tasks:
0-...: (0 ticks this GP) idle=732/140/0
softirq=1182/1186 fqs
On Mon, May 08, 2017 at 08:13:37PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit e66267161971155a8b4756b4e17f2f2f82b9f842
> Author
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 6f58284e666261162b2c95fdd8608f5e247e9a38
Merge: 7fd97bca bf74b20
Author: Stephen Rothwell
AuthorDate: Mon Apr 10 10:06:42 20
On pe, 2017-04-07 at 01:23 +0200, Andrea Arcangeli wrote:
> synchronize_rcu/synchronize_sched/synchronize_rcu_expedited() will
> hang until its own workqueues are run. The i915 gem workqueues will
> wait on the struct_mutex to be released. So we cannot wait for a
> quiescent state using those rcu p
synchronize_rcu/synchronize_sched/synchronize_rcu_expedited() will
hang until its own workqueues are run. The i915 gem workqueues will
wait on the struct_mutex to be released. So we cannot wait for a
quiescent state using those rcu primitives while holding the
struct_mutex or it creates a circular
On Tue, Mar 28, 2017 at 05:07:09PM +0800, Fengguang Wu wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 857811a37129f5d2ba162d7be3986eff44724014
> Author:
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 857811a37129f5d2ba162d7be3986eff44724014
Author: Boqun Feng
AuthorDate: Wed Mar 1 23:01:38 2017 +0800
Commit: Ingo Molnar
On Fri, Mar 17, 2017 at 10:12:12PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 02a5c550b2738f2bfea8e1e00aa75944d71c9e18
> Author
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 02a5c550b2738f2bfea8e1e00aa75944d71c9e18
Author: Paul E. McKenney
AuthorDate: Wed Nov 2 17:25:06 2016 -0700
Commit: Paul
On Mon, 2016-10-24 at 10:13 +0800, Fengguang Wu wrote:
> Hi Andy,
>
> On Sat, Oct 22, 2016 at 07:40:14PM +0300, Andy Shevchenko wrote:
> > On Mon, 2016-09-05 at 18:15 +0300, Andy Shevchenko wrote:
> > > +Heikki
> > >
> > > On Sat, 2016-09-03 at 16:25 +0800, kernel test robot wrote:
> > > > Greeti
--
> -+
> >
> > boot_successes| 63 | 0 |
> > 0 |
> > boot_failures | 0 | 26 |
> > 27 |
> > BUG:kernel_hang_in_boot_stage | 0 | 26 |
> > 27 |
>
> +---++--
---
> > --
> > -+
> > >
> > > | 68af490b03 | a13e19cf3d |
> > > 6fe4da5401
> > > >
> >
> > +---+++-
> > --
> > -+
> > >
> > > boot_successes| 63 | 0 |
> > >
On 10/14, Andi Kleen wrote:
>On Fri, Oct 14, 2016 at 12:56:00PM +0800, Ye Xiaolong wrote:
>> On 10/14, Ye Xiaolong wrote:
>> >On 10/13, Andi Kleen wrote:
>> >>Andi Kleen writes:
>> >>
>> >>Any comments on this?
>> >>
>> >>I still cannot reproduce the failure unfortunately.
>> >>
>> >
>> >Btw, you
| 0 | 30 |
+-+++
Booting the kernel.
Elapsed time: 510
BUG: kernel hang in boot stage
Linux version 4.8.0-rc8-4-gca54678 #1
Command line: ip=vm-vp-quantal-i386-24::dhcp root=/dev/ram0 user=lkp
On Fri, Oct 14, 2016 at 12:56:00PM +0800, Ye Xiaolong wrote:
> On 10/14, Ye Xiaolong wrote:
> >On 10/13, Andi Kleen wrote:
> >>Andi Kleen writes:
> >>
> >>Any comments on this?
> >>
> >>I still cannot reproduce the failure unfortunately.
> >>
> >
> >Btw, you can try below commands to reproduce the
On 10/14, Ye Xiaolong wrote:
>On 10/13, Andi Kleen wrote:
>>Andi Kleen writes:
>>
>>Any comments on this?
>>
>>I still cannot reproduce the failure unfortunately.
>>
>
>Btw, you can try below commands to reproduce the error on your local
>host, they will download the necessary images and run QEMU:
On 10/13, Andi Kleen wrote:
>Andi Kleen writes:
>
>Any comments on this?
>
>I still cannot reproduce the failure unfortunately.
>
Btw, you can try below commands to reproduce the error on your local
host, they will download the necessary images and run QEMU:
git clone git://git.kernel.org
On 10/13, Andi Kleen wrote:
>Andi Kleen writes:
>
>Any comments on this?
>
>I still cannot reproduce the failure unfortunately.
oh, sorry, missed you mail before, I'll try the tests you mentioned and
provide results later.
Thanks,
Xiaolong
>
>
>> Could you do two tests for me:
>>
>> - Enable CO
Andi Kleen writes:
Any comments on this?
I still cannot reproduce the failure unfortunately.
> Could you do two tests for me:
>
> - Enable CONFIG_MICROCODE_INTEL and see if it boots then
>
> - Add CONFIG_DEBUG_INFO to the config.
> Add -s to the qemu command line and boot again. Then when it h
On Sat, Oct 01, 2016 at 10:59:38AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> https://github.com/0day-ci/linux
> Andi-Kleen/x86-Report-Intel-platform_id-in-proc-cpuinfo/20160924-100841
> commit 811565123a194d9cc0b490719bef761e1730dbf4 ("x86: Report Intel
> platfo
apsed time: 310
BUG: kernel hang in early-boot stage, last printk: Probing EDD (edd=off to
disable)... ok
Linux version 4.8.0-rc7-1-g8115651 #1
Command line: ip=vm-lkp-st01-openwrt-ia32-12::dhcp root=/dev/ram0 user=lkp
job=/lkp/scheduled/vm-lkp-st01-openwrt-ia32-12/boot-1-openwrt-i386-2016
| 0 |
| boot_failures | 0 | 26 | 27 |
| BUG:kernel_hang_in_boot_stage | 0 | 26 | 27 |
+---++++
Booting the kernel.
Elapsed time: 500
BUG: kernel hang in boot stage
Linux version
Hi Tejun,
> Patches just got merged into mainline. Please let me know if the
> current git master doesn't fix the issue.
Seems to have worked - I don't see the kernel hangs anymore. What remains
are problems with DRI/DRM, but I will report separately.
Thanks a lot
Norbert
On Wed, Dec 09, 2015 at 02:22:53PM +0100, Michal Hocko wrote:
> [CCing Tejun]
>
> Seems to be the same issue as reported here?
> http://lkml.kernel.org/r/20151208145851.GJ9837@bark
Patches just got merged into mainline. Please let me know if the
current git master doesn't fix the issue.
Thanks.
[CCing Tejun]
Seems to be the same issue as reported here?
http://lkml.kernel.org/r/20151208145851.GJ9837@bark
On Tue 08-12-15 08:53:52, Norbert Preining wrote:
> Dear all
>
> (please Cc)
>
> running 4.4-rc4 (written as rc3+ but only the tag commit is missing),
> but I think also earlier in the
Wow,
OK. I'll try to debug it at this end if I can ...
Jeff
On 12/7/15, Norbert Preining wrote:
> Hi Jeff,
>
>> I am seeing this too but I think its related to Centos 7 not the build.
>
> Here I am running:
> Debian sid
> gcc (Debian 5.3.1-2) 5.3.1 20151206
>
>> > WARNING: CPU: 1 P
Hi Jeff,
> I am seeing this too but I think its related to Centos 7 not the build.
Here I am running:
Debian sid
gcc (Debian 5.3.1-2) 5.3.1 20151206
> > WARNING: CPU: 1 PID: 14 at kernel/cgroup_pids.c:97
> > pids_cancel.constrprop.8+0x2a
> > Modules linked in:
> > ...
> > CP
I am seeing this too but I think its related to Centos 7 not the build.
On 12/7/15, Norbert Preining wrote:
> Dear all
>
> (please Cc)
>
> running 4.4-rc4 (written as rc3+ but only the tag commit is missing),
> but I think also earlier in the rc releases, I occasionally see hangs
> on shutdown. N
Dear all
(please Cc)
running 4.4-rc4 (written as rc3+ but only the tag commit is missing),
but I think also earlier in the rc releases, I occasionally see hangs
on shutdown. Nothing works anymore, but this time at least there
was some output on the console.
Manually copied from screen:
WARNING:
On Wed, Nov 18, 2015 at 11:00:53PM +0800, Rui Wang wrote:
> The machine hang completely with the following message on the console:
>
> [ 487.777538] BUG: unable to handle kernel NULL pointer dereference at
> 0060
> [ 487.777554] IP: [] _raw_spin_lock+0xe/0x30
> [ 487.777557] PGD 42
The machine hang completely with the following message on the console:
[ 487.777538] BUG: unable to handle kernel NULL pointer dereference at
0060
[ 487.777554] IP: [] _raw_spin_lock+0xe/0x30
[ 487.777557] PGD 42e9f7067 PUD 42f2fa067 PMD 0
[ 487.777560] Oops: 0002 [#1] SMP
...
[
ister entities
> > from media_device_unregister(), and let drivers take care
> > of it. Drivers need to unregister to cover the case of
> > module removal. This patch fixes the problem by deleting
> > the entity list walk to call media_device_unregister_entity()
> > f
nregister to cover the case of
> module removal. This patch fixes the problem by deleting
> the entity list walk to call media_device_unregister_entity()
> for each entity. With this fix there is no kernel hang after
> a sequence of device insertions followed by removal.
>
> Signed-
f
> module removal. This patch fixes the problem by deleting
> the entity list walk to call media_device_unregister_entity()
> for each entity. With this fix there is no kernel hang after
> a sequence of device insertions followed by removal.
>
> Signed-off-by: Shuah Khan
This is M
all media_device_unregister_entity()
for each entity. With this fix there is no kernel hang after
a sequence of device insertions followed by removal.
Signed-off-by: Shuah Khan
---
drivers/media/media-device.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/media/media-device.c b/driv
On Mon 2015-09-21 17:33:21, Sheng Yang wrote:
> Thank you Paul! That's exactly the issue I met. I've read the whole
> thread and got a general idea of the issue.
>
> I try to summarize it and please correct me if I'm wrong:
>
> 1. The issue is the result of kill_bdev() when connection has been cu
Hi,
Thanks for the pointer Paul.
On Mon, Sep 21, 2015 at 05:33:21PM -0700, Sheng Yang wrote:
> Thank you Paul! That's exactly the issue I met. I've read the whole
> thread and got a general idea of the issue.
>
> I try to summarize it and please correct me if I'm wrong:
>
> 1. The issue is the
Thank you Paul! That's exactly the issue I met. I've read the whole
thread and got a general idea of the issue.
I try to summarize it and please correct me if I'm wrong:
1. The issue is the result of kill_bdev() when connection has been cut
when IO is still flying.
2. Other block devices driver d
Thank you Wouter!
(Add back lkml since I got another kernel issue...)
In fact I just hit another issue with nbd-server/client on the same
machine. The following commands hang after a while:
dd if=/dev/zero of=./test
When process hanging, dd/nbd-server are no long showing in high cpu
utilization
Hi, Markus,
I've experienced kernel bug and system hang regarding using
nbd-client/server on the same machine. Kernel verison is v4.2.
I know http://nbd.sourceforge.net/ said:
"Please note that read-write nbd with client and server on the same
machine is a bad idea: expect deadlock within seconds
Hi,
On 06/07/15 15:31, Roger Quadros wrote:
Users of find_cable_index_by_name() will cause a kernel hang
as the while loop counter is never incremented and end condition
is never reached.
Fixes: commit 73b6ecdb93e8 ("extcon: Redefine the unique id of supported external
connectors wi
Users of find_cable_index_by_name() will cause a kernel hang
as the while loop counter is never incremented and end condition
is never reached.
Fixes: commit 73b6ecdb93e8 ("extcon: Redefine the unique id of supported
external connectors without 'enum extcon' type")
Cc: Greg K
3.13.11-ckt12 -stable review patch. If anyone has any objections, please let
me know.
--
From: Quentin Casasnovas
If val_count is zero we return -EINVAL with map->lock_arg locked, which
will deadlock the kernel next time we try to acquire this lock.
This was introduced by 6ae
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Quentin Casasnovas
Fixes commit 2f06fa04cf35da5c24481da3ac84a2900d0b99c3 which was an
incorrect backported version of commit
d6b41cb06044a7d895db82bdd54f6e4219970510 upstream.
If val_count is
From: Quentin Casasnovas
3.12-stable review patch. If anyone has any objections, please let me know.
===
If val_count is zero we return -EINVAL with map->lock_arg locked, which
will deadlock the kernel next time we try to acquire this lock.
In 3.12, this was introduced by a0b8d8d9
3.13-stable review patch. If anyone has any objections, please let me know.
--
From: Gregory CLEMENT
commit dc4910d9e93f8cc56b190dd8fc9e789135978216 upstream.
When pci_base is accessed whereas it has not been properly mapped by
of_iomap() the kernel hang. The check of this
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Gregory CLEMENT
commit dc4910d9e93f8cc56b190dd8fc9e789135978216 upstream.
When pci_base is accessed whereas it has not been properly mapped by
of_iomap() the kernel hang. The check of this
Ok, opened up: http://bugzilla.kernel.org/show_bug.cgi?id=9026
and brought it up to date with the discussion and David's comments on this
thread. Timo, please feel free to revisit this later and update us when you find
the time to do so.
[ BTW I think the "add CC:" thing in bugzilla is broken, I w
On 9/16/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
> Hi Timo,
>
>
> On 7/15/07, Timo Lindemann <[EMAIL PROTECTED]> wrote:
> > To sum this up:
> >
> > the userspace 2.6.20.6 (the "good" kernel) and 2.6.22 (the "bad" kernel)
> > were compiled in is exactly the same setup. I recompiled "good" to che
Hi Timo,
On 7/15/07, Timo Lindemann <[EMAIL PROTECTED]> wrote:
> To sum this up:
>
> the userspace 2.6.20.6 (the "good" kernel) and 2.6.22 (the "bad" kernel)
> were compiled in is exactly the same setup. I recompiled "good" to check
> for that, earlier, but "good" also works then.
>
> "good" does
On Sunday 15 July 2007, Satyam Sharma wrote:
> On 7/15/07, Timo Lindemann <[EMAIL PROTECTED]> wrote:
> > It is just odd that up to (not including) the 2.6.21-series every kernel
> > boots, and after that, they just freeze.
On *your* system, note -- all my OHCI+PCI systems that have
been upgraded
To sum this up:
the userspace 2.6.20.6 (the "good" kernel) and 2.6.22 (the "bad" kernel)
were compiled in is exactly the same setup. I recompiled "good" to check
for that, earlier, but "good" also works then.
"good" does not exhibit the printks I placed in the section (the same
ones I did for "ba
On 7/15/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
On 7/15/07, Timo Lindemann <[EMAIL PROTECTED]> wrote:
[...]
> >>> after this, kernel apparently goes into busy waiting (fans gradually
> >>> turn louder) and hangs indefinitely. I have also made sure that writel
> >>> (in linux/include/asm/io.h
On 7/15/07, Timo Lindemann <[EMAIL PROTECTED]> wrote:
David Brownell wrote:
> On Thursday 12 July 2007, Satyam Sharma wrote:
>
> Note that hangs in that file almost always mean "your BIOS is goofy".
> Hunt for BIOS settings related to USB, and change them.
This laptop's BIOS only offers "legacy s
David Brownell wrote:
> On Thursday 12 July 2007, Satyam Sharma wrote:
>
> Note that hangs in that file almost always mean "your BIOS is goofy".
> Hunt for BIOS settings related to USB, and change them.
This laptop's BIOS only offers "legacy support" enabled or disabled,
both of which lead to fro
On Thursday 12 July 2007, Satyam Sharma wrote:
>
> > [2.] The version 2.6.22 of the linux kernel hangs when initializing the
> > integrated ohci controller of the nvidia MCP51 chipset (pci device ids
> > vendor:product == 10de:26d). I have traced through various printks that
> > pci_init calls pci
Hi Timo,
Thanks for your report!
On 7/12/07, Timo Lindemann <[EMAIL PROTECTED]> wrote:
a problem report to something giving me a real headache:
[2.] The version 2.6.22 of the linux kernel hangs when initializing the
integrated ohci controller of the nvidia MCP51 chipset (pci device ids
vendo
Hi all,
a problem report to something giving me a real headache:
[1.] Kernel hangs when initializing ohci-controller
[2.] The version 2.6.22 of the linux kernel hangs when initializing the
integrated ohci controller of the nvidia MCP51 chipset (pci device ids
vendor:product == 10de:26d). I have
, it boots on every other comp but my old
laptop.
After that kernel hang, I recompiled a few times, tried 2.6.16.52, 2.6.21.1 and
2.6.16.21-ck2 with dynticks. Each had the bug. I also booted with every
bootcode
listed in kernel-parameters.txt as "BUGS=x86-32", and it still hung at tha
In my notebook, a HP dv9205us, the kernel hang when I read the cmos clock.
To reproduce it, I just call hwclock one or two times. The kernel
don't show any oops. Just hang.
Another way to reproduce it, is 'while [ 1 ]; do cat /proc/driver/rtc;
done'. With some seconds, the kernel
On Thu, May 17, 2007 at 10:49:45AM +1000, Benjamin Herrenschmidt wrote:
>
> > I do not know why sk_buff->head would be null, or
> > would be set in a racy kind of way, or why the rt patches
> > would cause this. But the evidence implicates that.
>
> Would it be possible that a locking bug in spid
> I do not know why sk_buff->head would be null, or
> would be set in a racy kind of way, or why the rt patches
> would cause this. But the evidence implicates that.
Would it be possible that a locking bug in spidernet would cause it
under some circumstances to get a stale skb pointer ?
Ben.
-
(resending , Owa-san was cut from cc list!??)
Hi,
On Tue, May 15, 2007 at 08:09:02PM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2007-05-15 at 17:47 +0900, Tsutomu OWA wrote:
> > I encountered the following error when doing netperf from other machine
> > to Celleb running RT kernel. PREEPT
> On Thu, 22 Feb 2007 12:20:06 -0600 Kumar Gala <[EMAIL PROTECTED]> wrote:
> + if ((gfp_mask & (__GFP_FS|__GFP_IO)) != (__GFP_FS|__GFP_IO)) {
>
> The second seems to make more sense. I tested with the first last
> night which didn't help.
>
> With the proper patch in place things look go
Not that it'll help much: the VM calls throttle_vm_writeout()
for GFP_NOIO
and GFP_NOFS allocations, which is a bug. Because if the caller
holds
locks which prevent filesystem or IO progress, we deadlock.
I'll fix the VM if someone else fixes USB ;)
What else needs to be fixed?
Would be
On Feb 21, 2007, at 3:31 PM, Andrew Morton wrote:
On Wed, 21 Feb 2007 16:22:17 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
On Wed, 21 Feb 2007, Andrew Morton wrote:
It seems like usb-storage and aio are completely off in the weeds.
Ideas?
It seems usb-storage should remove some kmal
On Wed, 21 Feb 2007 16:50:23 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
> > + if ((gfp_mask & (__GFP_FS|__GFP_IO)) != (__GFP_FS|__GFP_IO)) {
>
> Is that really the correct test? I don't know enough about the memory
> management subsystem to say one way or the other. What's special abo
On Wed, 21 Feb 2007, Andrew Morton wrote:
> On Wed, 21 Feb 2007 16:22:17 -0500 (EST)
> Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 21 Feb 2007, Andrew Morton wrote:
> >
> > > > > It seems like usb-storage and aio are completely off in the weeds.
> > > > > Ideas?
> > > >
> > > > It se
On Wed, 21 Feb 2007 16:22:17 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
> On Wed, 21 Feb 2007, Andrew Morton wrote:
>
> > > > It seems like usb-storage and aio are completely off in the weeds.
> > > > Ideas?
> > >
> > > It seems usb-storage should remove some kmalloc and use mempool()
On Wed, 21 Feb 2007, Andrew Morton wrote:
> > > It seems like usb-storage and aio are completely off in the weeds.
> > > Ideas?
> >
> > It seems usb-storage should remove some kmalloc and use mempool() for
> > urb... Is someone working on this? And idea?
>
> I think Pete said that we're supp
On Thu, 22 Feb 2007 05:18:45 +0900
OGAWA Hirofumi <[EMAIL PROTECTED]> wrote:
> Kumar Gala <[EMAIL PROTECTED]> writes:
>
> >>> I usually run the following twice to get the hang state:
> >>>
> >>> time ./trunc_test bar 1 &
> >>> time ./trunc_test baz 1 &
> >>>
> >>> I was wondering
Kumar Gala <[EMAIL PROTECTED]> writes:
>>> I usually run the following twice to get the hang state:
>>>
>>> time ./trunc_test bar 1 &
>>> time ./trunc_test baz 1 &
>>>
>>> I was wondering if anyone had any suggestions on what to poke at next
>>> to try and figure out what is going
1 - 100 of 153 matches
Mail list logo
