Jiri Slaby <[EMAIL PROTECTED]> writes:
> Alex Romosan wrote:
>> this is on a thinkpad t40, not sure if it means anything, but here it goes:
>>
>> kernel: kernel BUG at fs/buffer.c:1235!
>> kernel: invalid opcode: [#1]
>> kernel: PREEMPT
>> kernel: Modules linked in: radeon drm binfmt_misc n
Alex Romosan wrote:
> this is on a thinkpad t40, not sure if it means anything, but here it goes:
>
> kernel: kernel BUG at fs/buffer.c:1235!
> kernel: invalid opcode: [#1]
> kernel: PREEMPT
> kernel: Modules linked in: radeon drm binfmt_misc nfs sd_mod scsi_mod nfsd
> exportfs lockd sunrpc
On Tue, 19 Dec 2006, Robert Hancock wrote:
>
> From what I've seen it appears that smartctl has the same problem, it was also
> reporting the device didn't support SMART..
No, there were actually two different problems, and to confuse people,
they had the same _symptoms_.
Commit 0e75f9063f5c5
On Tue, Dec 19 2006, Jens Axboe wrote:
> On Tue, Dec 19 2006, Robert Hancock wrote:
> > Jens Axboe wrote:
> > >Just noticed that most of the mails I wrote on this thread were
> > >apparently without linux-kernel cc'ed (dunno who removed the cc). So
> > >I'll write a small summary - the problem is t
On Tue, Dec 19 2006, Robert Hancock wrote:
> Jens Axboe wrote:
> >Just noticed that most of the mails I wrote on this thread were
> >apparently without linux-kernel cc'ed (dunno who removed the cc). So
> >I'll write a small summary - the problem is that hddtemp includes some
> >fragile code to chec
Jens Axboe wrote:
Just noticed that most of the mails I wrote on this thread were
apparently without linux-kernel cc'ed (dunno who removed the cc). So
I'll write a small summary - the problem is that hddtemp includes some
fragile code to check the sense info, and this commit:
http://git.kernel.d
On Thu, Dec 14 2006, Alistair John Strachan wrote:
> On Thursday 14 December 2006 21:50, Jeff Garzik wrote:
> > Alistair John Strachan wrote:
> > > Before I proceed with the horrors of an -rc1 bisection, could somebody
> > > send me the ADMA patches so I can eliminate those first?
> >
> > Run
> >
>
Alan wrote:
On Fri, 15 Dec 2006 11:50:14 -0500
Bill Davidsen <[EMAIL PROTECTED]> wrote:
Did I miss an alternate method of handling ftape devices, or are these
old beasts now unsupported? I occasionally have to be able to handle
that media, since the industrial device using ftape for control
On Mon, Dec 18 2006, Jens Axboe wrote:
> On Sat, Dec 16 2006, Linus Torvalds wrote:
> > That said: Jens - I think 0e75f906 was a mistake. "blk_rq_unmap()" really
> > should be passed the "struct bio", not the "struct request *". Right now
> > it does something _really_ strange with requests with
On Sat, Dec 16 2006, Linus Torvalds wrote:
> That said: Jens - I think 0e75f906 was a mistake. "blk_rq_unmap()" really
> should be passed the "struct bio", not the "struct request *". Right now
> it does something _really_ strange with requests with linked bio's, and I
> don't think your and FUJ
On Monday 18 December 2006 10:45, Stefan Richter wrote:
>Gene Heskett wrote:
>> On Sunday 17 December 2006 20:05, Stefan Richter wrote:
>>>What's missing in our implementation is that the use count of ohci1394
>>>goes up too once a "high-level driver" uses resources of a host driven
>>>by ohci1394.
Gene Heskett wrote:
> On Sunday 17 December 2006 20:05, Stefan Richter wrote:
>>What's missing in our implementation is that the use count of ohci1394
>>goes up too once a "high-level driver" uses resources of a host driven
>>by ohci1394.
>
> This needs some tlc then I assume?
Yes. It's now logge
On Sunday 17 December 2006 20:05, Stefan Richter wrote:
>Gene Heskett wrote:
>> The camera has been turned back off, but yes, it works absolutely
>> normally now. With no dv1394 in memory!
>>
>> Then with the camera on and kino controlling it:
>> [EMAIL PROTECTED] ~]# lsmod|grep 1394
>> raw1394
Gene Heskett wrote:
> The camera has been turned back off, but yes, it works absolutely normally
> now. With no dv1394 in memory!
>
> Then with the camera on and kino controlling it:
> [EMAIL PROTECTED] ~]# lsmod|grep 1394
> raw139432264 4
> ohci1394 39088 0
> iee
On Sunday 17 December 2006 15:21, Stefan Richter wrote:
[...]
>What if you prevent dv1394 from ever being loaded, or don't build it in
>the first place? CONFIG_IEEE1394_DV1394=n
How about '# CONFIG_IEEE1394_DV1394 is not set'?
Hand edited the .config and fired off my makeit script, which does it
(Cc linux1394-devel, for the record)
Gene Heskett wrote:
> On Sunday 17 December 2006 13:31, Stefan Richter wrote:
>> Is your version of kino still using dv1394 or does it work without
>> dv1394 loaded too?
>>
> AFAIK, its kino is 0.9.3. Ok, while kino is running I did a modprobe -rv
> dc1394 an
On Sunday 17 December 2006 13:31, Stefan Richter wrote:
>Gene Heskett wrote:
>...
>
>> while I didn't try
>> to capture a 2 hour movie, I did use kino to control the camera
>> playback, rewind etc stuff for about 10 minutes and had no problems
>> whatsoever.
>
>...
>
>> The only entry in the messag
Gene Heskett wrote:
...
> while I didn't try
> to capture a 2 hour movie, I did use kino to control the camera playback,
> rewind etc stuff for about 10 minutes and had no problems whatsoever.
...
> The only entry in the messages log for all this was:
>
> Dec 17 12:47:13 coyote kernel: WARNING:
On Thursday 14 December 2006 22:17, Gene Heskett wrote:
>On Thursday 14 December 2006 12:48, Stefan Richter wrote:
>[...]
>
>>(Anyway, that's unrelated to Gene's issues.)
>
>And which I haven't had a chance to check yet, the camera is still in
> the truck and I've been busier than a one legged man
On Saturday 16 December 2006 21:36, Linus Torvalds wrote:
> On Fri, 15 Dec 2006, Alistair John Strachan wrote:
> > In total isolation, v2.6.19..0e75f9063f5c55fb0b0b546a7c356f8ec186825e it
> > breaks. Reverting just 0e75f9063f5c55fb0b0b546a7c356f8ec186825e, it works
> > again.
> >
> > So I think thi
Alistair John Strachan wrote:
It could simply be that bisect isn't working here because it's actually broken
by two separate patches. Out of bad luck, I've ended up singling out the one
that already has a "fix", and the "real bug" hasn't been found.
I guess I should repeat the bisection, and whe
On Saturday 16 December 2006 21:36, Linus Torvalds wrote:
> On Fri, 15 Dec 2006, Alistair John Strachan wrote:
> > In total isolation, v2.6.19..0e75f9063f5c55fb0b0b546a7c356f8ec186825e it
> > breaks. Reverting just 0e75f9063f5c55fb0b0b546a7c356f8ec186825e, it works
> > again.
> >
> > So I think thi
On Fri, 15 Dec 2006, Alistair John Strachan wrote:
>
> In total isolation, v2.6.19..0e75f9063f5c55fb0b0b546a7c356f8ec186825e it
> breaks. Reverting just 0e75f9063f5c55fb0b0b546a7c356f8ec186825e, it works
> again.
>
> So I think this is the source, but I can't explain why it "goes away" before
On Fri, 15 Dec 2006 11:50:14 -0500
Bill Davidsen <[EMAIL PROTECTED]> wrote:
> Did I miss an alternate method of handling ftape devices, or are these
> old beasts now unsupported? I occasionally have to be able to handle
> that media, since the industrial device using ftape for control updates
>
Linus Torvalds wrote:
Ok, the two-week merge period is over, and -rc1 is out there.
I'm _really_ hoping that we can keep the 2.6.20 release calmer and without
any of the dragging-out-due-to-core-changes that we've had lately. We
didn't actually merge any really core changes here, with the bigg
On Thursday 14 December 2006 12:48, Stefan Richter wrote:
[...]
>
>(Anyway, that's unrelated to Gene's issues.)
And which I haven't had a chance to check yet, the camera is still in the
truck and I've been busier than a one legged man in an ass kicking
contest today. I did get 2.6.20-rc1 built
On Friday 15 December 2006 00:48, Alistair John Strachan wrote:
> On Thursday 14 December 2006 21:20, Jens Axboe wrote:
> > On Thu, Dec 14 2006, Alistair John Strachan wrote:
> > > Hi Jens,
> > >
> > > On Thursday 14 December 2006 20:48, Jens Axboe wrote:
> > > > On Thu, Dec 14 2006, Jens Axboe wro
Alistair John Strachan wrote:
I bisected all the way down to 0e75f9063f5c55fb0b0b546a7c356f8ec186825e, which
git reckons is the culprit. I wasn't able to revert this commit to test,
because it has conflicts.
Any ideas?
That would be this one I assume?
[PATCH] block: support larger block pc
On Thursday 14 December 2006 21:20, Jens Axboe wrote:
> On Thu, Dec 14 2006, Alistair John Strachan wrote:
> > Hi Jens,
> >
> > On Thursday 14 December 2006 20:48, Jens Axboe wrote:
> > > On Thu, Dec 14 2006, Jens Axboe wrote:
> > > > > I'll do that if nobody comes up with anything obvious.
> > > >
Le jeudi 14 décembre 2006 à 18:22 -0500, Jeff Garzik a écrit :
> Nicolas Mailhot wrote:
> > Alistair John Strachan sms.ed.ac.uk> writes:
> >
> >> `hddtemp' has stopped working on 2.6.20-rc1:
> >
> > → http://bugzilla.kernel.org/show_bug.cgi?id=7581
>
> I'm not sure I quite follow your bug repor
Nicolas Mailhot wrote:
Alistair John Strachan sms.ed.ac.uk> writes:
`hddtemp' has stopped working on 2.6.20-rc1:
→ http://bugzilla.kernel.org/show_bug.cgi?id=7581
I'm not sure I quite follow your bug report. Are you saying that the
patch you attached causes the problem?
Jeff
On Thursday 14 December 2006 21:50, Jeff Garzik wrote:
> Alistair John Strachan wrote:
> > Before I proceed with the horrors of an -rc1 bisection, could somebody
> > send me the ADMA patches so I can eliminate those first?
>
> Run
>
> git-whatchanged drivers/ata/sata_nv.c
>
> and that will gi
Alistair John Strachan wrote:
Before I proceed with the horrors of an -rc1 bisection, could somebody send me
the ADMA patches so I can eliminate those first?
BTW a bisection need not be blindly horrific... You can look at the
commit ids from git-whatchanged output mentioned in the previous e
Alistair John Strachan wrote:
Before I proceed with the horrors of an -rc1 bisection, could somebody send me
the ADMA patches so I can eliminate those first?
Run
git-whatchanged drivers/ata/sata_nv.c
and that will give you a list of recent changes. To obtain the "diff
-u" patch for
On Thursday 14 December 2006 21:33, Jeff Garzik wrote:
> Alistair John Strachan wrote:
> > Hi Jens,
> >
> > On Thursday 14 December 2006 20:48, Jens Axboe wrote:
> >> On Thu, Dec 14 2006, Jens Axboe wrote:
> I'll do that if nobody comes up with anything obvious.
> >>>
> >>> If you can just tes
Alistair John Strachan wrote:
Hi Jens,
On Thursday 14 December 2006 20:48, Jens Axboe wrote:
On Thu, Dec 14 2006, Jens Axboe wrote:
I'll do that if nobody comes up with anything obvious.
If you can just test 2.6.19-git1, then we'll know if it's the SG_IO
patch again.
Actually, you should tes
On Thu, Dec 14 2006, Alistair John Strachan wrote:
> Hi Jens,
>
> On Thursday 14 December 2006 20:48, Jens Axboe wrote:
> > On Thu, Dec 14 2006, Jens Axboe wrote:
> > > > I'll do that if nobody comes up with anything obvious.
> > >
> > > If you can just test 2.6.19-git1, then we'll know if it's th
Hi Jens,
On Thursday 14 December 2006 20:48, Jens Axboe wrote:
> On Thu, Dec 14 2006, Jens Axboe wrote:
> > > I'll do that if nobody comes up with anything obvious.
> >
> > If you can just test 2.6.19-git1, then we'll know if it's the SG_IO
> > patch again.
>
> Actually, you should test 2.6.19-git
On Thu, Dec 14 2006, Jens Axboe wrote:
> > I'll do that if nobody comes up with anything obvious.
>
> If you can just test 2.6.19-git1, then we'll know if it's the SG_IO
> patch again.
Actually, you should test 2.6.19-git1 with this patch applied as well.
From: FUJITA Tomonori <[EMAIL PROTECTED]
On Thu, Dec 14 2006, Jeff Garzik wrote:
> Jens Axboe wrote:
> >Is the hddtemp source not available?
>
>
> http://www.guzu.net/linux/hddtemp.php says
> http://www.guzu.net/files/hddtemp-0.3-beta15.tar.bz2
Thanks! I'll await the 2.6.19-git1 test to see how to proceede.
--
Jens Axboe
-
To unsub
Jens Axboe wrote:
Is the hddtemp source not available?
http://www.guzu.net/linux/hddtemp.php says
http://www.guzu.net/files/hddtemp-0.3-beta15.tar.bz2
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Alistair John Strachan sms.ed.ac.uk> writes:
> `hddtemp' has stopped working on 2.6.20-rc1:
→ http://bugzilla.kernel.org/show_bug.cgi?id=7581
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://v
On Thu, Dec 14 2006, Alistair John Strachan wrote:
> On Thursday 14 December 2006 19:57, Linus Torvalds wrote:
> > On Thu, 14 Dec 2006, Alistair John Strachan wrote:
> > > `hddtemp' has stopped working on 2.6.20-rc1:
> >
> > Hmm. Can you do the strace on a working kernel too? For example, is it
> >
On Thursday 14 December 2006 19:57, Linus Torvalds wrote:
> On Thu, 14 Dec 2006, Alistair John Strachan wrote:
> > `hddtemp' has stopped working on 2.6.20-rc1:
>
> Hmm. Can you do the strace on a working kernel too? For example, is it
> that the 0x30d ioctl (which is HDIO_GET_IDENTITY) used to work
Linus Torvalds wrote:
On Thu, 14 Dec 2006, Alistair John Strachan wrote:
`hddtemp' has stopped working on 2.6.20-rc1:
Hmm. Can you do the strace on a working kernel too? For example, is it
that the 0x30d ioctl (which is HDIO_GET_IDENTITY) used to work? If it's a
SATA device, and you _used_
On Thu, 14 Dec 2006, Alistair John Strachan wrote:
>
> `hddtemp' has stopped working on 2.6.20-rc1:
Hmm. Can you do the strace on a working kernel too? For example, is it
that the 0x30d ioctl (which is HDIO_GET_IDENTITY) used to work? If it's a
SATA device, and you _used_ to use the PATA driv
Hi Linus,
`hddtemp' has stopped working on 2.6.20-rc1:
[root] 19:25 [~] hddtemp /dev/sda /dev/sdb /dev/sdc /dev/sdd
/dev/sda: ATA WDC WD2500KS-00M: S.M.A.R.T. not available
/dev/sdb: ATA WDC WD2500KS-00M: S.M.A.R.T. not available
/dev/sdc: ATA Maxtor 6B200M0: S.M.A.R.T. not available
/dev/sdd: AT
Gene Heskett wrote:
> On Wednesday 13 December 2006 22:32, Linus Torvalds wrote:
>>On Wed, 13 Dec 2006, Gene Heskett wrote:
>>> Ok, one not so silly Q (IMO) from the resident old fart. I saw,
>>> sometime in the past week, a relatively huge ieee1394 update go by.
>>> And I have some issues with t
On Thu, 14 Dec 2006 14:59:23 +0100
"Alessandro Suardi" <[EMAIL PROTECTED]> wrote:
> On 12/14/06, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> >
> > Ok, the two-week merge period is over, and -rc1 is out there.
>
> Still need this libata-sff.c patch:
>
> http://marc.theaimsgroup.com/?l=linux-kerne
And the patch was reposted here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=116594961106441&w=2
On Thu, 2006-12-14 at 14:59 +0100, Alessandro Suardi wrote:
> On 12/14/06, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> >
> > Ok, the two-week merge period is over, and -rc1 is out there.
>
> Stil
On 12/14/06, Linus Torvalds <[EMAIL PROTECTED]> wrote:
Ok, the two-week merge period is over, and -rc1 is out there.
Still need this libata-sff.c patch:
http://marc.theaimsgroup.com/?l=linux-kernel&m=116343564202844&q=raw
to have my root device detected, ata_piix probe would otherwise
fail a
On Wednesday 13 December 2006 22:32, Linus Torvalds wrote:
>On Wed, 13 Dec 2006, Gene Heskett wrote:
>> Ok, one not so silly Q (IMO) from the resident old fart. I saw,
>> sometime in the past week, a relatively huge ieee1394 update go by.
>> And I have some issues with the present 2.6.19 version
On Wed, 13 Dec 2006, Gene Heskett wrote:
>
> Ok, one not so silly Q (IMO) from the resident old fart. I saw, sometime
> in the past week, a relatively huge ieee1394 update go by. And I have
> some issues with the present 2.6.19 version causeing segfaults and kino
> go-aways when trying to ca
On Wednesday 13 December 2006 21:06, Linus Torvalds wrote:
>Ok, the two-week merge period is over, and -rc1 is out there.
>
Ok, one not so silly Q (IMO) from the resident old fart. I saw, sometime
in the past week, a relatively huge ieee1394 update go by. And I have
some issues with the present
54 matches
Mail list logo
