On Tuesday 19 February 2008 18:10:35 Pierre Ossman wrote:
> Primarily, the udev startup locks up. If I abort it, it just locks up on
> more or less every action after that. Some quick debugging showed that I
> had a whole bunch of modprobe processes sitting around. The new
> CONFIG_USB_ANNOUNCE_NEW
On Sunday 10 Apr 2005 19:29, you wrote:
> Hello.
>
> I am trying to format the CD-RW disc
> on my NEC ND-3520A DVD writer, and the
> results are completely unexpected: I do
> cdrwtool -d /dev/cdrom -q
> It proceeds with the formatting, but
> while it does so, the system is pretty
> much dead. It ca
On Saturday 09 Jul 2005 17:04, Alistair John Strachan wrote:
> On Saturday 09 Jul 2005 16:57, Ingo Molnar wrote:
> > * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > Okay, I'll send you the vmlinux from -18 with a new digital photo, and
> > >
On Monday 11 Jul 2005 15:43, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > It's annoying that this is so readily reproducible here, yet almost
> > impossible to debug, and clearly a sideaffect of 4KSTACKS.. without it
> > actually b
On Monday 11 Jul 2005 19:46, Daniel Walker wrote:
> This may help ..
>
>
Unless Ingo's fixed it, x86-64 is broken at the moment anyway. I just get a
segfault from init.
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:CS/CSim Undergraduate
On Monday 11 Jul 2005 15:16, Ingo Molnar wrote:
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > might be an incorrect printout of stack_left :( The esp looks more or
> > less normal. Not sure why it printed -52.
>
> here's the stack_left calculation:
>
> + printk("ds: %04x es: %04x ss: %04
On Tuesday 12 Jul 2005 14:36, Arjan van de Ven wrote:
> On Tue, 2005-07-12 at 09:26 -0400, Peter Staubach wrote:
> > Horst von Brand wrote:
> > >>I am contacting you to express my concern over a growing trend in
> > >> kernel development. I am specifically referring to changes being made
> > >> to
On Wednesday 13 Jul 2005 16:30, Ingo Molnar wrote:
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > it worked upon the first try, and indeed my testbox crashed within 10
> > seconds:
> >
> > BUG: Unable to handle kernel NULL pointer dereference
> > BUG: Unable to handle kernel NULL pointer derefere
On Thursday 14 Jul 2005 20:34, FyD wrote:
> Dear All,
>
> I have a problem with a program named Gaussian (http://www.gaussian.com)
> (versions g98 or g03) and FC 4.0 (default kernel 2.6.11): I am used to take
> Gaussian binaries compiled on the RedHat 9.0 version, and used them on FC
> 2.0 or FC 3.
On Thursday 14 Jul 2005 21:16, Lee Revell wrote:
> On Thu, 2005-07-14 at 20:58 +0100, Alistair John Strachan wrote:
> > the responsiveness of our instrument to 300us which is low enough
> > for the real-time PCR industry
>
> PCR, as in polymerase chain reaction? They ca
Hi Ingo,
(I searched the list for rt realtime x86_64 x86-64 before posting this, so I
hope it's not a duplicate).
I've noticed -31 compiles without notable error or warning on x86-64, so I
thought maybe it was a valid time to file a bug report about it not working.
The machine currently runs 2
On Sunday 17 Jul 2005 17:29, Michal Schmidt wrote:
> Alistair John Strachan wrote:
> > Hi Ingo,
> >
> > (I searched the list for rt realtime x86_64 x86-64 before posting this,
> > so I hope it's not a duplicate).
> >
> > I've noticed -31 compil
On Tuesday 19 Jul 2005 17:47, Karim Yaghmour wrote:
> I have a usb-attached HD that I use from time to time. When it's connected
> to my desktop through a hub it works flawlessly. When connected to my Dell
> D600 Laptop, however, it sometimes randomly exhibits a loud click (as if
> the heads went b
On Sunday 07 Aug 2005 12:36, christos gentsis wrote:
[snip]
> >
> > I searched up google a bit and recieved some warnings about acpi causing
> > problems, so I disabled that, but was still unsucessful in getting that
> > to work. Please let me know if any other information is required.
> > Thanks
On Sunday 07 Aug 2005 19:54, Alistair John Strachan wrote:
> On Sunday 07 Aug 2005 12:36, christos gentsis wrote:
> [snip]
>
> > > I searched up google a bit and recieved some warnings about acpi
> > > causing problems, so I disabled that, but was still unsucessful in
Hi,
I just tried upgrading udev 053 to 067 on a 2.6.12 system and although the
system booted, firmware_class failed to upload the firmware for my wireless
card, prism54 was no longer auto loaded, etc. Even manually loading the
driver didn't help.
Any reason why 067 wouldn't work with 2.6.12? D
On Tuesday 16 August 2005 23:05, Greg KH wrote:
> On Tue, Aug 16, 2005 at 11:02:00PM +0100, Alistair John Strachan wrote:
> > Hi,
> >
> > I just tried upgrading udev 053 to 067 on a 2.6.12 system and although
> > the system booted, firmware_class failed to upload the f
On Wednesday 17 August 2005 00:09, Kay Sievers wrote:
[snip]
>
> Do you provide hooks for handling /etc/hotplug.d/? We are on the way of
> getting rid of that directory and recent udev versions don't handle
> that by default anymore. If you don't know, read the udev RELEASE-NOTES.
>
> Kay
I read t
Hi,
Today I decided to try Ingo's rt-preempt patch on 2.6.12 (V0.7.51-02). I'm
most interested in the CONFIG_PREEMPT_RT mode, so I selected this option
instead of the others. I enabled a couple of the debugging options, but I
wasn't totally clear on which options are most useful, so I just enab
On Wednesday 06 Jul 2005 12:57, Alistair John Strachan wrote:
[snip]
> Which debugging options are most useful for testing purposes? Is what I've
> selected enough? Also, I got a few unexpected messages in dmesg on bootup.
I decided to just enable everything, as I got a lockup within 5
On Wednesday 06 Jul 2005 19:41, Ingo Molnar wrote:
> * Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > does the patch below help? We initialized the timestamps to 0, but
> > with jiffies starting out negative, that means a ~5 minutes gap until
> > we first reach a value of 0. That would explain the mess
On Wednesday 06 Jul 2005 21:44, Ingo Molnar wrote:
[snip]
>
> the ACPI-idle bug's primary effects were the missed wakeups, but they
> should not cause lockups, because timer interrupts should always occur
> and should eventually 'fix up' such missed wakeups.
>
> but there's another side-effect of t
On Wednesday 06 Jul 2005 22:02, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > This is a completely unrelated question, but now we've got everything
> > under control.. how do I make "quiet" actually do something on the RT
> >
On Wednesday 06 Jul 2005 18:27, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > great! Do the softlockup warnings still occur?
> >
> > Yes, but in no greater a number.
>
> could you apply the patch below, so that we can see wh
On Wednesday 06 Jul 2005 18:01, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > I'm beginning to understand the issue, and I see why you think the
> > > proposed patch fixes it. I'll compile and boot V0.7.51-05 now.
> &
On Wednesday 06 Jul 2005 17:24, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > (generally i try to mark every message in the -RT kernel that signals
> > > some sort of anomaly with a 'BUG:' prefix - that makes it easy to do a
On Wednesday 06 Jul 2005 17:37, Alistair John Strachan wrote:
[big snip]
> >
> > could you try the patch below (or the -51-05 patch that i just
> > uploaded), does it fix this latency?
> >
> > Ingo
>
> I'm beginning to understand the issue, and I see wh
On Wednesday 06 Jul 2005 17:28, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > On Wednesday 06 Jul 2005 14:39, Ingo Molnar wrote:
> > > * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > > Then it continues to boo
On Wednesday 06 Jul 2005 14:39, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Then it continues to boot. I'm getting periodic lockups under high
> > network load, however, though I suspect that might be the ipw2200
> > driver I compi
On Wednesday 06 Jul 2005 14:31, Ingo Molnar wrote:
[snip]
>
> for the first bootup it makes sense to enable most of them - just to
> make sure everything is ok. They have performance overhead, but it
> shouldnt show up during everyday use. (it will show up in benchmarks
> though) Here's the options
On Wednesday 06 Jul 2005 21:44, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > here's an updated patch - it will print out all timestamps too. (you'll
> > > have to revert all previous softlockup patches first, via patch -R.)
On Thursday 07 Jul 2005 10:46, Alistair John Strachan wrote:
[snip]
>
> Okay, when I brought my laptop back into work today for audio work, it
> locked up again within two minutes. I realise now what the problem is, but
> I don't have a serial cable here, so I'll have to
On Thursday 07 Jul 2005 12:29, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Unfortunately, since this is called when the kernel crashes, it's
> > impossible for me to capture any messages prior to this spam, if there
> > even a
On Thursday 07 Jul 2005 12:42, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > do you have DEBUG_STACKOVERFLOW and latency tracing still enabled? The
> > > combination of those two options is pretty good at detecting stack
> > >
On Thursday 07 Jul 2005 13:15, Alistair John Strachan wrote:
> On Thursday 07 Jul 2005 12:42, Ingo Molnar wrote:
> > * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > > do you have DEBUG_STACKOVERFLOW and latency tracing still enabled?
> > > >
On Thursday 07 Jul 2005 13:29, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > http://devzero.co.uk/~alistair/oops1.jpeg
> >
> > I disabled the trace and the STACKOVERFLOW option seems to help; I've
> > got a (slightly truncated)
Hi,
Latest patch doesn't compile on non-i386 arches. I found all users of INIT_FS;
need to be audited to INIT_FS(init_fs); like i386; then it compiles fine.
Ingo, could you also respond to my other thread, I uploaded the screenshot you
requested.
--
Cheers,
Alistair.
personal: alistair()de
On Thursday 07 Jul 2005 21:14, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Latest patch doesn't compile on non-i386 arches. I found all users of
> > INIT_FS; need to be audited to INIT_FS(init_fs); like i386; then it
> > compiles
On Thursday 07 Jul 2005 12:42, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > > do you have DEBUG_STACKOVERFLOW and latency tracing still enabled? The
> > > combination of those two options is pretty good at detecting stack
> > >
On Friday 08 Jul 2005 12:48, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Well, just to let others who have this problem know, it's clear that
> > Ingo's rt-preempt patches increase stack pressure on systems (like
> > mine)
On Friday 08 Jul 2005 18:48, Jakub Jelinek wrote:
> On Fri, Jul 08, 2005 at 06:42:53PM +0100, Alistair John Strachan wrote:
> > > btw., which gcc version are you using?
> >
> > Not the GCC version known to bloat stacks ;-)
> >
> > 3.4.4, on both my machines.
On Friday 08 Jul 2005 12:46, Ingo Molnar wrote:
[snip]
>
> Ok. Could you try to debug this some more? In the -51-17 patch i've
> implemented a new stack-overflow debugging feature: 'stack footprint
> maximum searching'. It is automatically active if you have
> CONFIG_LATENCY_TRACE and CONFIG_DEBUG_
On Friday 08 Jul 2005 20:48, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Unfortunately I see nothing like this when the machine crashes. Find
> > attached my config, which has CONFIG_4KSTACKS and the options you
> > specified. Are you
On Friday 08 Jul 2005 20:48, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Unfortunately I see nothing like this when the machine crashes. Find
> > attached my config, which has CONFIG_4KSTACKS and the options you
> > specified. Are you
On Saturday 09 Jul 2005 12:58, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Got this (slightly better) oops. Figured out how to use my camera :-)
> >
> > http://devzero.co.uk/~alistair/oops6.jpeg
>
> this was a bit more useful -
On Saturday 09 Jul 2005 16:57, Ingo Molnar wrote:
> * Alistair John Strachan <[EMAIL PROTECTED]> wrote:
> > Okay, I'll send you the vmlinux from -18 with a new digital photo, and
> > config, with CONFIG_4KSTACKS enabled.
>
> this crash too seems to indicate tr
On Thursday 28 Jul 2005 18:25, Andrew Morton wrote:
> Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
> > Linus, please do an update from:
> >
> >rsync://rsync.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git
> >
> > ...
> > 65 files changed, 5059 insertions(+), 1122 deletions(-)
>
> The git-als
On Saturday 30 Jul 2005 20:42, Pavel Machek wrote:
> Hi!
>
> > I've attached a gzipped version of my Wireless Security Lock patch
> > for v2.6.13-rc4.
> > A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
> > One part is a receiver which you plug into any available USB port.
> >
On Tuesday 02 Aug 2005 20:05, Lukas Hejtmanek wrote:
[snip]
>
> I did not notice before, but my values (capacity and so on) are completely
> wrong. It should contain values in mWh instead of mAh.
mWh is mAh x operational voltage. They're not "completely wrong", probably
just whatever unit your ma
On Tuesday 16 August 2005 13:18, Ingo Molnar wrote:
> i have released the 2.6.13-rc6-rt3 tree, which can be downloaded from
> the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
>
> Changes since 2.6.13-rc6-rt2:
Ingo,
I haven't used any of the RT patches since V0.7.51-xx, but I upgr
On Tuesday 23 August 2005 16:51, Paul Rolland wrote:
> Hello Sergey,
>
> > Yes. Addresses for USB devices are assigned dynamically. If you
> > disconnect the modem from USB and connect it again, its address will
> > change.
>
> The problem I've is that nothing changed on the machine except that
>
On Saturday 27 August 2005 22:28, Chris Wedgwood wrote:
> On Sat, Aug 27, 2005 at 08:19:18AM +, Kent Robotti wrote:
> > I know that experience dosen't come from packing the kernel source,
> > or the zillion other tar archives on the internet.
>
> Are you deliberately trying to be annoying? Le
On Tuesday 30 August 2005 13:31, Tony Lindgren wrote:
[snip]
> >
> > Same issue, it's waiting on dynticks before being reworked.
>
> Also one more minor issue; Dyntick can cause slow boots with dyntick
> enabled from boot because the there's not much in the timer queue
> until init.
>
> This probab
On Wednesday 31 August 2005 22:49, Jose Luis Domingo Lopez wrote:
> On Wednesday, 31 August 2005, at 11:27:41 -0600,
>
> Jeff V. Merkey wrote:
> > I am very open to discussions of this. Please go ahead and argue the
> > merits of GPL vs. proprietary code. DSFS is platform
> > neutral and will also
On Sunday 04 September 2005 12:05, Giampaolo Tomassoni wrote:
> Dears,
>
> thanks to Jiri Slaby who found a bug in the AAL0 handling of the ATMSAR
> module.
>
> I attach a fixed version of the atmsar patch as a diff against the 2.6.13
> kernel tree.
>
[snip]
Just out of curiosity, is there ANY rea
On Sunday 04 September 2005 17:41, Grzegorz Kulewski wrote:
> On Sun, 4 Sep 2005, Alistair John Strachan wrote:
> > On Sunday 04 September 2005 12:05, Giampaolo Tomassoni wrote:
> >> Dears,
> >>
> >> thanks to Jiri Slaby who found a bug in the AAL0 handling of
On Sunday 04 September 2005 19:36, Giampaolo Tomassoni wrote:
[snip]
>
> This may be true for AAL5 support, which is the way by which data is
> actually transferred between ADSL DSLAMs and CPE equipment.
>
> This may not be generally true, however: most providers are already
> delivering internet+v
On Monday 05 September 2005 10:36, David Woodhouse wrote:
> On Sun, 2005-09-04 at 17:20 +0100, Alistair John Strachan wrote:
> > Just out of curiosity, is there ANY reason why this has to be done in the
> > kernel? The PPPoATM module for pppd implements (via linux-atm) a
> >
On Monday 05 September 2005 14:56, David Woodhouse wrote:
> On Mon, 2005-09-05 at 14:52 +0100, Alistair John Strachan wrote:
> > I'm not sure which module you're referring to, but the patch recommended
> > by the speedtouch people links to linux-atm, and does not require
On Monday 05 September 2005 18:41, Sam Ravnborg wrote:
> Hi Linus.
>
> kbuild updates as accumulated over the last few months.
> All patches has been in -mm in one or several versions.
>
> Most noteworthy:
> 1) -Wundef added to CFLAGS. This is the cause of several new warnings,
>which for the m
On Monday 05 September 2005 21:13, Sam Ravnborg wrote:
> On Mon, Sep 05, 2005 at 08:35:14PM +0100, Alistair John Strachan wrote:
> > On Monday 05 September 2005 18:41, Sam Ravnborg wrote:
> > > Hi Linus.
> > >
> > > kbuild updates as accumulated over the last fe
Bugzilla for this report: http://bugzilla.kernel.org/show_bug.cgi?id=9468
On Thursday 10 January 2008 17:28:22 you wrote:
> I saw your thread on LKML about the problem with r8169. Did you ever
> find a patch or solution?
No, we have not diagnosed the cause of the problem, beyond the swiotlb usa
On Tuesday 11 December 2007 23:31:18 Rene Herman wrote:
> Good day.
>
> Would some people on x86 (both 32 and 64) be kind enough to compile and run
> the attached program? This is about testing how long I/O port access to
> port 0x80 takes. It measures in CPU cycles so CPU speed is crucial in
> rep
On Tuesday 02 October 2007 04:41:49 Linus Torvalds wrote:
[snip]
> In other words, people who know they may be affected and would want to
> prepare can look at (for example)
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
>
> and generally get ready for the switch
On Sunday 07 October 2007 20:13:09 you wrote:
> On Sun, Oct 07, 2007 at 08:47:52PM +0200, Rene Herman wrote:
> > On 10/07/2007 06:12 PM, Ingo Molnar wrote:
> > >* Oleg Verych <[EMAIL PROTECTED]> wrote:
> > >>Coloring isn't useful. If it was, it would be implemented ~16 years
> > >>ago.
> > >
> > >C
On Monday 08 October 2007 00:10:10 Rene Herman wrote:
> On 10/08/2007 12:40 AM, Alistair John Strachan wrote:
> > Splash screens are clearly cosmetic, and it's kind of shameful (imo) that
> > important messages explaining real problems are obscured from view by
> > f
On Monday 08 October 2007 00:10:10 Rene Herman wrote:
> I find Alan's suggestion to provide the functionality the same way you'd
> provide for translated kernel messages (seeing as how there also are people
> that want those) much more sensible.
By the way, I agree that this is the best approach.
On Friday 05 October 2007 09:32:40 you wrote:
> On Fri, 5 Oct 2007, Sam Ravnborg wrote:
> > > > cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
> > > >
> > > > Obviously, this file has moved to arch/x86/boot, but it seems like
> > > > possibly unnecessary breakage. I've been c
On Tuesday 20 November 2007 01:53:31 Joe Perches wrote:
> diff --git a/drivers/scsi/NCR_D700.c b/drivers/scsi/NCR_D700.c
> index 9e64b21..99403a6 100644
> --- a/drivers/scsi/NCR_D700.c
> +++ b/drivers/scsi/NCR_D700.c
> @@ -182,7 +182,7 @@ NCR_D700_probe_one(struct NCR_D700_private *p, int
> siop, i
Hi,
I have recently assembled a Core 2 Duo system with 4GB RAM and I believe there
might be a bug in the r8169 driver in >4GB RAM configurations.
Initially I can use one of two active r8169 NICs on the motherboard with this
quantity of RAM with other devices, without issue. But after some amoun
On Sunday 25 November 2007 00:25:10 Francois Romieu wrote:
> Alistair John Strachan <[EMAIL PROTECTED]> :
> [...]
>
> > The "choke" affects other devices on the system too, notably libata,
> > which does not recover gracefully. In my logs, I see a stream of:
&
On Sunday 25 November 2007 01:27:54 Francois Romieu wrote:
> Francois Romieu <[EMAIL PROTECTED]> :
> > Alistair John Strachan <[EMAIL PROTECTED]> :
> > [...]
> >
> > > The "choke" affects other devices on the system too, notably libata,
> >
On Saturday 15 December 2007 21:24:09 Gene Heskett wrote:
> On Saturday 15 December 2007, Robert Hancock wrote:
> >Gene Heskett wrote:
> >> Greetings;
> >>
> >> When I asked about a sata controller earlier this week, I gave a link to
> >> it. Unforch (maybe) when it actually arrived, the cards box
clocksource for
the running kernel (2.6.24 here) after applying this patch.
Force enabled HPET at base address 0xfed0
hpet clockevent registered
hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0
hpet0: 4 64-bit timers, 14318180 Hz
Signed-off-by: Alistair John Strachan <[EMAIL PROTECTED]>
---
arch/x86/
On Tuesday 29 January 2008 01:12:33 Pallipadi, Venkatesh wrote:
> Patch looks good.
> If BIOS does not report HPET on more of such systems we may have to add
> other chipsets in ICH9 family (ICH9_8, ...) as well.
>
> Acked-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Hi Ingo,
Are you going to pick
On Sunday 13 March 2005 22:26, you wrote:
> Patrick McFarland <[EMAIL PROTECTED]> writes:
> > On Saturday 12 March 2005 01:31 pm, Greg Stark wrote:
> > > OSS Audio doesn't work properly for Quake3 in 2.6.10 but it worked in
> > > 2.6.6. In fact I have the same problems in 2.6.9-rc1 so I assume 2.6.
On Monday 14 Feb 2005 21:11, Pavel Machek wrote:
[snip]
>
> Table of known working systems:
>
> Model hack (or "how to do it")
> ---
>--- IBM TP R32 / Type 2658-MMG none (1)
> Athlon HP Omnibook X
On Tuesday 15 Feb 2005 12:12, Lorenzo Colitti wrote:
> Alistair John Strachan wrote:
> > On Monday 14 Feb 2005 21:11, Pavel Machek wrote:
> >>Table of known working systems:
> >>Model hack (or "how to do it")
> >>[...]
> >
On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
[snip]
>
> Ok, here is the output from dmidecode (Debian package) and from lspci. I
> don't have acpidmp and I don't know where to get it, but if you think
> it's necessary I can download it if you tell me where to find it.
Find below a diff of
On Tuesday 15 Feb 2005 21:09, Lorenzo Colitti wrote:
[snip]
> I would advise trying to compile a custom kernel from scratch with my
> .config first.
>
> I got S3 working first with a very basic kernel config, but I couldn't
> get it to work with my usual kernel. Assuming it was some feature that
>
On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote:
> tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan:
> > On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote:
> > [snip]
> >
> > > Ok, here is the output from dmidecode (Debian package) and from lsp
On Saturday 12 March 2005 21:47, Randy.Dunlap wrote:
> Reg Clemens wrote:
> > Any way to get larger fonts with xconfig?
> > On my system they are just about microscopic.
> >
> > I can do a to go to a different screen resolution,
> > but then I have all sorts of scanning to deal with.
> >
> > Ive
Hi Jens,
I guessed from the oops that you might have an idea what's causing this oops
on shutdown/unmount. The git version (describe), a screenshot showing the
oops, a config, and dmesg for a booted kernel are available from:
http://devzero.co.uk/~alistair/oops-20071031/
I went back to -rc1 an
On Thursday 01 November 2007 11:51:08 Sebastian Siewior wrote:
> * Jens Axboe | 2007-11-01 11:51:09 [+0100]:
> >On Wed, Oct 31 2007, Alistair John Strachan wrote:
> >> Hi Jens,
> >>
> >> I guessed from the oops that you might have an idea what's causing th
On Sunday 22 July 2007 22:04:24 Linus Torvalds wrote:
> So give it all a good whacking, and report back about all the neat new
> features!
I'm fairly sure this is already known about on SPARC64 (see David Miller's
email ""build-id" changes break sparc64"), but I just thought I'd let people
know
On Sunday 02 September 2007 21:23:16 Jesper Juhl wrote:
> On 02/09/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
> > Hi Jesper,
> >
> > On Sun, 2 Sep 2007, Jesper Juhl wrote:
> > > > - if (!(interface = usb_find_interface(&sisusb_driver,
> > > > subminor))) { - dev_err(&sisusb->s
On Tuesday 04 September 2007 15:18:23 Abhijit Bhopatkar wrote:
[snip]
> > Anyway, it'd be helpful if someone else can check the same MacBook
> > (1st generation, not Pro?) whether the problem is reproducible.
>
> To be precise its Macbook 1st Generation non pro. with subsystem id
> 0x106b0a00
>
>
On Monday 03 September 2007 09:06:25 Nicolas Mailhot wrote:
> Mats Johannesson bredband.net> writes:
> > On 2007-09-01 16:07:48 Torsten Kaiser wrote:
> > [...]
> >
> > > The good:
> > >> +hpet-force-enable-on-vt8235-37-chipsets.patch
> > >> +hpet-force-enable-on-vt8235-37-chipsets-fix.patch
> > >
On Tuesday 04 September 2007 16:26:27 Andi Kleen wrote:
> > Seconded. It's been largely ignored which is annoying because the HPET
> > works perfectly on this board. I assume the reason is still that nobody
> > from NVIDIA verified hardward support for the hack.
>
> It's IMHO a bad idea to add any
The real question is WHY do people keep writing essays about topics that have
_already_ been exhaustively explored in other threads? If you want a better
understanding of the situation, read the archives, DON'T post another
duplicate message about the same scheduler parade.
Unless you've got so
On Friday 03 August 2007 15:51:59 T. J. Brumfield wrote:
> > I'm not going to argue with this point because I think this is exactly
> > what Linus meant. He wanted a scheduler that worked. And he knew it
> > wouldn't work immediately after merging it. So he had to go with the
> > person that he tru
On Friday 03 August 2007 14:27:30 Андрій Мішковський wrote:
> Bad things may happen if Linus gives a right of making decision to
> other people (a big group of people). ;)
> As you said, Linux is a public OS, so Con's code never will be lost.
> That's the base of open source - people come and go, b
On Saturday 04 August 2007 14:17:34 Prakash Punnoor wrote:
> Unfortunately this doesn't seem to have made it into 2.6.23-rc2. I need it
> as well, to make Windows XP boot up w/o hanging or reebooting my host
> machine.
It isn't in 2.6.23-rc2. I guess Avi should re-send to Linus and hopefully
it'l
Hi,
I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a digital
photo of the oops. Alarmingly, a lot of the time it triple faults the machine
and I don't get a chance to grab it. This time I was lucky, though.
http://devzero.co.uk/~alistair/kvm-2.6.23-rc1.jpg
Unfortunately, som
> I have absolutely no idea what triggers this crash.
Checked the RAM on the box? Kinda weird if you're getting VRAM corruption, I
wonder if this is due to the RAM failing at the point where the framebuffer
is mapped?
Try running memtest86 on it.
--
Cheers,
Alistair.
137/1 Warrender Park Roa
On Sunday 29 July 2007 09:16:43 Avi Kivity wrote:
> Alistair John Strachan wrote:
> > Hi,
> >
> > I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a
> > digital photo of the oops. Alarmingly, a lot of the time it triple faults
> > the machi
On Sunday 29 July 2007 12:34:28 you wrote:
[snip]
> > Doesn't help, I still get the same crashes. I tried 2.6.22 again and it's
> > rock solid by comparison.
>
> Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
> Please describe your configuration *exactly*.
I'm using the kvm-
On Sunday 29 July 2007 14:47:57 you wrote:
> Alistair John Strachan wrote:
> > On Sunday 29 July 2007 12:34:28 you wrote:
> > [snip]
> >
> >>> Doesn't help, I still get the same crashes. I tried 2.6.22 again and
> >>> it's rock solid by com
On Sunday 29 July 2007 15:57:33 Gene Heskett wrote:
> Is this a known problem? Do I need to report it to nvidia somehow? It
> looks to me like it may be their problem, and I have submitted it, but if
> anyone has a better idea, please advise. System is FC6, uptodate as of
> yesterday.
Gene, thi
On Monday 30 July 2007 14:00:13 Avi Kivity wrote:
> How about the attached patch? (I haven't yet tried to reproduce, but
> this can cause an AMD-only oops).
This seems to have fixed the problem. Thanks Avi.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
-
To unsubscribe from th
1 - 100 of 210 matches
Mail list logo
