rs I found were u32),
the passkeys "00" to "967295" are slightly more probable than
"967296" to "99".
If my math is right (which I doubt), the difference in probability
for both entities is 4294:4293.
> Do we care?
I, personally, don't (y
From: Stefan Seyfried
The USB control messages require DMA to work. We cannot pass
a stack-allocated buffer, as it is not warranted that the
stack would be into a DMA enabled area.
Signed-off-by: Stefan Seyfried
---
This fixes at least dvb-usb-technisat-usb2 for me, but probably
the other
Hi Chris,
this fixes the problem for me, thanks!
Tested-by: Stefan Seyfried
Am 15.01.2017 um 13:58 schrieb Chris Wilson:
> intel_display_resume() may be called without a atomic state to restore,
> i.e. dev_priv->modeset_reset_restore state is NULL. One such case is
> following a li
rsive faults), so I doubt
this is the commit to revert, but apparently it still needs some more fixes.
Thanks,
Stefan
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
Am 08.07.2015 um 22:09 schrieb Stefan Seyfried:
> this is on a Thinkpad X200s, 5 years old and working fine, until 4.2rc1
> came along.
>
> With that booted, I do not have a WiFi card anymore, it doesn't even
> appear in "lspci" output.
> From diffing the dmesg&
Hi Ming,
Am 04.06.2015 um 12:24 schrieb Ming Lei:
> On Thu, Jun 4, 2015 at 5:11 PM, Stefan Seyfried
> wrote:
>> I can reproduce the backtrace after a reboot once (subsequent modprobe/rmmod
>> loop
>> do not complain anymore), but not the OOPS.
>
> One fix[1] was
t once (subsequent modprobe/rmmod
loop
do not complain anymore), but not the OOPS.
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unterneh
r failure, but any
> number of terrible things could happen now.
>
> FWIW, this will affect things other than KVM. For example, SIGKILL
> sent while a process is sleeping in that two-instruction window won't
> work.
>
> Takashi, can you re-send your patch so
x,0x78(%rsp)
0x816834c3 <+35>:callq 0x810504e0
0xffff816834c8 <+40>:jmpq 0x816836d0
End of assembler dump.
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
O
41d
r12 = 8801013d7f88
bx = 8168140d
r9 = 7ffa355bd470
ip = 7ffa32dc86f7
sp = 7fffa55f1748
looks somehow legit, to my totally untrained eye (ip and sp actually).
I'm off to bed now (01:20 around here ;), will be back in about 7 hours.
Best regards,
Stefan
--
Stefan S
is this userspace memory? It's not in the dump I have.
This issue is the first I have seen where having a full dump would be
really helpful apart from cosmetic reasons...
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Voh
crash
dump of 4.0-rc3 is at http://paste.opensuse.org/48196621
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubs
VIRT_TIME_ACCOUNTING is not set
CONFIG_PARAVIRT_CLOCK=y
So yes, PARAVIRT is enabled.
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner /
Am 18.03.2015 um 22:21 schrieb Andy Lutomirski:
> On Wed, Mar 18, 2015 at 2:12 PM, Stefan Seyfried
> wrote:
>> Am 18.03.2015 um 21:51 schrieb Andy Lutomirski:
>>> On Wed, Mar 18, 2015 at 1:05 PM, Stefan Seyfried
>>> wrote:
>>
>>>>> The r
Am 18.03.2015 um 21:51 schrieb Andy Lutomirski:
> On Wed, Mar 18, 2015 at 1:05 PM, Stefan Seyfried
> wrote:
>>> The relevant thread's stack is here (see ti in the trace):
>>>
>>> 8801013d4000
>>>
>>> It could be interesting to see what&
18, 2015 at 12:03 PM, Stefan Seyfried
> wrote:
>> Hi all,
>>
>> first, I'm kind of happy that I'm not the only one seeing this, and
>> thus my beloved Thinkpad can stay for a bit longer... :-)
>>
>> Then, I'm mostly an amateur when it comes
m 19:03 schrieb Andy Lutomirski:
> On Wed, Mar 18, 2015 at 10:46 AM, Takashi Iwai wrote:
>> At Wed, 18 Mar 2015 18:43:52 +0100,
>> Takashi Iwai wrote:
>>>
>>> At Wed, 18 Mar 2015 15:16:42 +0100,
>>> Takashi Iwai wrote:
>>>>
>>>> At Sun, 15 M
enSUSE Tumbleweed, so the backtrace is all I have for now.
Any hints?
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vo
Am 03.02.2015 um 22:50 schrieb Jens Axboe:
> On 02/03/2015 12:14 PM, Jens Axboe wrote:
>> On 02/03/2015 12:13 PM, Stefan Seyfried wrote:
>>> Am 29.01.2015 um 13:17 schrieb Ming Lei:
>>>> This reverts commit 76d697d10769048e5721510100bf3a9413a56385.
>>> The r
ng my USB stick crashes the kernel" problem
today and came to this very commit.
The revert is not yet in Linus' tree (but it should get there before
3.19 is released, or all USB-stick users will be unhappy).
Best regards,
Stefan
> Reported-by: Bart Van Assche
> Signe
Hi Takashi,
yes, this no longer crashes. No real-world test yet, but the obvious
crash is gone. Thanks!
Am 07.11.2014 um 14:22 schrieb Takashi Iwai:
> At Fri, 07 Nov 2014 12:10:46 +0100,
> Stefan Seyfried wrote:
>>
>> Hi all,
>>
>> since 3.18-rc1, setting up a PPP
Am 07.11.2014 um 12:56 schrieb Stefan Seyfried:
> Hi Paul,
>
> Am 07.11.2014 um 12:53 schrieb Paul Bolle:
>> Wild guess: is CONFIG_RCU_NOCB_CPU perhaps set in your
>> v3.18-rc3 .config?
>
> Yes it is:
> tux@linux:~> zgrep CONFIG_RCU_NOCB_CPU /proc/
Hi Paul,
Am 07.11.2014 um 12:53 schrieb Paul Bolle:
> On Fri, 2014-11-07 at 12:10 +0100, Stefan Seyfried wrote:
>> I bisected the issue multiple times and always arrived at
>>
>> # first bad commit: [d6dd50e07c5bec00db2005969b1a01f8ca3d25ef] Merge branch
>>
ric]
[ 164.453327] [] do_vfs_ioctl+0x2e7/0x4c0
[ 164.453327] [] SyS_ioctl+0x81/0xa0
[ 164.453327] [] system_call_fastpath+0x16/0x1b
[ 164.453327] [<7f4502d87397>] 0x7f4502d87397
I have a crashdump of the kernel, but given this is easily reproducible, I doubt
that I need to send this to
From: Stefan Seyfried
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 893d6f0..eeaf3e7 100644
--- a/Makefile
+++ b/Makefile
@@ -606,7 +606,7 @@ ifdef CONFIG_CC_STACKPROTECTOR_REGULAR
stackp-flag := -fstack-protector
ifeq ($(call
Hi Greg,
in order to avoid such regressions in the future, a comment in
the source and a note in the Kconfig help text might be useful
This patch is against
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-next
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant
From: Stefan Seyfried
The recent regression about NetMos 9835 Multi-I/O boards indicates
that comment pointing to the parport_serial driver could be helpful.
Signed-off-by: Stefan Seyfried
---
drivers/tty/serial/8250/8250_pci.c | 6 ++
drivers/tty/serial/8250/Kconfig| 2 ++
2 files
ee which problem it solves, but
it definitely breaks the additional ports on my multi-i/o board.
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF:
Hi all,
I hate to say it, but this regression from 3.9 is still present in
3.10-rc7 :-(
Am 19.06.2013 11:02, schrieb Stefan Seyfried:
> The suspend/resume failure is easily reproduced by
>
> * booting with "init=/bin/bash no_console_suspend"
> * mount /sys
> * ec
uld try to take a picture of the panic, but it looked not really
directly related, more like a stack overflow after too many errors or
something like that (it also takes a few seconds after resume for the
machine to panic).
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant &
= RESETTING
[ 466.811030] mei_me 0000:00:03.0: reset: init clients timeout hbm_state = 1.
[ 466.811044] mei_me :00:03.0: unexpected reset: dev_state = RESETTING
So it is not yet fixed, unfortunately.
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer --
Am 03.06.2013 21:48, schrieb Frederic Weisbecker:
> On Mon, Jun 03, 2013 at 11:47:17AM +0200, Stefan Seyfried wrote:
>> FWIW:
>> Tested-by: Stefan Seyfried
>>
>> This patch fixes the 0% CPU issue on openSUSE Factory kernels for me.
>
> Thanks! The patch has been
Am 03.06.2013 19:38, schrieb Stefan Seyfried:
> Or, to be more precise: it breaks resume.
>
> The machine seems to lock up hard after resume, then after a few seconds
> it panics (caps lock blinking).
>
> Reproduced on ThinkPad X200s
>
> 00:03.0 0780: 8086:2a44 (rev
output.
I could try to take a picture of the panic message if that would be helpful.
Best regards,
Stefan
--
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmen
gt;
> Reported-by: Mike Galbraith
> Suggested-by: Mike Galbraith
> Cc: Steven Rostedt
> Cc: Paul E. McKenney
> Cc: Ingo Molnar
> Cc: Thomas Gleixner
> Cc: Peter Zijlstra
> Cc: Borislav Petkov
> Cc: Li Zhong
> Cc: Mike Galbraith
> Signed-off-by: Frederic Weisbeck
v, hdev->name, hdev->type);
>
> - hci_unregister_sysfs(hdev);
> -
> write_lock_bh(&hci_dev_list_lock);
> list_del(&hdev->list);
> write_unlock_bh(&hci_dev_list_lock);
> @@ -914,6 +912,8 @@ int hci_unregister_dev(struct hci_dev *h
On Tue, Jul 31, 2007 at 04:43:34PM +0200, Stefan Seyfried wrote:
> On Tue, Jul 31, 2007 at 04:01:40PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > > > > # Running in *copy* of this code, somewhere in low 1MB.
> > > > > >
> &g
~10 seconds through the BIOS on a "normal" boot.
My Toughbook resumes on "Lid Opened" after S4, it doesn't after a shutdown.
So there will be differences.
I'm not saying that they are too important, but 20% faster resume still is
a good saving for me.
No need to rest
7; \
> - outb%al, $0x80; \
> - movb$-119, %al; \
> - outb%al, $66; \
> - outb%al, $0x80; \
> - movb $15, %al; \
> - outb%al, $66;
> -
> ALIGN
> .align 4096
> ENTRY(wakeup_start)
This hunk rejec
nk that's too early. The conversion to sysfs is not even
finished, so it will be less than 6 months.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
T
ude "the writers of this document
must have been on crack, or this document is unmaintained". I cannot
disagree with them.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding th
there using /proc/acpi, and
this should continue to work.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane Ge
Hi,
On Tue, Jul 10, 2007 at 10:59:57AM +1000, Nigel Cunningham wrote:
> On Saturday 07 July 2007 01:04:51 Stefan Seyfried wrote:
> > On Thu, Jul 05, 2007 at 09:04:27PM +1000, Nigel Cunningham wrote:
> > >
> > > Adding i8042.reset=1 to the commandline fixed it.
> &g
asn't there a quirk list where workarounds for i8042 on known bad machines
are stored? Maybe it would be a good idea to get your machine into it ;-)
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | &q
is a debugging option. Only root can set it. Its purpose is to make
"machine hangs during suspend" (even before it goes to sleep) debuggable.
It will only be set if the machine crashes anyways.
(We can taint the kernel if this control is set, if that helps you).
--
Stefan Seyfried
QA /
-hoc hack (which actually was only to illustrate
the idea) because a) it was enough to show the intent and b) i did not know
how to do it better ;-)
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well,
On Thu, Jun 28, 2007 at 09:12:44PM +0200, Rafael J. Wysocki wrote:
> On Thursday, 28 June 2007 19:25, Stefan Seyfried wrote:
> >
> > However, we don't know which consoles are safe to stay alive during suspend.
> > Generally, defaulting to suspending them all is not a b
.
However, we don't know which consoles are safe to stay alive during suspend.
Generally, defaulting to suspending them all is not a bad idea IMHO.
And IIRC it is plain luck if a serial console survives the suspend (or was
the serial code fixed recently?)
So i do not care too much, but my / Fra
> problems without having to change CONFIG_ or /sys/*".
Ok. Deal. Once you fixed all the console drivers, i'll gladly send a patch
that reverts the patch we are discussing now.
Note that this patch actually helps fixing those drivers, since you can
test much easier if a given driver surviv
t; > /sys/power/disable_console_suspend.
> > > >
> > > >
> > > > Signed-off-by: Stefan Seyfried <[EMAIL PROTECTED]>
> > > > Signed-off-by: Frank Seidel <[EMAIL PROTECTED]>
> > > > ---
> > > > Third try, renamed sysfs interface to console_su
On Thu, Jun 14, 2007 at 12:08:00AM +0200, Pavel Machek wrote:
> Hi!
>
> > I hate having to recompile the kernel, just to be able to debug suspend.
> > Remove CONFIG_DISABLE_CONSOLE_SUSPEND, replace it by a tunable in
> > /sys/power/disable_console_suspend.
>
> &g
I hate having to recompile the kernel, just to be able to debug suspend.
Remove CONFIG_DISABLE_CONSOLE_SUSPEND, replace it by a tunable in
/sys/power/disable_console_suspend.
Signed-off-by: Stefan Seyfried <[EMAIL PROTECTED]>
Signed-off-by: Frank Seidel <[EMAIL PROTECTED]>
---
Se
s on power up and on resume anyway,
so it is hard to see if the blink was from the BIOS or from Linux.
And don't we need to resume the keyboard controller before we can start
blinking the LEDs?
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, Joh
I hate having to recompile the kernel, just to be able to debug suspend.
Remove CONFIG_DISABLE_CONSOLE_SUSPEND, replace it by a sysctl in
/proc/sys/kernel/disable_console_suspend.
Signed-off-by: Stefan Seyfried <[EMAIL PROTECTED]>
---
Patch is against 2.6.22-rc4
Documentation/power/ba
have had a report, where "vga=0" (instead of using vesafb) worked
around a similar issue on a macbook. I don't know the kernel version, though.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg
it is not a video flag. And not ACPI. Just add another
sysctl if you care.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by in
you did not use
pm-hibernate to suspend, it is your very own problem).
You could of course simply go for GRUB's "default saved" and "savedefault"
feature, to always boot the last-booted kernel unless changed in the menu.
--
Stefan Seyfried
QA / R&D Team Mobile Device
ything
including filesystem cache.
And you simply cannot buy a new machine today that still supports APM suspend
to disk.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's
On Thu, May 17, 2007 at 06:35:48PM -0400, Len Brown wrote:
> Yes, SuSE enables polling mode by default, but that is just
> distro specific "value add" that should eventually be fixed.
I will do that for openSUSE FACTORY.
--
Stefan Seyfried
QA / R&D
enever a trip point is crossed, all trip points are updated.
I think they implemented hysteresis that way.
ISTR that hp nx5000 did something similar, but i might be wrong on this one.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX
on ACPI machines, "platform" is the right thing to do,
and i still think it will only break on machines that have a broken ACPI BIOS.
(Are there machines with broken ACPI BIOS around? ;-)
Your additional "fall back to shutdown if !(ops)"-fix looks very sane,
however, and is defi
3e c0 8b 40 14 8b 70 38 8b 7c 24 08 <8b> 47 0c 31 ff 3b 46
0c 0f 84 c1 00 00 00 8b 54 24 08 8b 42 0c
EIP: [] sysfs_move_dir+0x3e/0x117 SS:ESP 0068:dde11e20
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
-
To unsubscribe from this list: send
shutdown message for easier
> debugging
>
> Signed-off-by: Danny Kukawka <[EMAIL PROTECTED]>
FWIW:
Signed-off-by: Stefan Seyfried <[EMAIL PROTECTED]>
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
-
To unsubscribe from t
h ATI need different quirks
than the hp's with intel. Only thinkpads seem to almost universally work
with s3_bios,s3_mode, with some x86_64 models being the exception).
Something like that should be pretty easy once the whitelist is kept
in HAL.
--
Stefan Seyfried
"Any ideas, John?&qu
- boot your system with init=/bin/bash, mount /proc and /sys
- try the s2ram options in the combinations listed on the above page
- as soon as you find an option that works, please retry it from a
full booted system (including X)
- if it still works, please report the options used and the outpu
ist entry.
I strongly suggest that this is not a kernel problem but a user(space)
problem :-)
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-
To unsubscribe from t
On Tue, Feb 06, 2007 at 10:12:04AM -0500, Bill Davidsen wrote:
> Stefan Seyfried wrote:
> >On Wed, Jan 31, 2007 at 03:14:31AM +0100, Adrian Bunk wrote:
> >>On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
> >>>What? Throw a fresh-faced newbie instant
y.
Well, at work i probably have an USB floppy lying around somewhere,
but i doubt that it uses floppy.c ;-),
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
intainer) for a merge?
Hey, come on, "no new proc files", please ;-)
> > <0> $ cat /proc/bus/input/activity
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them&
have had
problems with suspend for a long time and just sometimes work "by accident".
ISTR that they do not really save and restore the line settings etc.
So it does not need to be the BIOS, it can also be a plain broken driver.
--
Stefan Seyfried
QA / R&D Team Mobile Devices|
On Tue, Jan 02, 2007 at 11:58:03AM +0100, Xavier Bestel wrote:
> On Tue, 2007-01-02 at 11:05 +0100, Stefan Seyfried wrote:
> > On Sat, Dec 16, 2006 at 08:05:24PM +0100, Lee Garrett wrote:
> > > I had the same problem (/boot on reiserfs, grub hanging for ages after
> > &g
On Mon, Dec 18, 2006 at 11:14:51AM +0100, Paolo Ornati wrote:
> On Mon, 18 Dec 2006 10:36:24 +0100
> Stefan Seyfried <[EMAIL PROTECTED]> wrote:
>
> > It depends on the BIOS. Many BIOSes have a setting where you can set the
> > "power fail mode" to "on&q
didn't find an update on this issue on LKML.
I'm pretty sure this is just a coincidence, an issue about how the kernel
image is actually layed out on your filesystem. I don't think it actually
has to do anything with the version.
--
Stefan Seyfried
QA / R&D Team Mobile Devi
It was an experimental feature in the words sense:
For experimentation. I never accepted any bugreports for that but told
the reporters to go away :-)
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well
y just opening the lid.
This all is, however, BIOS specific. I have also seen BIOSes where it did
not matter at all.
If you don't like it, you can easily switch it off by
"echo shutdown > /sys/power/disk" (in-kernel suspend) or by adding
"shutdown method = shutdown&quo
.net _is_ stupid, since the DSDT usually depends on things you
configured in your BIOS settings, memory size, etc.pp) it is probably
a good idea to keep this patch out of mainline.
It is usefull for debugging, sure, but somebody who can debug on this
level should also be able to patch his kernel
EAL_MEM_SIZE 0xa
#define REAL_MEM_BLOCKS0x100
struct mem_block {
I have this in our vbetool-0.7 packages and have no reports about
segfaults since then.
--
Stefan Seyfried
QA / R&D Team Mobile Devices| "Any ideas, John?"
SUSE LINUX Products GmbH, Nü
ad.
Many people are successfull in using DRI with suspend, even running 3D
Apps while suspend works now. Of course, for troubleshooting it is ok to
keep DRI off the picture, but usually suspend works fine with DRI
> - Firewire
> - SCSI
--
Stefan Seyfried \ "I didn&#x
~2.6.5 (that's
when i looked, the code was broken long before, i assume).
> feature-removal for a long time, and it should have been removed before.
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid f
is fine and
we enter C[n+1] after X miliseconds without BM activity. Now if there
are only 60-70 ticks per second, you never get X ticks without BM
activity so you never go deeper than C2.
Just a guess.
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D
ep resolution is? Something along the lines of "Get
> bent"?
MPlayer is using /dev/rtc and was running smooth for me since the good
old 2.4 days.
--
Stefan Seyfried
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
Denis Vlasenko wrote:
> On Tuesday 26 July 2005 13:15, Stefan Seyfried wrote:
>> This is _not_ an USB cd writer but an IDE drive.
>> You may not just pull it out.
>
> Interesting how he's connecting floppy to IDE ;]
The connector probably has IDE and USB, the floppy
Puneet Vyas wrote:
> ide : failed opcode was : unknown
> hdc : status error: status 0x00 { }
This is _not_ an USB cd writer but an IDE drive.
You may not just pull it out.
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices
t;> perfectly fine without it that i don't want to break ;-)
>
> I'll clean it up to add that stuff soon, but I've hit a problem with it on
> my main desktop, it won't come out of suspend using my patch, however
this is why it needs a boot-parameter :-)
--
Stef
x27;t want to break ;-)
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \-- Leonard Cohen
-
To unsubscribe from this list: send the
d in which slot). But when using both, I get this error
> message every few seconds:
>
> kernel: cs: pcmcia_socket0: unable to apply power.
Are you overriding the DSDT?
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices
nets ;-)
But i have no idea what went wrong for you, i'll have a look at the code
but i doubt that i'll find much of interest.
One thing which would be interesting:
You don't eventually have multiple swap partitions?
--
Stefan Seyfried \ "I didn't wan
re is invalidated even before reading the image, so theoretically
it should not happen.
> I will try to reproduce, but I'm curious if anyone else has seen this.
i have not seen anything like that, but i am not always running the
latest & greatest kernel.
--
Stefan Seyfried
sume scripts to kernel versions.
JFTR: i second this. There is already enough hackery involved if one
wants to provide a smooth user experience ;-)
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for wha
RR, but i
don't mind.
--
Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX Nürnberg.
"Any ideas, John?"
"Well, surrounding them's out."
--- linux/kernel/power/swsusp.c~2005-04-22 17:07:56.0 +0200
+++ linux/kernel/power/swsusp.c 2005-
Matt Mackall wrote:
> Any sensible solution here is going to require remembering passwords.
> And arguably anywhere the user needs encrypted suspend, they'll want
> encrypted swap as well.
But after entering the password and resuming, the encrypted swap is
accessible again and my ssh-key may be l
Pavel Machek wrote:
> Encrypting swsusp image is of course even better, because you don't
> have to write large ammounts of zeros to your disks during resume ;-).
and while we are at it: compressing before encryption will also reduce
the amount of data you have to write during suspend... ;-)
>
Barry K. Nathan wrote:
> On Sun, Apr 10, 2005 at 11:27:47PM +0200, Pavel Machek wrote:
>> Can you try without XFS?
>
> No, XFS is my root filesystem. :( (Now that I think about it, would
> modularizing XFS and using an initrd be OK?)
Yes, although it is not totally trivial.
> I'll see if I can r
Jaco Kroon wrote:
> Dmitry Torokhov wrote:
>>>OT: I think I prefer synaptics multi-finger tapping to the tapping in
>>>specific locations to get right and middle clicking, but that is another
>>>story that probably has nothing to do with the kernel, and quite likely
>>>something that is configura
Rafael J. Wysocki wrote:
> Hi,
>> On Fri, 2005-04-01 at 08:18, Pavel Machek wrote:
>> > I believe we should freeze hotplug before processes.
>
> I agree. IMO user space should not be considered as available once we have
> started freezing processes, so hotplug should be disabled before. By the s
Pavel Machek wrote:
> Hi!
>
>> Hello Pavel, I can now suspend to disk on the laptop with 2.6.12-rc1. There
>> is
>> no failures anymore. It resumes perfectly.
>
> No video hacks needed? Good.
suspend to disk. !(suspend to RAM).
:-)
Stefan
-
To unsubscribe from this list: send the line "unsub
Pavel Machek wrote:
> Hi!
> There's another feature that enables you to start resume manually with
> some echo to /sys... Perhaps it needs to be documented better, I'm
> looking for a patch ;-).
HANNES, where are you?
;-)
Stefan
-
To unsubscribe from this list: send the line "unsubscribe lin
Andy Isaacson wrote:
> OK, anything else I should try?
not really, i just wait for Vojtech and Pavel :-)
> Why does it only fail when I have *both* intel_agp and i8042 aux?
later...
> In the SysRq-T trace I see one interesting process: most things are
> in D state in refrigerator(), but sh sho
Andy Isaacson wrote:
> On Thu, Mar 24, 2005 at 03:27:15PM +0100, Stefan Seyfried wrote:
> Sysrq still prints stuff, so IRQs aren't locked. But most of the sysrq
> commands don't work... S and U don't seem to do anything (not too
> suprising I suppose) but B does reb
Andy Isaacson wrote:
> Dmesg is attached; hardware is a Vaio r505te.
>
> Unfortunately, the deadlock (?) is nondeterministic; it *sometimes*
> suspends successfully, maybe one time out of 10. And thinking back, I
> *sometimes* saw failures to suspend with 2.6.11-rc3, maybe one failure
> out of 2
1 - 100 of 120 matches
Mail list logo
