Hi,
I have an Intel NUC D54250WYK which no longer shuts down properly after
moving from 5.9.16 to 5.10.4, because systemd hangs. The kernel logs
make me beleive it is likely a locking issue in either DRM or ALSA or
both. Relevant messages which I could extract from the journal:
Jan 05 22:21:38
Hi,
On Wed, Jan 16, 2008 at 09:02:05AM +0800, Dave Young wrote:
> The rfcomm tty device will possibly retain even when conn is down,
> and sysfs doesn't support zombie device moving, so this patch
> move the tty device before conn device is destroyed.
>
> Signed-off-by: Dave Young <[EMAIL
On Mon, Jan 07, 2008 at 06:10:29PM -0600, Robert Hancock wrote:
> Gabor, I just noticed you said that it worked OK in 2.6.20, yet 2.6.22
> fails. 2.6.20 had ADMA support as well, so I wonder what change started
> causing the problem. Would it be possible for you to do a git bisect (or
> at
On Thu, Jan 10, 2008 at 09:11:17AM +0800, Dave Young wrote:
> For bluetooth device_move, the only child device of hci_conn dev is
> the rfcomm tty_dev. How about the following patch, please verify :
There is now no oops, instead the keyboard becomes almost completely
unresponsible when I switch
On Thu, Jan 10, 2008 at 09:11:17AM +0800, Dave Young wrote:
For bluetooth device_move, the only child device of hci_conn dev is
the rfcomm tty_dev. How about the following patch, please verify :
There is now no oops, instead the keyboard becomes almost completely
unresponsible when I switch
On Mon, Jan 07, 2008 at 06:10:29PM -0600, Robert Hancock wrote:
Gabor, I just noticed you said that it worked OK in 2.6.20, yet 2.6.22
fails. 2.6.20 had ADMA support as well, so I wonder what change started
causing the problem. Would it be possible for you to do a git bisect (or
at
Hi,
On Wed, Jan 09, 2008 at 06:16:02PM +0900, Tejun Heo wrote:
> Please confirm the attached patch fixes the oops. I'll separate it into
> two patches and forward them to Greg. But bluetooth code also needs to
> be updated such that it moves the refcommX device before killing the
> connection
Hi,
On Wed, Jan 09, 2008 at 06:16:02PM +0900, Tejun Heo wrote:
Please confirm the attached patch fixes the oops. I'll separate it into
two patches and forward them to Greg. But bluetooth code also needs to
be updated such that it moves the refcommX device before killing the
connection
On Tue, Jan 08, 2008 at 06:42:43PM +0900, Tejun Heo wrote:
> Thanks. Please apply the attached patch and report the oops.
Jan 8 14:23:29 twister kernel: XXX: moving /devices/virtual/tty/rfcomm0 under
/devices/pci:00/:00:02.0/usb1/1-3/1-3:1.0/hci0/acl001BAFE1624D/tty
Jan 8 14:23:29
On Tue, Jan 08, 2008 at 06:42:43PM +0900, Tejun Heo wrote:
Thanks. Please apply the attached patch and report the oops.
Jan 8 14:23:29 twister kernel: XXX: moving /devices/virtual/tty/rfcomm0 under
/devices/pci:00/:00:02.0/usb1/1-3/1-3:1.0/hci0/acl001BAFE1624D/tty
Jan 8 14:23:29
On Tue, Jan 08, 2008 at 12:24:05AM +0900, Tejun Heo wrote:
> Does the attached patch fix the problem?
No, it still oopses.
Gabor
--
-
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of
Hi,
On Sat, Jan 05, 2008 at 07:50:39AM +, Al Viro wrote:
> Could you stick
> if (!parent->d_inode)
> printk(KERN_WARNING "sysfs locking blows: %s",
> parent->d_name.name);
> right before
> mutex_lock(>d_inode->i_mutex);
>
Hi,
On Fri, Jan 04, 2008 at 09:05:42AM +0800, Dave Young wrote:
> Could you try the patch (on 2.6.24-rc6) following and check the debug
> messages?
>
> diff -upr linux/net/bluetooth/rfcomm/tty.c
> linux.new/net/bluetooth/rfcomm/tty.c
> --- linux/net/bluetooth/rfcomm/tty.c 2008-01-04
On Tue, Jan 08, 2008 at 12:24:05AM +0900, Tejun Heo wrote:
Does the attached patch fix the problem?
No, it still oopses.
Gabor
--
-
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of
On Wed, Jan 02, 2008 at 04:16:42PM +0100, Gabor Gombas wrote:
> So the patch referenced above does not help. But I've found a very easy
> way to trigger the bug:
>
> - do a "cat /dev/zero > /dev/rfcomm0"
> - switch the phone off
> - switch the phone on, and the ker
On Wed, Jan 02, 2008 at 04:16:42PM +0100, Gabor Gombas wrote:
So the patch referenced above does not help. But I've found a very easy
way to trigger the bug:
- do a cat /dev/zero /dev/rfcomm0
- switch the phone off
- switch the phone on, and the kernel oopses
FYI I also remember having
On Sat, Dec 29, 2007 at 04:07:04PM +0800, Dave Young wrote:
> Please try the -mm tree kernel, might have been fixed by :
> http://lkml.org/lkml/2007/11/18/141
Heh, it seems talking about a bug makes it trigger:
Jan 2 16:05:45 twister kernel: Unable to handle kernel NULL pointer
dereference at
On Sat, Dec 29, 2007 at 04:07:04PM +0800, Dave Young wrote:
> Please try the -mm tree kernel, might have been fixed by :
> http://lkml.org/lkml/2007/11/18/141
I've applied the patch on top of 2.6.24-rc6 (I don't want to run -mm
kernels on this machine). We'll see what happens.
Gabor
--
On Sat, Dec 29, 2007 at 04:07:04PM +0800, Dave Young wrote:
Please try the -mm tree kernel, might have been fixed by :
http://lkml.org/lkml/2007/11/18/141
I've applied the patch on top of 2.6.24-rc6 (I don't want to run -mm
kernels on this machine). We'll see what happens.
Gabor
--
On Sat, Dec 29, 2007 at 04:07:04PM +0800, Dave Young wrote:
Please try the -mm tree kernel, might have been fixed by :
http://lkml.org/lkml/2007/11/18/141
Heh, it seems talking about a bug makes it trigger:
Jan 2 16:05:45 twister kernel: Unable to handle kernel NULL pointer
dereference at
Hi,
Just FYI I've tried to enable ADMA again (now running 2.6.24-rc6) but
the bug is still present:
Jan 1 16:11:21 host kernel: ata7: EH in ADMA mode, notifier 0x0 notifier_error
0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0
Jan 1 16:11:21 host kernel: ata7: CPB 0:
Hi,
Just FYI I've tried to enable ADMA again (now running 2.6.24-rc6) but
the bug is still present:
Jan 1 16:11:21 host kernel: ata7: EH in ADMA mode, notifier 0x0 notifier_error
0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0
Jan 1 16:11:21 host kernel: ata7: CPB 0:
Hi,
I'm using my phone as a GPRS modem over Bluetooth. Sometimes Bluetooth
on the phone seems to stall and the phone has to be switched off & on to
get it back to a sane state. During this I sometimes get the following
Oops (this is kernel 2.6.24-rc6 on x86_64):
Dec 28 17:52:11 host kernel:
Hi,
I'm using my phone as a GPRS modem over Bluetooth. Sometimes Bluetooth
on the phone seems to stall and the phone has to be switched off on to
get it back to a sane state. During this I sometimes get the following
Oops (this is kernel 2.6.24-rc6 on x86_64):
Dec 28 17:52:11 host kernel:
On Tue, Oct 16, 2007 at 01:55:07PM -0700, [EMAIL PROTECTED] wrote:
> why is this any different from the external enclosures? they have always
> appeared as the type of device that connects them to the motherboard, (and
> even with SCSI, there are some controllers that don't generate sdX
On Tue, Oct 16, 2007 at 01:55:07PM -0700, [EMAIL PROTECTED] wrote:
why is this any different from the external enclosures? they have always
appeared as the type of device that connects them to the motherboard, (and
even with SCSI, there are some controllers that don't generate sdX devices)
On Wed, Sep 12, 2007 at 03:37:44PM -0500, Brent Casavant wrote:
> System V shmem is right out because the IPC key is publicly
> visible and there is no combination of permissions which
> will allow sharing the segment with just one other process
> (or at least just one other user). To my
On Wed, Sep 12, 2007 at 03:37:44PM -0500, Brent Casavant wrote:
System V shmem is right out because the IPC key is publicly
visible and there is no combination of permissions which
will allow sharing the segment with just one other process
(or at least just one other user). To my knowledge
Hi,
On Tue, Aug 14, 2007 at 06:30:28PM +0900, Tejun Heo wrote:
> Hmmm... That's timeout on cache flush, indicative of failing disk.
> Please post the result of 'smartctl -a /dev/sdc'.
Ok, so something is fishy in 2.6.22 wrt. SMART.
First, booting back to 2.6.20.5 I confirmed that SMART works
Hi,
On Tue, Aug 14, 2007 at 06:30:28PM +0900, Tejun Heo wrote:
Hmmm... That's timeout on cache flush, indicative of failing disk.
Please post the result of 'smartctl -a /dev/sdc'.
Ok, so something is fishy in 2.6.22 wrt. SMART.
First, booting back to 2.6.20.5 I confirmed that SMART works
On Tue, Aug 14, 2007 at 06:30:28PM +0900, Tejun Heo wrote:
> Hmmm... That's timeout on cache flush, indicative of failing disk.
> Please post the result of 'smartctl -a /dev/sdc'.
Will do when I get home. Note however that this only occurs in ADMA
mode. It never occured with 2.6.20 and it never
On Tue, Aug 14, 2007 at 06:30:28PM +0900, Tejun Heo wrote:
Hmmm... That's timeout on cache flush, indicative of failing disk.
Please post the result of 'smartctl -a /dev/sdc'.
Will do when I get home. Note however that this only occurs in ADMA
mode. It never occured with 2.6.20 and it never
Hi,
Since I have upgraded to 2.6.22.1 from 2.6.20 I have problems with
Samsung disks. Sometimes the disks stall for about half a minute and
then I have these messages in the logs:
Aug 6 20:10:11 twister kernel: ata7: EH in ADMA mode, notifier 0x0
notifier_error 0x0 gen_ctl 0x1501000 status
Hi,
Since I have upgraded to 2.6.22.1 from 2.6.20 I have problems with
Samsung disks. Sometimes the disks stall for about half a minute and
then I have these messages in the logs:
Aug 6 20:10:11 twister kernel: ata7: EH in ADMA mode, notifier 0x0
notifier_error 0x0 gen_ctl 0x1501000 status
On Mon, Jun 25, 2007 at 03:41:44PM +0200, Tomasz Kłoczko wrote:
> Sorry but skype does not for me after switching to ALSA (on skype cfg
> level). Probably ALSA developers can explain why :>
> All above on fresh FC6 and 1.3.53 skype.
$ dpkg -l | grep skype
ii skype
On Mon, Jun 25, 2007 at 01:36:23PM +0200, Tomasz Kłoczko wrote:
> ALSA still does not provides good soud devices virtualization for more then
> one application. Each day I'm using bludy words when I'm try to use skype
> which oppens /dev/mixer [...]
Not true anymore:
skype 32381 gombasg
On Mon, Jun 25, 2007 at 01:36:23PM +0200, Tomasz Kłoczko wrote:
ALSA still does not provides good soud devices virtualization for more then
one application. Each day I'm using bludy words when I'm try to use skype
which oppens /dev/mixer [...]
Not true anymore:
skype 32381 gombasg mem
On Mon, Jun 25, 2007 at 03:41:44PM +0200, Tomasz Kłoczko wrote:
Sorry but skype does not for me after switching to ALSA (on skype cfg
level). Probably ALSA developers can explain why :
All above on fresh FC6 and 1.3.53 skype.
$ dpkg -l | grep skype
ii skype
38 matches
Mail list logo
