Kjartan Maraas wrote:
ma., 10.12.2007 kl. 10.03 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
Hmmm... Ah.. okay. Wrongly splitted patch. Can you please do it one
more time?
Attached.
Alright, it works now but it seems both dmesgs are from no-filter patch.
I'm pretty sure it works too
ma., 10.12.2007 kl. 10.03 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
Hmmm... Ah.. okay. Wrongly splitted patch. Can you please do it one
more time?
Attached.
Alright, it works now but it seems both dmesgs are from no-filter patch.
I'm pretty sure it works too because one of
sø., 09.12.2007 kl. 15.46 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
to., 06.12.2007 kl. 11.38 +0900, skrev Tejun Heo:
Thanks. Almost there. Can you please try the attached two patches and
report the boot log?
Here we go again.
Hmmm... Ah.. okay. Wrongly splitted patch. Can
Kjartan Maraas wrote:
to., 06.12.2007 kl. 11.38 +0900, skrev Tejun Heo:
Thanks. Almost there. Can you please try the attached two patches and
report the boot log?
Here we go again.
Hmmm... Ah.. okay. Wrongly splitted patch. Can you please do it one
more time?
Thanks.
--
tejun
Index:
to., 06.12.2007 kl. 11.38 +0900, skrev Tejun Heo:
Thanks. Almost there. Can you please try the attached two patches and
report the boot log?
Here we go again.
Cheers
Kjartan
Initializing cgroup subsys cpuset
Linux version 2.6.24-rc4 ([EMAIL PROTECTED]) (gcc version 4.1.2 20071124 (Red
on., 05.12.2007 kl. 16.46 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
fr., 30.11.2007 kl. 19.39 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
on., 28.11.2007 kl. 10.09 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
on., 05.12.2007 kl. 16.46 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
fr., 30.11.2007 kl. 19.39 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
on., 28.11.2007 kl. 10.09 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
Thanks. Almost there. Can you please try the attached two patches and
report the boot log?
--
tejun
Index: work/include/linux/libata.h
===
--- work.orig/include/linux/libata.h
+++ work/include/linux/libata.h
@@ -1013,18 +1013,18
Kjartan Maraas wrote:
fr., 30.11.2007 kl. 19.39 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
on., 28.11.2007 kl. 10.09 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
using the latest fedora development kernel which is
fr., 30.11.2007 kl. 19.39 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
on., 28.11.2007 kl. 10.09 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
using the latest fedora development kernel which is 2.6.24-rc2-git6
Kjartan Maraas wrote:
on., 28.11.2007 kl. 10.09 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
using the latest fedora development kernel which is 2.6.24-rc2-git6
based. And I have the latest BIOS from HP IIRC.
This is an
Tomas Carnecky wrote:
I kindof had suspected that. The docking station has an ultrabay slot
where I currently have a cdrom drive (since the notebook itself doesn't
have any cdrom drive. Once I took the cdrom drive out, I was able to
successfully perform what I wanted to do in points 3a and 5!
on., 28.11.2007 kl. 10.09 +0900, skrev Tejun Heo:
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
using the latest fedora development kernel which is 2.6.24-rc2-git6
based. And I have the latest BIOS from HP IIRC.
This is an HP nc6400 intel
[cc'ing libata people]
Hello,
Kjartan Maraas wrote:
Here you go. It shows the error two times and then it gets it right and
continues to boot. No other problems arise from this that I can see.
Cool, it proves even my code works from time to time if the moon and
stars are perfectly aligned.
Tejun Heo wrote:
Your BIOS is probably trying to issue DCO freeze lock to all drives. I
don't have the faintest idea why it does but it does. I think there are
several choices here.
1. Ignore device errors for _GTF commands. Report the failure with
KERN_DEBUG priority and just keep
Kjartan Maraas wrote:
I get this exact error message on a normal first time boot here. I'm
using the latest fedora development kernel which is 2.6.24-rc2-git6
based. And I have the latest BIOS from HP IIRC.
This is an HP nc6400 intel based laptop:
Care to post boot dmesg? Or does harddisk
sø., 18.11.2007 kl. 21.16 +0100, skrev Tomas Carnecky:
Since this is becoming more an IDE/ATA issue, I added
linux-ide@vger.kernel.org to CC. I hope that's the right mailinglist.
Tomas Carnecky wrote:
(3) Once the notebook was in the docking station (whether I boot it
while in the dock
Since this is becoming more an IDE/ATA issue, I added
linux-ide@vger.kernel.org to CC. I hope that's the right mailinglist.
Tomas Carnecky wrote:
(3) Once the notebook was in the docking station (whether I boot it
while in the dock or boot it outside and then put it into the dock) and
I take
18 matches
Mail list logo
